Repeatedly had to reimage RoboRio

[wildJerry]

Hello, last week my team(2704) had a weird issue with one of our Rios.

The Roborio had to be re imaged multiple times over the course of a single day. Each time, the driver station would show robot communication, but it was not possible to redeploy code. Restarting both the laptop and the rio failed to fix it, only reimaging. The issue kept coming back after a while, despite the Rio not even having power cycled in the meantime.

Please advise me on how to make sure this doesn't happen again, and to confirm whether or not the Rio is dying. Right now all of our Rios are on robots, and the plan is for the Rio in question to become the backup once it's freed up, and in either scenario, it's very important that the board is reliable.

Thank you!

[ThaysMolina]

Hi,

I am Thays from Technical Support at NI.

Could you verify that the code is not consuming the CPU and making the roboRIO lose communication?

[wildJerry]

If the issue were CPU consumption, shouldn't it still be possible to deploy code?

If not, please inform on how to confirm whether or not that is the issue.

[BoKnows]

If the RIO CPU was at 100%, it's possible it could be unable to handle the request to reimage.  

How were you trying to deploy code?  Via USB cable?  Ethernet?  Radio?

Does that same method work after a reimage?

To test the CPU theory, you can reimage and try sending just a sample project to see if you see the behavior return.  You can potentially see issues in the console as well.

[wildJerry]

Even the program that we were running on that day doesn't have the issue, we're just trying to figure out why the rio neeeded to be reimaged multiple times a day and prevent it from happening again(!) We need to know that the RoboRIO is reliable, as it will likely be our competition backup.

We used USB and radio(may or may not have tried ethernet), everything failed before reimage, worked after - at least until the next time it needed to be reimaged.

I looked through logs which I confirmed to be the correct ones(Unfortunately I don't seem to still have them, Or I'd upload), and CPU was consistently low throughout the entire day.

Is there anything else we can check, or do we just have to hope that this issue that repeatedly arose was a fluke?

Sorry for the late reply, between an offseason event and the holidays I haven't had a chance to do much.