If the rover loses radio communication during operation it times out and stops moving after not receiving commands for a set period of time. This is intended outcome of the rover losing communication with the basestation during operation.
If operating via PS4 controller with a bluetooth connection and the controller loses connection while issuing a command. The command that was being issued at the time of the controller losing connection will be continously issued until the rover's e-stop is hit. This is very apparent when the rover is operated with a controller directly connected to the Jetson TX2.
This could likely be due to an issue with the joy node package or maybe something driver level with how the PS4 controller is handled in Ubuntu. Could be fixed in ROS2 migration
If the rover loses radio communication during operation it times out and stops moving after not receiving commands for a set period of time. This is intended outcome of the rover losing communication with the basestation during operation.
If operating via PS4 controller with a bluetooth connection and the controller loses connection while issuing a command. The command that was being issued at the time of the controller losing connection will be continously issued until the rover's e-stop is hit. This is very apparent when the rover is operated with a controller directly connected to the Jetson TX2.
This could likely be due to an issue with the joy node package or maybe something driver level with how the PS4 controller is handled in Ubuntu. Could be fixed in ROS2 migration