I’m trying to deploy my code to the robot using VS code but whenever I deploy it can’t find the RoboRio. I am connected to the robot as if I check on the FRC driver station. Does someone know a solution to this?
We’ll need more information to be sure of the solution, but please:
- verify your firewall is disabled (or properly configured, but disabling is a good temporary fix is that’s truly the cause), including any anti-malware software that may have similar functionality.
- Make sure you’re only connected to a single network (meaning wireless is disabled if you’re connected via ethernet.
- make sure everything is updated to the latest (roborio image is 2019, driver station/frc update suite/etc is 2019, wpilib extension in vscode is 2019, etc.
I could go on, but its a long list, so let me know once you’ve checked the above and we’ll go from there.
i updated everything and turned off my firewall and it still says ‘Missing target’
Are you sure your team number is correct in .wpilib/wpilib_preferences.json?
I’m not sure how to i get there?
In your VSCode project there should be a folder called .wpilib with that .json file in it. It should be set in there. Also, can you upload the exact error you’re getting?
I looked at the preferences and the team number is correct here is the error
BUILD FAILED in 4s
4 actionable tasks: 2 executed, 2 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
That really doesn’t give us enough info to help debug. Can you show us the part above this in the log? Namely where it’s looking for the different targets? You can use triple-backticks to block-quote.
it this what youre looking for?
Driver Station reported IP: 10.20.13.2
Task :discoverRoborio
Discovering Target roborio
admin @ 10.20.13.2: Connected.
Reason: InvalidImageException
RoboRIO Image invalid! RoboRIO: 2018_v16, allowed: [2019_v12]
admin @ null: Connected.
Reason: InvalidImageException
RoboRIO Image invalid! RoboRIO: 2018_v16, allowed: [2019_v12]
1 other action(s) resolved but not connected.
4 other action(s) failed resolution.
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
You need to reimage your RoboRIO for 2019. It still has the 2018 image. You may want to upgrade to WPILib 2019.2.1 as well, so you can use the latest 2019_v13 image (which fixes an issue with SPI gyros).
i re-immaged my roborio and now im getting this error
Discovering Target roborio
admin @ 10.20.13.2: Connected.
Reason: InvalidImageException
RoboRIO Image invalid! RoboRIO: 2019_v13, allowed: [2019_v12]
admin @ null: Connected.
Reason: InvalidImageException
RoboRIO Image invalid! RoboRIO: 2019_v13, allowed: [2019_v12]
1 other action(s) resolved but not connected.
4 other action(s) failed resolution.
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 4s
4 actionable tasks: 2 executed, 2 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
You need to update WPILib to 2019.2.1 (and update your project to use it) for the v13 image to work.
i updated that and now im getting a diffrent error
Task :discoverRoborio
Discovering Target roborio
admin @ 10.20.13.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-2013-FRC.local: Failed resolution.
Reason: UnknownHostException
No such host is known (roborio-2013-FRC.local)
admin @ roborio-2013-FRC: Failed resolution.
Reason: UnknownHostException
Not enough memory resources are available to process this command (roborio-2013-FRC)
admin @ roborio-2013-FRC.lan: Failed resolution.
Reason: UnknownHostException
No such host is known (roborio-2013-FRC.lan)
admin @ roborio-2013-FRC.frc-field.local: Failed resolution.
Reason: UnknownHostException
No such host is known (roborio-2013-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 4s
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
It looks like your robot isn’t connected to the computer, since the attempt through basically every possible way to connect failed. Does the DS see the RoboRIO? Can you ping it?
We pinged the rio and it was timing out and we were able to narrow it down to a faulty ethernet cord everything is working great now! Thanks for your help.
Our team also having this issue:
No such host is known (roborio-368-FRC.local)
But only deploying it wirelessly, if it’s connected through ethernet we could deploy no problem.
We made sure the team number is correct in the json file, the RoboRio is update to date, the WPILib is also up to date. Not sure what else to check.
@robo808 what diagnostics have you done from the programming station? Once it’s on wireless, can you ping the gateway address (the robot radio), or the roborio address 10.TE.AM.2? Tools in WIndows like ipconfig and ping will be your friend here.
1 Like
We are having the same issue. We’ve re imaged the roborio many times, and our ethernet and usb cords are both working. Can someone help?
Only through the radio? The above responses give a lot of the debugging steps. Seeing the complete error message vscode is outputting would help.