We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
A control interface to send thrust+attitude cmd to Copter in ROS2 is requested here, as discussed with @Ryanf55.
Is your feature request related to a problem? Please describe. No, thurst+attitude interface has been implemented in mavlink already.
Describe the solution you'd like A ros2 topic that accepts thrust and attitude commands to control the vehicle.
Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered.
Platform [ ] All [ ] AntennaTracker [ X ] Copter [ ] Plane [ ] Rover [ ] Submarine
Additional context Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered:
Do you want a verbatim copy of the mavlink message? If so, can you share which one?
Sorry, something went wrong.
Hi @Ryanf55 ,
I believe it is SET_ATTITUDE_TARGET that is also explained in Copter Commands in Guided Mode.
No branches or pull requests
Feature request
A control interface to send thrust+attitude cmd to Copter in ROS2 is requested here, as discussed with @Ryanf55.
Is your feature request related to a problem? Please describe.
No, thurst+attitude interface has been implemented in mavlink already.
Describe the solution you'd like
A ros2 topic that accepts thrust and attitude commands to control the vehicle.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Platform
[ ] All
[ ] AntennaTracker
[ X ] Copter
[ ] Plane
[ ] Rover
[ ] Submarine
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: