NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

Teststand deployment is duplicating files in supportvis folder.

Having a major, major headache with a Teststand deployment and would really appreciate anyones thoughts on this.

To give a bit of a background, we are creating a Testand deployment that will then run sequences off a USB key - i.e. we are creating a deployment that contains all the files and .vi's that will ever be needed, so that we can then generate new tests, place them on a USB key and run them without any issues.

To create the deployment we are using the 'Files' view in Testand to build up a hierachy of sequences and files as well as some .vi's that contain all the necessary components to run the tests from the USB key, and then using the deployment wizard to go and find all the files that we require.

The problem we are having is that we deploy this onto our system and then with a number of tests run from a USB key we get file location errors related to the supportvis directory. So for instance we might have an error that says 'cannot open C:\blahblah\blah.vi' as another vi with the same name from 'C\supportvis\blah.vi' is already loaded in memory'. We look and there are files in both locations which we believe is because in one sequence we might be calling a VI as a top-level, and in another case it is being called by a top level VI as a sub-vi.

If we delete the file in Support Files the test will still work, - it seems to force Teststand or the Vi to look in an absolute location rather than the relative support files.

The question is how do we deal with this - can we force the deployment to place files in only absolute locations and not duplicate, or are we going to have to do some post build to remove any duplicate files, or maybe there's a totally different answer to this problem.

Any answers or comments will be very greatfully received.

Dave C
David Clark
CLA | CTA
IDEX Biometrics UK Ltd
Hampshire, England
0 Kudos
Message 1 of 3
(1,901 Views)
Hi,
 
You are always going to have problem with the labVIEW when you have same VI's found in different locations.
When you deploy the VI's via TestStands deployment tool, it will place all the directly called VI's as individual VI's in the location you have defined and all sub-vi's in the SupportVIs.LLB.
Dont use the same VI as a top-level VI (ie called direct from teststand) and as a sub-VI. Have the Top-Level call the Sub-VI so at least you haven't got two VI's with the same code but with different filename.
 
Hope this offer some help
Regards
Ray Farmer
Regards
Ray Farmer
Message 2 of 3
(1,890 Views)
Hi Ray, Many thanks for your reply - it kind of confirms what I've been thinking about this - or worrying about as it's quite a large build! It probably means that we're just going to have to seriously re-organise the way we've done our code - the problem has arisen as we have set our system up to initialise all instrumentation and carry out a self test routine before loading the execution environment, so it is potentially going to be a fairly painful job to go through the whole lot to put it right.

Thanks for your reply once again.
David Clark
CLA | CTA
IDEX Biometrics UK Ltd
Hampshire, England
0 Kudos
Message 3 of 3
(1,882 Views)