Persistent iteration counter when not discarding missed periods in a timed loop

[BillMe]

I see this on LabVIEW 2009. The "Discard Missed Periods" option for a timed loop, when UNCHECKED, means the iteration variable in the loop will be peristent even if you stop and then re-start the VI in which the loop resides.

I understand the need for persistency if your current iteration is late and you want it to try and "catch up", but NOT if you actually stop and start the VI again. In this case, how do you get the iteration variable to reset to 0?

Bill M.

[BillMe]

Clarification: this only happens when you are running more than one timed while loop (each in its own VI). Behaves as expected with one loop.

[BillMe]

Switching to the 1KHz <reset on structure start> timing source obviates this behaviour. So to quote Gilda Radner from the original SNL: "Nevermind".