Task :discoverRoborio FAILED

Technical Programming
#1

I am unable to deploy code to the roborio and I can’t figure out what even changed. I am getting the same error that usually shows up when you forget to connect to the robot, but I am certainly connected to the robot and I have also tried to power cycle the robot. Does anyone have any idea what I may have changed to cause this? Here’s my error:

Task :discoverRoborio
Discovering Target roborio
admin @ 10.3.86.2: Resolved but not connected.
Reason: JSchException
socket is not established
admin @ 172.22.11.2: Resolved but not connected.
Reason: JSchException
socket is not established
admin @ roborio-386-FRC.local: Failed resolution.
Reason: TimeoutException
Discovery timed out.
admin @ roborio-386-FRC: Failed resolution.
Reason: UnknownHostException
Not enough memory resources are available to process this command (roborio-386-FRC)
admin @ roborio-386-FRC.lan: Failed resolution.
Reason: UnknownHostException
No such host is known (roborio-386-FRC.lan)
admin @ roborio-386-FRC.frc-field.local: Failed resolution.
Reason: UnknownHostException
No such host is known (roborio-386-FRC.frc-field.local)
1 other action(s) not started.
Run with --info for more details

Task :discoverRoborio FAILED

FAILURE: Build failed with an exception.

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

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

  • Try:
    Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

  • Get more help at https://help.gradle.org

BUILD FAILED in 18s
6 actionable tasks: 2 executed, 4 up-to-date
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.
The terminal process terminated with exit code: 1

#2

How are you trying to connect? Via Ethernet or USB?
If Ethernet does not work, try USB. If USB does work, then there is an issue with your IP settings on your host machine, or on the roborio. Confirm those.

If neither work, something is probably preventing your roborio from booting properly. Check the wiring and status lights.

#3

I have been connecting over the radio on the robot, but connecting through USB yields the same error message

#4

Well that’s strange. So I updated WPILIB in VS Code and now can deploy code, but only through the USB cable. I can’t, however, connect to the robot through driver station anymore, even though I could prior to the update

#5

What is your RoboRIO’s image version? What driverstation version are you using?

It sounds like your setup is out of date.

#6

Roborio version: FRC_roboRIO_2019_v14

Driverstation Version is not showing up in the Versions & Info section of driverstation, nothing is showing up there

#7

What is the GradleRIO version in your gradle config file?

#8

Where do I find the gradle config file with that version?

#9

build.gradle should have some version information at the top.

#10

Alright, the gradleRIO version is “2019.4.1”

#11

Are you able to ping the rio?

#12

I am unable to ping roboRIO-386-FRC.local both on the radio, using the USB cable and when using both

#13

On Driver Station when I am connected to the robot’s radio, the Robot Radio light in the Communications tab lights up, even though the main Communications light remains red

#14

Can you try pinging 10.3.86.2 instead to rule out mDNS issues? (Or 172.22.11.2 when only connected over USB)

#15

I am unable to ping 10.3.86.2, but I am able to ping 172.22.11.2

#16

Unplug from usb and try 10.3.86.2 again. Also try pinging 10.3.86.1. Make sure you are connected to the radio through either wire or wireless.

#17

Using wireless radio connection, 10.3.86.2 is unable to ping. However, 10.3.86.1 is able to ping this way

#18

All right, that matches what you were seeing in the DS earlier, which is good. At this point, I would try moving the ethernet cable connecting the radio and rio to the other port on the radio, or replacing the ethernet cable if that doesn’t work.

Also, it may be a good idea to confirm that your rio is configured for the correct team number, although a wpilib upgrade shouldn’t have changed that. To check, connect over usb and open the roborio configuration utility.

#19

Thank You !! Turns out what I did was I deleted or forgot to re-enter the team number when I re-imaged the RoboRio, so it was unable to connect to DS even though I was connected to the radio and rio properly

2 Likes
#20

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