Timeout exceeded in RobotDrive?

[Sparkyshires]

Hey guys, this errors been bugging us. It always constantly appears on the netconsole, no matter what we do, over and over again. Does anyone know what it means?

>>>>ERROR: A timeout has been exceeded: RobotDrive... Output not updated often enough. ...in Check() in C:/WindRiver/workspace/WPILib/MotorSafetyHelper.cpp at line 117

Thanks!

EDIT: we figured out the error. We use our own arcadedrive so that we can add modifiers, because an issue in the past has been one side runs slower than the other. However, I wasn't sure what SetSafetyEnabled and SetExpiration are in the RobotDrive class, so we instantiated a myRobot with bogus port numbers, just so we can do those functions. However, when we comment them out the errors disappear.

So my new question is thus: Are setsafetyenabled and SetExpiration required functions? If we don't instantiate a robotDrive at all, will that be an issue with the fms? I've been treating this robotDrive as black-box code, so if this question seems a bit silly, thats why xD

[Alan Anderson]

It means you have defined some robot drive motors, and you failed to set their values at least every 100 milliseconds. Look in Teleop to make sure something isn't blocking execution for a long time.