NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

PostUUTLoop callback not executed

hi,

 

a. i am using sequential process model

 

1.  I am using my   motor unload & all stop steps in the callback  PostUUTLoop  (i need it this way) in the cleanup steptype

 

2.   if there is some system error  comm. error etc the  teststand engine goes till   postuut callback but  end the execution there

 

3. i have also disabled the "Handle Termination" step   (looking in the sequentialmodel.seq)

 

why is the seq ending abrubtly

 

 

0 Kudos
Message 1 of 5
(4,984 Views)

one more info

 

my cleanup steps in  PostUUT  callback  generate error  messages

0 Kudos
Message 2 of 5
(4,981 Views)

What have you configured for "runtime error behavior"?

It sounds like you are aborting the execution!

 

Norbert

Norbert
----------------------------------------------------------------------------------------------------
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.
0 Kudos
Message 3 of 5
(4,976 Views)

thanks Norbert,

 

The answer to your question is   "On Runtime Error" =  Show Dialog 

 

------------------------------------------------------------

 

What I am not able to get is that  if there is an erorr in PreUUTLoop or Post UUTLoop  the   next  step is mostly Termination

 

the  sequence Pointer  does not go throuh all the cleanup steps after that.

I had expected the  Pointer to go through the Cleanup Group of PostUUTLoop

 

My issue is I am using the Device-Initialization  & Device De-Init steps  in PreUUTLoop & PostUUTLoop respectively.

 

and any error inbetwen aborts the  execution

 

Also I found that  the execution Jumps to " ProcessCleanup"  call back, If I select   "On Runtime Error" =  Show Dialog or  Run Cleanup

 

regards

Akshay

0 Kudos
Message 4 of 5
(4,963 Views)

Akshay,

 

depending where the runtime error occurred, the "run cleanup" does exactly what it tells: It only executes "Cleanup" steps. If the error occurred somewhere in the process model before PostUUTLoop, this callback will not get called as it isn't part of the cleanup steps of the execution entry point.

There is one exception where a runtime error might occur which does not (using the "run cleanup" option) call solely the cleanup stepgroup steps: If the error occurs in the MainSequence. In this case, the process model will continue normally, otherwise, you wouldnt get a report in case of an error in the MainSequence (and subsequences).

For all other instances where errors occur the "run cleanup" option makes sure that the complete callstack (including the toplevel process model) will only execute steps from the cleanup stepgroup.

 

Norbert

Norbert
----------------------------------------------------------------------------------------------------
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.
0 Kudos
Message 5 of 5
(4,951 Views)