Ticket #1824 (closed defect: fixed)
FSO: GPS time not available in TangoGPS
| Reported by: | hedora | Owned by: | alphaone |
|---|---|---|---|
| Priority: | normal | Milestone: | FSO |
| Component: | unknown | Version: | |
| Severity: | normal | Keywords: | |
| Cc: | Blocked By: | ||
| Blocking: | Estimated Completion (week): | ||
| HasPatchForReview: | no | PatchReviewResult: | |
| Reproducible: |
Description
The framework stuff seems to be stripping out the time info from the gps data. This breaks things like "average speed" and "trip duration" in TangoGPS, and likely prevents it from putting times in GPS traces. (Haven't confirmed the later).
Change History
comment:3 Changed 5 years ago by hedora
Updating to FSO-testing gives me a time in tango gps, but the 'trip duration' is still zero.
Worse, the GPS time says it's 7-1-1985, and the clock moved forward by 10-40 minutes each second. Perhaps the units used by gypsy don't match those expected by tangogps?
This happened during a stable, high quality GPS fix over a period of a few minutes. Haven't had time to see if its reproducible, but I've never seen it under 2007.2.
'opkg list_installed | grep tango' says:
tangogps-fso - 0.9.2-r1 -
comment:4 Changed 5 years ago by alphaone
- Status changed from new to assigned
- Owner changed from openmoko-devel to alphaone
tangogps-fso will go away soon and tangogps will just use the fso-gpsd compatibility layer. There might be new problems with that, but it should improve the situation. :-)
comment:5 Changed 5 years ago by alphaone
- Status changed from assigned to in_testing
- HasPatchForReview unset
Time report works well as soon as the GPS has current UTC time. GPS time is acquired pretty fast, but UTC parameters take considerable more time to update. Once we got the UTC parameters and (most important) the amount of leap seconds that UTC and GPS time are off we should get the time much faster on subsequent attempts (it should be instantaneous since we write the time back to the GPS chip).
You might need to let the FR sit with GPS enabled for quite a while to the the current UTC time, but then tangoGPS will show it.
Note that the system time needs to be correct for this to work. If it isn't then the time reported by the GPS chip will also be off by the same amount.
Please test with milestone4 and report back.
Yeah, the patch I wrote to make tangogps use the DBus signals is incomplete. (listening to the time is missing). We might think about another way so tangogps will get NMEA data again.