02-20-2008 03:39 PM
02-20-2008 04:26 PM
Hi,
[TestStand is complaining at runtime that it doesn't know this variable. ]
Can you expand on this. What variable is teststand complaining about, what error message are you seeing.
I would think that the easies solution would be to have your variable defined in the StationGlobals.
Regards
Ray Farmer
02-20-2008 05:33 PM
mrbean,
Is the sequence that you would like to have act on this information called as a subsequence of the main sequence? Or is it called asynchronously?
If your sequence is called as a subsequence of the mainsequence, then the best way to have that information available will be to create a parameter in the subsequence you are calling. You can then pass the information set in your setup step group into the subsequence.
Of course, if you are doing any of this asynchronously, then this approach is not appropriate. Using notifiers, fileglobals, or stationglobals will work.
02-21-2008 07:31 AM
I use StationGlobals and SequenceFileGlobals but as read-only. I don't want the user modifying these files in any way. That is why I went with parameters, since these just get used during runtime and return to their default state upon exit.
[You can then pass the information set in your setup step group into the subsequence] - how exactly is this done.
Also, I wrote a utility (VI) that allows me to get/set parameter values. I don't specify in which sequence the parameter resides, yet it seems to find the parameter. I'm not sure what it would do, however, if I had two parameters (in different sequences) with the same name.
02-26-2008 10:39 AM
I'm not sure (in this context) what you mean by "asynchronously"
" ...called as a subsequence of the main sequence? Or is it called asynchronously?"
In most cases, I call subsequences of the mainsequence. However, I'm trying to set a parameter while in the Setup group, and read it (from a VI) called in a subsequence of the MainSequence.
03-04-2008 04:05 PM