NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

TestStand 2010 Deployment not including TestStand VIs in deployment

Hi all,

 

I have a question about a deployment I am trying in TestStand 2010, having just recently upgraded from 4.2.1. I was building a particular deployment with no issues in TS 4.2.1, using LV 2010. The VIs in the project use the TestStand Get/Set Property VIs quite a bit, and in the 4.2.1 support VIs directory, you can see them there.

 

However, using the same deployment configuration, I tried to build the deployment in TS 2010. This deployment didn't have any of the TestStand VIs which were present in the 4.2.1 deployment. As a result, VIs that call the TestStand VIs are reported as broken. Note that the VIs were created while I was using 4.2.1, so the TestStand VIs are for that version (it has never been an issue for previous upgrades, however).

 

Recap:

 

TS 4.2.1, LV2010 - Deployment works fine

 

TS 2010, LV2010, using same deployment configuration file - Deployment broken, no TS VIs included in support VIs

 

Ideally I'd like to sort this out at a deployment level, rather than employ any workarounds. Is there a difference in the TS 2010 and 4.2.1 VIs? Or am I missing something glaringly obvious?

 

Any help is greatly appreciated!

 

Thanks,

Rob


________________________________
Rob Greene,
ATE Engineer,
Benetel Ltd.

Benetel Wireless and RF Solutions Certified LabVIEW Developer
0 Kudos
Message 1 of 6
(3,339 Views)

Hi,

 

With you TS 2010 deployment, I am assuming you started off with your TS4.2.1 deployment file. Did your Source and Destination setup show the TestStand VI?

 

 

 

 

Regards
Ray Farmer
0 Kudos
Message 2 of 6
(3,331 Views)

Hi Ray,

 

All I see in the "View Destination" tree is "<SubVIs: save to 'Support VIs' directory>". The Support VIs directory is where I would normally expect them to reside on the target machine. The same deployment in 4.2.1 results in the TestStand VIs being in this folder.

 

They don't seem to be referenced or mentioned at all in the "View Source" tree.

 

Hope that helps,

Rob


________________________________
Rob Greene,
ATE Engineer,
Benetel Ltd.

Benetel Wireless and RF Solutions Certified LabVIEW Developer
0 Kudos
Message 3 of 6
(3,329 Views)

Hi Rob,

 

Maybe it has something to do with the Filtering, checkout Chapter 14 of the Reference Manual and also the Filter.ini filter.

 

 

Regards
Ray Farmer
0 Kudos
Message 4 of 6
(3,321 Views)

Hi Ray,

 

Filter.ini has the following lines:

 

 

[Exclude_Company_Product]
...
COMPANY_3="National Instruments"
PRODUCT_3=TestStand
...

 

Would this be filtering out the TestStand VIs?

 


________________________________
Rob Greene,
ATE Engineer,
Benetel Ltd.

Benetel Wireless and RF Solutions Certified LabVIEW Developer
0 Kudos
Message 5 of 6
(3,318 Views)

Rob,

 

I tried a small demo using TS2010 and LabVIEW 8.6.1 (only have this on my system at present)

 

When I created my deployment image, I open the LLB that was created and present in the LLB was TestStand - Get Property Value (Number).vi.

 

I then changed one of the options in the LabVIEW VI Options dialog so that I excluded files from VI lib and then rebuilt the Deployment image, TestStand - Get Property Value (Number).vi was missing, as expected.

 

So It seems to be working for TS2010 and LabVIEW 8.6.1.

 

Can you check that you haven't got any options selected that are excluding files.

 

LabVIEW VI Options.PNG

 

 

Regards
Ray Farmer
0 Kudos
Message 6 of 6
(3,307 Views)