Jump to content
Corks

Script New LabVIEW Class

Recommended Posts

Hello LAVA,

First time poster here, so I'll do my best with background. This situation also happens to be my first exploration of scripting LabVIEW Classes. I am starting with my simplest use case, and scaling as I see some success. I am simply trying to add an existing VI to a newly created class, and facing a strange message when opening the class that I have created.

I have attached a snapshot of my code, BD.png

post-28063-0-51104600-1351553228_thumb.p

The code runs without error, and creates a class in the specified directory with the correct name. What's strange is that when I open the newly created class to view its contents I see the following message:

post-28063-0-89248100-1351553313.png

I have tried this same set of events using the LAVA host LVClass API, and face the same error message when opening the class. When I use property nodes to investigate the class members, the VI I have added is listed as a member. I went so far as compare the raw "XML" of a LabVIEW class I created manually in the project explorer to my scripted class, and the property configuration for the class appears identical. For this initial test, I am ensuring that the file I am adding is in the same directory as the class I am creating. The error dialog above occurs after a file search window appears, or I elect to ignore 'missing' items.

I am posting here to see if anyone has experienced this behavior, or perhaps my inexperience in this area has lead me to overlook a fundamental part of adding items to a class. I appreciate your time, am happy to provide any additional information, and look forward to your responses.

System Specs:

LabVIEW 2012 32-bit, Windows 7 64-bit

Share this post


Link to post
Share on other sites

I've had to use the method och storing the lvclass content in a string constant on the block diagram and write it to disk and then use the LvClass.Open invoke node.

Share this post


Link to post
Share on other sites

Thank you all for the replies. Ensuring the VI get saved corrected the issue. Using the LVClass API, I simply grab the reference to all files added to the newly created class, and save them before the script completes.

Much appreciated!

  • Like 1

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.