Process model not working the ! first ! time I run my Labview UI

[LoisLbsUromems]

Hi,

I have my own LabVIEW UI to execute TestStand sequences. It is based on the Teststand Simple UI package.

It works well but now I want to add a process model for my sequences I observe a strange behavior.

In LabVIEW dev environnement, first time I run my application, the process model is not detected. I can see that because the TestStand button (SinglePass) is not visible and the color of the sequence is blue in the sequence combobox. If I run my application a second time,  the process model is detected : the SinglePass button is visible and the color of the sequence is green.

Note :

- I noticed that the first time i run my application, my TestStand module initialized a bit more quickly.

- When I test in executable, single pass button is never visible.

- I tried to mass compile and clear cache

- In my TestStand environment, I set my process model both on the sequence file properties and for the TestStand environment default model

I attached a video showing the problem.

Thank you for your help.

[Oli_Wachno]

First of all.... having the screen capture helps a lot!

I would start investigating at this point

IMHO executing this node takes far too long.

I bet, there is some hidden run-time error / timeout in the routines above the code for the run "Entry Point 1/2 Button" registration and as such, the rest of the node doesn't get executed....

[LoisLbsUromems]

Thank you for your answer.

To have more visibility, I have change the property node by all Write properties VIs :

I can see my application takes time on the second VI when it initialized the application manager with the GetEngine function : 

But nothing changed between the first and the second call, the function GetEngine is called on both and takes a little longer the second time.

I think the problems really comes from my Teststand initialization, so I don't know what to do...

[Oli_Wachno]

Initializing the engine takes quite some time, this is correct. Same thing as when launching the SequenceEditor

From the vid, it felt quite long though... 

So there are no errors during initialization. Do you happen to use Functional Global Variables or unitialized shift registers in the context of your TestStand bject?

[LoisLbsUromems]

I am not surprise about the time Teststand initializes because indeed the Teststand environment is always a bit long to open. But I am surprise the time is not the same the first and the second time i run my application.

I am not sure to understand your question about FGV and shift registers?

[Oli_Wachno]

---

@LoisLbsUromems wrote:

I am not sure to understand your question about FGV and shift registers?

---

My train of thoughts was.... maybe some references are not shut down properly since they are held in a data struct like this.

Way back in the day, I wrote a library for us to be called to do (parts of) what you are doing at the moment. I remember faintly, that I saw some issues there as well., but got them solved. Need to check...

[LoisLbsUromems]

Hi,

For now I've just do a temporary workaround by transferring the logic of the ProcessModel in my Sequence Callbacks, but I didn't solve my problem yet...

I have juste one more information : my problem happens when I load my Teststand environnement. 

Indeed, for each projects, I used a custom Teststand environnement that I call by this way : 

So, the first thing I do in my Teststand UI Module is to set the environnement like this : 

When i disable this VI (therefore I guess the general Teststand environnent is called) the process model works the first time I run my application.

[Oli_Wachno]

Ok... we use the following code

It works every time 🙂

[LoisLbsUromems]

Thank you for your answer :

I modified the function like yours but I still have the same wrong behavior... 

[Oli_Wachno]

Are you setting the enviornment before actually starting the engine or after?