Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UAV Trajectory Control Problem #65

Closed
karaf17 opened this issue Mar 27, 2021 · 3 comments
Closed

UAV Trajectory Control Problem #65

karaf17 opened this issue Mar 27, 2021 · 3 comments
Assignees
Labels
type: question Further information is requested wontfix This will not be worked on

Comments

@karaf17
Copy link

karaf17 commented Mar 27, 2021

Hello There!
We've written a publisher node which publishes to /crazyflie2/command/trajectory topic in type of MultiDOFJointTrajectory(). When we publish a trajectory via our node, we can see the publish command on terminal which we run roslaunch as "[ INFO] [1616880768.235356078, 23.238000000]: PositionController got first MultiDOFJointTrajectory message.". But the UAV is not going the point we published. It moves randomly. How can we solve this problem? Or Is there anything you can recommend for UAV controls?
Also we tried to publish a waypoint to UAV with using "rosrun rotors_gazebo waypoint_publish 5 5 1 0 __ns:=crazyflie2" but the result was the same.

@welcome
Copy link

welcome bot commented Mar 27, 2021

Thanks for opening your first issue here! Make sure that no other issues on the same topic have already been opened!

@gsilano gsilano self-assigned this Mar 28, 2021
@gsilano gsilano added the type: question Further information is requested label Mar 28, 2021
@gsilano
Copy link
Owner

gsilano commented Mar 28, 2021

Hi @karaf17!! As described in the previous issues (e.g., #55), the current position controller does not allow any trajectory tracking. It was meant only to show the capabilities to simulate the behavior of the Crazyflie 2.0 nano-quadrotor.
If you really want to implement a trajectory tracking controller (no matter if a trajectory or just waypoints are published over the network), then you need to design your own high-level and low-level control (this part could be omitted if you plan to reuse what is already there).

An interesting repository that is dealing with (i.e., trajectory tracking controller in a predictive manner) is available at the link: https://github.com/bcbarbara/crazyflie_nmpc.

I hope this helps. If you have any further questions, please do not hesitate. I'm not going to work on this project anytime soon, but I could help you out if you really want to start this activity.

@stale
Copy link

stale bot commented Jun 2, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix This will not be worked on label Jun 2, 2021
@stale stale bot closed this as completed Jun 9, 2021
@gsilano gsilano mentioned this issue Jul 15, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: question Further information is requested wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

2 participants