robamu-org / tmtccmd Goto Github PK

The GUI still needs some updates to be usable properly

• Proper implementation of communication interface handling. This includes a connect and disconnect button
• A way to chose op codes depending on the selected service

The current approach of specifying command definitions is quite inflexible because it only allows one sublayer (op codes as the sublayer of the service).

A more flexible approach which would also be possible to implement in the GUI would be to allow specifying the command definitions in a tree format, where the user can build build a command definition tree, where a command path consists of full path from root to a command leaf. For example, it could look like this

root

• core (n)
• • reboot (l)
• test (n)
• • ping (l)
• acs_subsystem
• tcs_subsystem
• • tcs_ctrl
• • • set_mode
• • poll_all_temps

The full path is passed to the user feed callback, for example as a slash or colon separated string, for example: tcs_subsystem:tcs_ctrl:set_mode. A tree like that would also be traversable in both CLI and the GUI.

Furthermore, introduce QT configuration window for TCP/IP configuration and stop prompting from user

The current version of PUS TM handling is still tightly bound to the Flight Software Framework using an object ID. An adaption to support packets without an object ID would be a good addition.