Hurst,
There are many variable types with varying levels of scope. Locals are active only for the sequence that you create them in. Sequence File Globals are active for the entire sequence file. Station Globals are active for every sequence file that runs on that TestStand machine. If you have more questions about the scope and creation of each of these variables, I'll refer you to the user manual. The manual describes each of these variable types very well. You can access the manual from TestStand by going to Help>>TestStand User Manual.
I'm not sure what you mean when you say "UUT scope TestStand variables." If you want variables that are active during the UUT's execution, you can create a local variable within your process model. To do this, open the pro
cess model you are using and click on the Locals tab. Right-click and choose "Insert" just as you would do in your client sequence. When you want to access that variable from your client sequence, use the Lookup String "RunState.Root.Locals.NewVariable" where NewVariable is your variable name. Then again, a sequence file global may suit your needs. Any of the locals or sequence file globals can be created in any client sequence file or process model file.
If you have other questions or need clarification, please let us know.
Regards,
Shannon R.
Applications Engineer
National Instruments
