|
Re: How to determine root cause of robot dropping from Teleop to Disabled during matc
The WAIT_FOR_PID is a command we use in our beescript autonomous. When auto starts, we do an elevator reset, which homes the elevator, and resets the encoder, then puts the elevator in pid control. This command just waits until the elevator is under the pid control, before sending it a target height. Obviously, they have a typo in the script or the command name and they don't match up. Not an issue for this event, as we were just sitting and not moving in auto, but something on the list to fix.
The joystick error has been happening all season, but has not been an issue, except for throwing the error. The code runs in periodic tasks, and is setting the joystick rumble for the driver and operator. The operators joystick will rumble if he hits an overtravel on the elevator, and the drivers joystick will rumble when the there is a tote in position to stack.
Greg, if you want to send me you github username I will add you to the repository, if you want to check out the joystick error.
I will try to get additional information from the drivers at tonight's meeting.
We also checked all of the fuses after this match, and nothing was found to be loose.
__________________
The sooner we get behind schedule, the more time we have to catch up.
Last edited by tr6scott : 24-03-2015 at 06:12.
Reason: a
|