[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [gpsd-users] Non functional SiRF
From: |
Dominic Amann |
Subject: |
Re: [gpsd-users] Non functional SiRF |
Date: |
Tue, 8 May 2018 15:40:41 -0400 |
On 7 May 2018 at 17:06, Gary E. Miller <address@hidden> wrote:
>
> Cool. What version gpsd? From where?
>
Sadly, version 3.7 from savannah.gnu.org. Reason for old version is
that later versions wont compile under Yocto. I tried 3.15 and later
versions and I got a weird Python include problem that I couldn't get
to the bottom of. Yocto is a huge cross-compiling framework.
If you think a later version fixes the problem I can probably hack the
compile to not bother with the python stuff (although Yocto makes it
like doing keyhole surgery over a remote link).
>
> Ouch. Send a log file (gpspipe -R > GPS.log) and I'll look at it.
>
gpspipe doesn't appear to come with 3.7.
> As you see, not reliable. Best way is to use some other way to force
> your GPS into the mode you want, and save that as the default config
> in the GPS. The start gpsd with "gpsd -b" so gpsd does not override your
> configuration.
Yes, I found this method eventually.
>
> 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 I am trying that, it seems to work sometimes but not always. I
need to do a bunch of other things in my startup to enable the serial
port and gps first, and then I want to disable it so the user can
switch it on or off manually. A bit of work on my part, but yes what
you describe should be feasible.
> 'gpsctl -n' can be run while gpsd is running to try to put the GPS
> in NMEA mode. Give it a try.
Tried that. Also not reliable (would sometimes hang indefinitely).
--
It is not because things are difficult that we dare not venture. It is
because we dare not venture that they are difficult - Seneca.
Dominic Amann
M 416-270-4587