View Single Post
  #3   Spotlight this post!  
Unread 10-02-2014, 21:25
BradAMiller BradAMiller is offline
Registered User
AKA: Brad
#0190 ( Gompei and the Herd)
Team Role: Mentor
 
Join Date: Mar 2004
Location: Worcester, MA
Posts: 588
BradAMiller has a brilliant futureBradAMiller has a brilliant futureBradAMiller has a brilliant futureBradAMiller has a brilliant futureBradAMiller has a brilliant futureBradAMiller has a brilliant futureBradAMiller has a brilliant futureBradAMiller has a brilliant futureBradAMiller has a brilliant futureBradAMiller has a brilliant futureBradAMiller has a brilliant future
Re: Output Not Updated Often Enough

The "output not updated often enough" comes from the MotorSafetyHelper, a class inside WPILib. The idea is that it makes sure that your program is continuously updating motor values otherwise it stops the motors. By default it is only enabled for the RobotDrive class, those messages are coming from a RobotDrive object in your program.

Look for a place where you give the drive a value and then do a wait, maybe Timer.delay(). If the values to the RobotDrive object aren't update at least every 100ms, then the drive motors stop operating and that message comes out.

The reason the motor safety checks exist is to protect you against broken code that stops regularly updating the motors, causing the robot to "run away".

You can either make sure that you are continuously sending values to the RobotDrive object or use the method:

myRobotDriveObject.setSafetyEnabled(false);

and it will turn of the motor safety checks for the robot drive object. Do this right after you do the:

myRobotDrive = new RobotDrive(...);
__________________
Brad Miller
Robotics Resource Center
Worcester Polytechnic Institute
Reply With Quote