-
Notifications
You must be signed in to change notification settings - Fork 153
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
command interface using px4 #21
Comments
Hello @DavidePatria , Sorry for the late reply. The final path is published by the Planner Control Interface (PCI) which publishes it as a Let me know if this helps. Best, |
Hi, thank you for your response. |
What commands does your controller provide to the px4? If you are sending position waypoints to px4, then your controller will have to send one waypoint at a time and send the next waypoint only after the robot has reached the first one. |
I am using this, which takes the waypoints and sends attitude commands (I believe), which works with other programmes I am using, with an higher number of waypoints |
Hi @DavidePatria , Sorry for the late reply. Best, |
I am trying to use this planner with px4 as I would like to simulate a drone I will later build.
I was looking for the actual commands sent to the drone, which are usually passed as
mavros_msgs/AttitudeTarget
or astrajectory_msgs/MultiDOFJointTrajectoryPoint
.Analyzing the topic
/rmf_obelix/command/trajectory
I found that there a message of the latter type is published in it, but at a very slow rate and probably not for the purpose at which such messages are normally published, so I have a doubt about it. Is it used to keep a rough track of/rmf_obelix/command/motor_speed
instead publishes a message of typemav_msgs/Actuators
direclty to gazebo, which I understand is the used way to move the drone.now, is there a way to get the planner to output one this type of messages among the two mentioned above?
The text was updated successfully, but these errors were encountered: