LabWindows/CVI

cancel
Showing results for 
Search instead for 
Did you mean: 

Async Timer events

Solved!
Go to solution

I am using CVI 2009 and TestStand 4.1.1 for testing products.

I create an Async timer when I call a function from Teststand that powers up the UUT.

My timer seems to start OK, but there are only 3 Tick Events before the timer callback is no longer called.

 

What could cause the timer events to stop?

 

Thanks

0 Kudos
Message 1 of 3
(2,982 Views)
Solution
Accepted by johnswan

1.  Discarding the timer.

2,  Timer callback is stuck or delayed and doesn't return so timer events are queued up and not serviced.

3,  Another async timer was created prior to the one you're using for UUT power up so that timer has priority and is busy handling enqueued callbacks so your UUT power callback is getting starved.

4.  Async timer thread can't get scheduled.

 

I recently solved an async timer scheduling problem by using an LED indicator on my GUI and setting it ON when entering my async timer callback and off when I left.  I made sure it stayed on at least 200 msec so I could see it.   Main thread set the LED on / off per a global since you can't manipulate the GUI directly from the async callback.

0 Kudos
Message 2 of 3
(2,971 Views)

Thanks.

 

My timer got stuck servicing my CAN bus data acquisition and the events backed up.

0 Kudos
Message 3 of 3
(2,959 Views)