Meinberg Time Error

  • 1
  • Question
  • Updated 2 weeks ago
New PC, clean install of Win 10 Pro (1709 / 1803) Meinberg installed, time checked using time.is web site. On my other PC (Intel i5 NUC) consistent "your time is exact" response. On the new PC (Dell Optiplex i7 32GB 250 GB SSD) I'm getting a consistent "your PC is 0.6 seconds slow. I don't think that 0.6 seconds will have any impact on FT8 or JT65, but why the error? Would switching to "D4" be a better choice?
Photo of WA2SQQ

WA2SQQ

  • 393 Posts
  • 84 Reply Likes

Posted 3 weeks ago

  • 1
Photo of Greg Day, N8GD

Greg Day, N8GD

  • 136 Posts
  • 67 Reply Likes
Stay with Meinberg.  It's much more acurate than Dimension4, which is not bad in its own right, but Meinberg updates continually (every 10 seconds, by default, whereas D4 is more like every 15 or 30 minutes.

If you don't have the Meinberg monitor installed, go here and install it to check on Meinberg's status:

https://www.meinbergglobal.com/english/sw/ntp-server-monitor.htm

Once you open the Monitor, click on the "NTP Status" tab (second from  the left) and look at the "Current local NTP status" line..There you will find the IP address of the NTP server used and the current offset in milliseconds.

A couple of things you might check: Open Windows Services and make sure the service named "Network Time Protocol Daemon" is enabled and running (this is the Meinberg service).  Second, make sure that the "Windows Time" service is stopped AND disabled.  The last item can interfere with Meinberg.  Normally Meinberg disables the Windows Time service, but in the process of updating to Version 1803, it may have been turned back on and is interfering with Meinberg.  Meinberg survived my 1803 update and Windows Time service is still disabled after tht as well.

Just a few things to check.
Photo of Tim - W4TME

Tim - W4TME, Customer Experience Manager

  • 8952 Posts
  • 3382 Reply Likes
Darn, Greg beat me to it.  I agree with everything Greg said.
Photo of WA2SQQ

WA2SQQ

  • 393 Posts
  • 84 Reply Likes
I'll check these things thanks very much but what's interesting is that I had the exact same error using Windows 10 1709 before the upgrade the 1803. I even tried uninstalling and then reinstalling it. Wasn't aware of the monitor I'll try that
Photo of Greg Day, N8GD

Greg Day, N8GD

  • 134 Posts
  • 66 Reply Likes
Especially check the two services I mentioned.  Make sure that Windows Time service is disabled and Network Time Protocol Daemon is enabled and running.  I've seen many time settings programs fail to turn off Windows Time service and it overrides the one you've installed!
Photo of Ria - N2RJ

Ria - N2RJ, Elmer

  • 2199 Posts
  • 850 Reply Likes
Meinberg doesn’t update periodically. Instead it skews the clock by speeding up or slowing down. It’s a smoother way to sync. Dimension 4 simply abruptly steps your clock. Frankly I think most who get it, get it for the cool name and not functionality.
Photo of Greg Day, N8GD

Greg Day, N8GD

  • 136 Posts
  • 67 Reply Likes
That's correct.  Meinberg's operation is a completely different process from other time setting apps.  It's also more difficult to understand its operation and configuration.  Basically, just install it and enjoy its accuracy.
Photo of WA2SQQ

WA2SQQ

  • 393 Posts
  • 84 Reply Likes
Totally baffled. No matter what I've tried I'm getting a consistent .9-1.0 second behind the correct time error. My other PC's are dead on using time.is web site. Even tried uninstalling and reinstalling. This has been consistent using either Win 10 1709 or 1803
Photo of WA2SQQ

WA2SQQ

  • 393 Posts
  • 84 Reply Likes
Regarding the 4 servers, honestly I have no idea. I installed Meinberg using all the defaults just as I've done on my other two PC's. One runs Win 7 and the other Win 10. Both show the exact time. Is it possible that the default settings for Meinberg have changed?

The default Windows time services are definitely disabled.

"That latency between you and your peer NTP servers and the accuracy of their clocks will also factor into how long it takes." I totally agree, but I would think that if this contributed any error, wouldn't it be consistent on all 3 PC's? The real unknown is whether 1 sec is too much of an error for the digital formats...
Photo of Greg Day, N8GD

Greg Day, N8GD

  • 134 Posts
  • 66 Reply Likes
Probably for FT8, but other modes can tolerate up to 2 seconds.  Also, see my post above and install the Meinberg Monitor to check its settings.  It's pretty technical, but if you just look at the settings, you may get a clue as to what's wrong.
(Edited)
Photo of WA2SQQ

WA2SQQ

  • 393 Posts
  • 84 Reply Likes
Tim, this might be a clue ... Using the NTP Time Server Monitor, selecting NTP Status, it updates once every second. It shows, "No Association ID"
Photo of Bill W2PKY

Bill W2PKY

  • 431 Posts
  • 74 Reply Likes
On the Meinberg Monitor click NTP Status to see the servers. Make sure the service is started on the main panel. May need to start as Administrator.
Photo of WA2SQQ

WA2SQQ

  • 393 Posts
  • 84 Reply Likes
OK, it's working! I think they made a change in the setup file. In the 3rd screen it asks if you want to make a configuration file, I selected YES. On the older version it had a default selection - on the latest version in addition to selecting YES, you need to select a config (location). Selected US and it's now showing Time is Exact.