[SFDXA] SFDXA Digest, Vol 229, Issue 10

[J.F. Samuels - K2CIB]

Meinberg, or others using Internet time to various servers, works well 
for local purposes, but not well for stations that are remotely located.

For FT8, for example, and even more important for other more fussy 
protocols, it is necessary to synchronize on the received signals.  The 
latency of a remotely operated station can be from 100 to 500 msec.  
Those amounts of latency may not prevent you from decoding FT8 signals, 
but might be a problem if the receiving station also has clock errors.

TimeFudge allows you to manually adjust the time in selected increments 
to received signals and works well.  JTSync should work well if you use 
the feature that analyzes the received signals and automatically adjusts 
the clock, but not the default which is to synchronize with the NTP 
time.  I could not make the former part work yet.

*

*/73, John, K2CIB/*



*
On 5/14/2023 12:40 PM, sfdxa-request at mailman.qth.net wrote:
> Message: 1
> Date: Sun, 14 May 2023 16:39:45 +0000
> From: Howard Rensin<Howard at rensin.com>
> To:"sfdxa at mailman.qth.net"  <sfdxa at mailman.qth.net>
> Subject: [SFDXA] Computer time updates
> Message-ID:<8f8482ad277647f2a3f42eed3f544ef0 at ADEX.Rensin.com>
> Content-Type: text/plain; charset="us-ascii"
>
> I have used Meinberg NTP on all my PCs for a long time. It is written in assembler so it is very light on the OS. It runs in the background and easily installs and it's free.
> Every time I check my PC against Time. Is it is always within. 06 seconds.
> Strongly recommend this software for great time keeping.
> Howard
> KC3D
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.qth.net/pipermail/sfdxa/attachments/20230514/492668ac/attachment.html>