TestStand engine does not run the sequence an OI tells it to run.

[DLMC]

Useful information

Windows 11 enterprise

LV 2022

TS 2021

Operator Interface used to call a TestStand sequence file.

I'd previously asked this question in the LabVIEW forum, but closed it and moved it here because it seems like TestStand is causing this, not the LabVIEW OI.

Something unexpected is happening with operator interfaces and teststand sequence calling.

I have 5 operator interfaces that each are programmatically told to open a specific TestStand sequence file.  I am using an invoke method on the Application Manager to set the sequence file to use that is saved in a control of that OI top level VI.

However, TestStand runs a sequence file called from any of the OIs that was called in the last OI that was run, not the one set to run from the OI I fired off.

Four tests use the same OI with a different top level VI each which calls a different sequence.  One OI is a different project from the others, but acts the same, it will use the last sequence called (even from the other project), not the one it is told to use.

You can see this happen, the OI comes up and the control holding the sequence file I want to run is displayed there.  Then when TestStand starts and I answer the administrator login, which always happens when you start TestStand, you see the control's setting change to the prior run sequence file.  Some interaction between TestStand and the LabVIEW OI happens and the sequence file changes.  

Why is this?  I have been banging my head against a board about this.  Somewhere TestStand is deciding to run the last run sequence file instead of the one the OI tells it to run.

be well,

DLC

[DLMC]

Useful information

Windows 11 enterprise

LV 2022

TS 2021

Operator Interface used to call a TestStand sequence file.

I'd previously asked this question in the LabVIEW forum, but closed it and moved it here because it seems like TestStand is causing this, not the LabVIEW OI.

Something unexpected is happening with operator interfaces and teststand sequence calling.

I have 5 operator interfaces that each are programmatically told to open a specific TestStand sequence file.  I am using an invoke method on the Application Manager to set the sequence file to use that is saved in a control of that OI top level VI.

However, TestStand runs a sequence file called from any of the OIs that was called in the last OI that was run, not the one set to run from the OI I fired off.

Four tests use the same OI with a different top level VI each which calls a different sequence.  One OI is a different project from the others, but acts the same, it will use the last sequence called (even from the other project), not the one it is told to use.

You can see this happen, the OI comes up and the control holding the sequence file I want to run is displayed there.  Then when TestStand starts and I answer the administrator login, which always happens when you start TestStand, you see the control's setting change to the prior run sequence file.  Some interaction between TestStand and the LabVIEW OI happens and the sequence file changes.  

Why is this?  I have been banging my head against a board about this.  Somewhere TestStand is deciding to run the last run sequence file instead of the one the OI tells it to run.

be well,

DLC

[DLMC]

In my best Rosanne Rosannadanna voice "Never Mind".

I am now back to thinking it is a LabVIEW bug after more testing.  The LV code opens TS before setting the sequence file, which makes sense.  The Invoke Node for the Application manager that opens the sequence file is what changes the file to be opened, not TestStand.

Single-stepping through the code, it runs correctly, running full out, it does not.

Adding delays doesn't change anything when running full speed.

This must be a bug and I'm done with it.  Hopefully NI2025 fixes it.

So, ignore this question, since it appears to actually be a LabVIEW bug, not what I thought at all.  If I could delete this question I would.

be well,

DLC

[Anand_Jain]

Hi, 

Not sure what is happening specifically in your case. Will it possible to post an example or privately sent an example to me?

One possible reason could be if ApplicationMgr.ReloadSequenceFilesOnStart - NI is set to true. If set to True, once the user logs in, the ApplicationMgr will reload the sequences files. Please refer to Working with the TestStand Simple User Interface - LabVIEW - NI and review the shipping full feature User Interface with TestStand for more information. 

Regards, 

Anand Jain

NI

[DLMC]

---

@Anand_Jain wrote:

Hi, 

Not sure what is happening specifically in your case. Will it possible to post an example or privately sent an example to me?

One possible reason could be if ApplicationMgr.ReloadSequenceFilesOnStart - NI is set to true. If set to True, once the user logs in, the ApplicationMgr will reload the sequences files. Please refer to Working with the TestStand Simple User Interface - LabVIEW - NI and review the shipping full feature User Interface with TestStand for more information. 

Regards, 

Anand Jain

NI

---

The test code is pretty massive and I am not experienced enough yet to condense it to a trivial example.

Thanks for the pointer, I never knew that one was there. I tried it but nothing changed.  I will do more reading.

I am using the OI code that I inherited and admit I have not dug deeply into the hows/whats/whys of the OI because it just appeared to work.  This code is migrated from NI2010 and it worked without this problem in NI2010 on ancient Windows 7 machines.

be well,

DLC