Issues with grip on raspberry pi.

[Arhowk]

Network Tables is currently brokenly unreliable on the field. It killed us in two of our only three losses and continued to pester us in eliminations. You'd have to talk with the FTA to establish a temporary workaround

[axiomofdarkness]

Originally Posted by Arhowk

Network Tables is currently brokenly unreliable on the field. It killed us in two of our only three losses and continued to pester us in eliminations. You'd have to talk with the FTA to establish a temporary workaround

Can anyone else confirm this? We're currently using Network Tables to communicate between our Pi and our RoboRIO and I'd rather not have it fail during a match. If this is the case, what other ways could we go about sending information over?

[Arhowk]

Originally Posted by axiomofdarkness

Can anyone else confirm this? We're currently using Network Tables to communicate between our Pi and our RoboRIO and I'd rather not have it fail during a match. If this is the case, what other ways could we go about sending information over?

For Lansing, we will be using a custom C++ dashboard that communicates via TCP socket and has all of the data we need. I can share the communication code once I get it solid.

For this weekends competition we had to use the workaround of rebooting robot code every time we got on the field and got connected. Just make sure to have a "connection indicator" widget shown. I'd also recommend sending a sine wave over so you can verify that network tables is valid via SmartDashboard (SmartDashboard and GRIP both use the same net tables library but there's no indicator when GRIP fails)

On a side note it never seemed to fail during a match, it would only fail to connect and once fixed by the driver was fine throughout the match (I think? We mainly used it for auton selection...)