NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

Operator interface and Batch model

Hi, I use Batch model.
I want my Operator Interface automatically jump to active execution (active test socket). Now it didn't show active socket automatically. The user have to found active socket to see current execution.
How I can always see active socket in OI ?
0 Kudos
Message 1 of 8
(4,570 Views)
Hi Marta1402,

Are you using a pre-defined OI or a custom one?  Is it a LV, CVI, etc interface?  What do you mean by the "active" socket?  In Batch, there should be several active ones, right?  It would also help if you could post a screen shot of what you are seeing versus what you would like to see.

Cheers,

David Goldberg
National Instruments
Software R&D
0 Kudos
Message 2 of 8
(4,557 Views)

Hi,

actually I use Sequential Batch model, CVI Operator Interface.

I mean when current test socket is in running, OI don't update execution window (steps of my sequence) on the right side. OI shows me old execution window of previous socket. I have to click on current test socket (on the list of sockets on the left) to see current socket.

But I want OI execution steps window automatically changing (according to current test socket). Is it possible to do ?

(Sorry for my English, I hope now you understand my question.)

 

0 Kudos
Message 3 of 8
(4,541 Views)
Hi Marta,

Under Configure -> Station Options, make sure that "Enable Tracing" and "Allow Tracing into Setup/Cleanup" are checked.


Message Edited by AEDavid on 09-18-2006 11:30 AM

Cheers,

David Goldberg
National Instruments
Software R&D
0 Kudos
Message 4 of 8
(4,521 Views)

This only displays the one Test Sockets information.

How do i change the to view test socket 1 and then test socket 2 in the same window?

Help share your knowlegde
0 Kudos
Message 5 of 8
(3,952 Views)

Hello Shako,

 

Unfortunately, there is not a simple feature you may toggle on or off to force reports to share a window. You would have to rewrite the code within your UI. 

 

I would recommend reviewing the following document:

 

Best Practices for NI TestStand User Interface Development

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

Regards,

Shawn S. | NIC
Instrument Driver/IVI PSE
National Instruments
0 Kudos
Message 6 of 8
(3,924 Views)

Try adding a statement step to the beginning of your main sequence with the following expression and see if it behaves more like you are intending:

 

RunState.Engine.PostUIMessage(RunState.Execution, RunState.Thread, UIMsg_OpenWindows, 0.0, "", RunState.Execution, True)

0 Kudos
Message 7 of 8
(3,914 Views)

Hi

 

I found a solution to my problem and it seems to work as expected.

What i done was  create a sequence using the batch model in sequential Batch Mode.

Under the model option i then hide the Batch model Execution Windows.

untitled.PNG

 

I then use the sequence call steps to call another sequence file, using an if statements with the this condition "RunState.TestSockets.MyIndex==0" to know the which sequence to call and i set the execution options as follows :

 

original.png

 

By calling the sequence as a new execution it automatically places it as the active execution.

 

In the Operator Interface i then enabled the Execution Selection so that after the test is complete the user can then select the previous execution to review the trace.

 

It took me a while to figure this out just happy that its works as i expected it to work.

 

Help share your knowlegde
0 Kudos
Message 8 of 8
(3,909 Views)