Hi,
I understand your concern that it doesn't make sense to have to reboot your controller every time you restart your VI, to get the right time. While not a pleasant behavior, this is actually quite an expected behavior. In Windows, a process running in Time-critical priority will actually also slow down the system clock. This behavior can be seen when TSR (Terminate Stay Resident)programs will actually slow down the system clock. This is due to the same reason as in RT, interrupt service requests to the system clock can be preempted by higher priority processes.
In an RT system, the timer interrupt is much lower priority than LabVIEW's priority. So thus you see this issue we have been discussing. R&D is aware of this situation. Although not a bug, we are working on some new timestamp VIs that use the hardware registers directly. If you allow me some time, I can play around with the Timestamp VIs (gethighrestimestamp function) and see if I can come up with a good solution for you.
Thanks for your patience!
Anu Saha
Academic Product Marketing Engineer
National Instruments
