Bob, Meinberg recommends local pool servers, at least four. "# Use a NTP server from the ntp pool project (see http://www.pool.ntp.org) # Please note that you need at least four different servers to

If the whole internet is down, I personally think that running WSJT-X will be far back in our minds... Larry / W1DYJ

Please do a test to see if any NTP server has ~<= 3 ms latency. Hi Chuck, You seems to have a really high speed internet connection! My typical Delays are tens of milliseconds while Meinberg keeps

Hi, Bob:  Good point in spite of the "overly dramatic"s. ;-) A NTP client with both internet and GPS time servers will favor the servers with less 'jitter'. If the internet servers are unavailable

~ 500/186000=0.002688172043011 I suggest that there may be no NTP servers within ( apparent ) 500 miles. Please do a test to see if any NTP server has ~<= 3 ms latency. +1 A first test everyone can

Yes, but if the Zombie Apocalypse arrives, FT8 is the least of my worries. JS8Call has a way to sync to the constellation of other users, and there are other options as well. If ZA _and_ GPS still

Chuck’s 2 cents is certainly good advice, but all this begs the question: What happens in the Zombie Apocalypse? If that seems overly dramatic, then I ask: What do we do if the the World Wide Web

If you were 2+ seconds off your Meinberg was obviously not correctly installed or set up. It should be with no more than 50 or so Milliseconds with that as checked by timeis. Outlook LT Gil

IIRC, my NTP client monitors RTT latency with multiple time servers and adjusts the time accordingly. Time adjustments are done  s l o w l y  in adjustments of thousandths of seconds, not as an 'at

before I do any band change, I turn off "monitor" first. then change bands, monitor will turn back on. perhaps that will help Dave Garber VE3WEJ / VE3IE mac.com@groups.io> wrote:

I had done the latest update to w11, and my audio went erratic. did your's update? I returned to older version of w11, and all is working fine. Dave Garber VE3WEJ / VE3IE

Some interesting thoughts in this thread. so I might as well throw in my 2 cents worth! I use D4 with the update time set to 15 minutes (it could probably be longer). Bob (KN6UXD) mentioned switching

ntpd (which Meinberg is also a compile of) is designed to compensate for propagation delay. It queries the time server, listens for the reply, and can deduce the transit time pretty well, so that

Just for completeness, I note that I was using using Meinberg on my Mac, and the time differential was 2.1 to 2.3 seconds. I switched to an Apple server in Cupertino (I am in San Diego) and the

The Band Activity grid at DXHeat.com shows this at a glance.

Did you install the 64-bit OpenSSL if you are running the 64-bit WSJTX? Mike W9MDB

Hi to Alan, Brian and Kari, That is very interesting! I changed the time update period earlier, and that did seem to make a difference. I think I went from 1 minute to 5 minutes, and noticed it

I followed the instructions in section 3.1 and am still getting the error message. So, now I've installed openSSL and vcredist_x64.exe with the problem still present. Anyone have any other

Many have found that too frequent time sync can cause dropouts as the time is a higher priority that FT8 when it comes to CPU resources. I would think a time sync of NO LESS than 30 minutes would

To clarify a point, Meinbers is nothing more than a compile of "ordinary ntpd on *nix" (which already supported a windows buildP with a windows installer and a few other things added for ease of use.