We are having problems getting our driver station to connect after our last competition. We have reimaged the radio for home use. We can ping ip of radio(10.28.76.1) and roborio(10.28.76.2). We can ping roborio using mdns name(roborio-2876-frc.local). We can connect to roborio via usb and see it has ip addresses assigned to it. The driverstation shows robot radio and robot lights green in diag tab. The communications and robot code lights are red. Never turn green.
We tried connecting to the roborio using ethernet cable. We could ping mdns name (ping showed a response with ipv6?). But we could not ping using 10.28.76.2. In driverstation we did not see enet link light in diag tab turn green. None of the lights in diag tab turned green.
We are running windows 10. Turned off windows firewall, Uninstalled 3rd party virus software.
We tried two different ethernet cables. We tried two different laptops. We see the green/orange lights lit on the roborio ethernet port.
We don’t see any fault leds lit on roborio. During competitions everything worked fine… we connected to roborio using ethernet in pits or practice field.
Does the Driver Station find the roboRIO if you are only connected to it via the USB port?
It’d probably be worth getting that simplest connection to work before moving on to Ethernet & wireless.
Try Disabling all other NICs on the PC in case the extras are causing some confusion. Don’t connect to the Internet at the same time, for instance.
On the DS Setup tab, click on the arrow next to your team number entry to see if anything is listed there.
If you don’t see anything listed then try shift-click on the arrow to see if that lists anything more.
Get the roboRIO IP address via the USB and try typing that into the team number spot on the DS Setup tab.
Does the Driver Station find the roboRIO if you are only connected to it via the USB port?
It’d probably be worth getting that simplest connection to work before moving on to Ethernet & wireless.
I think we tried this… and no, DS did not find roboRIO. I would like to double check tho… While connected via usb we did bring up the imaging tool and it found roboRIO.
Try Disabling all other NICs on the PC in case the extras are causing some confusion. Don’t connect to the Internet at the same time, for instance.
Did that.
On the DS Setup tab, click on the arrow next to your team number entry to see if anything is listed there.
Did that, we see 2876. Tried typing in 2876 again…
If you don’t see anything listed then try shift-click on the arrow to see if that lists anything more.
Get the roboRIO IP address via the USB and try typing that into the team number spot on the DS Setup tab.
The roboRIO address would be 10.28.76.2 in this case? Will try that. We did try typing in mdns name and variations(found in another thread you posted). mdns names didn’t work.
I forgot to add that we also tried uninstalling the NI sw and re-installing it.
We meet once a week now so we may not get a chance to try any of this or other suggestions till next Wednesday. Thank you for the ideas Mark.
If you connect directly via USB it will be 172.22.11.2
If you connect via Ethernet/wireless, then the easiest way to look up the Ethernet address is to also connect via USB and browse to 172.22.11.2 and see what the roboRIO webpage says the address is.
The roboRIO gets it via DHCP from the radio (when the radio is setup for home use) and it’ll be an address like 10.28.76.20 or higher.
The DS Setup page should return a list under your team number of either a DNS address, an IP address, or it should say “None found”
Windows 10 has three different firewalls installed and running by default. Make sure you turned all of them off. There’s Windows Firewall, Windows Firewall with Advanced Security, and Windows Defender. I saw plenty of teams who disabled one or two of them, but left at least one on and it caused problems. Not sure if that’s actually what’s causing your problem, but it’s something you should check.
If you remember correctly and the imaging tool finds your rio but the laptop can’t connect to the webdash, it sounds like you need a reimage. If it does connect to the webdash, then something is keeping the DS from accessing the roborio. That is likely either a firewall problem or a DCHP/mDNS problem.