Roborio imaging tool not see the roborio 1

hi we have a problem with our imaging tool, we have a roborio 1, that we’re trying to reformat, however, the imaging tool does not see the roborio.
we are connected to the roborio via USB cable, like the wpilib doc shows, and it says we have comms in the driver station,but the imaging tool still won’t recognise the roborio.

thank you,
6740.

make sure:

  1. if you have any anti-virus/malware ← to disable it or allow firewall full access for the all the tools. [this includes the MS Defender firewall]. remember these are specific to each network property types - domain/public/private.

  2. for the most part, the USB network interface should default to be private. But if you ever use Wifi/Ethernet make sure they are on/set/change to private. And if you ever update your device drviers, double check (and even sometimes pain in the rear MS update will change this).

  3. Do not even try to do it using a Mac/Linux. Yes it can be done, no, majority of the teams just shouldn’t even bother trying.

1 Like

thank you but for us the imaging tool won’t evan recognize the roborio itself, its simply not there.

Try a different cable if you haven’t already. If the USB still isn’t working, try Ethernet instead. We have one specific RoboRio V1 with a bad USB port but is fine otherwise and we use it for the practice bot only.

Check the USB port on the RoboRio for damage as well

we’ve tried multiple different firewall settings and such, nor are we using a usb interface, and don’t worry were on windows.

another quick way to see if you USB cable is working or not is to open the Windows Device Manager, when you plug in and unplug the USB cable, the appropriate USB NIC device/driver should show up. If the manager doesn’t even update, then your computer doesn’t even at least see the cable and something new on the other end.

One time, the USB “ethernet” driver shows up but was in ‘disable’ mode, so a quick ‘enable’ should turn it on.

We actually have an old RoboRIo with a loose ethernet jack now. So it’s stand on 1 leg, hop 4 times while spinning in a clock wise circle and not fall for that cable to stay connect. :slight_smile:

1 Like
1 Like

Were you able to solve your problem, if you are can you tell me how you did because we are facing the same problem right now with our roborio and we have competition at the end of the week.

Thank you.

I learned recently that if the NI System Web server on a Rio 1 is disabled (e.g. you might have done this because your robot code needed the space) the imaging tool will not be able to find the rio.

If that’s the case, you can turn the web server back on the with WPILIB roborio team number setter tool.

OR see the above-mentioned “Recovering a roboRIO using Safe Mode”.

1 Like

I just imaged a rio 1 a few days ago and did with ethernet worked perfectly

The presence/absence of the webserver should have no impact on imagability. It’s simply a process running on the Rio OS.

The rio shows up in the imaging tool if it can be found via mDNS (and potentially other mechanisms).

1 Like

I don’t know why this is the case but we ran into the same behavior. Booting into safe mode fixed it.

I agree, “it should have no impact”. But see: roboRIO Imaging Tool can't connect roboRIO if web server is disabled · Issue #74 · wpilibsuite/2025Beta · GitHub

… huh. Thats news to me

1 Like

We figured that the ip of the roborio accidently turned to 0000 while we were working on the electric. I changed it and now i am able to deploy but thank you anyways.

1 Like