From ac98b545a8c850bdaa16dc6e70d93d33f1cceaf4 Mon Sep 17 00:00:00 2001 From: Holger Hans Peter Freyther Date: Fri, 26 Jul 2013 21:23:40 +0200 Subject: sysmobts-calib: For gps the sign/difference appears to be different For the sysmoBTS 2050 this appears to have a different sign. We can't test this with NWL right now so we will need to see if this is a case of ping/pong. --- contrib/sysmobts-calib/sysmobts-calib.c | 10 ++++++++++ 1 file changed, 10 insertions(+) (limited to 'contrib') diff --git a/contrib/sysmobts-calib/sysmobts-calib.c b/contrib/sysmobts-calib/sysmobts-calib.c index 053032d5..a111d1d5 100644 --- a/contrib/sysmobts-calib/sysmobts-calib.c +++ b/contrib/sysmobts-calib/sysmobts-calib.c @@ -318,6 +318,16 @@ static int calib_get_clock_error(void) return -1; } + /* + * Empiric gps error determination. With revE and firmware v3.3 + * the clock error for TCXO to GPS appears to have a different + * sign. The device in question doesn't have a networklisten mode + * so it is impossible to verify that this only applies to GPS. + */ + if (source == SuperFemto_ClkSrcId_GpsPps) + clkErr *= -1; + + /* this is an absolute clock error */ printf("The calibration value is: %d\n", clkErr); return 0; -- cgit v1.2.3