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

Mark Sims holrum at hotmail.com
Tue Jul 19 22:46:53 EDT 2016

I get the Z3801A leap pending flag from the #T1 or #T2 time stamp in the :PTIM:TCOD? response.   For the date, either :PTIM:LEAP:DATE? or :PTIM:LEAP:GPST? depending upon the unit type.

And now for some more receiver leapsecond shenanagins:

The Ublox receivers work well.  You can calculate the day of the leapsecond from almanac info (gps week and day-of-week) returned in the 0x0B 0x02 leapsecond message.

The Trimble receivers have a leap pending flag in the primary timing message.  They also have a message (0x58, subcode 5) that returns the data needed to calculate the date of the leapsecond.   However, the GPS week number it returns is not compensated for week rollovers.   You need to do that yourself.   Also, don't send the original (non-SMT) Resolution-T receiver the 0x38 message to request the 0x58 message.  Doing that causes the receiver to get confused for at least three seconds.

The Motorola VP/UT/M12 receivers send the leap pending flag in the @@Bj message.  It is supposed to work in all Motorola receivers,  but the M12+ always reports no leap pending.  The M12's have an @@Gj message that reports the date of the leapsecond,  It says 2017/01/01,  not 2016/12/31.

None of the other receivers have messages that report leapsecond related info.
> Which messages are you looking at? 		 	   		  

More information about the time-nuts mailing list