06-22-2011 03:08 PM
I am currently trying to get TestStand 4.2 to work with VIs created in LabView 9.0.1. I looked in the LabView adapter and the development system that I am using is chosen. I am currently going through the booklet for using LabView with TestStand and it states that I must TestStand default value, but I can not find where this value exists.
Solved! Go to Solution.
06-22-2011 05:47 PM
I'm sorry but your question is unclear. Where does the booklet state "that I must TestStand default value"? The values you used for controls in LabVIEW when you last saved your VI become the default values in TestStand. These can be changed in TestStand's Module tab by unchecking the default box and entering a value or expression in the 'value' box.
06-23-2011 07:36 AM
The booklet "Using LabView and LabWindows/CVI with TestStand" states that if someone is using LabView 8.6.xx or later development system, that the person is supposed to do the following
1. Create a copy of TestStand - Default Values 86.11b.
2. Rename the copy TestStand- Default Values xx.11b, where xx indicates the version of LabVIEW, with out a revision number, you want to use with TestStand.
3. Mass compile TestStand - Default Values xx.11b using the version of LabVIEW you want to use with TestStand.
These directions do not make sense to me. I have started TestStand and so far I can read my VIs just fine. I had to uncheck the "Reserve Loaded VIs for Execution" option since I could not work with editing the VIs with TestStand running.
06-23-2011 01:37 PM
The folder of interest is below:
C:\Documents and Settings\All Users\Documents\National Instruments\TestStand 4.2.1\AdapterSupport\LabVIEW
I attached a picture of my folder contents.
I believe you need to copy 'TestStand - Default Values 86.llb' to 'TestStand - Default Values 90.llb'. Be sure after copying to make the LLB NOT read only before you mass compile. It may not be 86 or whatever version is installed by default.
I don't know where these VIs come into play but I have had to perform the copying when I was using Clusters in connector panes when I was calling LabVIEW VIs. There are probably other reasons.
Good luck,
PH