h
doesn't have this problem.
/tvb
- Original Message -
From: "Björn"
To: "Discussion of precise time and frequency measurement"
Sent: Saturday, July 04, 2015 1:30 PM
Subject: Re: [time-nuts] End of the World, or beginning of a new one?
"Yes the Tymserve an
"Yes the Tymserve and other similar DATUM / Symmetricom products which
use the Trimble ACE board will fail again in 2016. This is due to the
way the GPS epoch is calculated inside the 2100 : the DATUM engineers
estimated the future leap second insertions to determine GPS epochs,
which was not a
Michael A. Waldron writes:
>
> Olivier from Heol says that it will revert to 1995 again in a few
months, although he was unspecific as to the
> exact reasons he said they simulated it in their lab.
>
> I've decided I'd like to upgrade the GPS in my 2100-rb, but it will
probably be a little
Olivier from Heol says that it will revert to 1995 again in a few months,
although he was unspecific as to the exact reasons he said they simulated it in
their lab.
I've decided I'd like to upgrade the GPS in my 2100-rb, but it will probably be
a little while before I get the job done.
-Mike
As I look at my Tymserve 2100 sitting in the rack to my left, the date it's
displaying is JUL 02 2015.
So the week rollover bug was coupled to the leap second? No wine to drink today
(it's still early)...
Anyone else with a TS2100 that's suddenly acting strange, er, correct for the
first time
On Thu, Jul 02, 2015 at 04:47:02PM +, Frister wrote:
> To be honest, I didn't know that the sleep command could be utilized with a <1
> Foolish of me to not have tried it.
It's an extension, as sleep used to only work with integer numbers
of seconds, e.g.
http://pubs.opengroup.org/on
Thank you Martin,
To be honest, I didn't know that the sleep command could be utilized with a <1
Foolish of me to not have tried it.
On 02/07/2015, Martin Burnicki wrote:
> Frister wrote:
>> My NTP server did a double 59 on the terminal. for anybody who is
>> interested
>> I captured the even
Frister wrote:
My NTP server did a double 59 on the terminal. for anybody who is interested
I captured the event :
https://youtu.be/OpNci29CI7E
I think you need to be careful if you just watch the time in a loop with
a "sleep 1". Due to slightly varying sleep intervals the time when the
"date
Bob Camp wrote:
Well it sounds like there are (so far) no major reports of extreme behavior.
There still seem to be
*lots* of reports of systems that do not handle things gracefully. I wonder if
the data above is
specific to a chip set (which it probably is) or to how Glonass handles leap
sec
> As expected, on the leap second the display on the 8183 showed 6:59:60 (the
> 8183-A showed 23:59:60), but the TV400 displayed 7:00:00 at that moment.
> The TV400 remained one second ahead until it displayed 7:00:03 for a two-
> second period, then from 7:00:04 forward it was properly synced.
O
t...@leapsecond.com said:
> Am I reading this right -- those GPS receivers applied the leap second 16
> seconds before they were supposed to, resulting in a double 23:59:44 instead
> of 23:59:59 and 23:59:60? So not only did they use GPS instead of UTC but
> the opted for the double second instead
second.
/tvb
- Original Message -
From: "Hal Murray"
To: "Discussion of precise time and frequency measurement"
Cc:
Sent: Tuesday, June 30, 2015 8:38 PM
Subject: Re: [time-nuts] End Of The World
>> Any observations of anomalous behavior yet?
>
> From a BU-
Hi
> On Jul 1, 2015, at 6:25 AM, Martin Burnicki
> wrote:
>
> Bob Camp schrieb:
>> Hi
>>
>> So are we all still here? Any portion of the group blasted into
>> non-existance by the leap second please speak up :)
>>
>> ===
>>
>> Any observations of anomalous behavior yet?
>
> From a NVD8C-CSM
My NTP server did a double 59 on the terminal. for anybody who is interested
I captured the event :
https://youtu.be/OpNci29CI7E
I did measure an odd behaviour on leapsecond day from time-a.nist.gov NTP server
usually it runs about 8 mS behind my local PPS but all the sudden went
to +22 mS for
most
> Le 1 juil. 2015 à 09:02, Hal Murray a écrit :
>
>
> michael.c...@sfr.fr said:
>> Lady Heather just went told me 23:59:59 , 00:00:00 and stayed there for 2
>> secs, No 23:59:60 :-(
>
> What sort of device was it looking at?
>
a T-Bolt. Firmware 3.0 GPS 10.2 .Mfg. 2002. Leap status was "Lea
Bob Camp schrieb:
Hi
So are we all still here? Any portion of the group blasted into non-existance
by the leap second please speak up :)
===
Any observations of anomalous behavior yet?
From a NVD8C-CSM v3.1 module in Glonass-only mode:
$GPZDA,235958.00,30,06,2015,00,00*65
$GPGGA,235959.00,
At home I recorded the following seconds:
Tunderbolt GPSDO 58 59 60 00 01 02
Meinberg LANTIME M200 58 59 59 00 01 02
hopf DCF 7001 58 59 60 01 02 03
Conrad DCF Time Terminal 58 59 00 01 02 03
The (old 1999) DCF hopf clock in particular was a strange one. It
announced a
time-nuts@febo.com said:
> As expected, on the leap second the display on the 8183 showed 6:59:60 (the
> 8183-A showed 23:59:60), but the TV400 displayed 7:00:00 at that moment. The
> TV400 remained one second ahead until it displayed 7:00:03 for a two-second
> period, then from 7:00:04 forward it
michael.c...@sfr.fr said:
> Lady Heather just went told me 23:59:59 , 00:00:00 and stayed there for 2
> secs, No 23:59:60 :-(
What sort of device was it looking at?
--
These are my opinions. I hate spam.
___
time-nuts mailing list -- time-nuts@f
Lady Heather just went told me 23:59:59 , 00:00:00 and stayed there for 2 secs,
No 23:59:60 :-(
> Le 1 juil. 2015 à 03:03, Bob Camp a écrit :
>
> Hi
>
> So are we all still here? Any portion of the group blasted into non-existance
> by the leap second please speak up :)
>
> ===
>
> Any obs
On Wed, Jul 1, 2015 at 1:03 AM, Bob Camp wrote:
> Hi
>
> So are we all still here? Any portion of the group blasted into non-existance
> by the leap second please speak up :)
>
> ===
>
> Any observations of anomalous behavior yet?
I was eagerly connecting to various things to watch for problems
Hi,
Some of us have found ourselves in Besancon this week for the EFTS,
which is extraordinary but not strange.
I found myself explaining Delta and Omega counter responses with
hockey-puck ADEV responces on the whiteboard for the lab-session.
Cheers,
Magnus
On 07/01/2015 03:03 AM, Bob Camp
.
HAPPY LEAP EVENT EVERYONE!!
Respectfully,
Sean Gallagher
Malware Analyst
571-340-3475
-- Original Message --
From: "Bob Camp"
To: "Discussion of precise time and frequency measurement"
Sent: 6/30/2015 9:03:30 PM
Subject: [time-nuts] End Of The World
Hi
So are we
---
Date: Tue, 30 Jun 2015 21:03:30 -0400
From: Bob Camp
To: Discussion of precise time and frequency measurement
Subject: [time-nuts] End Of The World
Message-ID: <66d6b7a9-aa39-4d5d-8a34-dd5f78488...@n1k.org>
Content-Type: text/plain; charset=us-ascii
Hi
So are we all still her
..@febo.com] On Behalf Of Bob Camp
Sent: Tuesday, June 30, 2015 8:04 PM
To: Discussion of precise time and frequency measurement
Subject: [time-nuts] End Of The World
Hi
So are we all still here? Any portion of the group blasted into non-existance
by the leap second please speak up :)
===
Any
> Any observations of anomalous behavior yet?
>From a BU-353:
57203 86380.750 $GPRMC,235940.000,A,3726.0893,N,12212.2627,W,0.52,64.49,300615
,,*20
57203 86381.748 $GPRMC,235941.000,A,3726.0889,N,12212.2627,W,0.45,78.54,300615
,,*2D
57203 86383.138 $GPRMC,235942.000,A,3726.0883,N,12212.2627,W,0.82,
Hi
So are we all still here? Any portion of the group blasted into non-existance
by the leap second please speak up :)
===
Any observations of anomalous behavior yet?
Bob
___
time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to https://
27 matches
Mail list logo
