This content is not available in your preferred language.

The content is shown in another available language. Your browser may include features that can help translate the text.

Error 7 When Adding a Custom Device to Veristand

Updated May 12, 2023

Reported In

Software

  • VeriStand

Issue Details

I have successfully built an NI VeriStand Custom Device that I created from the Custom Device Template Tool. When I try to add it 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 2011\Custom Devices\Error_Seven\Error_Seven Configuration.llb\Error_Seven Initialization VI.vi

Built Application or Shared Library (DLL): Make sure all dynamically loaded VIs were properly included in the build specification for the application or shared library.

LabVIEW Real-Time: VIs built into executables cannot be accessed through VI Server calls. Use Source Distributions to dynamically call VIs on Real-Time targets. 

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:
  • Did you rename your initialization VI? By default, the name of your VI should be Custom Device Name Initialization VI.vi.
  • Is the 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.
  • Does the XML match the project settings? Ensure that the path in the XML matches the actual path of the Initialization VI after the LLB is built.
  • Is the custom device 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.

 

Related Links

Other Support Options

Ask the NI Community

Collaborate with other users in our discussion forums



Request Support from an Engineer

A valid service agreement or active software subscription may be required, and support options vary by country.