[NotInControl]

Originally Posted by compwiztobe

We switched from C++ to Java after seeing our issues, and while it was hard to reproduce with C++, everything we have tried so far with Java has shown no sign of the problem.

That is interesting. I have to admit I have not yet confirmed this to be the cause of the symptoms I saw on our robot in the pits this passed weekend.

The robot in question is now bagged, however I will be trying to recreate these problems on our practice bot over the next few days.

The symptoms expressed in this thread were very similar to the symptoms we saw which is why I think this bug may be a suspect.

However, we have always had all of our smartdashboard calls in a separate thread that gets started on robot init. The reason for this is to reduce the amounts of writes per second.

The only smarthdashboard call I have that is running in the same thread as the robot thread is our autonomous sendable chooser which runs in the disabledPeriodic() block.

We are going to do testing with and without this function call to see if we can get the robot to hang again. During our quick diagnostics in the pits, the only way we could re-establish full comms was by restarting the robot, and the driverstation/dashboard. Doing just one or the other was not enough to correct the problem.

I am more concerned with preventing the robot from hanging then having my dashboard work.

We have never seen this problem on the field, as we always have a standard practice to shut robot off, and exit all dashboard/driverstaion windows prior to every match.