Quote:
Originally Posted by Alan Anderson
That sounds like you have circuit breakers tripping. Check your drive train for binding gears, too-tight chain, excessive friction, or anything like that. It might even be a wiring problem with motors fighting each other.
|
Hi, I am the lead (student) programmer for Team 848. huskyrobotics is as you all could tell, a team-wide account. RedWolf55AJ is the account I made so that I wouldn't have them looking over my shoulder.
As it turns out, 2 minutes after I posted that last message, one of the other guys came over saying that it was probably a circuit breaker problem. I agreed.
Now we have an arguably worse problem. The circuit breaker issue only happens when we deploy OUR code. When we format the cRIO via the cRIO imaging tool, the robot drives like a dream. As soon as we upload the code pictured above, the controls become laggy (.5-1 second delay).
what is even worse is that mysteriously, the right side of the robot stopped working, without any changes in code that I could see. Fearing a joystick problem I swapped the joysticks in USB Ports 1 and 2. The Right Jaguar Speed Controller remained inoperative regardless of the joystick. When I did reach into the code to switch which USB Port fed which side of the "Tank Drive" VI, the problem then switched to the other motor/jaguar. I fear that somewhere between "Open Joystick" (USB 2) and "Close Joystick" USB 2 some input is being lost. Can anyone help me with that? I really only have one more day to work on this thing and I'm fighting time.
The problems above only occur when we deploy our code.
PS, I can see that the cRIO retunrs to "46% empty" each new time we deploy/run our code. When the time comes, how will we get our code to "Stick" to the robot's cRIO? I want it in deeper than just RAM or wherever it is now.