irst negative leap second before 2030. See
http://leapsecond.com/pages/lod/earth-lod-10.gif which I need to update from
last year, but you get the idea.
/tvb
- Original Message -
From: "Hans Holzach"
To:
Sent: Sunday, January 25, 2015 8:03 AM
Subject: Re: [time-nuts] GP
Hans,
For POSIX type clocks, 1 July 2015 will have two seconds denoted
00:00:00, but for real UTC clocks it will be 30 June that has 23:59:59
and 23:59:60.
You will be at UTC+2h since it will be summer-time.
Cheers,
Magnus
On 01/25/2015 05:03 PM, Hans Holzach wrote:
true, this depends on t
I agree, it looks kinda OK, even if a bit of unconventional format.
Would be interesting to hear the motivation for not listing it at the
last of June.
Cheers,
Magnus
On 01/25/2015 03:59 PM, Tom Van Baak wrote:
Well, Said can tell us for sure (since he owns the firmware in the Fury) but
you
true, this depends on the definition of "pending". however, i found it a
bit odd that the software reports a scheduled (but not pending this
month) leap second on july 1st. it's june 30 that is 86401 seconds long,
not the day after. in my opinion there is nothing between june 30 and
july 1 that
Well, Said can tell us for sure (since he owns the firmware in the Fury) but
you could call this is correct, because:
1) a leap second is not pending this month
2) the current leap second count is still 16
3) the next leap second happen between 2015-06-30 and 2015-07-01
4) the current month ends
my jackson labs fury (1.22) reports:
leapsecond pending: 0
leapsecond accumulated: 16
leapsecond date: 2015,7,1
leapsecond duration: 60
strange...
hans
___
time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to https://www.febo.com/cgi-bin
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
And not to be left out of the pre-leap second party, those of you with
HP/Symmetricom SmartClock's can also have fun. That would include the
58503-series T&F standards as well as most of the Z38-series. Send these
commands ASAP and (surprise) see what you get:
*cls
:ptim:leap:acc?
:
At 7:39 AM -0700 8/5/05, Tom Van Baak wrote:
By the way, if someone has access to world
population sorted by timezone see if you can
calculate the exact percentage of people left
of Greenwich vs. right of Greenwich.
/tvb
This photo could be used for the raw data, since it approximates the
nu
Tom Van Baak wrote:
>While I get to preview UTC New Years or leap
>seconds at 4 PM PST here in Seattle (UTC-8),
>there's a billion people in China (UTC+8) that
>have to wait until 8 AM on Jan 1.
>
>
Slightly off-topic, but this brings back memories of Y2K. I was on our
company's SWAT team ("The
In message <[EMAIL PROTECTED]>, "Tom Van Baak" writes:
>By the way, if someone has access to world
>population sorted by timezone see if you can
>calculate the exact percentage of people left
>of Greenwich vs. right of Greenwich.
CIA's factbook ?
--
Poul-Henning Kamp | UNIX since Zilog Ze
> On the other hand, I'm still wondering if the data itself is correct.
> It looks like @@Gj is saying that the leap second will occur on Jan. 1
> at 00:00:00. Is that the correct thing for this message to indicate for
> a leap second that will occur on Dec. 31 at 23:59:60? Perhaps the @@Gj
In message <[EMAIL PROTECTED]>, Jim King writes:
>On the other hand, I'm still wondering if the data itself is correct.
>It looks like @@Gj is saying that the leap second will occur on Jan. 1
>at 00:00:00. Is that the correct thing for this message to indicate for
>a leap second that will occ
Poul-Henning Kamp wrote:
In message <[EMAIL PROTECTED]>, Jim King writes:
M. Warner Losh wrote:
We started seeing the GPS future leap second being broadcast today
here. Just as a sanity check, are others seeing it as well?
Warner
I noticed it yesterday in my ntpd clockstats
In message <[EMAIL PROTECTED]>, Jim King writes:
>M. Warner Losh wrote:
>
>>We started seeing the GPS future leap second being broadcast today
>>here. Just as a sanity check, are others seeing it as well?
>>
>>Warner
>>
>>
>
>I noticed it yesterday in my ntpd clockstats file, although in a
>som
In message <[EMAIL PROTECTED]>, "Tom Van Baak" writes:
>Yes, I see it with my Trimble Resolution-T but not
>with my 58503A yet. Last time Oncore VP's didn't
>like so much notice. It will be interesting to see
>what happens with them.
I just checked my Oncore UT+.
@@Gj says 2006-01-01 00:00:00
@
From: "Tom Van Baak" <[EMAIL PROTECTED]>
Subject: Re: [time-nuts] GPS Leap Second
Date: Thu, 4 Aug 2005 15:53:51 -0700
Message-ID: <[EMAIL PROTECTED]>
Tom,
> > Warner,
> >
> > > We started seeing the GPS future leap second being broadcast today
>
In message: <[EMAIL PROTECTED]>
"Poul-Henning Kamp" <[EMAIL PROTECTED]> writes:
: So even though there is still four months to the leapsecond, we
: have already found the first bug ?
Well, rediscovered. The old timers at work predicted this would
happen w/o updated firmware to the sma
In message <[EMAIL PROTECTED]>, "Tom Van Baak" writes:
>I think it's a simple HP firmware bug where they
>sort of took the leap second guidelines too literally:
>
>"first preference is given to the opportunities at
> the end of December and June, and second
> preference to those at the end of Marc
> > Yeah, my 58503B SmartClock just picked it up too.
> > But as I suspected, based on what was reported in
> > 1998, it has the date wrong:
> >
> > scpi > ptime:leap?
> > 1
> > scpi > ptime:leap:stat?
> > 1
> > scpi > ptime:leap:acc?
> > +13
> > scpi > ptime
> Warner,
>
> > We started seeing the GPS future leap second being broadcast today
> > here. Just as a sanity check, are others seeing it as well?
>
> I see it too on my Z3801A. "+1 leap second pending".
>
> Cheers,
> Magnus
Yeah, my 58503B SmartClock just picked it up too.
But as I suspected,
From: "M. Warner Losh" <[EMAIL PROTECTED]>
Subject: [time-nuts] GPS Leap Second
Date: Thu, 04 Aug 2005 11:24:38 -0600 (MDT)
Message-ID: <[EMAIL PROTECTED]>
Warner,
> We started seeing the GPS future leap second being broadcast today
> here. Just as a sanity check,
day, August 04, 2005 10:24
Subject: [time-nuts] GPS Leap Second
> We started seeing the GPS future leap second being broadcast today
> here. Just as a sanity check, are others seeing it as well?
>
> Warner
___
time-nuts mailing list
t
M. Warner Losh wrote:
We started seeing the GPS future leap second being broadcast today
here. Just as a sanity check, are others seeing it as well?
Warner
I noticed it yesterday in my ntpd clockstats file, although in a
somewhat alarming fashion:
53586 1.311 127.127.30.0 ONCORE[0]: Le
We started seeing the GPS future leap second being broadcast today
here. Just as a sanity check, are others seeing it as well?
Warner
___
time-nuts mailing list
time-nuts@febo.com
https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
31 matches
Mail list logo
