VeriStand 2011 LabVIEW 2009 SP1 compatibility

[Changi]

Hi,

Our company has a lot of libraries with sources in LabVIEW 2009 SP1. We call them using the NI TestStand adapter using custom step types.

I am trying to create a similar library for NI VeriStand. But, I want to use VeriStand 2011 for this since it has really good features.

However, when I install VeriStand 2011, there is no palette for it created in LabVIEW 2009. I want to programmatically call VeriStand functions from LabVIEW as part of my library.

I know some KBs say I must use LabVIEW 2011 for VeriStand 2011, but it is not an option for me, since I will have to migrate all my earlier libraries to the latest LabVIEW version also.

Please help!

Thanks and regards,

Aditya CHANGAVALLI

LabVIEW 2009 SP1

TestStand 4.2.1

[StephenB]

The supported way to use LV and NIVS together is to use the matching version year.

however, if you only intend to make calls to NIVS for automation, via the execution time API, these LV VIs are really just wrappers for the public .NET API. So you could drop .NET constructor, invoke, and property nodes to call to NIVS 2011 directly or you could go through the significant effort of getting the wrapper VIs from LV 2011 and doing "save for previous" on everything.

[Changi]

Thanks Stephen.

I will try this. If indeed this works, I don't understand why NI would stress on version being the same!

Also, Do you think I can make custom devices using LabVIEW RT 2009 SP1 in VS 2011? It will be great if I could do this.

Aditya

[Jarrod_S.]

You  need to use LabVIEW 2011 to build a custom device to be used in VeriStand 2011. The main reason VeriStand 2011 only has compatibility with LabVIEW 2011 is that VIs saved in versions of LabVIEW other than 2011 will not be able to be loaded in VeriStand, which runs in the LabVIEW 2011 Run-Time Engine.

[StephenB]

Unfortunately no. NI VeriStand uses the Labview run time engine that matches the version year. So any plug-in code must also use that version

[Changi]

Thank you Stephen and Jarrod.

However, I will not be using the custom device through the VeriStand Workspace application. I just want to deploy the custom device on the RT system and then I will call APIs of VeriStand (using LabVIEW 2009 SP1) to interact with the deployed custom device. I am hoping the RT controller will be able to run custom devices built on LV 2009 also.

Do you think this will work?

Aditya

[StephenB]

I'm not quite sure what you mean here. Overall, NI VeriStand version year 20xx can only run custom devices made with LabVIEW 20xx.