Return-Path: Received: (qmail 51035 invoked from network); 13 Feb 2004 09:00:52 -0000 Received: from unknown (HELO ptb-mxscan03.plus.net) (212.159.14.237) by ptb-mailstore04.plus.net with SMTP; 13 Feb 2004 09:00:52 -0000 Received: (qmail 70936 invoked from network); 13 Feb 2004 09:00:51 -0000 X-Filtered-by: Plusnet (hmail v1.01) X-Spam-detection-level: 11 X-Priority: 3 X-MSMail-Priority: Normal Received: from ptb-mxcore03.plus.net (212.159.14.217) by ptb-mxscan03.plus.net with SMTP; 13 Feb 2004 09:00:50 -0000 Received: from post.thorcom.com ([193.82.116.20]) by ptb-mxcore03.plus.net with esmtp (Exim) id 1ArZBq-000IKV-4z for dave@picks.force9.co.uk; Fri, 13 Feb 2004 09:00:50 +0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-Fake-Domain: majordom Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1ArZAt-0006V3-6D for rs_out@blacksheep.org; Fri, 13 Feb 2004 08:59:51 +0000 Received: from [195.101.39.227] (helo=GWOUT.thalesgroup.com) by post.thorcom.com with esmtp (Exim 4.14) id 1ArZAs-0006Ui-Hc for rsgb_lf_group@blacksheep.org; Fri, 13 Feb 2004 08:59:50 +0000 X-Fake-Domain: thalescan.corp.thales Received: from thalescan.corp.thales (200.3.2.3) by GWOUT.thalesgroup.com (NPlex 6.5.026) id 402BB6990000984A for rsgb_lf_group@blacksheep.org; Fri, 13 Feb 2004 09:59:57 +0100 X-Fake-Domain: tccplex.tcc.thomson-csf.com Received: from tccplex.tcc.thomson-csf.com ([200.3.1.11]) by thalescan with InterScan Messaging Security Suite; Fri, 13 Feb 2004 09:58:59 +0100 X-Fake-Domain: NODALNET.clb.tcfr.thales Received: from NODALNET.clb.tcfr.thales (146.11.5.4) by tccplex.tcc.thomson-csf.com (NPlex 6.5.026) id 3EC391A20051D61F for rsgb_lf_group@blacksheep.org; Fri, 13 Feb 2004 09:59:56 +0100 Received: by NODALNET.clb.tcfr.thales with Internet Mail Service (5.5.2653.19) id ; Fri, 13 Feb 2004 09:58:59 +0100 X-Bad-Message-ID: no DNS (argos.clb.tcfr.thales) Message-ID: <8840D182F8BB7540B173D2B1FA0CA9AB018AE32F@argos.clb.tcfr.thales> From: Jean-Louis.RAULT@fr.thalesgroup.com To: rsgb_lf_group@blacksheep.org Date: Fri, 13 Feb 2004 09:59:38 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) 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.3 required=5.0 tests=NO_REAL_NAME 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 all Please keep in mind that Windows operating systems are very poor "time keepers". They drift very quickly, depending on the programs you are running. A drift of one second up to one minute per day is not uncommon (specially with "data crunchers" softwares like real time FFT computing)! I'm not talking about the drift of the PC hardware clock itself which is quite good (the time base xtal oscillator drifts around 2 s per month on my own computer), but from the Windows time management. It seems that the time management on the Windows multitask OS has a very low priority ... I verified this on Windows 95, Windows 98 and Windows Me. Any other experience with other operating systems ? 73 de Jean-Louis F6AGR > -----Message d'origine----- > De : 0482183881-0001@t-online.de [mailto:0482183881-0001@t-online.de] > Envoyé : jeudi 12 février 2004 23:19 > À : rsgb_lf_group@blacksheep.org > Objet : Re: LF: Timing GPS > > > Stewart Bryant schrieb: > > If GPS is not an option, then NTP (clock timing via the Internet) > > might be an alternative. > > > > There is some info on accuracy at > > > > http://www.ntp.org/ntpfaq/NTP-s-algo.htm#AEN2361 > > > > - Stewart G3YSX > > > 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. > > there is a problem in synchronizing the PC clock by DCF77 (as > with other > standard time signal transmitters): During lf transmittings > of your own > station there will be no clocking because the DCF77 receiver will be > overloaded (what is it in english "zugestopft"?). > > if the program "Africam" will come into fashion agn (I played with it > and the SD KIT abt 20 years ago) the case is`nt as critical > as it sounds: > if I rember right there are two helpfull knobs, Autotrack and > Aütofrequency. > > BTW. if my station transmits all night long my neighbour runs > into trouble with his employer: the radio alarm synchronized by DCF77 > doesnt wake him (the neighbour) up. > > regards > Uwe/dj8wx > > > > > > > > > > > >