I am calling a class from a VI using the "Get LV Class Default Value By Name.vi" and the "To More Specific Class". The code is supposed to select the correct child class for a given class. The DSSP.lvclass represents the Device Specific Software Plugin from the Hardware Application Layer model. The Child class is called InstX and has 2 versions. The InstX Version Read.vi reports back with a message saying what version it is (this is done to test the mechanics of the class selection). It all works very well. That is until I create an executable application to deploy to a runtime machine. Then I get this message. Other details. I get this message in the labview environment as well when I try to run the VI without having the project open where the DSSP classes are. Any idea why labview cant or wont load the classes?

I had the same problem and fixed it a little bit different. While placing the classes on the block diagram is working perfectly fine you always have to remember that you have to do this for ever new class you add to your project. I added the whole classes folder to the build spec with the "always include" option. Then load all the classes in this folder by path ("Get LV Class Default Value.vi"). Now I can use the "Get LV Class Default Value By Name.vi" everywhere I need it without bothering about adding an object of it to the block diagram first.

Add something like this to your factory VI, and the builder will include the child classes automatically. Spoiler (Highlight to read) Edit: I've never personally used "Get LV Class Default Value By Name.vi". AFAIK, the typical factory pattern uses "Get LV Class Default Value.vi" instead, which takes in a path to the class not its name. Probably why it doesn't run in dev environment unless the classes are in memory. Not sure if it has something to do with the runtime troubles. Here's my full factory VI. Spoiler (Highlight to read)

LabVIEW

Executable can't load class

Solved!

Note: you don't need the hard coded false case structure for cube dropping. Class constants by themselves don't result in any executable code.

~ Helping pave the path to long-term living and thriving in space. ~

Message 11 of 11

(141 Views)

LabVIEW

Executable can't load class

Re: Executable can't load class