My Ball/EFRATOM MFS-209's MGPS receiver has announced there is a
leap second scheduled for 6/30/2015 at midnite.
The MGPS's engine is a 6 channel Trimble of some sort.
-Chuck Harris
Götz Romahn wrote:
my monitor ( see http://www.romahn.info/tbolt2lcd/ ) also shows "leap sec
pending".
This inf
my monitor ( see http://www.romahn.info/tbolt2lcd/ ) also shows "leap
sec pending". This info is from Thunderbolt.
Götz
=
I see no spurious indications from the NTP servers I happen to be using. I
wrote a program to check:
http://www.satsignal.eu/software/net.
my monitor ( see http://www.romahn.info/tbolt2lcd/ ) also shows "leap
sec pending". This info is from Thunderbolt.
Götz
Am 23.01.2015 um 04:38 schrieb Didier Juges:
Re: "Note that this is not a GPS problem, nor a Trimble problem. It's just
a problem with user written software."
I agree with Ma
Agreed that simply showing the status of the leap-pending bit is the logical
thing to do, and it's definitely not something I would call a bug. It would be
extremely cool, though, if it used the data from packet 0x58 to display a
countdown timer. I'd volunteer to make the change, but I have an
Re: "Note that this is not a GPS problem, nor a Trimble problem. It's just
a problem with user written software."
I agree with Mark's comment. His software makes no attempt to "interpret"
or "correct" the information put out by the Thunderbolt, it simply reports
it. My Thunderbolt Monitor does the
Nope, it's not an error or a problem.
That column of data is showing a decode of the 16 status bits that the Tbolt is
providing.The Trimble docs say that bit is a "Leap Pending" bit, so that
is what Heather displays. It would be wrong to try and mask/adjust the report
of the receiver's
I was just sent a nice TBolt / Heather.exe screenshot from alert time-nuts
reader Steven Reyer showing "LEAP PENDING!".
The good news is that, yes, there will be another leap second (in June).
The bad news is that, no, there is not a leap second at the end of this month
(January) nor at the end
