We’re having some kind of fundamental network issue with our roboRIO. It surfaced when the CameraServer crashed while trying to connect GRIP to the camera Server via Http running on the roboRIO. Everything was working fine a couple days ago. Most things are still working fine, strangely enough. We’re able to connect to the robot, deploy code, drive it around, SmartDashboard is displaying various controls properly, including the camera. But roboRIO-1024-FRC.local is not resolving or responding.
We can see minimal rio webdashboard config via 172.22.11.2, when connected via USB Ethernet.
When I ping roboRIO-1024-FRC.local it does not respond.
When I ping the IP address from the webdashboard, 10.10.24.2, it does not respond
We have run the Update Suite.
The rio has been imaged with our team number.
We’ve tried power cycling the robot, and restarting the laptop (Windows 10).
I’ve gone through the WPILIB Network Troubleshooting. These steps seem to indicate it is a problem with the laptop Network Configuration, because pinging the IP address of the rio fails. But the lapotp’s network settings are set to Obtain an Address Automatically.
I’m attaching a screenshot of our webdashboard.
As far as the Web Dashboard, that’s how it’s supposed to look. You have to configure motor controllers etc. through their vendors’ tools from now on (for example Phoenix Tuner for Talon SRXs). For everything else, our team has had problems with finding IPs too, so someone else’s help would be appreciated
Somehow we also ran into that problem.
roboRIO-1690-FRC.local is not resolving or responding (when connected by Ethernet or USB).
We can ping the IP 10.16.90.2 just fine and the webdashboard is showing fine on that IP.
We can deploy code (when deploying to 10.16.90.2 and not roboRIO-1690-FRC.local) and run it.
We didn’t tried to re-image the roboRIO yet, but we did try to ping roboRIO-1690-FRC.local from two different laptops with no success.
Did anyone else encountered this problem and got some clues on how to solve it?
We fixed our connection issues through grip by connecting as an IP camera through this address right here: http://10.10.24.2:1181/?action=stream
You just use the address http://10.TE.AM.2:1181/?action=stream.
Do you have iTunes installed on the Windows machine? If not, you’ll have problems getting mDNS responses worked out as they don’t really have a good native resolver that works. Shortest path to success there is to just install iTunes so that the Bonjour Service is installed and taken care of for you.
Secondary issue:
Your Roborio/FRC Radio are not configured to spit out DHCP addresses, so if you have it setup to obtain the IP automatically it will not necessarily work. Simply setting the IP address of the host computer to one that is within the 10.TE.AM.0 network will make it so you can connect via Ethernet or Wifi just the same.
Tertiary issue:
The camera server streams are available on incremental ports if you’re trying to use the CameraServer class as an output stream. The URL can be http://10.TE.AM.2:1181/stream.mjpg, then http://10.TE.AM.2:1182/stream.mjpg (and so on with each mjpg stream you create).
It’s important to note. The .local address is resolved to a IPv6 Link Local address. Make sure you have IPv6 enabled on your computer and you have a IPv6 Link Local address by doing ipconfig in the windows command line. A Link Local address starts with fe80.
I’ve noticed sometimes roboRIO-####-FRC.local not responding. But 10.TE.AM.2 is, so I’ve just switched to that when I run into it. I question whether it is sometime to do with the mDNS service, though I haven’t looked to deeply.
At one time I remember there being a case to install other software to do that, like Apple’s Bonjour, but since I haven’t thought about it much I just figure that Win10 takes care of that now. I didn’t find much about this (I did browse through a question about it: https://superuser.com/questions/1330027/how-to-enable-mdns-on-windows-10-build-17134). I might try this, if I do encounter it again. Otherwise, I’ll watch here for anyone that knows.
