RoboRio 2 Unrecoverable Error

[Aydan.L]

Hi,

I recently tried to image a new RoboRio 2, but after flashing the microSD card, the Rio cannot be recognized as a device by any laptop or the imaging tool. Additionally, the status light is blinking continuously, which indicates an unrecoverable error. The microSD card is flashed with the FRC_roboRIO2_2025_v2.0.img image using balena etcher.

I also tried putting it into safe mode with reset button but it reverts to the continuous blinking. What could I do to solve this? Thanks!

[Aydan.L]

Hi everyone,

It has been a few days since my previous post, and I wanted to follow up regarding the issue with one of our RoboRIOs. Our team only has three Rios, and one of them has an unrecoverable error. I was wondering if I could contact a NI support staff to troubleshoot this issue. Any help would be greatly appreciated!

Sincerely,

Aydan

[nahuel_ch]

Hi Aydan10131,

I hope you´re doing great!

This is Nahuel from NI, I have reached out to you via DM for further information and steps.

Have a great day!

[Aydan.L]

Hi everyone,

I recently posted about an issue with my RoboRIO, and one of the staff members kindly reached out to help me privately. However, I haven’t received a response for over 2 weeks, and I’m still struggling with the problem.

Could any other NI staff members please assist me? I really appreciate any help or suggestions you can provide.

Thank you so much for your time and support!

[aeastet]

I know this is probably a silly question but did you follow these directions?

https://docs.wpilib.org/en/stable/docs/zero-to-robot/step-3/roborio2-imaging.htmlhttps://docs.wpilib.org/en/stable/docs/zero-to-robot/step-3/roborio2-imaging.html

Please make sure the firmware on the roboRIO is the correct version. This will make a difference as well.

[mshafer]

Hello,

I'm Matthew with NI. I will be taking over this support thread. @Aydan.L, I sent you another direct message to follow up (I did get the notes from nahuel_ch, so we're not starting over).

[aeastet]

OK I have two things I am wondering about this:

First: Why are you hiding the responses in DM's? If you keep the discussion here others may find what you did to help these guys useful in the future. The rest of the forum allows user to help where they can. I would also prevent responses from taking weeks.

Second: Why would you discourage user from helping where they can. This is another reason that NI is loosing so much ground in FIRST. No real support. No transparent communication. Teams do not feel supported and you can see that in so many of these requests for help.

When you take the discussion privet you lose the learning capabilities and the support from people that want to help. I have been a FIRST mentor since 2010. There is not much left to support for LabVIEW in FIRST. It is because of this type of behavior I believe that this is true. Do you believe that the main LabVIEW forums would be so useful if everyone took the discussion private and told the user not to help?

It really is sad to see where LabVIEW and NI have gone in FIRST. I guess I will not have to watch it die for too much longer. Still sad though.

[mshafer]

aeastet, 

Thank you for your concern. We move to DM's when we start discussing the possibility of an RMA. This is in part because we have to communicate shipping information which should not be posted publicly.

If we can reply to a thread with standard steps that any team should try (like the imaging process you linked), we do that first.

[mshafer]

And please do continue to try to help peers. I was replying to the request that another NI person to get in contact.

[aeastet]

I appreciate your response. If you are to the RMA phase I would expect that you would not place all of the personal information on the forum. If you are not in the RMA phase then seeing the steps to recover this device would be beneficial. I did not see any help or suggestions in the  tread to discuss how to recover this device before you got to the RMA phase.

This discussion would be good for other FIRST teams to see. Most of them may have no programming experience and many will have never heard of NI or LabVIEW. Was there a discussion? If so why was it not in this tread so others could see it?

The turn around on responses to these teams is also not good. We have a very limited time (6-8 weeks) to design, build and get our robots ready for competition. Waiting weeks to give a response is not OK.

That is all I am saying.