On 05/12/2018 17:41, Dana Myers wrote:
On 12/5/2018 4:32 AM, Bill Somerville wrote:
Anyway, reading the link Dana kindly posted, it is hardly a simple
facility. You must edit several registry values just to get it
working and it seems very unpolished for a desktop offering.
You need only edit the registry values to get the highest (1mS)
accuracy from the Win 10
time service; the time service works with the default settings, I was
seeing no problem
with FT/JT operation, and random checks showed that I was always
within a few tens of mS.
73,
Dana K6JQ
Hi Dana,
that's not my understanding of the link you posted. It seems to say that
the registry value changes are required to achieve even 1s accuracy
assuming the network route, hops, lack of asynchronous up vs. down
latencies is suitable. To achieve the higher accuracies of 50ms or 1ms
the networking requirements are higher along with restrictions on system
CPU load but no extra registry changes are needed. It even hints that a
local stratum 1 NTP device may be needed to achieve the highest accuracy
(1ms).
Reading it again, it is ambiguous because of the following two requirements:
*
The target system must synchronize time from an NTP hierarchy of
time servers, culminating in a highly accurate, Windows compatible
NTP time source.
*
All Windows operating systems in the NTP hierarchy mentioned above
must be configured as documented in the Configuring Systems for High
Accuracy
<https://docs.microsoft.com/en-us/windows-server/networking/windows-time-service/configuring-systems-for-high-accuracy>
documentation.
It all hangs on the mean of "All" in the second point. If all means all
then that includes the target system, if all means all the time servers,
but not the target system, then the implication is that 1s accuracy is
possible without registry changes. It may help to know that the W32Time
service is also a server that other clients can synchronize from. Clear
as mud ;)
If you are achieving better than 1s accuracy using the W32Time service
then I suspect your systems real-time clock and calendar are able to
maintain that over a 24h period or more. That is definitely not the case
for many motherboards, some struggle to hold 1s accuracy over a hour or
less.
I would check those registry settings on your system, assuming you have
not changed them. They specify the NTP poll and time setting intervals.
You could also try typing into a command window:
net stop w32time
and then see how well you hardware keeps time with no external
synchronization.
YMMV & 73
Bill
G4WJS.
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
