Currently, the control server software does not attempt to reconnect to the flight computer if it suddenly loses connection. If the TCP socket drops, it just drops and fails to send any more messages.
The control server should automatically detect either an intentionally closed connection to the flight computer or a physical interruption to the connection and attempt to reconnect.
This may require adding an additional async context/thread to do periodic checking. If so, that is fine. Just make sure that it does not have high overhead, as that can kill transmission speeds. Detecting physical interruptions to the signal may also require keep-alive packets sent between the FC and CS.
Currently, the control server software does not attempt to reconnect to the flight computer if it suddenly loses connection. If the TCP socket drops, it just drops and fails to send any more messages.
The control server should automatically detect either an intentionally closed connection to the flight computer or a physical interruption to the connection and attempt to reconnect.
This may require adding an additional async context/thread to do periodic checking. If so, that is fine. Just make sure that it does not have high overhead, as that can kill transmission speeds. Detecting physical interruptions to the signal may also require keep-alive packets sent between the FC and CS.