cRio Communication Errors

[icecube45]

Originally Posted by Greg McKaskle

I"m curious whether there was excessive loss or lag before the drop. Also, the DS pings anytime anything happens to the comms. It pings and logs any changes to the four possible devices. This helps determine if the radio is still there and reachable and only the cRIO is down, etc.

If the radio is really there and only the comms or code lights go down, that indicates that the code is bringing down the cRIO. What language? Does this correspond to any particular robot feature like vision processing, etc?

Greg McKaskle

The funny thing is, this was working just fine until we did some cable management on our robot, now it doesn't work on any robot.
We are using java this year, but we have gone back to barebones code, confirmed working, and have the same problem.
We also switched to some very basic c++, same problem.

It doesn't correlate to anything, and is just plain weird