09-14-2006 10:43 AM
09-15-2006 12:41 PM
09-17-2006 08:23 AM
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.)
09-18-2006 11:30 AM - edited 09-18-2006 11:30 AM
Message Edited by AEDavid on 09-18-2006 11:30 AM
11-18-2011 01:42 AM
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?
11-22-2011 01:17 PM
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
11-23-2011 02:58 PM
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)
11-24-2011 12:36 AM - edited 11-24-2011 12:38 AM
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.
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 :
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.