Re: [gpsd-users] Polling for GPS data using python3 API

[pisymbol .]

On Mon, Aug 12, 2019 at 5:22 PM pisymbol . <address@hidden> wrote:

On Mon, Aug 12, 2019 at 5:12 PM pisymbol . <address@hidden> wrote:

On Mon, Aug 12, 2019 at 5:09 PM pisymbol . <address@hidden> wrote:

On Mon, Aug 12, 2019 at 5:00 PM Gary E. Miller <address@hidden> wrote:

Yo pisymbol!

On Mon, 12 Aug 2019 16:49:48 -0400
"pisymbol ." <address@hidden> wrote:

> Still getting None now on 3.19:
>
> $ pip3 list | grep gps
> gps                           3.19

OK. so how are you starting gpsd?

Usually something like this:

# gpsd -n /dev/ttyS0

You can see your running gpsd this way:

# pstree -paul | fgrep gpsd

> 'report' here is always None.

Which seems like gpsd is no running...

It is running. The Trimble unit emits strings on 192.168.142.1:5017. I was using systemd. However, let's take that out of the equation for now:

$ sudo gpsd tcp://192.168.142.1:5017
$ pstree -paul | grep gpsd
  |-gpsd,12951,nobody tcp://192.168.142.1:5017

$ sudo gpsd -D4 -N  tcp://192.168.142.1:5017
gpsd:INFO: launching (Version 3.19)
gpsd:INFO: listening on port gpsd
gpsd:PROG: NTP: shmat(0,0,0) succeeded, segment 0
gpsd:PROG: NTP: shmat(32769,0,0) succeeded, segment 1
gpsd:PROG: NTP: shmat(65538,0,0) succeeded, segment 2
gpsd:PROG: NTP: shmat(98307,0,0) succeeded, segment 3
gpsd:PROG: NTP: shmat(131076,0,0) succeeded, segment 4
gpsd:PROG: NTP: shmat(163845,0,0) succeeded, segment 5
gpsd:PROG: NTP: shmat(196614,0,0) succeeded, segment 6
gpsd:PROG: NTP: shmat(229383,0,0) succeeded, segment 7
gpsd:ERROR: shmget(0x47505344, 20816, 0666) for SHM export failed: Invalid argument <----- LOOK AT ME?
gpsd:INFO: stashing device tcp://192.168.142.1:5017 at slot 0
gpsd:INFO: running with effective group ID 20
gpsd:INFO: running with effective user ID 65534
gpsd:INFO: startup at 2019-08-12T21:11:36.000Z (1565644296)

Cleaned up shm, now attaches, still get Nones with python3 API! WTF?!

-aps