FRC - roboRIO 2 issues - Replacement/Diagnostic Request

[MichaelKubacakFRC9137]

First date of attempted use was March 21st. The roboRIO was not recognized/not found by imaging tool with going through the steps outlined on the FRC website. Multiple other cords and other microSD cards were used in attempts to continue imaging roboRIO with no success. Status lights behaved as normal during attempted imaging. Attempts were also made in safemode with no success. At our first competition, our mentor team 1477 loaned us one of their spare roboRIO 1.0, this loaned roboRIO worked right away with no issues. After that competition, team 1477 took home our nonworking roboRIO 2.0 to see if they could figure out what the issue was and why it was not being recognized, with no success. They could not get it to work and also could not figure out what the issue was. They returned it to us shortly after in which a few more attempts were made to image the roboRIO. After the further attempts were made the roboRIO began constantly flashing indicating the unrecoverable error. No further attempts were made.

[mshafer]

Hi kubacakm,

Thanks for posting on the forums. I'm Matthew with NI.

We've had several teams get hung up on this.

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

[MichaelKubacakFRC9137]

Matthew, thank you for your fast response.

This was attempted using BalenaEtcher several times throughout the season using the instructions directly from the link you sent with no success.

[mshafer]

Can you try Raspberry Pi imager?
(and make sure your using the .img.zip file, the non img file is used for the original roboRIO)

[MichaelKubacakFRC9137]

Just tried Raspberry Pi imager and got the same results. We can seemingly successfully write the image using the BalenaEtcher and Raspberry Pi Imager software, but when we plug the roboRIO 2.0 into the computer to use the roboRIO Imaging Tool software the software does not detect the roboRIO2. Every time we get the error message <No roboRIO targets found>. We then try and go through the next option of clicking the "SD" button above the "Select Image" box to manually select the file but it still does not work. 

Something that is concerning to me is that if I try to open the actual FRC_roboRIO2_2023_v3.2.img file, I get an error "Couldn't Mount File" message stating "The disc image file is corrupted." I have no idea if this is normal when trying to open the actual .img file or not.

[mshafer]

Imaging Tool is only used to set the team number (and provide a shortcut to the images) for the roboRIO 2.

With the unit plugged in via USB, are you able to ping 172.22.11.2 ?

If not, can you try walking through the steps here: https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z0000019NlgSAE&l=en-US

And let me know which step it fails at?

[MichaelKubacakFRC9137]

Good afternoon, 

My apologies for the late response.

In attempting to go through the list sent to me: it failed at step 5 of trying to ping the roboRIO 2.0. When trying to ping the roboRIO 2.0, I was given the following error message: "Reply from 66.76.29.13: TTL expired in transit." This response was received when firewall was enabled and then again when firewall was disabled. When not connected to the internet, the following response was received both when firewall was enabled and when firewall was disabled: "Request timed out." and "Reply from 10.255.3.151: Destination host unreachable."

I attempted to ping the roboRIO 1.0 loaned to us by 1477 with the same USB plugged in the same ports and all the same wires for power, ethernet, etc. and the ping was successful, therefore I do not believe the computer port, associated drivers, and USB cable used are the issue.

No further steps were successful as we cannot ping the roboRIO 2.0.

I believe the issue is the USB port on the roboRIO 2.0.

[MichaelKubacakFRC9137]

Can I please get a response to my previous post?

[mshafer]

Sorry for the delay, I sent you a private message on next steps.

[PeterGehbauer]

We are having the same issue with a roboRIO2. Tried the same things but no joy. Code, electronics, etc., works fine with RoboRIO (original). What remedy is recommended? Currently on summer vacation but will return in early September. No access to the roboRIO2 until we return.