MAVLink Settings

The final step in ensuring you have a connection to your vehicle, or other MAVLink device, is to configure the MAVLink settings. To do this, navigate to the MAVLink Settings tab by clicking on this symbol:

For most single-vehicle operations the default configuration will work fine, as the target system ID auto detect feature will automatically assign the correct system ID. When a heartbeat message is regularly received (a minimum of once every 5 s or 0.2 Hz) that matches the set Target System ID then a green tick will display on the MAVLink settings symbol:

Should you have any issues in getting the green tick, or if you have a more complicated vehicle setup, please see the tables below for more information on what each of the fields in the MAVLink settings tab does:

Target Settings

Defining the "address" of the system that we are sending commands too:

Field	Explanation
System	The system ID that commands will be targeted at. This is blanked out if Auto Detect is checked.
Auto Detect	If checked, the system ID that is received from the first heartbeat message is assigned as the target.
Component	The component ID that commands will be targeted at.
Custom Target per Action	If checked, this allows the target system ID to be set in the individual Stream Deck actions. This option is useful for those that want to send commands to multiple vehicles, all connected at the same time.

Own Settings

Defining the "address" that KH Control shows up as in the MAVLink data stream:

Field	Explanation
System	The system ID value that KH Control will populate into the heartbeat message that it sends. Commands from KH Control will all show up in the MAVLink data stream with this system ID.
Component	The component ID value that KH Control will use. Commands from KH Control will all show up in the MAVLink data stream with this component ID.

Heartbeats and stearates

KH Control does not send MAVLink heartbeats to the vehicle, loss of connection will not trigger a GCS fail safe. KH Control does not configure or request stream rates for any messages. This is to avoid conflicting with the primary GCS.