Constant Error Message from NetConsole

[William Kunkel]

We've been debugging robot code, and we wanted to see some values via the cRIO NetConsole. However, it's hard to view our code's output, because roughly every second, we see the message:

0x10eef90 entered connection state: GOT_CONNECTION_FROM_CLIENT
Starting task: Server Connection Reader Thread
0x10eef90 entered connection state: CONNECTED_TO_CLIENT
Bad message: A server should not receive a protocol version unsupported message
0x10eef90 entered connection state: SERVER_ERROR
Close: 0x10eef90
Task exited normally: Server Connection Reader Thread
task 0x1106e60 (FRC_Server Connection Reader Thread) deleted: errno=9 (0x9) status=0 (0)

Has anyone else seen this before, or know a way to fix it?

[BradAMiller]

I believe that you have an old version of NetworkTables on one side of the connection. Is it possible that you are running a beta version of the C++ library on the robot?

Brad

[William Kunkel]

I doubt it, but I'll look into it and check back later.

[JefferMC]

We are currently getting the same message from our C++ program, although it comes and goes. After a while of this happening it appears to progress to the point that it throws an exception in the debugger, and we have to reset the cRio and reload the computer.

While I did have the 2012 WindRiver / SmartDashboard installed on this PC, I never installed any beta. I did follow the instructions for the 2013 updates.

We have some objects declared that are not actually connected on the robot at this time, and I've been attributing it to that for now. But I thought I'd search to see exactly what the connotations of this message are.

[mitchellweb1]

Hey guys,

What clients are you running on your computer? Roborealm, SmartDashboard, LabView Dashboard, Network Table Viewer, etc. If you are using Roborealm make sure that you have updated to the latest version as I know that there have been a bunch of updates to that.

--Mitchell

[JefferMC]

I discovered the mid-season updates last night (WindRiver and Driver Station) and applied them. This particular error has gone away since.