[Elecraft] CODEC

[Bob McGraw K4TAX]

Or if you will, when you sit down to operate, go to Windows Time and Date and update the time.   More than adequately accurate for several hours of operation. 

Bob, K4TAX


Sent from my iPhone

> On Oct 6, 2018, at 3:15 PM, Larry (K8UT) <K8UT at charter.net> wrote:
> 
> David
> 
> >There should be very little reason to use Dimension 4
> There is often a significant gap between Theory and Practice, and such is the case with using Windows as a self-regulated timepiece. True, Windows is a well behaved ntp client, but the default interval for Windows "phoning home" to resync is 7 days. In 7 days my PC has drifted so far that FT8 operation is impossible.
> 
> The user has two choices: use Regedit and mess with the Windows registry to reduce the interval; or install a time sync program. For most, the second option is easier.
> 
> -larry (K8UT)
> 
> ------ Original Message ------
> From: "David Woolley" <forums at david-woolley.me.uk>
> To: "Mike Greenway" <K4PI at bellsouth.net>; elecraft at mailman.qth.net
> Sent: 2018-10-06 08:27:19
> Subject: Re: [Elecraft] CODEC
> 
>> 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:Elecraft at mailman.qth.net
>> 
>> This list hosted by: http://www.qsl.net
>> Please help support this email list: http://www.qsl.net/donate.html
>> Message delivered to k8ut at charter.net
> ______________________________________________________________
> Elecraft mailing list
> Home: http://mailman.qth.net/mailman/listinfo/elecraft
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:Elecraft at mailman.qth.net
> 
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html
> Message delivered to rmcgraw at blomand.net