Robots not under driver control- does it happen- do you determine why?

[boomergeek]

I'm curious about the prevalence and root cause analysis of issues controlling robots during competition:

Has your drive team ever lost complete control of the robot for a second or more in any match?

Has responsiveness been delayed by more than a quarter of a second and made it unnatural to drive?

Did you have the proper analysis tools to find out a root cause to the problems?

What percentage of control problems were you able to isolate?

What percentage of problems didn't show up again, but had no clear indication of what caused the problem in the first place.

My perception is solid problems are isolated and solved clearly. Intermittent problems and sluggishness are sometimes considered part of life instead of being isolated and resolved.

How do best teams determine that they have enough safety margin on their radio signal to never worry about being in a hard pushing scrum with three other robots in the corner farthest from radio access point?

We were brainstorming about logging voltage, radio signal, transmission delay to the DS and transmission delay from the DS at a 100ms rate and link it to video for the matches.

By the way, the DAP-1522 manual:
"Keep your product away (at least 3-6 feet or 1-2 meters) from electrical devices or appliances that generate RF noise."
ftp://ftp.dlink.com/Multimedia/dap15...manual_120.zip