Error 7 When Adding a Custom Device to Veristand

Issue Details

When I try to add a custom device to my system definition file, I get the following error message:

Error 7 occurred at Open VI Reference in Custom Devices Storage.lvlib:Initialize New Custom Device.vi

Possible reason(s):

LabVIEW:  File not found. The file might have been moved or deleted, or the file path might be incorrectly formatted for the operating system. For example, use \ as path separators on Windows, : on Mac OS X, and / on Linux. Verify that the path is correct using the command prompt or file explorer.

VI Path: C:\Users\Public\Documents\National Instruments\NI VeriStand 20XX\Custom Devices\Error_Seven\Error_Seven Configuration.llb\Error_Seven Initialization VI.vi

...

How can I fix this issue?

Solution

When a custom device is added to the system definition file, the initialization VI is called.  This VI is dynamically loaded by VeriStand.  If there is an inconsistency between the XML and the custom device project, VeriStand will not find the VI.  You can check these possible issues when you receive Error 7:

• Check that your initialization VI name is Initialization VI.vi. By default, the name of your VI should be Custom Device Name Initialization VI.vi.
• Make sure your build specification configured correctly.  The VI should be Always Included in the Source Files category. In the Destinations category, the destination of the initialization VI should be Custom Device Name Configuration LLB.llb.
• Ensure that the path in the XML matches the actual path of the Initialization VI after the LLB is built.
• Verify that the custom device is in the proper directory. The default custom device directory is: C:\Users\Public\Documents\National Instruments\NI VeriStand 20XX\Custom Devices

• If you get a CD as archived file (e.g. Errer_Seven.zip), check that the LLB is in the direct subfolder, e.g. in ...\Custom Devices\Error_Seven\... , not in ...\Custom Devices\Error_Seven\Error_Seven\... .

If the problem persists after correcting the above items, please contact NI support to continue troubleshooting.