Jump to content
Sign in to follow this  
Mirash

Passing LV Class to TestStand as a parameter

Recommended Posts

Hi all,

I came across developing some custom step types in TestStand with LabVIEW code modules. My LabVIEW code module is architectured with LVOOP concept. But now I wonder how can I pass an LV Class object to TestStand for further use in other step types.

Currently I managed to store it in a LV Global and use it later. But are there any other way?

Regards,

Mirash

Share this post


Link to post
Share on other sites

Hi there Mirash

Firstly what version of TestStand are you working with ?

From what I remember ,there are a few issues with dynamic dispatch not working as it should from TestStand. You have to provide a wrapper around the vi's and let LabVIEW dynamically dispatch. If you try to do this from TestStand you end up always calling the parent method.

You also need to specifiy the LabVIEW class as part of the step settings else come deployment time the TestStand deployment utility see multiple vi's with the same name and throws an error. (It doesn't see the .lvclass part of the name)

Good luck

Chris

Share this post


Link to post
Share on other sites

Hi Chris,

Thank for the reply.

I am using TestStand 4.2 and LabVIEW 2009 SP1.

Obviously I wanted to use the dynamic dispatch functionality. but I am kind stuck in the initial stage itself ;).

When I inserted a LabVIEW Action step type with a code module having a Class as output, I am getting the properties as shown below.

Code Module Properties.PNG

Now I am not sure how do I pass this Parent Class Out to a different code module. As this type is shown as Unknown, I am not able to pass this to a variable also.

parden me if this issue is very silly, but some how I am stuck here.

Looking forward to here form you,

Mirash

post-9666-0-59189900-1323933019_thumb.pn

Share this post


Link to post
Share on other sites

OK,

you need to pass the class data out of the LabVIEW action step to a TestStand variable (of data type Object Reference) and then pass it as an input param to the next LabVIEW step that needs the class data however I am not sure if that is available to you using TestStand 4.2, not sure if TestStand 4.2 allows LabVIEW classes to be passed as an object ref.

Chris

Share this post


Link to post
Share on other sites
you need to pass the class data out of the LabVIEW action step to a TestStand variable (of data type Object Reference) and then pass it as an input param to the next LabVIEW step that needs the class data however I am not sure if that is available to you using TestStand 4.2, not sure if TestStand 4.2 allows LabVIEW classes to be passed as an object ref.

You're absolutely right - TestStand 4.2 doesn't support the LVOOP object, so the best bet to to flatten it to a string and pass it around in TestStand as a binary string <- note the emphasis, as passing it around as an ASCII string will corrupt it.

TestStand 2010 supports the LVOOP object, but does not support dynamic dispatch.

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.

Sign in to follow this  

×
×
  • Create New...

Important Information

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