Quote:
Originally Posted by engbrech
Robot code always breaks until the power on the robot is reset.
|
Do you mean that the Driver Station says "No Robot Code" until you powercycle the rio? And then it works until you fire the catapult, and it crashes back to "No Robot Code"?
If so, that's a code issue. (Unless it's something to do with LabVIEW deploy vs run, I'm not familiar with LabVIEW.)
If you're using a camera to autoaim, make sure when you do any calculations on the camera data, it actuslly exists. For example, in C++, we are using GRIP to get camera information via NetworkTables. If the camera doesn't see a target, GRIP doesn't publish any information to the network table.
Attempting to use those non-existant numbers results in the rio crashing and rebooting, while showing "No Robot Code". To fix that, we simply have an if block around that code saying "if (!table.empty())"
However, if you are actually losing power to the rio or Radio, it sounds like you have a short circuit somewhere. 9V is low, but not reboot everything low.
I'd suggest pulling breakers out of the PDP, one by one, until you isolate the issue.
Edit: When pulling breakers, be careful that you don't overload a motor. For example, if your catapult requires both motors to draw back, and having only one will stall the motor pull both breakers.