[gpsd-users] Comments: Using gpsd with Suse, KDE, Marble, ntpd

[Tom Hardy]

I'm also using a gps mouse that came with Microsoft Streets and Trips. It 
speaks NMEA, and is also identified as:

lsusb
...
Bus 003 Device 017: ID 1546:01a5 U-Blox AG 

I don't think that's in your database.

Running gpsd manually:

gpsd -n -N -D2 /dev/ttyACM1

gpsd:INFO: launching (Version 3.5)
gpsd:INFO: listening on port gpsd
gpsd:INFO: NTPD ntpd_link_activate: 1
gpsd:INFO: stashing device /dev/ttyACM1 at slot 0
gpsd:INFO: opening GPS data source type 2 at '/dev/ttyACM1'
gpsd:INFO: speed 115200, 8N1
gpsd:INFO: speed 9600, 8O1
gpsd:ERROR: PPS ioctl(TIOCMIWAIT) failed: 25 Inappropriate ioctl for device
gpsd:INFO: speed 115200, 8N1
gpsd:INFO: gpsd_activate(): activated GPS (fd 5)
gpsd:INFO: device /dev/ttyACM1 activated
gpsd:INFO: running with effective group ID 16
gpsd:INFO: running with effective user ID 65534
gpsd:INFO: startup at 2013-10-30T07:14:18.000Z (1383117258)
gpsd:INFO: /dev/ttyACM1 identified as type Generic NMEA (0.002610 sec @ 
115200bps)
gpsd:WARN: unknown sentence: "$GPTXT,01,01,01,PASH inv format*36\x0d\x0a"
gpsd:WARN: unknown sentence: "$GPTXT,01,01,01,PGRM inv format*34\x0d\x0a"
gpsd:WARN: unknown sentence: "$GPTXT,01,01,01,PSRF inv format*2B\x0d\x0a"
gpsd:WARN: unknown sentence: "$GPTXT,01,01,01,PFEC inv format*2C\x0d\x0a"
gpsd:WARN: unknown sentence: "$GPTXT,01,01,01,PTNL inv format*3A\x0d\x0a"
gpsd:WARN: unknown sentence: "$GPTXT,01,01,01,PFEC inv format*2C\x0d\x0a"
gpsd:WARN: unknown sentence: "$GPTXT,01,01,01,PASH inv format*36\x0d\x0a"
gpsd:WARN: unknown sentence: "$GPTXT,01,01,01,PMTK inv format*3E\x0d\x0a"
gpsd:WARN: GPGSV field 3 value of 14 != actual count 12
gpsd:WARN: GPGSV field 3 value of 14 != actual count 12
gpsd:WARN: GPGSV field 3 value of 14 != actual count 12
...

Let me know if there is anything I can do that you'd be interested in.

Regarding Marble, I'd reported a bug that resulted in a fix, but it may be a 
gpsd bug.  It's at https://bugs.kde.org/show_bug.cgi?id=312212

Synopsis: Losing the GPS fix often results in gpsd reporting status as ok, but
reporting nan as position. These invalid coordinates result in broken
position data (nan as position, random painting on the map) and likely
also crashes.

udev: There are no rules concerning a ttyACM gps device. I run gpsd manually.

suspend/resume: If the gps mouse is plugged at suspend and at resume, the 
device file remains constant, but gpsd needs to be tickled to start working 
again. (I disable/reenable gpsd in Marble.) ntpd, however, won't resume unless 
gpsd is restarted.

It's only when unplugging/plugging the gps mouse that the device file changes.

Does that accord with your expectations?

Thanks.

-- 
Tom Hardy <address@hidden>