[EricH]

Originally Posted by kylelanman

If the best of the best can't figure it out then there is clearly something wrong here. FIRST should not provide us with a control system that is so advance that no one is able to troubleshoot.

Most of the time, the best of the best did figure it out. The one they couldn't figure out was why a particular combination of new/old adapters would trigger a field-wide comm loss for no apparent reason. No other combination did that. Try troubleshooting that one...

Originally Posted by kylelanman

We tried to do that. We had the newer bridge and were trying to configure it during matches. We asked a question regarding the WPA or WPA2 setting to the WPA inspector. He did not answer the question instead took the radio set it to factory settings plugged it in to his computer and tried to use his script/program to configure it. He got confused as to why it didn't work and wanted to go watch his own team compete. When we tried to call a timeout to configure it and swap radios the head ref told us no.

The WPA inspector apparently didn't read the update that informed everyone of the program. You can't use it on the new bridge--it has to be done manually. His wanting to go see his own team compete, however--while that's understandable, there's a time and place to do it, like when there's not a team that needs your help right now to be able to compete.

As for the timeout, there are specific rules regarding when you can/can't use one. Quals, you're out of luck. Elims, there's a specific window to call it--if you don't call it in that window, you're out of luck.

Regarding the loss of comms and the loss of video feed at the same time on two different teams: It may be that there were separate failures that just happened to happen at the same time--say, alliance partners hit each other by accident and both cables come loose simultaneously. That's not a field issue, it's a robot issue.