Can't download to roboRio after 2022 update

Technical NI LabVIEW
1

Code ran fine for 2021. Updated PC to 2022 LabView. Updated roboRio to 2022
Now any code won’t download to roboRio. It gets so far and then says it can’t connect to target.
This happens 19 times out of 20.
Wireless off
Tried 3 USB cables.
Updated roboRio firmware from version 6 to 8
Tried a second roboRio.
Made sure all anti-malware was turned off on the PC.

Before 2022 the same PC with the same roboRio loaded just fine…

I am out of suggestions. Any help appreciated

2

When did you update the firmware, before or after you were seeing issues?

3

We also encountered this issue.

1 Like
4

We also encountered this issue. We reformatted the Rio and reinstalled the third party libraries and that fixed it.

3 Likes
5

We also had this issue, and resolved it in the same manner.

1 Like
6

Thanks for your reply. We did the firmware first. Then the 2022 stuff. That is when the problems started. Then we fell back to the previous firmware then loaded the 2022 stuff.

All was well before the upgrades. Not sure how to procede

7

Same thing keeps happening to us even after updating firmware, reinstalling libraries, and restarting.

Does anyone know the root cause of this issue?

8

I might be giving you a bit of a red herring but have you tried using SSH to access the RoboRio to find the problem. I have ran into a few errors where it decided to change its IP address to something random.
I know my suggestion only helps for wireless issues but if you are totally lost I guess it’s worth a shot.

9

Thanks to all who replied. I changed the target address from the DNS name to 172.22.11.2 and it fixed everything. I should have known.

Did ssh in and look around. All seemed well. Not sure why DNS was so flaky. But that is for another post.

2 Likes
10

@bplodiguy How did you go about changing the DNS name to 172.22.11.2?

11

Sorry to be so late replying.
Right click on Target. Choose Properties.
Leave the name as Target but change the address to 172.22.11.2 instead of
the DNS name. That fixed it for us.

12

If you do this, make sure you always/only connect via the USB. Once you do this, you can no longer connect via ethernet.

13

Got it. Thanks.

14

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