Quote:
Originally Posted by JesseK
I've done a few things in the 2 matches we sat this year. - Look at any D/S logs for errors. Depending on how you're setup/configured, the errors may be gone by the time the robot makes it back to the pit - especially if COMMS comes back. This may provide crucial info to the pit crew in diagnosing the errors.
- "Reboot RoboRIO" sometimes works, but could take as long to come back as there is left in the match
- Bring up driver's station performance characteristics (taskmgr, custom stuff, etc)
- Use the time to specifically coach the HP on a new strategy/technique for rolling the balls
- Keep mashing buttons
- Tell the partners, discuss what to do next. Answer their questions about your robot "Can I push you?" etc.
|
Driver Station logs are saved with a timestamp, they will always remain until you delete them manually.
Reboot RoboRIO won't work if you don't have comms to the radio (which is almost always the issue due to a power cycle as many teams have pointed out)
Getting an alliance partner to push you over the defense is almost always a bad idea. If you lost power because of an impact (i.e. faulty circuit breaker or wiring), getting a second sudden hit from your alliance isn't going to be good news. Not only that, but it takes time away from what they could be doing, like breaching or shooting.