mjb/altos/src/ao_gps_skytraq.c, branch teleterraAltOS - the operating system for Altus Metrum products
https://git.ethernal.org/mjb/altos/atom?h=teleterra2010-09-02T02:53:24+00:00altos: Bounds check Skytraq GPS tracking data array2010-09-02T02:53:24+00:00Keith Packardkeithp@keithp.com2010-09-02T02:53:24+00:00urn:sha1:1177e0a684328422be5adc68093d0091a218a824
Missing GPS serial data could cause the tracking array reset to
get skipped, causing the array to be overrun, smashing critical data
beyond the array.
This was detected using the 'altosui' flash command to program a
device from TM. Hitting the USB that hard caused TM to crash with a
mutex error (3 beeps) after the ao_gps_task structure was overwritten
with zeros.
Signed-off-by: Keith Packard <keithp@keithp.com>
altos: print GPS state flags in GPS 'g' command2010-08-26T22:59:09+00:00Keith Packardkeithp@keithp.com2010-08-26T22:59:09+00:00urn:sha1:aa6c27df5db6bdae59d00affccb891854a6caa18
Having the GPS state information can help with GPS debugging.
Signed-off-by: Keith Packard <keithp@keithp.com>
Log GPS data on pad after boost detect.2010-02-14T00:42:27+00:00Keith Packardkeithp@keithp.com2010-02-14T00:42:27+00:00urn:sha1:876e9a10b9096ead85fbe08ec9a6a0329cf7cbd4
This wakes up the two GPS reporting tasks and gets them to report out
any existing GPS data to the log file. To make sure the timestamps in
that GPS data are accurate, this also records GPS time on receipt of
the GPS data instead of when that is logged.
Signed-off-by: Keith Packard <keithp@keithp.com>
Missing ao_mutex_put in gps_dump2010-02-12T05:23:35+00:00Keith Packardkeithp@keithp.com2010-02-12T02:48:56+00:00urn:sha1:2a6350149407c7d2e7d143906c40c5e331248aebAdd simple gps dump command 'g'2010-01-10T04:57:48+00:00Keith Packardkeithp@keithp.com2010-01-10T04:57:48+00:00urn:sha1:28346736a7799c0767e54511d9949cd61d35e471
This just dumps out the data in a very simple format to verify the GPS
receiver.
Signed-off-by: Keith Packard <keithp@keithp.com>
Add --cal to man page2009-12-16T07:58:29+00:00Keith Packardkeithp@keithp.com2009-12-16T07:58:29+00:00urn:sha1:7ac8efea5d60b81adccdc1e38ac4c13facfae7c9Decode HDOP data from skytraq GPS2009-11-22T04:37:53+00:00Keith Packardkeithp@keithp.com2009-11-22T02:57:45+00:00urn:sha1:80b23f3044a654d61212891a61fadb8a3a4e5572
The hdop data was getting dropped on the floor, but is rather useful
when deciding if the GPS position is crazy or not. This reports HDOP *
5 (giving a useful range of .2-50).
Signed-off-by: Keith Packard <keithp@keithp.com>
Stop using SiRF state info.2009-11-16T00:20:18+00:00Keith Packardkeithp@keithp.com2009-11-16T00:20:18+00:00urn:sha1:b0d7e3f9c9322542e9b649bb6ad7f7e5bb99dffa
With the switch to the skytraq GPS unit, we don't have the same level
of detail in the GPS stream, so stop reporting that in the telemetry
stream, in the UI and writing it to eeprom.
Signed-off-by: Keith Packard <keithp@keithp.com>
Add date to GPS data, captured from GPRMC packet.2009-11-16T00:19:52+00:00Keith Packardkeithp@keithp.com2009-11-16T00:04:41+00:00urn:sha1:524665fc221b0d483453c67b7211e282cebc8980
Pull the date out of the GPS stream and send it over the telemetry
link and write it to the eeprom.
Signed-off-by: Keith Packard <keithp@keithp.com>
Initial packet bits. Just testing transmission2009-10-30T23:39:15+00:00Keith Packardkeithp@keithp.com2009-10-30T23:39:15+00:00urn:sha1:7b14c3e609749f4fc00dbd660541375048535218