02-08-2011 07:05 AM
Hi,
I am new to using the TestStand Property Loader. I have seen examples where the limits are loaded from a property file using the <Step Name> to identify the steps
The sequences I am using unfortunately have certain steps with the same name so this is not the best option for me. Is there anyway I can load the limits by indentifying the steps using the Index instead?
Or are there any workarounds that anyone knows of for this
Regards
Kewal
02-08-2011 08:47 AM
Hi,
Are they in the same sequence or different sequences?
02-08-2011 09:10 AM
same sequence
is there any way to get the limits using the step index instead of name?
02-18-2011 10:11 AM
Hey Kewel,
I have just had a bit of a play with the property importer/exporter and it seems you are absolutely correct - it does reference steps via "Step Name" not index. Therefore you can only really use the Property Loader for sequences with uniquely names steps.
Which does beg the obvious question... if your test steps require different settings, why dont you give them unique names? It sounds like they are performing subtely different testing.
Regardless, I do have a potencial method for importing the different limits for steps that share the same name.
Please open the attached zip file, which contains a sequence, a LabVIEW code module and an example property file.
My Sequence has common names for the tests
Rather than loading the testlimits directly, I have bound individual test limits to local variables. I am then using the property loader to import different values into the variables depending on what the user selects from a simple popup box.
This is the Popup user prompt...
When the user selects "Different Limits for each Test" the resulting report looks like this...
When the user selects "Same Limits for each Test" the resulting report looks like this...
02-20-2011 02:18 PM
thanks for the reply and solution
although in the end i ended up creating my own property loader in labview which while not as flexible as the one provided by NI, does what I need! references the steps based on index