2022 FRC Build and Deployment Issue

[!!1sustaitaj]

I am trying to build my program in order to deploy, and it will not let me. When I click "Build All" it then gives me a "Build Error" under it it states; "This build specification uses VIs from Vision Acquisition Software which is currently in evaluation mode. During evaluation, LabVIEW is unable to disconnect type definitions and remove unused polymorphic VI instances." I then click view support page and it leads me to "LabVIEW Application Builder Module" I downloaded it and I tried to activate it with my serial number and it wont activate. Does the 1 year FRC LabVIEW subscription not cover this, if not, what do I do? I am stuck and need help. 

[oscarfonseca]

I noticed this as well with one of the teams during an event where I was a CSA. This is what I did. I hope it works for you as well:

1. Activate using the license provided by NI to your team account: Find My FRC Team's NI Serial Number to Activate Software 
   Not everything in the license manager will be activated, and that's okay.
2. Reboot the computer
3. If the issue still shows up, unselect disconnect type definitions and remove unused polymorphic VI instances from the Build Specification properties under "Additional Exclusions".

If you still have the problem after these suggestions, please share with us the items successfully activated by the license manager, and those having still evaluation periods. This is what I have in my machine:

[!!1sustaitaj]

Thank you for your response Oscar! 

I did the steps and it did let me build the program. Now I am having an error where it will not let me deploy. I do not have robo code. The status light blinked twice and searched what the problem was and it stated "Software error, reimage roboRIO" I reimaged it and it still will not work. It also askes me after it reimages it to place the file somewghere but it will not let me. It states "IV file not found, check the file name and try again." 

[oscarfonseca]

I'm glad you're able to build now!

Interesting. I don't recall having that problem. Can you walk me through the steps you're following, including screenshots or copy-paste of the errors you see? It's easier to understand where the problem may be.

My recommendation is the following, since you are able to build now:

1. Connect the roboRIO to your computer using a USB cable and the roboRIO's USB port
2. If you have a roboRIO 1.0, use the imaging tool to reimage it. If you have a roboRIO 2.0 use the SD card reimaging procedure.
3. Once the roboRIO is reimaged (and has been setup with the correct team number, in case of the roboRIO 2.0), ensure you can communicate with it through the Driver Station (the robot code LED will be red, and that's okay and expected). If you don't see the roboRIO, then follow: Unable to Connect to roboRIO in Driver Station, Imaging Tool or LabVIEW 
4. Once we can see the roboRIO in the driver station, open LabVIEW, build your project, and try to deploy the build specification using "Run as Startup". If it can't find the roboRIO, then follow: LabVIEW for FRC Shows Connection Failed to My roboRIO 

Cheers,

[!!1sustaitaj]

I have tired to reimage the roboRIO 1.0 and 2.0

This is what I see when the reimage fails to work. I have ran it as an administrator and have put the roboRIO into SafeMode as well. What could this possibly be?

[oscarfonseca]

I've seen that happen with the roboRIO 1.0 when the connection to the computer is too slow, or when teams try to image through the radio (I assume you're connecting through USB, so this shouldn't be it). We can try the steps here: FRC roboRIO Imaging or Firmware Update Failing 

For the roboRIO 2.0 you shouldn't need to use the imaging tool to image the device, since you can do it to the SD card directly, then just use the imaging tool to set the team number using the "Edit Startup Settings" option.

If you still have issues with the imaging process in either device, let us know if the error you get is still the same and we can help you further troubleshoot it.

Cheers,