NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

TestStand exceution stops but resumes on mouse click

Hi,
I am using TestStand version 3.0.0 and VB.net code modules for my test.
The execution stops after executing a long test step (2.5 hours).
But the execution resumes and executes the next step
if I click on the operator interface GUI.
 
Anybody has seen this behavior? I would appreciate any help to
fix this problem.
 
Thank you for your time.
 
Mano
 
TestStand 3.0.0
VisualBasic.NET 1.1
 
0 Kudos
Message 1 of 13
(5,044 Views)
Hi Mano,

We haven't seen this behavior before.  Which Operator Interface are you using?  Is it one of the prebuilt ones or is it one that has been modified?  Does the execution resume when you click any where on the Operator Interface?  Also, after the long step runs, what does the Operator Interface look like?  Is it frozen?  Are you able to click any buttons or menus?
0 Kudos
Message 2 of 13
(5,014 Views)

Hi Terry,

Please find my answers below.

 

Which Operator Interface are you using? 

I am using the modified operator interface (OI) developed using VB.net and VS2003

 

Does the execution resume when you click any where on the Operator Interface? 

Yes.

 

Also, after the long step runs, what does the Operator Interface look like?  Is it frozen?  Are you able to click any buttons or menus?

It is responsive to the mouse clicks and is not frozen.

But it just stops after executing the long step.

Mouse click will execute the next step in the sequence.

 

Regards,

Mano

0 Kudos
Message 3 of 13
(4,980 Views)
Hi Mano,

Did you ever see this behavior in the TestStand Sequence Editor?  Also, is it possible for you to run this sequence in the default Operator Interface ?  If so, does the behavior still exists?  Lastly, would it be possible for you to post your modified Operator Interface, so I could possible test it out on my side?
0 Kudos
Message 4 of 13
(4,953 Views)
We have the same kind of problem! Is there any solution to it?  Thanks in advance.
0 Kudos
Message 5 of 13
(4,706 Views)
Hey Jaggs,

I have some of the same questions for you that Terry asked above.  Does this issue occur if you run this sequence in TestStand Sequence Editor or just in your modified OI?  Also, does this behavior happen with one sequence file or many?  I look forward to hearing back from you.
Best Regards,
Software Engineer
Jett R
0 Kudos
Message 6 of 13
(4,677 Views)
You must be using the VB.net operator interface as i have seen the same problem
0 Kudos
Message 7 of 13
(4,672 Views)
Our application is a LabView EXE.  Just recently it was migrated from LV6.1 to LV8.5.  The application uses different kinds of priority and executions.  The problem is that the UI gets updated when we are doing something on the system but if left alone for about 1 or 2 hrs (random time intervals), the UI kind of freezes and as soon as mouse is moved, it starts executing.  All the objects in loops in different VIs, which use UI thread freezes suddenly.  Remaining VIs which do not use UI thread for execution, such as not explicitly set as UI execution or does not contain any property nodes or similar kind or UI thread execution orjects, run fine.  Mainly most of the VIs in application use objects related to Ui thread and they just freeze until we again move the mouse. 
We don't have screen saver or monitor shutdown.  We were thinking that as 8.5 used 4 threads for each (priority and execution) pair and we use VIs which have high priority so the operating system may be putting the UI thread to sleep.  Ouerating system is XP.
 
The same EXE runs fine on some computers, so we kind f believe that its upto the OS to assign threads.  We have couple of VIs which run in are background priority and UI thread and mainly these VIs don't get executed.
 
 
0 Kudos
Message 8 of 13
(4,660 Views)
Hey Jaggs,

Thanks for the quick response.  I am sure you have already tried this, but what happens when you change the high-priority VIs to a normal priority?  Does the UI thread respond then?  Also, do you have any while loops in your VIs (especially the high-priority) that have small execution wait times?  We can try increasing any wait times smaller than 20ms to 50 or 100ms.  Lastly, you can profile your VIs from the Tools»Profile menus option in LabVIEW; this profile will let us know if there are any memory leaks, etc.  I look forward to hearing back from you.
Best Regards,
Software Engineer
Jett R
0 Kudos
Message 9 of 13
(4,638 Views)
If any of you are posting UI messages please see this thread in case your problem is similar.

http://forums.ni.com/ni/board/message?board.id=330&message.id=18260#M18260

See my post in that thread for an explanation.

-Doug


Message Edited by dug9000 on 02-18-2008 10:23 AM
0 Kudos
Message 10 of 13
(4,616 Views)