[Blackphantom91]

Day one is over at St.Louis Regional and as Jspatz posted above we are experiencing the same issues like we did in KC heres Settings again:

Which event? Kansas City
Wireless bridge radio HW revision? (A or B) A
Programming language? Labview
Using a dashboard app? Is it SmartDashboard? No
Using vision with Axis Camera and cRIO processing? Passing image, no processing
Using vision with driver station processing? No
Did you have the radio mounted near motors/large metal structure? Yes
Using classmate (or similarly slow computer) as driver station? Yes

On Thursday there was a ton of robots not being able to connect(Including our team) to the field mostly on blue side this also is the field that was used at bayou, In which one team couldn't connect the entire day on Thursday. We all had different firmware versions like 1.40,1.20 and 1.30 So they all downgraded the routers at the regional to 1.2 and every robot was able to connect to the field but we still get this "intermittent" com drop when we go to get a ball at a side in the arena.

There are alot of teams here that are or seem to be having the same issue of really high trip times from the FMS even after code is modular and changed.(Shout outs to helping all the teams FTA'S)

What gets me that It only happens on one part of the field closest to the Antenna to the FMS?

Anyone else having this issue? Also if you have trouble at your regional with networking check the version It also makes a really big difference if you are version 2.00 Hardware Revision B which also doesn't work on the field. One robot with a different one can cause a major drop out for potentially the entire field. (Which happened This goes for RevA also) Really good job FTA's on figuring this out