View Single Post
  #10   Spotlight this post!  
Unread 14-07-2012, 18:30
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,751
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: Possible solution to Eisenstein problems.

As in the other thread, could we be more precise than "six communications failures".

Three of those were caused by a loose sensor signal wire and code that spun when the value was out of range. The code loop was in auto code and didn't happen in tele mode. Thus tests in the heat of competition failed to repeat the issue.

One was a failed ethernet cable -- not sure if it was purchased or shop-made.

One involved wiring the radio to the unprotected 12V circuit rather than the dedicated and protected 12V.

The radio reboot due to wiring had to do with a suspended crimp connection whose movement weakened and broke the copper wire after repeated vibration and impact -- at least this is my understanding as to why the crimp failed.

Another issue mentioned in the report, but not in the root cause section was a faulty main breaker installed between Quals and Einstein.

Communications failure might be how someone would describe the symptom, but it is not how I'd describe most of these root causes when wearing my CSA hat.

I think it is highly valuable to discuss how to improve the system and identify the issues that are too difficult to debug, etc. Vague terminology and statistics based on small sample size will not help matters.

Greg McKaskle
Reply With Quote