I'm calling a subsequence which has many steps.
Now, I wish to find (in the RunState......variables) the result of some steps in that same sequence (not the MainSequence).
There is a dedicated line for the Previous Step (which is very comfertable), I'd like to use a similar one for other steps.
Solved! Go to Solution.
other suggestion. Try parsing Locals.ResultList to find the step's result.
I think U can use RunState.Sequence.Main["Step Name"].Result to get the results of all steps.
Why are writing "think" ? You can canel it. Your hint is it working great!
To Rafi: scurp my suggestion to litter basket a believe lordsathi...
I would like to convert my test stand sequence file to an like run time executable ( Ex: file.exe ). Upon search, I found Test Stand Sequence File converter. I tried GUI version. By setting password to prevent viewing as well as editing. I was successful in hiding the sequence from viewing or editing. This option worked for me for few sequences ( Sequences with standard test stand steps). For some sequences (Sequences with custom and standard steps), if I keep a break point or trace enable and start running the sequence. It stops at the break point and every thing is viewable. I REALLY DON'T UNDERSTAND THIS.
Are there any options that I can make this not viewable irrespective of the custom or standard steps. What is NI recommended way of protecting the files? I tried all the search options in Google or NI web site? Please advice.
Note TestStand supports password-protecting sequence files to deter editing and viewing within the sequence editor and user interfaces that use the TestStand User Interface (UI) Controls. The TestStand API limits access to a file protected from viewing but cannot prevent access to the file content during execution. National Instruments does not recommend using passwords as the only way of protecting intellectual property.