cockpit icon indicating copy to clipboard operation
cockpit copied to clipboard

Manual control of boats requires mavlink functions on buttons

Open Williangalvani opened this issue 2 years ago • 4 comments

Also note that Rover does not have firmware-side handling of buttons. they should all be handled with mavlink.

This image implies that is happening: Screenshot 2023-06-02 at 18 11 18

but nothing can be configured anywhere

Williangalvani avatar Jun 02 '23 21:06 Williangalvani

Better stating what is happening:

Rover does not use the buttons on MANUAL_CONTROL messages for vehicle control, and instead use only the axes inputs from there, and expect commands to be sent separately, on dedicated mavlink command messages (e.g.: MAV_CMD_COMPONENT_ARM_DISARM).

I'm adding arm, disarm and mode toggle on #349 to start, but will create a separated protocol for custom mavlink commands.

rafaellehmkuhl avatar Jun 03 '23 18:06 rafaellehmkuhl

@Williangalvani are there other necessary commands for the Boat besides Arm/Disarm, or are all the other optional and we can implement in a generic MAVLinkCommand action?

rafaellehmkuhl avatar Dec 14 '23 00:12 rafaellehmkuhl

mode changes would be nice too, I think arming/disarming and mode changes are the essential ones

Williangalvani avatar Dec 14 '23 02:12 Williangalvani

MAV_CMD_DO_SET_RELAY would also be useful, as raised in this forum thread, but like with mode changes it's better suited to an approach that allows some configuration (like @rafaellehmkuhl's suggested "generic MAVLinkCommand action"), so we don't have to manually define every option as a separate action.

ES-Alexander avatar Jan 16 '24 01:01 ES-Alexander