GPS data from gllin
jsuggs at murmp.com
Mon Aug 6 22:11:15 CEST 2007
Ken Yale wrote:
> The GLLIN sends NMEA sentences to named pipe "/tmp/nmeaNP".
> The OMGUI uses this output to plot positions, satellite strength, etc.
> on various OMGUI test panels.
> Close your handle to /tmp/nmeaNP to stop the GLLIN (if it was opened
> with "-np" option).
> Below is a typical NMEA output sequence from the GTA01 showing the
> position (RMC,GGA), time (UTC format) (RMC,GGA), satellites used (GSA),
> satellites tracked (GSV), satellite signal strength (GSV), and satellite
> position (GSV), type of fix (GSA), and various other details (GGA
> especially has lots of miscellaneous information).
> Google "NMEA" and you'll find excellent tutorials about NMEA. (Be sure
> not to type too fast and end up with "NEMA" which, among other things,
> is a medical-imaging file exchange standard.)
> The OpenMoko team will plug the GLLIN into the GPSD (see module
> omgui/gllin.cpp for sample GLLIN start/stop code to use as the basis for
> the GPSD). I hear the DBUS link planned for GPS information
> distribution beyond the GPSD multi-cast is done.
> Ken Yale
Thanks for the info, I'm looking into the gpds documentation right now.
I'm somewhat familiar with DBUS, but will need to get my hands dirty
with it before I feel truly comfortable. Any DBUS and/or GPS gurus out
I know possibly premature, but what would be the "correct" way to get
You can get the raw output like is demonstrated in the wiki
Or you could call d-bus methods (ie turnOn, turnOff, curPosition,
curElevation, curSpeed, etc). Do we have any idea what that address
would be and/or has anyone worked on those interfaces/methods?
I would think something like the dbus interface could make for "cleaner"
more (re)usable code, plus you could hide some of the underlying
complexities in the gpsd setup.
More information about the community