timed loop period ceased working

[Norbert_B]

bah, i think i am blind (wondering why....)

Your "benchmark" does not reflect the time the timed loop takes. The problem is: Your "initial" timestamp is taken when the timed loop is already running (for an unknown amount of time....)! To prevent this, the error cluster you passed to the sequenceframe for the initial timestamp has to be wired through it and after this to the timed loop....

this should reveal a better result then.....

Norbert

[cld8812]

20.4 seconds.....

[Norbert_B]

So i can hope that your benchmarking code you are currently using is looking something like this:



Or in other words: Please post your current VI again.

Norbert


[Edit]: Using this approach, the timing of the timed loop fits quite well. You must not forget that this benchmark does not reflect the timed loop itself but exiting/entering the sequenceframes, taking the timestamps....

Message Edited by Norbert B on 06-27-2008 10:24 AM

[cld8812]

here u go

[Norbert_B]

Sadly, my tests all showed the desired behaviour of the timed loop: The timing was correct.

Since i cannot execute your VI, please create another example showing this odd behaviour.  Please keep track what changes you have done to the timed loop if you can reproduce this in another VI.

thanks,
Norbert