Cannot imagine RoboRIO because the static IP was changed

Technical Control System
1

Hi, I’m the programmer from rookie team 10034. Basically our previous programmer didn’t read the manual carefully, and set the roborio’s ip to 10.10.3.87. So I tried to change the ip to 10.100.34.2 via web, and it indeed worked. But somehow I can’t do basically anything after that.

This is our current situation:

  • I can’t change the ip back, even I reset the roborio for 5 seconds for various time.
  • I can’t connect it via usb wire, because I changed the default usb ip
  • to 10.100.34.2 too (is it possible?) and it seems the default usb ip is something like 169.xxx.xx.xx, which is not 172.22.11.2.
  • I can ping http://roborio-10034-frc.local/ from cmd, but I can’t access it.
  • I can’t ping and access to 10.100.34.2.

We would be grateful if anyone can give us any suggestion to reset the ip, and help us to change the ip correctly :slight_smile:

May you guys have a great new year - from team 10034

2

Have you tried using the roborio team number setter or imaging tool? Both of these can configure the team number and by extension the IP config. If neither of these work, you can try reimagine the rio. Since you are a rookie team, I assume you have a roborio 2, which you can reimagine by pulling out the micro sd and plugging it into a computer.

1 Like
3

Thank you. We use a roborio 1, and we can’t reimagine our roborio, because the ip was set wrong somehow.
Our team number was set correctly, so I don’t think number setter works here, and I didn’t see the ip config option in number setter tool.

4

螢幕擷取畫面 2024-12-28 151354
螢幕擷取畫面 2024-12-28 151354942×572 23.2 KB

This is what we meet now. Do you recommend us to change the ip directly through this interface? We tried but failed, and the robot shows “unrecoverable error” light.

5

Highly recommend using USB to image the Rio 1. That will never require manually changing IPs.

Also, as a rookie team, you should be receiving a full control system in the KoP at Kickoff next weekend. This will include a Rio (almost certainly a Rio2)

1 Like
6

You should always reimage your roboRIO 1.0 over USB not over Ethernet.

1 Like
7

Thanks for suggestion. I apologize if my description was not clear, but we did tried to re-imagine roborio by cable and it didn’t work because of the ip was set to 10.100.34.2.

8

Hmm, I’ve never seen the IP settings affect the USB connection before, afaik, changing the USB IP shouldn’t be possible.

Do you get an IP address when you ping the “.local” address?

And the imaging tool can’t find the roboRIO?

9

I think it’s unlikely that changing IP addresses caused the roboRIO to report unrecoverable. That needs to be solved first. The good news is that once you’ve recovered from the unrecoverable error, the IP addresses will be reset.

First try Recovering a roboRIO using Safe Mode — FIRST Robotics Competition documentation and if that fails then try https://knowledge.ni.com/KnowledgeArticleDetails?id=kA03q000000kOHkCAM&l=en-US

10

Um it found roborio, but couldn’t do anything because when the ip was changed then it shows a “corrupt firmware” error message. After various times it was fixed, but I am still unable to change our ip from the wrong one 10.10.3.87 to the correct one.

11

I tried to use the first method and somehow it finally works after ten-ish tries. I have no idea why some of the attempts failed though but it did work.
I feel grateful for the second link too.

12

Hmm, can you SSH into the roboRIO?

Maybe you can change it through there

13

Based on my understanding, the USB IP address (172.22.11.2) is provided by the NI toolkit running on the PC you’re using for imaging. If you’re encountering issues with that process, I’d recommend restarting the PC or trying a different computer with the NI Game Tools installed.

1 Like