operator interface does not open the sequence it is programmatically told to open.

[DLMC]

Useful information

Windows 11 enterprise

LV 2022

TS 2021

Operator Interface used to call a TestStand sequence file.

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.

This works fine immediately after building the OI for any of the OIs involved.  After that, the TestStand sequence file called from any of the OIs already built will be the last sequence file that was run, not the one set with the invoke node.

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

Why is this?  I have been banging my head against a board about this.  Is the application manager saving state somewhere I can get to?

be well,

DLC

[DLMC]

---

This works fine immediately after building the OI for any of the OIs involved. 

---

Update.  No, even after I build a new OI for another test, the last sequence file run is still selected.  This is a problem since I have 5 project OI's built, but I have to "do something I have not quantified yet" in order to get the project's required sequence file to be run.

be well,

DLC

[DLMC]

I am closing this question here in LabVIEW, because the "flip" occurs after the TestStand RTE gets fired up, I think this is coming from something that TestStand is doing, not my LabVIEW OI build.  I am moving this question to TestStand.

For those interested, the TS question is here:

https://forums.ni.com/t5/NI-TestStand/TestStand-engine-does-not-run-the-sequence-an-OI-tells-it-to-r...

be well,

DLC

[DLMC]

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.

I'm done with it until I get a NI2025 RTE license on a test computer.

be well,

DLC

[dkfire]

To things that I can come up with. 

1) Are you closing the TestStand session correctly when you close the OI ? 

2) Have you tried to unload all files before loading in the new file ? 

Application Manager has a method for closing the files: ApplicationMgr.CloseAllSequenceFiles()

 There is also a ActiveX component that can display the loaded sequence files.

[DLMC]

---

@dkfire wrote:

To things that I can come up with. 

1) Are you closing the TestStand session correctly when you close the OI ? 

2) Have you tried to unload all files before loading in the new file ? 

Application Manager has a method for closing the files: ApplicationMgr.CloseAllSequenceFiles()

 There is also a ActiveX component that can display the loaded sequence files.

---

I am using a flavor of the simple user OI that someone created years ago and I have migrated to a newer NI version.  

I am properly closing the OI.  I have checked and there are no rogue threads running.

I do close all sequence files.  I have singled stepped through it and it works as expected doing that, but if I let run "full speed" it does the "I will ignore what you said and do what you did last time". I've attached the string of invoke nodes used.  I'll not put it in the message here because that is never legible on a screen.

be well,

DLC

[dkfire]

Did some check on what I normally do. 

I think the main problem is that you are loading the sequence file too early. 

Under normal operation, a user has be logged into the TestStand engine before you can load a sequence file. 

How are your user logging into TestStand or do you setup a default user ??  

[DLMC]

---

@dkfire wrote:

Did some check on what I normally do. 

I think the main problem is that you are loading the sequence file too early. 

Under normal operation, a user has be logged into the TestStand engine before you can load a sequence file. 

How are your user logging into TestStand or do you setup a default user ??  

---

Thanks for the reply.  I have TestStand automatically login as the windows user.  There is a special Windows user for the test stands.

be well,

DLC

[dkfire]

It should be possible for you to verify that the user is logged into TestStand before loading the sequence file.