Driverstation Looses Communications after 6 minutes

[rc4rest]

We are using LABVIEW and if we run our robot for just over 6 minutes of run time, the robot stops working. If we run for 3 minute intervals by disabling the robot, and then re-enable it we can run forever. All indicators say that we have communications from the driver station to the robot, but nothing works. We have to reboot the robot and the PC to get everything back. We have used multiple computers for the drivers station, different routers, with the same results. Is there something wrong with our code?

[Mark McLeod]

Maybe a code issue. You can do anything in code after all.
Did you use "Run as startup", or are you using the white arrow to run your code?

Some possible non-code reasons:

• Are you running in Practice mode? (Practice mode will cause your robot to halt after a fixed time, but you can re-Enable it.)
• Is anyone touching the Classmate keyboard while this is happening? (Hitting the space bar causes the robot to halt and must be rebooted to resume.)

[rc4rest]

We are using the enable button on the driver station dash board. with the code deployed to the robot

We are not using the classmate as the drivers station. We are using the same laptops we used last year, as we are going to be using the classmate on board for video processing from the Kinect.

No one is touching the keyboard.

[Mark McLeod]

It's odd that you have to reboot the PC.
Are you running a custom Dashboard?

Maybe try running without the Dashboard to see if the robot still locks up and then if only rebooting the robot lets you continue.

Rebooting the robot alone would indicate a code issue on the robot side (except for the space bar E-stop).
It's the having to reboot both sides that is odd.

You can try disconnecting the Kinect/Classmate and any other special peripherals to see if they are contributing to the issue.