Leap second bug in BNC

[k.fenaughty]

We are running v2.6 of BNC. The latency calculations produced by this software have been incorrect since the leap second of July 1 2012. The bug is in the module rtcm3torinex.c which does not feature the latest leap second.

The result is that latency messages are being logged every second instead of at the proscribed interval (perfIntr), and of course the calculations are wrong (negative latencies!).

[k.fenaughty]

It was pointed out to me by a colleague that you have already found the above bug and fixed the source code in late June and early July. When can we expect new executables to be available from the GNSS Data Center? This is causing a major impact with measuring quality of service for our GNSS streams in the meantime.

Thanks,
Kevin Fenaughty

[pgentle@…]

This issue is also affecting our stats reporting for our service.

Are you able to inform us when you will be releasing the fix?

I could get our programmers to look at it but I don't want to waste their time if you will be releasing it in the next couple of days.

Thanks

[stuerze]

The leap seconds within the current module rtcm3torinex.c are up to date