Re: [time-nuts] Leap second to be introduced at midnight UTC December 31 this year
noah.robin@gmail.com said:
Discovered that my commercial GPS appliances opted to apply yesterday's
pending leap second, which has made for an interesting day.
Could you please say more?
How are you working around it?
Vendor? Model? Can you take the cover off (or peer in through the vents)
and see what type of GPS receiver they are using?
I assume the gear is recent or the problem would have been discovered the
last time we had a leap second. Have you contacted the vendor? Have they
confirmed the problem? Any estimate on when they will ship new firmware?
Has anybody else noticed the problem? (I tried google news and NANOG but
didn't find anything.)
--
These are my opinions. I hate spam.
On Jul 21, 2016, at 5:23 AM, Hal Murray hmurray@megapathdsl.net wrote:
noah.robin@gmail.com said:
Discovered that my commercial GPS appliances opted to apply yesterday's
pending leap second, which has made for an interesting day.
Could you please say more?
How are you working around it?
Vendor? Model? Can you take the cover off (or peer in through the vents)
and see what type of GPS receiver they are using?
In earlier email.
I assume the gear is recent or the problem would have been discovered the
last time we had a leap second. Have you contacted the vendor? Have they
confirmed the problem? Any estimate on when they will ship new firmware?
We just finished replacing our previous gear with this a week ago; timing is everything. :) Vendor was contacted yesterday and have supplied a patch this morning to reduce the GPS->UTC offset back to 17 until they get a more permanent fix from Trimble. I've not installed it yet, but the vendor states the patch won't persist across reboots.
--n
Every year... always makes me wonder, do these vendors even test this themselves? I know at least one vendor who disn't have GPS simulators and relied on Trimble's built-in test mode - which gives you 13-bit week counters, whereas the satellites give you 10-bit counters. So the vendor assumed 13-bit and was comparing the current wc to 13-bit that never came. Luckily I found the issue months before the event, and only because we purchased GPS simulators - which I recommend to anyone running timing services in production.
Oh well, at least this keeps us busy.
Original Message
From:noah.robin@gmail.com
Sent:21 July 2016 5:11 p.m.
To:time-nuts@febo.com
Reply to:time-nuts@febo.com
Cc:hmurray@megapathdsl.net
Subject:Re: [time-nuts] Leap second to be introduced at midnight UTC December 31 this year
On Jul 21, 2016, at 5:23 AM, Hal Murray hmurray@megapathdsl.net wrote:
noah.robin@gmail.com said:
Discovered that my commercial GPS appliances opted to apply yesterday's
pending leap second, which has made for an interesting day.
Could you please say more?
How are you working around it?
Vendor? Model? Can you take the cover off (or peer in through the vents)
and see what type of GPS receiver they are using?
In earlier email.
I assume the gear is recent or the problem would have been discovered the
last time we had a leap second. Have you contacted the vendor? Have they
confirmed the problem? Any estimate on when they will ship new firmware?
We just finished replacing our previous gear with this a week ago; timing is everything. :) Vendor was contacted yesterday and have supplied a patch this morning to reduce the GPS->UTC offset back to 17 until they get a more permanent fix from Trimble. I've not installed it yet, but the vendor states the patch won't persist across reboots.
--n
time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.
Follow up: Spectracom has released an official document which broadens the known impact to include their Accutime GG antenna:
http://support.spectracom.com/articles/FAQ/Why-is-there-a-1-second-time-error-from-my-GPS-reference
On Jul 21, 2016, at 12:02 PM, Noah noah.robin@gmail.com wrote:
On Jul 21, 2016, at 5:23 AM, Hal Murray hmurray@megapathdsl.net wrote:
noah.robin@gmail.com said:
Discovered that my commercial GPS appliances opted to apply yesterday's
pending leap second, which has made for an interesting day.
Could you please say more?
How are you working around it?
Vendor? Model? Can you take the cover off (or peer in through the vents)
and see what type of GPS receiver they are using?
In earlier email.
I assume the gear is recent or the problem would have been discovered the
last time we had a leap second. Have you contacted the vendor? Have they
confirmed the problem? Any estimate on when they will ship new firmware?
We just finished replacing our previous gear with this a week ago; timing is everything. :) Vendor was contacted yesterday and have supplied a patch this morning to reduce the GPS->UTC offset back to 17 until they get a more permanent fix from Trimble. I've not installed it yet, but the vendor states the patch won't persist across reboots.
--n