Leaderboard

Don't forget the support! Support for NI devices is second-to-none. It is this you are truly paying for.

Hi, I had been having this problem for a while too, but I finally fixed it yesterday. I installed Wireshark to discover that my application was constantly sending Internet requests to Verisign. I looked the request up on Google and it appears that it is a .Net known bug that leads to the application verifying automatically the signature of .NET components by Authenticode. This leads to networks timeouts and long delays when launching the application when not connected to the Internet, but having an active network connection. I found the fix on ni.com. Here is the link: http://digital.ni.com/public.nsf/allkb/9A7E2F34EC9DDEDE86257A09002A9E14 I guest there was nothing wrong with my program after all! Benjamin

The 14 ms is an OS limitation (for WinXP that has an internal timer that has an update rate just above 50 Hz). If I use Get Current Time is has a resolution of 1 uSec. When converting this to double you'll have rounding issues limiting you to 0.5 uSec. Technically a timestamp can store much greater resolution. If you go subtracting almost similar timestamps (like your TS1 and TS2) you'll better use Cluster substraction: Ton