Quote:
Originally Posted by 4ndr3wl
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
|
The voltage drops to about 9volts.
The robotdrive is in the execute method.
We didnt drive on the carpet, only on the practice field.
This happens to driving. I re-coded the drive a bit, to compensate a dual joystick controller for one of our drivers. I am hoping that is going to fix it as well as setting the setSafetyEnabled to false.