RoboRio Not connecting

When deploying our code, which has previously worked, it is failing and returns:

Discovering Target roborio
admin @ roborio-5806-FRC.lan: Failed resolution.
Reason: RuntimeException
Unknown Host
admin @ roborio-5806-FRC.local: Failed resolution.
Reason: TimeoutException
Discovery timed out.
admin @ roborio-5806-FRC.frc-field.local: Failed resolution.
Reason: RuntimeException
Unknown Host
admin @ roborio-5806-FRC: Failed resolution.
Reason: RuntimeException
Unknown Host
admin @ 10.58.6.2: Resolved but not connected.
Reason: RuntimeException
com.jcraft.jsch.JSchException: timeout: socket is not established
admin @ 172.22.11.2: Resolved but not connected.
Reason: RuntimeException
com.jcraft.jsch.JSchException: timeout: socket is not established
1 other action(s) not started.
Run with --info for more details

Task :discoverroborio FAILED
Missing Target!
=============================================
Are you connected to the robot, and is it on?
=============================================
GradleRIO detected this build failed due to not being able to find “roborio”!
Scroll up in this error log for more information.

FAILURE: Build failed with an exception.

When I try to ping the rio it returns:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Also, the rio is the latest image and the updated as well. Does anyone have any ideas about how to fix this?

Is your team number still set in the Driver Station?
What connectivity does the Driver Station Status tab show?

Have you tried this while connected via USB?
Ethernet PC to radio?
WiFi?

I deployed using USB and have tried to ping the RoboRio again but all packets are lost. Additionally, it returned the error in the Driver Station that

FRC: The mDNS service is too slow to respond. Check firewall settings.

All Windows defender firewalls are disabled.
In the Driver Station, Communications is connected to the robot radio, wifi, usb, and firewal, but not the robot when we are connected by USB and wifi.

So it sounds like just the rio connection is failing for some reason.

There a few things to check, but start with the simplest connection pc-USB-rio.
Then start the roboRIO Imaging Tool just to see if it finds the rio.
After a moment of searching under the roboRIO Targets window it should display “roboRIO-5806-FRC”

That’ll tell you that the team number is setup correctly on the rio and that the network connection is good.

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.