Router Issue? (Watchdog not Feed)

[simpsonboy77]

Originally Posted by bvisness

The "watchdog" on the robot is simply checking for new inputs from the driver station while the robot is running. If the code lags or you lose connection so that new inputs can't be sent, the "watchdog" isn't "fed" new inputs, and it automatically stops the robot's movement. This is a basic safety feature to ensure that the robot doesn't keep driving and kill someone if you lose connection.

The way to improve the problem? Just fix your communications, like you did, and make sure that your code isn't slowing down to the point where it can't get new inputs often enough.

This is just wrong. No answer is better than a wrong answer. The watchdog has nothing to do with network communication.

The watchdog will stop all outputs from the cRio when the watchdog is not fed. You put feed statements in your program to inform the cRio that your user code is still running and isn't hung up in a loop. Either the set expiration was set too low, or you have a slow loop somewhere. Set expiration is basically setting the amount of maximum amount of time you want to allow between 2 feeds without disabling the robot.