Thread: How to determine root cause of robot dropping from Teleop to Disabled during match.
View Single Post
  #24   Spotlight this post!  
Unread 24-03-2015, 22:37
Monochron's Avatar
Monochron Monochron is offline
Engineering Mentor
AKA: Brian O'Sullivan
FRC #4561 (TerrorBytes)
Team Role: Engineer
  
Join Date: Feb 2007
Rookie Year: 2002
Location: Research Triangle Park, NC
Posts: 910
Monochron has a reputation beyond reputeMonochron has a reputation beyond reputeMonochron has a reputation beyond reputeMonochron has a reputation beyond reputeMonochron has a reputation beyond reputeMonochron has a reputation beyond reputeMonochron has a reputation beyond reputeMonochron has a reputation beyond reputeMonochron has a reputation beyond reputeMonochron has a reputation beyond reputeMonochron has a reputation beyond repute
Re: How to determine root cause of robot dropping from Teleop to Disabled during matc
Quote:
Originally Posted by plnyyanks View Post
It sounds like the CSA was on to something - a radio reboot typically takes between 30 and 40 seconds to come back (the DS logs tell you exactly how long your robot was down). In contrast, a roboRIO will take around 25 seconds to reboot.

Common symptoms of radio reboots:
- Brownouts due to your battery being low. These events correlate to large current draws
- PDP Fuses. Push them in all the way
- Multiple things plugged into the radio source on the VRM
- The barrel connector not being plugging in all the way, especially if it's an older one
Yeah we didn't notice any unusually large voltage spikes in the logs but I'm still checking different possible causes.