Share File Globals between sequence files

[vglinden]

Hi,

I have a VeriStand project for a test and I need to automate it with TestStand.

I'm using the Initiate Veristand for automatically opening the project. This block stores the Veristand reference information (file path...) in the File Global. This information is presented as a "struct" containing multiple fields.

The architecture that i'm proposing has multiple sequence files and each file has to keep the Veristand reference information the same way the main sequence file does. Otherwise, any other Veristand block which communicates to the project "won't know" what project it's communication with.

How can I share this automatically generated information to every called module (sequence file)?

Thank you.

[kosist90]

The straightway solution is to keep this information not in FileGlobals, but in StationGlobals - then the value will be keeped even between TestStand Engine calls (because value of StationGlobals is written/read to/from file automatically by TestStand).

This is also what you could do - write values of your FileGlobals variables to file, and then read from this file while loading another sequence.

But, keep in mind, that references values will be not valid anymore - so you can keep like this just values of some statical data types (of course, you can keep also dynamical types, but their values will be not valid between sequences start/stop).

Sincerely, kosist90

Check out new features and changes in LabVIEW 2017!

[vglinden]

Thank you kosist90 for taking interest in helping me.

I belive you may be familiar with the Veristand library steps. When you use the Deploy Veristand Project, the step automatically generates the information on the File Globals. That is why I did want to "globalize" File Globals instead of a alternative. I know there is a option for "All executions share the same file globals", but I'm currently not able to get it working. It's probably because I'm using different Sequence Files instead of Subsequence. (Agreed?)

I believe your's is a good solution and I will try to execute it. I have tried something alike this passed week but, since I'm new to TestStand, it's not guaranteed.

About your second idea (writing a file and then loading it), how is this technique called? Do you have a documentation for it?

Thank you