Quote:
Originally Posted by Al Skierkiewicz
Sorry I didn't answer this before...
In reality "losing communications" is a catch all for what problems actually took place. We only know the robots stopped moving. We know (knew at the time) some of the robots that stopped moving were connected to the field and the RSL lights on the robots showed they were enabled. The problem(s) is(are) far more complex than you might think.
Very few robots this year had on board computers in addition to the Crio. I inspected none in four events. Those teams that really wanted to incorporate the Kinect on the robot used them and a few others for vision processing. I don't remember seeing any on Einstein but it was pretty dark in the pit.
|
Our "losing communications" moments at QCR involved 3 matches of a working hybrid mode, then as soon as teleop started, no comms, no code. One match, about 3 seconds of hybrid mode, then no comms, no code. One match - as soon as the match began, no comms, no code. Four of the five matches, a connection was reestablished with about :10 left in the match; the last one, we never had connectivity during the match. These issues appeared at different stations and different alliances. When we reset the router firmware from v1.4 to v1.2 it appeared to fix the problems (the last two matches, we saw no communication issues). We had no comm issues at BMR, during practice at QCR, or the first half of Friday at QCR. We had no extra onboard computer.
As Al said, the "losing communications" catchall really envelops a lot of symptoms and issues, and ours -seems to- have been traced back to an individual robot issue.
It is a tangled web indeed, and I do not envy those charged with unraveling it. As has been said before, I hope a bumpercrop of identifiable and repeatable issues pop up in June.
Sorry to hijack the Einstein thread with a regional vignette, but I felt it was part of the greater picture.