The new remote design uses MQTT_GW to transfer 'text hex' encoded CCSDS packets through an MQTT broker. In order to do this, new features need to be added to KIT_TO.
On the remote system, KIT_TO will need to wrap telemetry messages in a special MQTT_GW telemetry message. MQTT_GW will subscribe to this special message and encode the wrapped telemetry message as a 'text hex' MQTT topic In order to reduce MQTT traffic a mechanism needs to be designed that identifies which telemetry messages should be sent to MQTT_GW. KIT_TO's kit_to_pkt_tbl.json 'packet' definition can be used. A new field should be added indicating whether a packet is wrapped and sent to MQTT_GW. This field should have a generic name because wrapping a message could be used for any external interface similar to the Software Bus Network app.
A mechanism needs to be designed that allows the local Basecamp system to identify which packets arrived from a remote system, It looks like the CFE_MSG_Get/SetSystem() API could be used for this purpose. This needs to be verified before building this into the apps.
The local KIT_TO can receive messages for the same app from both the local and remote systems. KIT_TO should be enhanced so it can be commanded to output either the local telemetry or the remote telemetry.
The new remote design uses MQTT_GW to transfer 'text hex' encoded CCSDS packets through an MQTT broker. In order to do this, new features need to be added to KIT_TO.