So something weird is happening… On our teams programming laptop, I can connect to the robot perfectly and drive normally, however on my personal laptop, I used to be able to connect to the robot on my personal laptop, but for some reason, it just doesn’t connect anymore.
I’ve tried:
Disabling the firewall settings.
Reinstalling the frc game tools
Connecting directly to the roborio via Ethernet.
None of those worked. Has anyone encountered this?
Do the two laptops have a different windows update or version? Something along those lines is what I think it might be.
Have you tried direct connection with a USB cable?
Can you take a snapshot of the Driver Station with the Diagnostics Tab open?
the only thing that was on the diagnostics tab when I checked was the enet and the robot radio. if it helps, I also can’t deploy code to the roborio.
No the two laptops are both running windows 10 and I believe they are up to date.
Check the Wireless/Ethernet adapter properties (depending on how you are connecting) to see if it all looks proper.
For instance, they sometimes get stuck with a static but blank IP address depending on what else you have been doing, or it could have a static IP address that isn’t compatible with your roboRIO.
Search for “Network Connections”
Right click on Ethernet or Wi-Fi and choose Properties
Click on the IPv4 line and choose Properties (or just double-click).
It should have “Obtain an IP address automatically” selected.
Since you can see the robot radio I assume your team number is set correctly in the Driver Station.
Ill try that! Thanks! What would have caused that to stop working with the driver station? Because before today I was able to connect to the robot just fine. Is it possible I did something with my computer that is stopping it from connecting?
There are some FRC utilities, e.g., the radio config tool, that set temporary static IP addresses on the PC and they can leave the adapter in a funny state if they don’t finish properly.
Doesn’t mean that’s your issue, but we see frequently see that on the playing field.
I’ve been messing around with the roborio imaging tool with our rio 2, could that have something to do with it?
Definitely, could have something to do with it.
Just bringing up the Imaging Tool should display how the RIO2 is setup: firmware/image/team number, so you can use it to check that the RIO 2 is setup correctly.
With the RIO 2 did you use the Imaging Tool to set the team number on the Rio (using Edit Startup Settings)?
To actually image the Rio 2 we typically use balenaEtcher or similar tools rather than the Imaging Tool.
I never got that far. I tried to image it with etcher as well but the rio 2 still doesn’t actually work. It’s when I try to connect to another rio 1 that I’m having this problem.
Yes my team number is correct but something interesting happened this morning. I tried again to connect to the rio and this time, this is what I could see:
Does this also have to do with the “Obtain an IP address automatically” setting? I made sure that it was set to this option in the ipv4 settings.
Your Public firewall is still on I see.
Probably want to turn that off to avoid blocking network traffic.
I assume your radio shows up in the PC wireless connection list?
That fixed it! Thanks so much!
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
