A strong suggestion from a network engineer.
Major NTP servers like time.nist.gov are the most accurate clocks, but
they aren't meant for everyone to use -- that's just too much traffic
and latency hurts their accuracy if they're abused.
A huge number of highly dedicated time-geeks run over four thousand time
servers around the world. You can read about this at http://ntppool.org.
Using pool.ntp.org instead of time.nist.gov (or a few dozen other
awkward choices) will point you to a nearby, highly accurate source of time.
73 -- Lynn
On 5/17/20 11:44 AM, Barry wrote:
Here's something that might help. FT8 only decodes in a certain
time slot. Make sure your computer is accessing an NTP server and get
the correct time. Win10 can be set to automatically to access
time.nist.gov. I spent a long time trying to get a ham buddy going the
other day and couldn't figure it out. Another buddy picked up on the
fact that time was not set correctly and he fixed it after which decodes
started. I missed that one. So, just get the correct time and I infer
that should fix your problem. You only need tro be seconds off to not work.
73,
Barry
K3NDM
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[email protected]
This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [email protected]
