ERROR 1 Robot Drive... Output not updated often enough

[Team3740 Storm]

I have been experiencing particular difficulty in the running of my java programs for our teams robot. Everything downloads fine and everything is green on the the driver station, but as soon as I enable Teleop period is spams me with this error: [ERROR 1 Robot Drive... Output not updated often enough. java.lang.Thread.run(Thread.java:745)]. This problem is not exclusive to my current program either, I've tried to run multiple other sample programs in its place to try and determine if it is the code but still come up with the same error. I have attempted the setSafetyEnabled(false) function but to no avail. I must add that is does move for a split second when the desired input is given but then instantly disconnects and disables the Teleop period.

Any help is appreciated if any of you may know the answer to this problem.

[nickbrickmaster]

You should be setting the motor power every loop, very quickly (I don't remember the limit for the watchdog.)

Are you using the iterative structure? If so, is there something that's slowing your code down?

[jajabinx124]

I think the error message means that the robot is expecting to receive joystick values frequently and is not. It's suppose to be a safety measure. That's weird that setSafetyEnabled(false) didn't work, because that's what I would have suggested..

Could you post your code? Are you using the Iterative program structure? (which constantly loops the code, thus updating the values)

[Team3740 Storm]

I am using command but cannot post my code until Tuesday for the laptop it is on is at our school. I think the weirdest thing is that this happens on all the sample programs too. I'll post the code as soon as possible, thank you for the support.

[wharrier2450]

We had this issue yesterday. Was caused by our RobotDrive not having a default command.

[garyk]

Not sure what you mean by a default command for the RobotDrive class.

It'd be interesting to call

yourrobotdrive.isSafetyEnabled();

and confirm that the returned boolean is false.

[wharrier2450]

Actually, the default command is not configured on the RobotDrive but on the subsystem that contains it. Our drivetrain Subsystem that owned the robot drive did not have a default command configured.

I spent hours commenting out everything in our Robot code trying to figure out what was causing it. When I configured the default command for our drivetrain subsystem, this error went away. Can't explain why because the error seems completely unrelated, but that's what made it go away. Toggled it back and forth to verify and it was the culprit.

[Xanawatt]

It might have something to do with setExpiration(), if you used robotbuilder, this might have been inserted automatically and you might try removing it. If it isn't there, then add it and try messing around with the numbers.

[gregzetko]

We had this issue last year. We ended up not using any of WPIlib's RobotDrive functions (Tankdrive,Arcadedrive) but rather writing one ourselves and running it in teleop periodic. Here is our code https://github.com/frc2609/FIRSTPRES...bot/Robot.java if you need more comments, let me know. It starts from line 134

[arichman1257]

Here's an old thread. It's from 2010 so some things may be a bit out of date but the "watch dog not fed" error can not have changed all that much