View Single Post
  #5   Spotlight this post!  
Unread 18-03-2013, 22:33
Andrew Lobos Andrew Lobos is offline
Registered User
FRC #0225 (TechFire)
Team Role: Mentor
 
Join Date: Feb 2011
Rookie Year: 2011
Location: Lancaster, PA
Posts: 61
Andrew Lobos is a jewel in the roughAndrew Lobos is a jewel in the roughAndrew Lobos is a jewel in the rough
Re: Problem with driving

When I was helping you in your pit with your compressor code, I noticed the debug output from the cRIO said Robot drive not updated often enough. Since it did that right when the cRIO was enabled, and then stopped, I assumed that you had some initialization stuff happening that took time to complete. I didn't notice any output after that.

Is this happening while you are driving?

In your testing, are you driving on carpet? I noticed you were running 1 CIM through a CIMple box with 6in wheels. How far is your voltage dropping when you drive? If you use the Driver station log viewer app, you can see the cRIO log (including voltage) from your matches.

If you still believe it is a code problem, make absolutely sure your RobotDrive or motor controller objects are having their drive/set methods called every loop.

- Andrew

Last edited by Andrew Lobos : 18-03-2013 at 22:34. Reason: Removed quote block