A GPS Chip Made to Sip Power, Not Guzzle

From: ComSec <ComS..._at_gmail.com>
Date: Thu, 13 Aug 2009 10:26:39 -0700 (PDT)

>From - Sat Mar 02 00:57:25 2024
Received: by 10.90.214.3 with SMTP id m3mr883591agg.5.1250291871786;
        Fri, 14 Aug 2009 16:17:51 -0700 (PDT)
Received: by 10.90.214.3 with SMTP id m3mr883589agg.5.1250291871754;
        Fri, 14 Aug 2009 16:17:51 -0700 (PDT)
Return-Path: <d..._at_geer.org>
Received: from absinthe.tinho.net (absinthe.tinho.net [166.84.5.228])
        by gmr-mx.google.com with ESMTP id 16si260803gxk.1.2009.08.14.16.17.51;
        Fri, 14 Aug 2009 16:17:51 -0700 (PDT)
Received-SPF: neutral (google.com: 166.84.5.228 is neither permitted nor denied by best guess record for domain of d..._at_geer.org) client-ip6.84.5.228;
Authentication-Results: gmr-mx.google.com; spf=neutral (google.com: 166.84.5.228 is neither permitted nor denied by best guess record for domain of d..._at_geer.org) smtp.mail .._at_geer.org
Received: by absinthe.tinho.net (Postfix, from userid 126)
        id BA02E33EE9; Fri, 14 Aug 2009 19:17:50 -0400 (EDT)
Received: from absinthe.tinho.net (localhost [127.0.0.1])
        by absinthe.tinho.net (Postfix) with ESMTP id A9D9633ED3
        for <TSCM-..._at_googlegroups.com>; Fri, 14 Aug 2009 19:17:50 -0400 (EDT)
From: d..._at_geer.org
To: TSCM-L2006_at_googlegroups.com
Subject: Re: [TSCM-L] {4138} A GPS Chip Made to Sip Power, Not Guzzle
In-Reply-To: Your message of "Thu, 13 Aug 2009 10:26:39 PDT."
             <619201f5-ead4-424a-b0fa-e1d9b73d6239_at_z34g2000vbl.googlegroups.com>
Date: Fri, 14 Aug 2009 19:17:50 -0400
Message-Id: <20090814231750.BA02E33EE9_at_absinthe.tinho.net>


One way to do this is to offload the trig calcs to the
cloud as the sampling (of the GPS sky) is 5% of the power
required to achieve a fix while the trig is 95%. Or so
I am told by some company or other that makes GPS tracking
devices that wake up every few hours and put a 100 ms slice
of the sky into flash memory. At journey's end, the flash
is read off-device so the battery consumption for the recorder
is actually 1/20th of what would otherwise be required if what
you were doing was recoording position rather than raw data.

--dan
Received on Sat Mar 02 2024 - 00:57:25 CST