Troubleshooting Hardware

cancel
Showing results for 
Search instead for 
Did you mean: 

Team 3459 has 2 dead roborios - FTAs at official events told us they needed to be RMAs

> Do we need anything other than roborio? I will checkin daily until we have this figured out. For now, I'm assuming we can simply plug power into the roborio and report the LEDs we see and what patterns they show? Will that be a good starting point?

 

roboRIO + power supply (likely a PDP) + an SD card (for the v2)

 

This is of course assuming the SD card is imaged, and the rio is still in an error state (if not, a laptop with Driver Station / imaging tools installed would be needed to query the unit further)

0 Kudos
Message 11 of 18
(607 Views)

Ok. I'll try to gather those tonight and see if we can explore it tomorrow evening.

 

Thanks,

 

Rob.

0 Kudos
Message 12 of 18
(596 Views)

finally got a chance to run these. just added power and nothing else. What comes next?

roborio_2_0.jpg

robotrio_1_0.jpg

0 Kudos
Message 13 of 18
(554 Views)

Are all 3 lights staying on constantly on both units?

(The Status light SHOULD either turn off, or start blinking a code after at most 30 seconds).

0 Kudos
Message 14 of 18
(543 Views)

A bit of context here, "unrecoverable" is a term that's generally used to describe a bad state for the OS.  You'd see this with a flashing STATUS light.

 

There's different ways to handle this for the roboRIO and roboRIO2.0.  With respect to your rush, these fixes are generally faster than going through the RMA.  I trust when the FTA mentioned this term they were describing this situation.

 

If that's not what you're seeing, it'll help if anyone is able to recall any details around what you were seeing previously.  That helps narrow down any troubleshooting.  Ideally, we get you up and running today (we can ignore the costs.  For your time, it's often the best solution).

0 Kudos
Message 15 of 18
(535 Views)

At this point, having them working in time for January would be amazing. I took video of each of them as well. Don't know if I took enough video. 

For the roborio 2.0, nothing strobed. The status light went out at about 14 seconds.

On the original roborio, nothing strobed but i only have about 3 seconds of video taken after the at a time after the status light went out.

I can take longer videos or take different actions but doing this through this forum will be slow unless you can tell me what I need to get for you. Best if I can take several steps at once.

I can't post the videos because even 3 second file is too big for this server apparently. if you really need it I'll figure out how to reduce the file size, just zipping them didn't do it. Hopefully, the verbal acount above is enough for you.

0 Kudos
Message 16 of 18
(520 Views)

Ok, solid on can also mean unrecoverable error (I've only seen the constant flash myself, but it's in the list here: https://docs.wpilib.org/en/stable/docs/hardware/hardware-basics/status-lights-ref.html)

 

For the 2.0 -> can you try re-imaging the SD card using either BalenaEtcher or the Raspberry Pi imager and the .img.zip file as described here: https://docs.wpilib.org/en/stable/docs/zero-to-robot/step-3/roborio2-imaging.html 

 

 

For the original -> can you try to reset the device to factory image following the steps documented here: https://knowledge.ni.com/KnowledgeArticleDetails?id=kA03q000000kOHkCAM&l=en-US 

 

0 Kudos
Message 17 of 18
(506 Views)

The good news is that following the instructions you provided allowed us to recover both roborios to the point that we can access the on board configuration webpage and can connect to them with a drivers station. 

 

The next step is that we will put them in a robot and see if they can work under load correctly.

 

Thank you so much for your help.

0 Kudos
Message 18 of 18
(481 Views)