View Single Post
  #62   Spotlight this post!  
Unread 23-03-2016, 15:35
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: COMM lost way to many times

Quote:
Originally Posted by Joe Johnson View Post
Does anyone have data on the frequency, number, and duration of COMM problems over time (meaning year over year)?

I get the feeling that the problems are worse this year but I freely admit that I am a biased observer.
At present I have only my observations, with no solid data in hand to back up what I "feel" is the case. I will be asking around in the next few weeks to see if anyone I know has that data. But what I observe is that communication problems are very rare this year compared with the last two years.

I do not count cases where power was lost (loose connections, faulty crimps, a main breaker being accidentally hit by a stray robot part, etc.) or where an error in a team's programming caused the robot software to crash. Those can have similar symptoms to a "comm problem", but the underlying cause is unrelated to the field-to-robot communication method.

(Power issues this year are extremely prevalent, though. Teams simply aren't checking regularly to make sure their battery and breaker connections are tight, or that wires are properly inserted into the Weidmuller connectors.)
Reply With Quote