04-21-2017 10:10 AM - edited 04-21-2017 10:12 AM
04-21-2017 01:40 PM
A quick solution would be to change the FileGlobal scope so that these two executions share the same fileglobals. You can set it under Edit » Sequence File Properties » Sequence File Globals = All Executions Share the Same File Globals.
That being said, there are probably better solutions depending on what your real goal is. For example, you could pass a reference as a parameter to these sequences and only share what you need.
Is there any reason to spawn off two new executions from LabVIEW instead of using one execution that calls your two sequences sequentially?
04-21-2017 01:53 PM
Thanks for the suggestion. But i will not be able to run the subsequence with "All execution share same file global". Reason follows,
My two subsequence would be intializing instrument and configuring instrument. Now i have to execute these 2 subsequence at different instant of my test and pass the session opened in initialize instrument to configure instrument. Since both the subsequence is part of same sequence file, I thought somehow if i can able send the session id from initailize to configure through file global.
Also I can have the scenerio where i will have two same instruments, so i have to run the initialize instrument twice and configuration twice and yet pass the session id respectively.
Any suggestion are welcome! Thanks in advance
Navin S
CLA
04-24-2017 01:36 AM - edited 04-24-2017 01:37 AM
Hi Navin S
What Adapter you are using if LabVIEW the Session Id can be maintained in LV2G and can be transferred between steps and Sequences,If you are using TestStand alone Use Parameters in Sub Sequences and a Local variable in Main Sequence to transfer data between main and sub sequences.