Motors stop after bot disconnects from WiFi
I am working on a robot that runs with ROS which seems to show a dependency on WiFI even though I am currently not using code that connects it with WiFi. Some of the motors stop running after WiFi is disconnected and they resume once the connection is made again. I am using WiFi for other purposes (such as to ssh remotely, sending data to a remote repository) but running just the ROS nodes with driver functions and navigation logic is causing this problem. This is a problem that I noticed recently after my bot went out of range from the router. My best guess is that the motors are stopping due to a watchdog timer which is pinging the WiFi router for some reason. Removing the watchdog, starting the robot without WiFi and then connecting again after the bot is running solves the problem but is no way a permanent fix. Any ideas what might be causing this? Any help would be much appreciated.
I am only working on a single robot and am not trying to set up multiple robots in the same network.
ROS_VERSION=1
ROS_PYTHON_VERSION=3
ROS_ETC_DIR=/opt/ros/noetic/etc/ros
ROS_MASTER_URI=http://localhost:11311
ROS_ROOT=/opt/ros/noetic/share/ros
ROS_DISTRO=noetic
Ubuntu 20.04.3 LTS 64 bit
What do you mean by "removing the watchdog"? If you already know what code is causing the problem, what is it that you are asking us?