Thread: How to determine root cause of robot dropping from Teleop to Disabled during match.
View Single Post
  #5   Spotlight this post!  
Unread 22-03-2015, 15:34
Greg McKaskle Greg McKaskle is offline
Registered User
FRC #2468 (Team NI & Appreciate)
  
Join Date: Apr 2008
Rookie Year: 2008
Location: Austin, TX
Posts: 4,752
Greg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond repute
Re: How to determine root cause of robot dropping from Teleop to Disabled during matc
Watching the RSL pattern in the video, and looking at column B of your logs, it looks like the first period where your outputs were disabled was 11 seconds, and the second was 2.3 seconds. The log file on the DS will have some messages indicating whether the DS lost comms with the field, with the radio and robot, or just the robot. It also contains messages every few seconds showing the laptop CPU usage, roboRIO CPU usage, and lots of other stuff. Please post the file or contact me and I'll give you email instructions and I'll be happy to help you identify the issue.

Also, it looks like they started working about the time the FTA made it to their station. Does the drive team have an idea of what was done at the DS? Did they reconnect the ethernet cable? Did they reboot their code?

Greg McKaskle