Are there “good practices” when communicating from a ground station computer with a GUI to an onboard computer connected to the flight controller? I am thinking mostly safety wise. I am using ROS2.
I was thinking these things:
-
Necessary “heartbeat” between ground station and onboard computer. If the heartbeat fails go into hold mode
-
Use services instead of messages so that you always get a response that the onboard computer got the message
-
Have error codes that can be written to the flight controller via the onboard computer so that in the event of an incident, there is more information available for the analysis.
-
Having a ROS2 bag always store communication information during a flight for post incident analysis (would this slow anything down?)
Are these 4 things worth merit (I am not 100% sold on #2 if it truly makes a difference). Are there other things I should consider when having a ground station computer with a GUI talk to an onboard computer?