We have communications with the driver station (the indicator says we have coms and we can see info such as current battery voltage) yet we can not deploy code / connect to the roboRio through LabView.
Error: “Failed to connect to the target”.
Conflict resolution: “Unable to resolve from current dialog”
We’ve attempted to re-image the roboRio multiple times, boot it in safe mode, and reconfigure our router.
Windows firewall is off and we’ve attempted to connect through multiple computers, and to directly connect with an ethernet cord.
Pinging the roboRio’s ip works.
This problem started after we upgraded our software to the 2018 version.
What is the roborio firmware version that is showing on the driver station?
If you deploy code to the roborio do you get errors? If you get an error can you post it?
Did you set up your team number in the robot project file? What name shows in the project file setup?
Can you connect to the robot in the driver station?
I know our team has observed a similar issue this last release of certain computers sometimes just not connecting to the RIO, while others do. We don’t have a solution to this, I suggest just trying on other computers.
Try these steps to see if they help deploy the code.
- Use Internet Explorer to browse to the roboRIO webdash at http://roboRIO-2230-FRC.local
- Check the box for “Disable RT Startup App” & Save
- Restart the roboRIO
- Try using “Run as startup” to deploy your project
- Uncheck the “Disable RT Startup App” & Save (and restart the roboRIO)
Are you using TalonSRX’s through CAN?
Given you have the comms light in the driver station, it appears as if you’ve got a way to talk to the roboRIO.
The error you’re showing suggests there’s a timeout when the project tries to talk to the roboRIO. I’d suggest posting a screenshot of the project. I suspect the IP/DNS name of the roboRIO has changed in your project. It’s trying to reach something that doesn’t exist and is timing out.
I would wager you have a problem with mDNS. It can be finicky on different computers. Try going all static IP address. That usually solves most of the wonky coms issues like this. Even if it doesn’t solve it, at least you’ve removed the mDNS as a potential cause.
I had to do this, though I didn’t spend much time troubleshooting the mDNS. I’d never had mDNS issues on this particular computer earlier, and in fact it was working up until I configured and flashed the radio for 2018.
Flashing the radio has nothing to do with the mDNS responder that LabVIEW installs. Something else must have been happened.