Having a permanent window on screen

[knight2]

Hi all

Firstly, my apologies if I’m posting this to the wrong forum – I’m not sure whether this is a Labview related issue or a Teststand one (or perhaps both?).

 

I have a project I’m currently working on where several Labview VIs are called in sequence from Teststand. When I run the sequence, I’d like to have a permanent window on screen, which I can pass a string to, to indicate what VI is being executed and to display various test results. I can call a VI to do this, but can’t seem to stop it from being automatically closed down and the front panel disappearing - something I'd only want to happen when the sequence completes. Is there any way of doing this?

 

Any advice would be much appreciated. I’m using Labview 7.1 & TestStand 3.1.

 

Thanks

Bruce

[GovBob]

What your describing sounds alot like a TestStand User Interface. There are fully operational examples in the TestStand directory. These were written in several languages including LabVIEW. They could be adapted to your particular needs. If you are going to do this make sure you use a copy of the original. The LabVIEW UI's use ActiveX controls and indicators and not just regular LV ones.

Hope this helps.

[qool]

I've done what you've said by using a Custom Operator Interface and TestStand API in Labwindows CVI. I'm sure you can do something similar by using Labview.

TestStand runs test programs as a thread so the only way I could find to communicate between TestStand Operator Interface and test program during execution is using PostUIMessageEx (..) method in Test Program to send data to Operator Interface.

You need to add your own status message box to Custom UI. Then you need to handle User Messages that are sent from Test Program and display data however you like.

You can check this tutorial for more information:

http://zone.ni.com/devzone/cda/tut/p/id/4532

[TSJim]

Hi -

A simpler solution may be to use queues.  Check the example at: C:\Program Files\National Instruments\TestStand 3.1\Examples\Auto Schedule\LabVIEW is Installed\AutoSchedule.seq

Thanks,
Jim

[knight2]

Thanks to everyone for your replies - that's been a great help.

Regards

Bruce

[Josh_W]

knight2,

You can use the same method as outlined in this example to display a string:

Launching a Floating LabVIEW Panel in TestStand

[knight2]

Hi Josh W.

Do you know where I can get a 3.1 version of that TestStand sequence in the example? I'm assuming it would still work on 3.1.

Thanks

Bruce

[Manooch_H]

Bruce -

Here you go.

[knight2]

Hi Manooch H.

I tried running the 3.1 sequence but it gives me a runtime error for the precondition to launch the GUI, saying that 'RunState.Engine.ApplicationIsEditor' cannot be evaluated. Is there something else I should be doing first?

Thanks

Bruce

[Manooch_H]

Bruce -

Sorry, I didn't catch this when saving the file to 3.1. This file was originally saved in TestStand 4.0 in which you are allowed to call TestStand API in Expressions. I had removed two of the expressions and replaced them with ActiveX steps but missed the Precondition along with the call to Engine.GetInternalOption() in the parameter of the VI. I've updated these to use ActiveX steps and TestStand properties instead.

The updated sequence file saved in 3.1 is attached. Hope this helps.