diff options
author | Nuno Goncalves <nunojpg@gmail.com> | 2016-07-18 14:55:36 -0700 |
---|---|---|
committer | Gary E. Miller <gem@rellim.com> | 2016-07-18 14:55:36 -0700 |
commit | 1e138a6261ebed754409f292a8880e02e8a0ec44 (patch) | |
tree | 97fa56f172635c2d633c0d7165efe53025f876c0 | |
parent | 247b56166f2038a3afc1450cfee17d80bceecc02 (diff) | |
download | gpsd-1e138a6261ebed754409f292a8880e02e8a0ec44.tar.gz |
TSIP: fix time offset
The Trimble serial time offset is all over the map. Give up on
taking a best guess.
Signed-off-by: Gary E. Miller <gem@rellim.com>
-rw-r--r-- | driver_tsip.c | 14 |
1 files changed, 12 insertions, 2 deletions
diff --git a/driver_tsip.c b/driver_tsip.c index 5647c97e..8685297f 100644 --- a/driver_tsip.c +++ b/driver_tsip.c @@ -1129,8 +1129,18 @@ static void tsip_mode(struct gps_device_t *session, int mode) #ifdef TIMEHINT_ENABLE static double tsip_time_offset(struct gps_device_t *session UNUSED) { - /* FIX-ME: is a constant offset right here? */ - return 0.075; + /* + * the offset depends on the generation and is not reliable, it often + * depends on the number of SV being tracked + * some example measurements: + * Trimble Resolution T : 0.03s to 0.200s + * Trimble Resolution SMTx: 0.300 to 0.500s (unpredictable) + * Trimble RES SMT 360 : 0.028s (this appears very stable) + * + * Trimble users tend to be very picky, so we leave the offset to them. + * If we could detect the Trimble model maybe we could pick an offset. + */ + return 0.0; } #endif /* TIMEHINT_ENABLE */ |