Error 7 VeriStand Deployment Fails Because of Missing Instrument Addon Custom Device Files

Updated Jan 10, 2023

Reported In

Software

  • VeriStand

Issue Details

I have a VeriStand Project on an old PC that uses the Instrument Addon custom device but deploys and works fine.
When I install the same version of VeriStand and the Instrument Addon to a new computer and copy over my existing project, the project fails to deploy and the error message points to missing files related to the Instrument Addon custom device. How do I fix this?

Solution

The names of some of the components of the Instrument Addon have changed between versions. 
For example, the "Engine.llb" has been renamed to "Engine Windows.llb".

To resolve this issue we have a few options:
  • Install an older version of the Instrument Addon custom device - If you use the same versions as on your previous PC, you can guarantee the same version is used. This will ensure there are no file hierarchy or file name mismatches. You can zip up the "Insturment AddoInstrumentat C:\Users\Public\Documents\National Instruments\NI VeriStand 20XX\Custom Devices Where 20xx represents your version of VeriStand
  • Otherwise, in your existing project you can export the configuration of the Instrument Addon custom device and then remove the custom device instance. On the new PC add a new instance of the custom device and import the configuration file. This has updated the project from using the old version of the Instrument Addon custom device and is now using the newer version with a file structure that matches what is installed.
    • Make sure any mappings are also exported/imported or manually readded as well.