RoboRio 1 connectivity issue

[Hank_Team1351]

We are unable to connect our RoboRios, with s/n 30EB294 and 306CDDD, to our laptop. The POWER, STATUS, and RSL lights all indicate other systems are operational, however, the COMMs system is nonfunctioning nonetheless. 

[mshafer]

Hello!

This is Matthew from NI. Thanks for posting on the forums.

Are you trying to connect over USB or over Ethernet? (If just one, can you test the other?)

Is the imaging tool able to find it?

If you reboot the laptop and robot and then open the imaging tool before any other software, is it able to find it then?

You can also try booting the roboRIO into safe mode (https://docs.wpilib.org/en/stable/docs/software/roborio-info/recovering-a-roborio-using-safe-mode.ht...), and running the imaging tool as admin (right click, run as admin) -> does that help it communicate with the rio?

[NWPat]

Hi,

I am a mentor with Team 3826, and we are having a similar problem. In our situation we have a V1 RoboRIO and a Lenovo E530 laptop running Windows 10. 

We were able to use the RoboRIO imaging tool (2023) over USB. Everything appeared normal, the roboRIO showed up and the app indicated success, for both "Update Firmware" (roboRIO_6.0.0.cfg), and "Format Target" (FRC_roboRIO_2023_v3.1.zip). We also updated the radio, and the resulting unique radio name showed up as expected in the laptop's list of available wireless networks. The laptop successfully "connects" but that's as far as it goes - the driver station communications indicator stays red. In addition to connecting via wireless, we've also tried wired, both ethernet and USB separately, and neither of those lead to a green indicator for driver station communications either, so the roboRIO currently has no team code loaded.

When "connected" to the radio via Wifi, the laptop's network properties shows "Unknown Network" with two IP addresses, 10,38.26.201, and 10.38.26.129, respectively (I assume for the radio and the roboRIO). Both IP addresses can be pinged successfully from a command box.

When the roboRIO is directly connected via USB cable, network properties shows an "Unknown Network" with an IP of 172.22.11.1. That IP can also be pinged successfully from a command box.

When the roboRIO is directly connected via ethernet cable, network properties shows "Unknown network" again, but no IP is shown. IP assignment is listed as "Automatic (DHCP)", so from the docs I read, shouldn't mDNS have provided one? In any event, pinging any of the prior three IP addresses (from the wireless and USB cases) did not succeed.

During communication attempts, only one cable was connected to the roboRIO at a time - that is, either ethernet from the radio, ethernet directly from the laptop, or USB direct to the laptop. When testing USB, we tried disabling all wireless (including Bluetooth) and Ethernet devices using DevMgr, but doing that made no difference. All activity was performed using an Admin account, with laptop virus protection and all firewalls turned off. We did not reboot between every test, by did reboot frequently, both roboRIO and laptop. We did not boot to safe mode, though, so may try that today. Finally, DevMgr reports no errors for any installed drivers, the laptop passes all built in diagnostic/ health checks, and all Windows update and Lenovo system update offerings are current.

Any help to get this resolved would be appreciated.

Thanks,

Pat Volk

[mshafer]

@NWPat, Please post a new thread so we can discuss your specific issue without conflating which device we're talking about.

[NWPat]

Thanks for the quick reply and implicit advice on forum protocol.

Reposted this question under subject line: "No Driver Station communication when apparently connected - whether with wireless, ethernet, or USB "