Error code 7 source: Get LV Class Default Value.vi when running exe using Adlink LabVIEW SubVIs inside a LabVIEW module

[Kim66]

We have a DQMH module (LV2020) calling Adlink LabVIEW subVIs (to operate an Adlink PCI-9111HR DAQ board) which runs fine in the development environment. The issue we have is that the executable version produces the following error:

         Error code 7 source: Get LV Class Default Value.vi  

The Get LV Class Default Value.vi requires a path as an input that is provided by its caller, the Adlink Dispatch.vi. The class that is needed for this application is the PCI-9111HR.lvclass, which is able to be located at run-time when operating in the development environment, but somehow fails to be located for use by the executable.

We've run the code in development mode and moved the three Adlink classes that are in memory up into the project and then added them to the build spec. Unfortunately this did not work, producing a different error along the lines of "some vi's have no block diagrams...."

We'd appreciate any suggestions or solutions.

[wiebe@CARYA]

---

@Kim66 wrote:

We've run the code in development mode and moved the three Adlink classes that are in memory up into the project and then added them to the build spec.

---

How did you add them to the build spec?

Simply adding classes to 'always include' is, in my experience, not enough.

I'd simply add the VI that's loaded by it's path in a diagram that is in the exe for sure. The trick is to make sure it's not being removed by dead code removal. Putting the VI in a true case with a false constant will remove the VI, so wire a hidden constant to it.

[Kim66 · Accepted solution]

Problem solved through following instructions from Adlink (https://cdn.adlinktech.com/webupd/en/Upload/faq/FAQ_CS_DAQLVIEWPlus_SW_Win_How_to_Build_an_Applicati...) which involved including all the common Adlink classes and the class for the particular Adlink DAQ board into the project and then including them in the build spec under Source Files.

Note: the built executable must be ran from the same folder as all the built files which contains the .exe, .aliaises, .ini, and the files in the data folder (dlls).