Skip to content

Draft: [Topics] Added support for multiple concurrent target systems

Alberto Nidasio requested to merge topics into main

The idea is basically to follow the TargetName/In|Out/MessageName pattern and you to have:

  • Mavlink modules subscribing to TargetName/Out and publishing to TargetName/In
  • Other widgets subscribing to TargetName/In and publishing to TargetName/Out

This way, you can connect as many receivers as you want and communicate with all of them selectively.

Previously only one target system could be connected at a time, because no distinction was being made on the internal topics used in SkywardHub.

Now the topics follows this pattern: TargetName/In|Out/MessageName

  • The TargetName identifies one of the possible target systems (e.g. Main, Payload, ...)
  • In or Out are used to specify the messages that are coming into the system or going to the target
  • MessageName is unchanged (e.g. PAYLOAD_FLIGHT_TM, ...)

Previously the topics followed the pattern Mav/MessageName.

Changes where made to CommandPad, CustomCommandPad, FilterSelector and BaseMavlinkModule to add a ComboBox for the target system and the required logic to make this feature work.

This commit should address #9.

Edited by Alberto Nidasio

Merge request reports