-
Notifications
You must be signed in to change notification settings - Fork 1k
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 sent using COMMAND_INT receives "COMMAND_ACK:UNSUPPORTED" #1933
Comments
I'm unsure how you got unsupported, since command int do not expect to get COMMAND_ACK after COMMAND_INT: mavros/mavros/src/plugins/command.cpp Lines 292 to 302 in 227bb05
Bthw: |
The COMMAND_ACK I see is from the specific commands that I'm sending using COMMAND_INT in the mavproxy window. So when I send a CONDITION_CHANGE_ALT command using command int i see "Got COMMAND_ACK:CONDITION_CHANGE_ALT:UNSUPPORTED" from the autopilot |
Ah, i see. MAVProxy catches COMMAND_ACK and prints it on that console. But that's simply on a firmware side. Have you tried to send that command via mavproxy? |
I've found the issue, only very specific commands can be sent using COMMAND_INT. I will close the issue and update it to help any future lost souls. Thanks for your help @vooon. |
To anyone having this issue
Sending CONDITION_CHANGE_ALT is not yet supported but similar commands are.
See wiki: https://ardupilot.org/dev/docs/copter-commands-in-guided-mode.html
Issue details
Sending MAVLink messages via Command_Int is returning COMMAND_ACK:[COMMAND_NAME]:UNSUPPORTED. I am using MAVROS built using ROS2 Foxy to pack and send these commands, using the Command_Long MAVROS service to send a Set_Mode message works but returns COMMAND_ACK:DO_SET_MODE:DENIED. I have sent the message with frames, MAV_FRAME_GLOBAL, MAV_FRAME_LOCAL_NED, MAV_FRAME_MISSION, MAV_FRAME_GLOBAL_RELATIVE_ALT, MAV_FRAME_GLOBAL_RELATIVE_ALT_INT to no avail.
Current usage:
MAVROS version and platform
Mavros: 2.6.0
ROS: Foxy(ROS2)
Ubuntu: 20.04
Autopilot type and version
[X] ArduPilot
[ ] PX4
Version: 4.4/4.3/4.2
Node logs
Diagnostics
Check ID
Result of running
ros2 run mavros mav checkid
after sourcing ros2 setup with mavros connected to sitl.The text was updated successfully, but these errors were encountered: