Skip to content

Conversation

Davidsastresas
Copy link

@Davidsastresas Davidsastresas commented Feb 8, 2025

Add multi-GCS support, see ArduPilot/ardupilot#29252

<entry value="65536" name="MAV_PROTOCOL_CAPABILITY_FLIGHT_INFORMATION">
<description>Autopilot supports the flight information protocol.</description>
</entry>
<entry value="131072" name="MAV_PROTOCOL_CAPABILITY_PARAM_ENCODE_C_CAST">

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Well, this is interesting but perhaps unrelated.

The component should fall back to the system GCS (if any) when it is not directly controlled, and may stop emitting CONTROL_STATUS.
The flow is otherwise the same as for requesting control over the whole system.
</description>
<param index="1" label="Sysid requesting control">System ID of GCS requesting control. 0 when command sent from GCS to autopilot (autopilot determines requesting GCS sysid from message header). Sysid of GCS requesting control when command sent by autopilot to controlling GCS.</param>

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not a fan of this.

mavlink nodes should generally not change behaviour based on whether they're a GCS or an autopilot. So in this case the autopilot appears as if it is trying to take control of the GCS, which is odd.

Suggest a distinct command for the autopilot asking the GCS if it is OK for it to transfer control elsewhere

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants