Return-Path: X-Spam-DCC: paranoid 1233; Body=2 Fuz1=2 Fuz2=2 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on lipkowski.org X-Spam-Level: X-Spam-Status: No, score=-0.7 required=5.0 tests=BAYES_00,DNS_FROM_AHBL_RHSBL, RATWARE_GECKO_BUILD,SPF_PASS autolearn=no version=3.1.3 Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by paranoid.lipkowski.org (8.13.7/8.13.7) with ESMTP id u9UHWoW3008769 for ; Sun, 30 Oct 2016 18:32:50 +0100 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1c0trF-0003hX-5F for rs_out_1@blacksheep.org; Sun, 30 Oct 2016 17:25:21 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1c0trE-0003hO-IH for rsgb_lf_group@blacksheep.org; Sun, 30 Oct 2016 17:25:20 +0000 Received: from mout2.freenet.de ([2001:748:100:40::2:4]) by relay1.thorcom.net with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.87) (envelope-from ) id 1c0trC-00086v-0a for rsgb_lf_group@blacksheep.org; Sun, 30 Oct 2016 17:25:19 +0000 Received: from [195.4.92.142] (helo=mjail2.freenet.de) by mout2.freenet.de with esmtpa (ID dl4yhf@freenet.de) (port 25) (Exim 4.85 #1) id 1c0tr9-000248-9F for rsgb_lf_group@blacksheep.org; Sun, 30 Oct 2016 18:25:15 +0100 Received: from localhost ([::1]:41923 helo=mjail2.freenet.de) by mjail2.freenet.de with esmtpa (ID dl4yhf@freenet.de) (Exim 4.85 #1) id 1c0tr9-0008AW-4t for rsgb_lf_group@blacksheep.org; Sun, 30 Oct 2016 18:25:15 +0100 Received: from mx12.freenet.de ([195.4.92.22]:60081) by mjail2.freenet.de with esmtpa (ID dl4yhf@freenet.de) (Exim 4.85 #1) id 1c0toI-0006lQ-S3 for rsgb_lf_group@blacksheep.org; Sun, 30 Oct 2016 18:22:18 +0100 Received: from x4d08639d.dyn.telefonica.de ([77.8.99.157]:59188 helo=[192.168.178.26]) by mx12.freenet.de with esmtpsa (ID dl4yhf@freenet.de) (TLSv1.2:DHE-RSA-AES128-SHA:128) (port 587) (Exim 4.85 #1) id 1c0toI-0006zl-MQ for rsgb_lf_group@blacksheep.org; Sun, 30 Oct 2016 18:22:18 +0100 To: rsgb_lf_group@blacksheep.org References: <157b3bf43d2-111e-bfa3@webprd-a11.mail.aol.com> <0f1b59cf-e10d-1daf-125b-ad4aca471a06@gmail.com> <580205DC.80508@posteo.de> <58020BE2.1020107@posteo.de> <289454467.20161015210855@chriswilson.tv> <5808C23D.6060006@posteo.de> <580CE812.40500@posteo.de> <580CEA96.2010200@posteo.de> <4e343fa907bf9f2652ce9f25fe56d62a@smtp.hushmail.com> <580E12A9.9070309@posteo.de> <58160F3F.2010600@abelian.org> From: =?UTF-8?Q?Wolfgang_B=c3=bcscher?= Message-ID: <451a5b86-55e8-b677-a81a-b4e0065b07d4@freenet.de> Date: Sun, 30 Oct 2016 18:22:14 +0100 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <58160F3F.2010600@abelian.org> X-Originated-At: 77.8.99.157!59188 X-Scan-Signature: 8556389a5ea14fbbf9b9d801ab70c592 Subject: GPS pulse timing (was: Re: LF: Idiot's guide to receiving Ebnaut?) Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-SA-Exim-Scanned: Yes Sender: owner-rsgb_lf_group@blacksheep.org Precedence: bulk Reply-To: rsgb_lf_group@blacksheep.org X-Listname: rsgb_lf_group X-SA-Exim-Rcpt-To: rs_out_1@blacksheep.org X-SA-Exim-Scanned: No; SAEximRunCond expanded to false X-Scanned-By: MIMEDefang 2.56 on 10.1.3.11 Content-Length: 3024 Status: O X-Status: X-Keywords: X-UID: 9304 Hello Paul, Thanks for the details. I guess the pulse jitter cannot go down much further, unless the GPS receiver can "pull" its own oscillator in frequency, which is definitely not the case with the Garmin (but maybe with the trimble). The Garmin receiver can only shift the output pulses in multiples of its internal CPU clock, which iirc was 40 MHz, and thus 25 ns "stepwidtdh" (can easily be seen with an oscilloscope triggered by a good GPSDO). you wrote: > Wolf wrote: > > measured the standard deviation in the GPS sync pulse > > timing. Used an E-MU 0202 at 192 kSamples/second. > > Ran a quick trial here. > > With the Trimble 10uS directly into an E-MU 0202 at 192k/sec I > get 100nS std dev of the raw intervals. The timing system here > uses smoothed intervals which reduces the jitter to below 30nS. > > Same setup at 48k/sec is useless, the raw std dev is around > 6uS. Watching the pulse on vtscope, the waveform changes > significantly from one pulse to the next. This is so at both > sample rates but seems worse at 48k. Looks like waveshape > depends on just when the pulse arrives with respect to the > soundcard's internal A/D sampling. > Yes, but that's not a bad waveform - it *must* be like that if the card uses a good delta-sigma converter. And that's what my interpolation algorithm actually relies on. By interpolating those ugly waveforms, and running them through a windowed sinc filter (with cutoff frequency at half the original sampling rate) we get a *constant* waveform again, which only shifts along the timescale depending on the relative pulse time (within one ADC sample). But the peak of the reconstructed pulse at f_sample_interpolated = 4 * 192 kHz is always identical, even if the waveforms *before* the interpolation look very different. The principle would completely fail with a simple (non delta-sigma) ADC as built inside many microcontroller. Consider it this way: The "frontend" of the ADC is a one-bit A/D converter running at a sample rate of dozens of Megahertz, and the output at the end of the decimator chain is perfectly predictable, even if the waveform looks strange and seems to vary. The interpolator / windowed sinc lowpass in the software delivers a signal at a higher sampling rate than delivered by the soundcard, but the information about the precise GPS pulse time "is still in there". It only depends on the number of sigma-delta stages and the ADC's "oversampling" factor. Example: 24 stages (for up to 24 bit resolution) plus 8-fold oversampling : 24 * 8 * 192 kHz = 36.864 MHz for the "one-bit" input stage, which is a crystal frequency seen in many soundcards. This should be good enough for a time resolution of 27 nanoseconds (if there was no noise and other imperfections) -> std dev around 14 ns. Add the jitter from the GPS itself, say another 25 ns for the GPS18LVC, and -i guess- even less for 'better' receivers. With the Trimble GPS, you already arrive there, which is remarkable ! All the best, Wolf .