LabVIEW dashboard works in the pits but not on the field

[Arhowk]

How essential are these variables? If it's something that must be configured mid-match than I'd recommend switching to smartdashboard. If they are pre configuration than I'd just set them up via tether than detect in code if the values are good than save else discard and retain old.

You mentioned you had a modified dashboard so that's most likely the root of the cause. did you try starting from scratch and rewriting the dash with basic commands?

[Alan Anderson]

There is still some voodoo involved with getting Dashboard (NetworkTables) communication running. For it to work, many things have to take place in the right order.

The easy way to ensure that everything happens properly is to restart the robot code immediately after the Driver Station is talking to the robot. (I have only seen that fail once, and while I'm not sure what the extra problem was, I suspect it was because the team had the wireless network adapter enabled on the DS computer.)

[Greg McKaskle]

The voodoo is caused by corner-case bugs in the error handling of the TCP reconnect cases. There are several edits needed, some in the DB and some in the DS. As mentioned, the diamonds should tell you definitively whether the variables are synchronized.

Greg McKaskle

[forbes]

Thanks everyone for your input.

We decided to continue not using the dashboard at our Regional last week due to the uncertainty.

A few days ago I saw team update 3/23 that addressed the issue with this document: http://wpilib.screenstepslive.com/s/...24193/l/327864

We may decide to re-implement some of our dashboard features before the World Championship.

[FrankJ]

We are using smart dashboard so maybe not directly applicable.... We were told to restart smart dashboard & DS after tethering in the pits & before connecting to the field. Didn't have any issues with smart dashboard connecting. Didn't try it the other way to test the theory either.