Re: [time-nuts] Leap second to be introduced at midnight UTC December 31 this year

[Noah]

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.ro...@gmail.com> wrote:
> 
> 
> 
>> On Jul 21, 2016, at 5:23 AM, Hal Murray <hmur...@megapathdsl.net> wrote:
>> 
>> 
>> noah.ro...@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.

Re: [time-nuts] Leap second to be introduced at midnight UTC December 31 this year

[Noah]

> On Jul 21, 2016, at 5:23 AM, Hal Murray  wrote:
> 
> 
> noah.ro...@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.

Re: [time-nuts] Leap second to be introduced at midnight UTC December 31 this year

[Noah]

Trimble Res-SMT-GG GNSS receivers are affected; in my case, they're installed 
in Spectracom SecureSyncs. And yes, the extra second got into system time which 
broke 1 or 2 things. 

--n

> On Jul 20, 2016, at 5:26 PM, Gary E. Miller <g...@rellim.com> wrote:
> 
> Yo Noah!
> 
> On Wed, 20 Jul 2016 17:12:14 -0400
> Noah <noah.ro...@gmail.com> wrote:
> 
>> First time poster; just subbed. Not a time hobbies the; my team @
>> work runs NTP infrastructure. So , that's a brief intro out of the
>> way...
> 
> Yes, a few of us NTP people here.  We are several orders of magnitude
> coarser tham a true time-nut.
>> 
>> Discovered that my commercial GPS appliances opted to *apply*
>> yesterday's pending leap second, which has made for an interesting
>> day.
> 
> Got any details?  GPS model?  Did it get past your NTP into system time?
> 
> I'm passing this info onto NTPsec devel folks.  Time to 'Name and Shame".
> 
> RGDS
> GARY
> ---
> Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
>g...@rellim.com  Tel:+1 541 382 8588
___
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.

Re: [time-nuts] Leap second to be introduced at midnight UTC December 31 this year

[Noah]

First time poster; just subbed. Not a time hobbies the; my team @ work runs NTP 
infrastructure. So , that's a brief intro out of the way...

Discovered that my commercial GPS appliances opted to *apply* yesterday's 
pending leap second, which has made for an interesting day.

--n

>> On Jul 19, 2016, at 8:39 PM, Jay Grizzard  
>> wrote:
>> 
>> On Tue, Jul 19, 2016 at 11:39:29PM +, Mark Sims wrote:
>> The GPS satellites are now reporting the pending leapsecond...
>> 
>> The Z3801A has it messed up...  it says the leap will occur on 30 Sep
>> 2016 (73 days).  The Z3801A has two different messages that report the
>> leap day...  both are wrong. 
> 
> I think some (modern!) Trimble gear may also has a problem. I have an ICM 
> SMT 360 board that's (slowly) flipping back and forth between showing a UTC
> offset of 17 seconds and an offset of 18 seconds. This is their currently
> shipping timekeeping chip, so it's surprising, but I don't know how else
> to explain the behavior outside of a firmware bug.
> 
> (I've sent an email to Trimble support, but haven't heard anything back yet.)
> 
> -j
> ___
> 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.
___
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.