Error after updating to latest roboRIO version

Hello, after updating to the latest roboRIO and VScode versions, we cannot connect to the roboRIO. We’ve tried multiple different codes, computers, and roboRIO’s but they all yield the same error. I’ve pasted the error below.

Discovering Target roborio
admin @ 10.68.5.2: Resolved but not connected.
Reason: RuntimeException
com.jcraft.jsch.JSchException: socket is not established
admin @ 172.22.11.2: Resolved but not connected.
Reason: RuntimeException
com.jcraft.jsch.JSchException: socket is not established
admin @ roborio-6805-FRC.local: Failed resolution.
Reason: TimeoutException
Discovery timed out.
admin @ roborio-6805-FRC: Failed resolution.
Reason: RuntimeException
Unknown Host
admin @ roborio-6805-FRC.lan: Failed resolution.
Reason: RuntimeException
Unknown Host
admin @ roborio-6805-FRC.frc-field.local: Failed resolution.
Reason: RuntimeException
Unknown Host
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.

  • What went wrong:
    Execution failed for task ‘:discoverroborio’.

A failure occurred while executing edu.wpi.first.deployutils.deploy.target.discovery.TargetDiscoveryWorker
Target roborio could not be found at any location! See above for more details.

Thank you, and if you need any more information please ask.

Did you reset your team number on the roboRIO after updating it (probably not an issue with multiple roboRIOs)?
What does the Driver Station Diagnostic tab show?
How are you connecting the PC to the roboRIO?

Thank you, currently we’re unable to connect to the robot through the FRC driver station. We’re getting the error -44019 FRC: The mDNS service is to slow to respond. Check firewall settings. We’ve connected with both through wifi and direct connection through the roboRIO. On the driver station, we can connect to the Radio so I don’t think that’s the problem. Thank you.

So concentrate on the roboRIO, since it can’t be seen.

Are these roboRIO 1.0’s or a 2.0?
If this happens on several roboRIOs with several PCs, then make sure you swap cables, in case that’s the issue.
If you haven’t already try the USB A-B cable directly to the roboRIO.

Try running the roboRIO Imaging Tool again to see if it can detect the roboRIO.
That’ll bypass things like the DNS.

Here are the WPIdocs for network troubleshooting:

I had a similar issue for a computer. If you have a certain VPN enabled/installed, it could be blocking it.

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