From owner-freebsd-hardware Wed Oct 8 11:39:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA06601 for hardware-outgoing; Wed, 8 Oct 1997 11:39:45 -0700 (PDT) (envelope-from owner-freebsd-hardware) Received: from ns.mt.sri.com (SRI-56K-FR.mt.net [206.127.65.42]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA06585 for ; Wed, 8 Oct 1997 11:39:40 -0700 (PDT) (envelope-from nate@rocky.mt.sri.com) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.7/8.8.7) with ESMTP id MAA03184; Wed, 8 Oct 1997 12:39:19 -0600 (MDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id MAA11594; Wed, 8 Oct 1997 12:39:16 -0600 (MDT) Date: Wed, 8 Oct 1997 12:39:16 -0600 (MDT) Message-Id: <199710081839.MAA11594@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Mike Smith Cc: Nate Williams , cliff ainsworth III , freebsd-hardware@freebsd.org Subject: Re: project truck.....ideas wanted In-Reply-To: <199710081825.DAA00927@word.smith.net.au> References: <199710081658.KAA10961@rocky.mt.sri.com> <199710081825.DAA00927@word.smith.net.au> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Um. So you are saying that the "introduced" jitter, ie. SA (Selective > Availability), is actually predictable? And that this prediction is > available to a commercial consumer? What's the point of it then? It's not predictable (well, it is, but it's a fairly complex algorithm that is not published, essentially making it unpredictable). The point is that the jitter introduced is the same across all of the recievers in the same general area, so if one of the receivers isn't moving, you can take the 'difference' of the changes made to it and apply it to the values on the other receivers taken at the same time. (In case anyone is concerned, my brother-in-law at the State of Montana is also doing this, so it's not like it's a state secret or anything. *grin*) Another rumor I've heard about is that the introduced jitter may go away. Interestingly enough, during the most recent 'war' (Desert Storm), there weren't enough GPS receivers that could read the 'encrypted' channel which has no introduced jitter, so they ended up turning off SA and using standard commercial receivers. It kind of defeats the purpose. That, and DGPS has made it virtually useless for anything 'sensitive', so there is serious consideration being made to kill it. But, many of the GPS manufacturers are fighting it, because it makes alot of their 'new generation' products useless, which rely on the introduced jitter. *sigh* Capitalism at it's worst. Nate