View Single Post
  #62   Spotlight this post!  
Unread 13-07-2012, 20:21
Bryan Herbst's Avatar
Bryan Herbst Bryan Herbst is offline
Registered User
AKA: Bryan
FRC #2052 (KnightKrawler)
Team Role: Mentor
 
Join Date: Sep 2007
Rookie Year: 2007
Location: Minneapolis, Minnesota
Posts: 545
Bryan Herbst has a reputation beyond reputeBryan Herbst has a reputation beyond reputeBryan Herbst has a reputation beyond reputeBryan Herbst has a reputation beyond reputeBryan Herbst has a reputation beyond reputeBryan Herbst has a reputation beyond reputeBryan Herbst has a reputation beyond reputeBryan Herbst has a reputation beyond reputeBryan Herbst has a reputation beyond reputeBryan Herbst has a reputation beyond reputeBryan Herbst has a reputation beyond repute
Re: [FRC Blog] Einstein Report Released

After thoroughly reviewing the report, I have come to two conclusions:

1) FIRST did an incredible job of researching all of the factors that went into what happened on Einstein.

2) Any team, regardless of experience and ranking can have those simple little problems that could contribute to larger problems such as what happened on Einstein.

Regardless of whether or not the code and electrical problems were the root cause of the Einstein failures, each and every team should review this document and ask themselves whether or not they might have similar electrical/programming problems.

Loops without sleeps and bad crimps are problems that are easy to look for in your robot, but not necessarily easy to diagnose. If teams add these to their list of things to check on their robots during the build season, we can help ensure that robots are running to the best of their ability. Should any further malicious behavior take place, removing these problems as a potential source will assist in troubleshooting as well.
__________________
Team 2052- KnightKrawler
Mentor and volunteer
Reply With Quote