From: tz <tz2026@gmail.com>
To: Hal Murray <hmurray@megapathdsl.net>
Cc: thumbgps-devel@lists.bufferbloat.net, gpsd-dev@nongnu.org
Subject: Re: [Thumbgps-devel] [gpsd-dev] PPS over USB
Date: Wed, 2 May 2012 17:43:02 -0400 [thread overview]
Message-ID: <CAFv7Oijh5Kpi9RxJ0kQaY1eyMmz-FdTFhBoMkBebsV8ysQcNTA@mail.gmail.com> (raw)
In-Reply-To: <20120502211935.9EAE180003B@ip-64-139-1-69.sjc.megapath.net>
[-- Attachment #1: Type: text/plain, Size: 984 bytes --]
Depending on the gps, there can be a dead-reckoning mode that will
extrapolate things for some time (often settable). The pps may or may not
follow.
On May 2, 2012 5:19 PM, "Hal Murray" <hmurray@megapathdsl.net> wrote:
>
> gem@rellim.com said:
> > Looking for that check in the gpsd code, I do not see it in the PPS path
> or
> > in the NMEA path. I wonder when that disappeared? That may explain some
> > things... I'll go add that back in now.
>
> I think there is another piece of fine print in that area. I'm not sure
> where I saw it, probably one of the Garmin docs.
>
> The idea is that you can't trust the first few seconds of data when it
> switches from not-enough satellites to enough. I've seen it give bogus
> position (way off) marked as valid. I think they all happened right after
> recovering from not-enough-satellites.
>
> I'll scan log files if anybody wants examples.
>
>
> --
> These are my opinions, not necessarily my employer's. I hate spam.
>
>
>
>
[-- Attachment #2: Type: text/html, Size: 1364 bytes --]
next prev parent reply other threads:[~2012-05-02 21:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20120501151435.4a6a5373.gem@rellim.com>
2012-05-01 22:16 ` [Thumbgps-devel] Fwd: " Dave Taht
2012-05-02 1:40 ` [Thumbgps-devel] " Dave Taht
2012-05-02 3:07 ` Jim Thompson
2012-05-02 3:33 ` Eric S. Raymond
2012-05-02 7:58 ` Hal Murray
2012-05-06 21:28 ` Eric S. Raymond
2012-05-02 11:09 ` tz
[not found] ` <20120502131310.7dd7f799.gem@rellim.com>
2012-05-02 20:33 ` tz
2012-05-02 21:19 ` Hal Murray
2012-05-02 21:43 ` tz [this message]
2012-05-02 13:40 ` Ron Frazier (NTP)
[not found] ` <20120502124227.28ef9fa6.gem@rellim.com>
2012-05-03 4:07 ` Ron Frazier (NTP)
2012-05-06 22:09 ` Eric S. Raymond
[not found] ` <4FA43068.2080606@wildgooses.com>
[not found] ` <20120504160455.4514ac26.gem@rellim.com>
[not found] ` <20120506214138.GB14699@thyrsus.com>
[not found] ` <4FA6F396.70307@tmsw.no>
[not found] ` <4FA7BDF1.7030708@wildgooses.com>
[not found] ` <4FA7CFB2.9080807@tmsw.no>
[not found] ` <4FA7E197.9010902@wildgooses.com>
[not found] ` <20120507205843.GA21259@thyrsus.com>
2012-05-07 21:14 ` Dave Taht
2012-05-07 21:52 ` Eric S. Raymond
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAFv7Oijh5Kpi9RxJ0kQaY1eyMmz-FdTFhBoMkBebsV8ysQcNTA@mail.gmail.com \
--to=tz2026@gmail.com \
--cc=gpsd-dev@nongnu.org \
--cc=hmurray@megapathdsl.net \
--cc=thumbgps-devel@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox