After we made the mandatory update in C++, our ability to tune PID failed – it starts to work, and then we get an error that appears to kill the motors every second or so. (Please keep in mind that our code worked fine before the update).
Interspersed between our printed data, we get:
0xcd99b8 entered connection state: GOT_CONNECTION_FROM_CLIENT
Starting task: Server Connection Reader Thread
0xcd99b8 entered connection state: CONNECTED_TO_CLIENT
Bad message: A server should not receive a protocol version unsupported message
0xcd99b8 entered connection state: SERVER_ERROR
Close: 0xcd99b8
Task exited normally: Server Connection Reader Thread
task 0x11177f0 (FRC_Server Connection Reader Thread) deleted: errno=9 (0x9) status=0 (0)
We are also getting
Bad message: Unknown Network Table Message Type: 128
Close: 0xcd99b8
Task exited normally: Server Connection Reader Thread
task 0x11177f0 (FRC_Server Connection Reader Thread) deleted: errno=9
This problem is occurring whenever the robot is on, including when it is disabled. We have print statements to show our shooter rate data every 20 loops, and these errors are interspersed at rates that appear to be inconsistent with the main teleop while loop.
Any assistance that anyone can provide would be very appreciated.
Looks like your Dashboard, or other network tables client is not the right version. Make sure your SmartDashboard is the latest version.
We updated the dashboard the day before… and did it again after your suggestion, just to be sure. Same problem.
We tried again, only this time with a laptop that has not yet been updated. Everything worked fine, and we were able to tune our PID with no difficulties outside that which is normal when trying to tune PID.
As this update is mandatory, this concerns us rather muchly.
Your best bet is probably filing a bug report at the WPILib project, attaching the code that causes the issue will probably help. If everything worked before the update then it sounds like a regression which I’d imagine the WPILib developers want to hear about
We don’t use any dashboard, so setting the dashboard to Remote Dashboard stopped the error for us.
Ah, so you had the same error after the update?
Any resolution for this? We just noticed the same errors and we need the Dashboard!
TIA
Yes, our programmers figured it out. I’ll ask Spencer to post details ASAP.
The problem has been solved. The error goes away when using the SmartDashboard, which was easy enough to set up. Thanks for the help, everyone.
Does that mean that the default dashboard had an issue?
Is this because the PID collection wasn’t created on the robot? The default dashboard doesn’t have a template for making PID objects, but it can be done.
Greg McKaskle
In our case, using the FRC Dashboard and Smart Dashboard at the same time produces a flurry of mangled messages and kept us from playing. When we use only the Smart Dashboard we get the occasional error (printed to console) but the robot continues to operate.
When we ran the mandatory update, we got an error that prevented us from being able to do anything at all. Once we installed the Smart Dashboard, the error went away and we could do whatever we needed to do.