Hi Jon, I found the main cause of my problem. When the step time has expired and the state machine moves to the next take, it takes one complete loop cycle to do this. That loop cycle is not counted as part of the overall lenght of test. In other words, if I run the test for 10 hours, cycling between step 1 and step 2 every minute, that would be 600 cycles not counted. If my loop time is 10 hertz, then the test will run 60 seconds longer. So I created a difference factor and shortened the upcoming step cycle on each it iteration. So a step may be 59.89 instead of 60 seconds. Now the test runs perfect all the time no matter what loop rates I choose or how many local variables I may use.
Also, if I insert a phony lag in the cycle, the counters will account for that as well.
