Currently, if KPI_Rover/Communication module stops receiving packets from the remote side, it stalls indefinitely, leaving the motors actively running. Instead, if there were no packets in 50ms, the communication needs to be considered as failed, and all motors shall be deactivated until further packets override this new state.
Currently, if
KPI_Rover/Communicationmodule stops receiving packets from the remote side, it stalls indefinitely, leaving the motors actively running. Instead, if there were no packets in 50ms, the communication needs to be considered as failed, and all motors shall be deactivated until further packets override this new state.