View Single Post
  #6   Spotlight this post!  
Unread 08-04-2015, 10:56
Alan Anderson's Avatar
Alan Anderson Alan Anderson is offline
Software Architect
FRC #0045 (TechnoKats)
Team Role: Mentor
 
Join Date: Feb 2004
Rookie Year: 2004
Location: Kokomo, Indiana
Posts: 9,112
Alan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond repute
Re: Gremlins and Troubleshooting

Quote:
Originally Posted by Chief Hedgehog View Post
So my question is this: What is your order of trouble-shooting the robot?
Step zero: check the obvious power connections. Main breaker, PDP input, PDP fuses, wiring to roboRIO/VRM/D-Link. Plus the battery terminals.

If it works properly in the pit and when tethered on a practice field, I figure the robot itself is probably okay, and I start troubleshooting with the Driver Station logs. That will often point to an intermittent power connection or a communication issue. If power is okay, I look at the network settings. If they're good, I check for firewalls, antivirus scanners, software updaters, and other potentially disruptive background tasks.

Then I suppose I start following hunches instead of checklists.
Reply With Quote