CTT Test conditions changing state too fast?

[asemle]

I have an AE Server with a condition that can change from the active to inactive state and vice-versa at a rate of once a second. The CTT test seems to have trouble acknowledging this state change. I routinely fail the following tests.

RunTime Tests/IOPCEventServer/AckCondition /Case 1, 2, and 8
-All of these failures relate to an invalid (old) ActiveTime (i.e. SubConditionLastActive)
RunTime Tests/IOPCEventServer/StateMachine /Case 1, 2
-The test isn’t specific about the failure but my server tracing shows that it is also an invalid (old) ActiveTime in the acknowledgment.

From reviewing my trace logs I can see that the CTT test is trying to acknowledge an old state transition, hence the failures.

If I slow things down the test passes without a problem. Is the CTT test dependent on conditions not changing state too quickly? If so what is the recommend max rate of change?

[Matthias Isele]

There is no minimum time the test would wait before acknowledging a condition. This depends just on how fast the test code runs. Of course if the states change to fast in the server you can get this kind of problem.
I suggest you just slow down the change rate a little.
However please send me the *.ctd file with one test run. So I can analyze the problem and see if we can speed up the test a little.