Extra Window for LabVIEW User Interface's Subpanel

[Chickentree]

Hello,

I am using TestStand 2016 and LabVIEW 2017. I have a similar problem described in the following thread. However, it didn't really help me solve my problem.

https://forums.ni.com/t5/NI-TestStand/Extra-Window-when-using-SubPanel/td-p/2705251

I have a user interface as shown below. I modified the shipped simple UI example. The Show Front Panel VI's front panel is inserted into the subpanel correctly but it's never active there. A window pops up instead and that's where the front panel is updated.

In the Initialize step, the subpanel reference is inserted into the TestStand UI Data cluster. 

This is the Register Event Callbacks step. I added the UI Message Event callback.

This is the front panel of the UI Message Event callback VI.

This is part of the block diagram.

If I use the interface from the following link (first ZIP file), the subpanel works just fine. I don't know what makes the difference.

https://forums.ni.com/t5/Example-Programs/Dynamic-LabVIEW-Subpanel-in-a-TestStand-User-Interface/ta-...

[Norbert_B]

I think you are running in one of the two caveats:

• When running the UI in the LabVIEW development system, the LabVIEW adapter must also use the development system.  If the UI is running as an executable, the LabVIEW adapter must be configured to execute VIs in the Runtime engine.
• if the code module is called in a new thread, whether by existing in a subsequence call in a new thread or through the use of the Run VI Asynchronously step, the VI will execute in a separate window as well

[Chickentree]

Hello Norbert,

I haven't built an executable yet. If I open TestStand (the version selected by TestStand Version Selector), I see that LabVIEW Development System (2017) is correctly selected on the adapter configuration panel. No new thread is called and there is no asynchronous step in the simple example sequence.

[Chickentree]

I found that the extra window pops up only if I run the user interface VI after opening its project file. If I open the interface VI without the project window open, it works fine. I wonder why. The project doesn't even contain anything from the sequence file.

[t@nim@t0R]

Will you ever need to open the VI in the project and in TestStand simultaneously?

[Chickentree]

---

t@nim@t0R wrote:

Will you ever need to open the VI in the project and in TestStand simultaneously?

---

No, I can't think of any reason to do that.