Global scope can be achieved in many ways: station globals, file globals, engine temp globals, execution runtime variables, local variable propagation, some tricks with process model, perhaps some tricks with synchronization manager. Each of the above-mentioned methods has some limitations and not all of them can be said to be "true global".
Anyway, if you want to output your results from a VI, l would suggest to use sequence context as an input and use it with one of the mentioned options. If you really don't want to pass context as an input you can use Automation Open LabVIEW primitive or TestStand Manager Controls to access e.g. engine globals or synchronization manager and read/write your globals.
Michał Bieńkowski
CLA, CTA, CPI
- Did someone devote their time to help solve your problem? Appreciate it and give kudos.
- Problem solved? Accept as a solution so that others can find it faster in the future.
- Contribute to the development of TestStand by voting on the TestStand Idea Exchange.