From 1e138a6261ebed754409f292a8880e02e8a0ec44 Mon Sep 17 00:00:00 2001 From: Nuno Goncalves Date: Mon, 18 Jul 2016 14:55:36 -0700 Subject: 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 --- driver_tsip.c | 14 ++++++++++++-- 1 file changed, 12 insertions(+), 2 deletions(-) (limited to 'driver_tsip.c') 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 */ -- cgit v1.2.1