Timed state machine

[RTSLVU]

---

@mcduff wrote:

@RTSLVU

Well, the suggestion is there if you are ever feeling naughty.

Another suggestion that probably does not matter much, is to protect your current while loop against an edge case, that is, the system time has been changed. My suggestion is to use the difference with the Tick Count VI. Since the output is U32 you do not need to worry about overflow, it just works.

Cheers,

mcduff

---

Sure but my way accounts for data acquisition time and any variations in that time so the data collection intervals are always equal.

I have been using this method for over a decade (even on long term tests that have ran 24/7 for years) and never ran into any overflow issues.

[mcduff]

@RTSLVU

I have been using this method for over a decade (even on long term tests that have ran 24/7 for years) and never ran into any overflow issues.

What happened when the clock switch for daylight saving time, etc? If the system clock is never messed with, then it should always work, but if the system clock is messed with your time interval may not be accurate.

mcduff

[RTSLVU]

---

mcduff wrote: 

What happened when the clock switch for daylight saving time, etc? If the system clock is never messed with, then it should always work, but if the system clock is messed with your time interval may not be accurate.

mcduff

---

I don't know the question or any issues never came up.