02-18-2023 01:37 PM
Hello,
Last week, we tried to update our Labview to the 2023 version, following this guide. We uninstalled LABVIEW 2022 as recommended, and proceeded to download LABVIEW 2023 for FRC from the National Instruments website here. We proceeded to install the software and entered the serial number provided to us when prompted.
Our lead programmer couldn’t find the program to open it and chose to install it again. After this, we found that Labview wasn’t working. We could now open Labview and open our code, but several Vis were missing. We discovered that the blocks we needed to control our robot (such as the motor controller blocks and the PWM blocks) were missing. We attempted to reinstall and update Labview again, several times, trying different things, like updating NIPM and using the offline installer. Even though we could open and use Labview, it simply didn’t have any FRC components installed. The last time I attempted to do the install, I compared the pictures from the instructions to what the install was saying and noticed the installer was not including the FRC Labview addon, and did not provide an option to do so, which I think is the root of the problem.
We contacted National Instruments to attempt to solve the issue, but their customer support informed us that they do not offer support for FRC, and told us the Serial number we used to activate Labview had already expired its license.
Solved! Go to Solution.
02-18-2023 05:10 PM
This can happen if LabVIEW for FRC is installed after the FRC Game Tools. I recommend running the FRC Game Tools installer again to ensure your LabVIEW installation is configured with the FRC functions.
Let us know your results.
02-22-2023 01:12 PM
We've done as you suggested and re-installed the FRC Game tools. Now we can view and use FRC blocks, but when we try to deploy code to the robot, we get an error message:
"Deploying <VI NAME>, <VI NAME> deployed with errors on the target and was closed. Deployment completed with errors"
where the exact VI mentioned changes from time to time, and sometimes it will give an additional error message.
We attempted to solve the issue by forcing the VI to recompile and by trying to clear Labview's cache, but both were unsuccessful.
02-22-2023 05:37 PM
I have seen that behavior happen when there's a slow connection between the roboRIO and the computer (for example, when the team attempts to run code through wireless connections). Is this happening over USB, Ethernet, or WiFi? Do you see it in multiple computers? Does it deploy properly after you reimage the roboRIO?
Cheers,
02-22-2023 08:17 PM
We’ve seen it in both of our laptops. We were using ethernet before, but all of our last testing was with USB. When we can access the robot again we will try to reimage the roborio, but we have done testing after trying to update and reformat the firmware.
02-24-2023 02:14 PM
Problem solved: Code deployed correctly wirelessly and works on new cords. We are now replacing our old cords.