On Tue, Dec 23, 2014 at 9:42 PM, Rudolf J Streif <[email protected]> wrote: > Thanks, Kevron. > >> >> A lot of it probably has to do with tool familiarity. > > Indeed, folks stick to what they know. I do it. > >> gpsd has some >> nice tools. In AMB: >> >> amb-listen Location >> or >> amb-get Location >> >> will tell you if it's working. If you want to know why it's not >> working, running ambd with -d5 or -d7 will spit out a lot of debug >> about the NMEA messages from the gps device. > > We will definitely look into it. I suppose it won't just get me the location > but also speed, track, climb and the timestamp of course. > > >> >> This type of feedback is really appreciated because it gives us an >> idea where documentation and overall support needs to improve. What >> do you find useful in cgps? Would adding a "SatellitesInView" >> property that you can easily get via amb-get/amb-listen be useful? >> Possibly a "GpsFix" property that tells you what level of fix (1, 2, >> or 3D fix)? > > cgps is just convenient when it comes to testing. I can immediately see if the > receiver is working and fixing the sats. A GpsFix property is actually very > useful since it tells me if the reading is usable for a certain purpose. >
I'll probably look into adding both GpsFix and GpsSatellitesInView in AMB 0.14. > I do want to use AMB with GPS and OBD-II in combination to correlate data. I > have one of these ELM327-based USB OBD-II devices. > I plan on doing a "Howto" blog on getting GPS with OBD-II and Bluemonkey as soon as I can figure out how to publish my blogs on 01.org. I'll send a link to relevant mailing lists when it's out. Merry Christmas and the best new year, Kevron _______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
