[prev in list] [next in list] [prev in thread] [next in thread]
List: gpsd-users
Subject: Re: [gpsd-users] Non functional SiRF
From: "Gary E. Miller" <gem () rellim ! com>
Date: 2018-05-09 19:06:46
Message-ID: 20180509120646.70b34e3d () spidey ! rellim ! com
[Download RAW message or body]
Yo Dominic!
On Wed, 9 May 2018 08:07:46 -0400
Dominic Amann <dominic.amann@gmail.com> wrote:
> On 8 May 2018 at 15:49, Gary E. Miller <gem@rellim.com> wrote:
> I think I am now one step beyond the last build failure:
> | TypeError: expected a character buffer object:
Uh, are you trying to use Python 3?
> Here is some of it piped through od -x
Uh, not useful. I need the super raw binary.
> >> > You might also try using gpsctl to put the GPS into NMEA mode and
> >> > then start gpsd with the -b flag so it does not overwrite your
> >> > GPS settings.
> >> >
>
> Yes, and each subsequent time I turn off my gps, and then turn it back
> on again, it seems gpsd re-acquires it and turns it into binary mode.
If gpsd is doing that with the -b flag then that is a bad bug. are
you sure you are saving the GPS config in non-volatile storage?
> > One way to improve things is to only compile gpsd with the drivers
> > that you need. The way gpsd gets lost is when it can't figure out
> > which driver the GPS needs. TSIP is especially nasty and grabby.
> >
>
> It seems to pick the SiRF driver every time - which ought to be
> correct.
Except you did say it gets hung, which is the symptom of hung TSIP mode.
> It just can't grok this chips' output.
Which is why I ask for a binary sample to see what it says to me.
RGDS
GARY
---------------------------------------------------------------------------
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
gem@rellim.com Tel:+1 541 382 8588
Veritas liberabit vos. -- Quid est veritas?
"If you can't measure it, you can't improve it." - Lord Kelvin
[Attachment #3 (application/pgp-signature)]
[prev in list] [next in list] [prev in thread] [next in thread]