There should be very little reason to use Dimension 4, with step updates
at fixed intervals. The full implementation of ntpd is available for
all the Windows NT family, i.e. everything after Windows 95, and
versions or w32time that can be configured to implement the older
version of NTP have been supplied with Windows since at least Windows XP.
The standard ntpd always works by managing clock frequency, so there are
no abrupt time steps unless something has gone sufficiently wrong to
result in a step of at least 200ms. w32time can be configured to work
that way, although generally installing the standard (reference) version
of ntpd is preferred. (ntpd can be configured to almost never step the
time.)
Although Windows is not a good platform for time keeping, both these
approaches ought to produce times accurate to about 20ms, and only
slowly changing with time. In some circumstances, Linux can produce
several orders of magnitude better results.
On 04/10/18 22:32, Mike Greenway wrote:
As previously posted the problem had nothing to do with CODEC or the K3S.
Problem turned out to be the time update of the computer by Dimension 4. I had
it set for updates every 1 sec as I didn’t think that was a problem. I now
have it set for 30 Mins and probably and hour would not hurt anything as every
15 secs it does about .049 correction on my computer. I don’t think it is
abnormal for the Rates on WSJT-10 to jump out of range when a time update is
done to the computer. Something you cant see on WSJT-X or JTDX. Thanks to all
that wrote with suggestions, all of them good. 73 Mike K4PI
______________________________________________________________
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]
