Hello all,
My team’s robot has an issue where we can connect to the robot just fine after loading firmware and configuring code for the bridge, but that’s the only case where communications can be established between the driver station and the roboRIO. If I were to disconnect, I won’t be able to re-establish comms even though I’m connected to the bridge. In the DS, the robot radio light is green, but the robot light is not. Please help, as having to load firmware and configure the bridge every time I want to connect is slow and tedious.
FYI, I have already imaged and installed java on the roboRIO, otherwise it wouldn’t have connected in the first place. Although I have yet to try re-imaging it, if anyone here thinks that my help.
Thanks in advance to anyone who takes their time out to read this.
Here are some things to test that might help us identify the issue you are having.
Bring up a command prompt
ping roborio-3017-frc
ping roborio-3017-frc.local
ping roborio-3017-frc.lan
ping roborio-3017-frc.frc-robot.local
*ipconfig /all *and look for what’s listed close to the top for DNS Suffix
You can also connect to the roboRIO via USB and use IE to browse to 172.22.11.2, then tell us what Ethernet IP address is assigned and what the full DNS name is.
yeah, i would try connecting your computer via usb to the roborio, like Mark above suggested, and check to see if you get robot code and robot communication. if you do, it might be the radio, if not, then its not your radio and has something to do with either your rio image or you didnt update your eclipse to match the version of your roborio, which, if that was the case, you wouldnt be able to send code over to your rio anyways.
try reading up on it some more::rtm:: ::rtm:: the screensteps might have something to do with it.
Thanks for the replies guys!
I’ll try those commands tomorrow when I’m at school again.
For clarification, the robot works. Everything is fine. But after I disconnect from the wifi bridge, I can reconnect but can no longer establish communications with the roborio. This also happens if I were to turn the robot off. The only way to re-establish communications is to “load firmware” and then “configure” through the radio configuration tool.
I have also tried using last year’s OM5P-AN and this issue still occurs.
Do the ping tests both when it is all working, and then again after it all stops working.
I’m suspecting that the DNS names are changing between when the radio first starts getting used after being configured, and when it reissues them again after a disconnect/reconnect.
Add this too-
from a command prompt on the PC type *ipconfig /all *and look for what’s listed close to the top for DNS Suffix
We have seen a similar issue at different points of power cycles. The WiFi will connect on the Driver Station but no communication to the RIO. We are usually able to get operation again by cycling power on just the radio. If this continues this way, beginning of matches is going to be painful.
+1 and also Windows Defender if you’re on Windows 10. Some of our computers block the mDNS software and/or the DriverStation jar file, we had to make firewall exceptions for them.
We are experiencing a very similar issue, where we have to reboot the PC after every robot power cycle or we won’t have connection to the RoboRIO through the radio. Can you try the following?
Get the PC and robot into that problematic state where you can connect to the radio but not the RoboRIO.
Power cycle the robot (RoboRIO and radio). After power cycling the robot, based on my understanding of your descriptions of the problem, you should still be unable to connect to the robot through the radio.
Restart the PC.
Connect to the radio.
See if you have connection now, on the driver station or through ping. If you are able to successfully connect here, you may be experiencing the same problem as us, Team 2930.
Now power cycle the robot again.
Connect to to the radio again.
Check again for connection to the RoboRIO. If you once again do not have connection here, after having connection the first time after the PC reboot (step 5), you definitely have the same problem as Team 2930.
We have been trying to debug this problem for the last couple weeks. It would be great to know that there are other teams also running into this problem. This PC is the same PC we used for code development for the past two years and we have not had this problem until this year. However, this is the first year we are using Java for development.
So far, it seems to be an mDNS issue. The RoboRIO seems to get its roborio-2930-frc.local address from the radio correctly the first time after a PC reboot, but not any time thereafter. All firewall settings seem to be correct, and we have tried explicitly adding the mDNS responder and UDP port 5353 as exceptions to the firewall. Our next step for debugging is probably going to be disabling the Java dashboard.
raytsou, I hope you are able to solve your problem! If you are successful, please tell us how you did it. In the mean time, if your problem is the same as ours, you can work around it by restarting the PC.
And of course, thanks to everyone else who has been chiming in to help!
Hey guys,
So today, I first tried to connect to the robot with the laptop that we were using the previous year. Surprisingly, the old laptop was able to connect and reconnect to the robot just fine. After that, I disconnected the old laptop and tried my own laptop. Long story short, I couldn’t get it to connect at all. For now, my team has decided to just work around the issue by using the old laptop.
I suspect it may have to do with the settings in the laptop. The biggest difference between the laptops is that my laptop is running Windows 10 Version 1607, while the old laptop was running Version 1511. I don’t know if that’s the issue, but I suspect it may play a part. @JABot67, may I ask what version of windows you are running and if you have updated your laptop at any point in the last year?