Two RoboRIOs need Repair; RMA Request

[CitrusCircuits]

Dear NI Support Team,

I am reaching out on behalf of FRC Team 1678 Citrus Circuits and we are currently experiencing issues with two of our RoboRIO units. One RoboRio (SN: 3064EF3) has a faulty power system and does not turn on; The other RoboRio (30A0DE8) has a bad storage system, and cannot be used properly.

Below are the serial codes and MAC addresses for the two RoboRIOs in question:

RoboRIO Serial Code: SN: 3064EF3 MAC: 00802F1903CE

RoboRIO Serial Code: SN: 30A0DE8 MAC: 00802F21A933

Please let us know the address to which I can send these units to start the RMA process. Further details can be given if needed. Thank you in advance for helping resolve this issue.

All the best,

Team 1678 Citrus Circuits

[JessNI]

Hi Team 1678 Citrus Circuits,

My name is Jessica, I work at NI. You mention one of the RoboRIOs has a faulty power system, did this suddenly happen when you tried to turn it on, or were there any external factors involved (ex: was the RIO turned on and working, did it bump into anything…)?

As for the second RoboRIO, why do you believe it to have a bad storage system? When did it stop working? Same as the other RoboRIO, were there any external factors involved?

[CitrusCircuits]

Hello Jessica,

The RoboRIO with a faulty power system didn't turn on when we attempted to use it after it was kept in storage. We ran a few checks on it, and it showed no signs of visible power when given a proper power supply. For the second RoboRIO, it powered on and seemed to be functioning, but after a few checks that didn't seem to be the case. The first thing that was noticed was that the RoboRIO showed up on the team number setter, but didn’t show up on the imaging tool- we could see it, it just came up in the place we needed it to to configure it properly. It showed us packet loss, but software didn’t find any glaring possible issues with hardware, and after cross-referencing similar issues other teams have had, we figured out it was a Storage problem.

Both RIOs were being kept in storage, and seem to have had no external factors that could have damaged them. If there are any other pieces of information that you need, we'd be happy to provide it.

All the best,

Team 1678 Citrus Circuits

[JessNI]

Hi Team 1678 Citrus Circuits.

Thank you for the information provided!

For the first roboRIO (3064EF3), I've sent you a direct message to coordinate the repair. For the second (30A0DE8), let's try to connect to the device using USB connection and attempt to reconnect. If you can SSH into the roboRIO, try running badblocks -s /dev/sda and see if it detects any issues. This command is safe to use on mounted drives.

Also, Happy Holidays!