Closed nraines2002 closed 4 months ago
I'm unsure how you got unsupported, since command int do not expect to get COMMAND_ACK after COMMAND_INT:
Bthw: ros2 run mavros mav checkid
I'm unsure how you got unsupported, since command int do not expect to get COMMAND_ACK after COMMAND_INT:
Bthw:
ros2 run mavros mav checkid
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.
The same message captured by mavros: CMD: Unexpected command 113, result 3
(unexpected because as i said, mavros do not wait and do not expect to get ACK).
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.