Custom Device Page VI Not Executable in VeriStand System Explorer

Issue Details

I am migrating an old custom device to a recent version of VeriStand and LabVIEW. After compiling the custom device successfully, I am observing that the VeriStand System Explorer shows the following Page Error message when selecting a page from the custom device:

The following Custom Device page VI is not executable. The VI was not found at the expected location, or it is missing dependencies required to run. Please contact the Custom Device vendor for more information on this problem.

 

Broken Page: C:\Users\Public\Documents\National Instruments\Nl VeriStand 2023\Custom Devices\Custom Device\Custom Device Configuration.llb\Main Page.vi.

I have confirmed that the VI mentioned in the error exists at the path location referred and that it doesn’t show any errors or conflicts when opening in LabVIEW. How can I fix this problem?

Solution

It is possible that some of the dependency VIs used in the custom device are also utilized and built-in with the VeriStand engine. Therefore, when VeriStand loads the custom device during runtime, it creates a broken VI error due to the same dependency file name conflict.

To resolve this issue, follow these steps:

• Open the Custom Device Configuration from the Custom Device LabVIEW project.
• Navigate to the Source File Settings tab.
• Set a prefix with the custom device name for all dependency items to make them unique names.
• Rebuild the Custom Device Configuration.

Additional Information

The solution proposed can also solve an issue with custom devices that show an "RT Driver VI no executable" error during deployment by adding a prefix to the dependencies used by the Custom Device Engine.