@Norbert B wrote:
@Jeff Bohrer wrote:
[...]These are OS dependant since the OS schedules the servicing of the Real Time Clock on Windows its about once a millisecond that it updates (but it counts the ones it misses too- so...it approaches a good clock. [...]
This is also not entirely up-to-date for LV (sorry). Please read this knowledge base for further information.
Please note that the nanosecond engine was introduced with LV 8.0 (as basic for timed structures).
The system RTC is only a reference the nanosecond engine synchronizes to.
Technically, it is possible to achieve wait times of less than ms on a Windows system with LV and the nanosecond engine (though you will not achieve ns, despite its name!).
But since Windows is no real time OS, it is broadly accepted/acknowledged, that jitter peaks of >10ms are "common". Therefore, it does not make sense to get easy access to a timing resolution which is "just disappearing in noise", does it?
hope this helps,
Norbert
Nicely said. And very informative! I guess I'll have to work harder for position #21 though, the air is rarified on that page!
"Should be" isn't "Is" -Jay
