Return-Path: Received: (qmail 45643 invoked from network); 12 Feb 2004 23:05:52 -0000 Received: from unknown (HELO ptb-mxscan02.plus.net) (212.159.14.236) by ptb-mailstore04.plus.net with SMTP; 12 Feb 2004 23:05:52 -0000 Received: (qmail 95805 invoked from network); 12 Feb 2004 23:05:52 -0000 X-Filtered-by: Plusnet (hmail v1.01) X-Spam-detection-level: 11 Received: from ptb-mxcore02.plus.net (212.159.14.216) by ptb-mxscan02.plus.net with SMTP; 12 Feb 2004 23:05:51 -0000 Received: from post.thorcom.com ([193.82.116.20]) by ptb-mxcore02.plus.net with esmtp (Exim) id 1ArPu2-000Ont-Ot for dave@picks.force9.co.uk; Thu, 12 Feb 2004 23:05:50 +0000 X-Fake-Domain: majordom Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1ArPtR-0004d4-Ez for rs_out@blacksheep.org; Thu, 12 Feb 2004 23:05:13 +0000 Received: from [194.73.73.89] (helo=uranium.btinternet.com) by post.thorcom.com with esmtp (Exim 4.14) id 1ArPtQ-0004cv-Vj for rsgb_lf_group@blacksheep.org; Thu, 12 Feb 2004 23:05:13 +0000 Received: from [213.122.176.164] (helo=Main) by uranium.btinternet.com with smtp (Exim 3.22 #25) id 1ArPtQ-0001Ck-00 for rsgb_lf_group@blacksheep.org; Thu, 12 Feb 2004 23:05:12 +0000 X-Bad-Message-ID: no DNS (Main) Message-ID: <001a01c3f1bc$ad30ad60$6507a8c0@Main> From: "Alan Melia" To: rsgb_lf_group@blacksheep.org References: <20040210184134.KTHX20454.tomts35-srv.bellnexxia.net@smtp.bellnexxia.net> <402A6646.4030006@virgin.net> <1ArPAc-19FrkH0@fwd00.sul.t-online.com> Date: Thu, 12 Feb 2004 23:05:08 -0000 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Subject: Re: LF: Timing GPS Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on post.thorcom.com X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 X-SA-Exim-Scanned: Yes Sender: Precedence: bulk Reply-To: rsgb_lf_group@blacksheep.org X-Listname: rsgb_lf_group X-SA-Exim-Rcpt-To: rs_out@blacksheep.org X-SA-Exim-Scanned: No; SAEximRunCond expanded to false X-PN-SPAMFiltered: yes X-Spam-Rating: 2 Hi Uwe, is it not possible to allow for the delay down the connecting wire to the NTP sever. In the days I played TCP/IL over packet the PING facility gave the round-trip delay for paths through regenerators, and packet nodes. At least that software might be useful for keeping my home network all in sync Cheers de Alan G3NYK alan.melia@btinternet.com ----- Original Message ----- From: "jannsen" <0482183881-0001@t-online.de> To: Sent: 12 February 2004 22:18 Subject: Re: LF: Timing GPS > Hi Stewart es All, > I do some PC clock synchronizations via internet using the program > "Time Watch", downloaded from http://www.blue-series.de. the NTP server > transmitting the synchronization signals must be in your vicinity. > it is not usefull telling us that their timer is <1uS accurate > (in my case dirived from GPS receivings) if there is a long wire to the > server. it`s something else if you would know the phase fault on the line > and can correct it in some way. > > reading the PC clock in mSec from the window "Time Decoder" of SpecLab > of one PC with the clock (motherboard and sound card) permanent > synchronized by the standard time signal station DCF77 and at the > same time reading the mSec from the screen of the other PC just > clocking by the signals from the internet server, I believe I see > a difference, DCF77 in front. > > be that as it may, we should reach an agreement about what kind of > synchronization we will make use of. >