Hello,



Does anyone know of a comprehensive list of time synchronization hardware
and software?



Thanks



Al

Alkruse@gmail.com
_______________________________________________
questions mailing list
questions@lists.ntp.isc.org
https://lists.ntp.isc.org/mailman/listinfo/questions

Alan Kruse wrote:

>Hello,
>
>
>
>Does anyone know of a comprehensive list of time synchronization hardware
>and software?
>
>
>
>Thanks
>
>
>
>Al
>
>Alkruse@gmail.com
>_______________________________________________
>questions mailing list
>questions@lists.ntp.isc.org
>https://lists.ntp.isc.org/mailman/listinfo/questions
>
>  
>
It's not quite what you asked for but:

Publishers of Computer Time Synchronization Software 
<http://tf.nist.gov/timefreq/general/softwarelist.htm>

and

Manufacturers of Time and Frequency Receivers 
<http://tf.nist.gov/timefreq/general/receiverlist.htm>

Hi there


"Richard B. Gilbert" wrote:

> It's not quite what you asked for but:
> 
> Publishers of Computer Time Synchronization Software
> <http://tf.nist.gov/timefreq/general/softwarelist.htm>
> 
> and
> 
> Manufacturers of Time and Frequency Receivers
> <http://tf.nist.gov/timefreq/general/receiverlist.htm>

Comments on which of these actually handled the leap second correctly would
be nice.


Regards,
Rob
-- 
+----------------------------------------------------------------------+
|                   Rob van der Putten, rob@sput.nl                    |
|               http://www.sput.nl/spam/spam-policy.html               |
+----------------------------------------------------------------------+

Rob van der Putten wrote:
> 
> Comments on which of these actually handled the leap second correctly would
> be nice.
> 
That's still being reviewed, having just gotten through the first
leap-second event in 7 years.

Danny
_______________________________________________
questions mailing list
questions@lists.ntp.isc.org
https://lists.ntp.isc.org/mailman/listinfo/questions

Rob,

I can confirm that the Spectracom GPS and WWVB receivers, Arbiter GPS 
receiver, TrueTime NTS-200 GPS/NTP server, WWV/H audio driver and those 
systems with the NIST leapsecond file, either via ftp or Autokey, 
handled the lurch correctly. On the other hand, the EndRun CDMA/NTP 
server took about five minutes to lurch.

Dave

Rob van der Putten wrote:
> Hi there
> 
> 
> "Richard B. Gilbert" wrote:
> 
> 
>>It's not quite what you asked for but:
>>
>>Publishers of Computer Time Synchronization Software
>><http://tf.nist.gov/timefreq/general/softwarelist.htm>
>>
>>and
>>
>>Manufacturers of Time and Frequency Receivers
>><http://tf.nist.gov/timefreq/general/receiverlist.htm>
> 
> 
> Comments on which of these actually handled the leap second correctly would
> be nice.
> 
> 
> Regards,
> Rob

David L. Mills wrote:
> Rob,
> 
> I can confirm that the Spectracom GPS and WWVB receivers, Arbiter GPS 
> receiver, TrueTime NTS-200 GPS/NTP server, WWV/H audio driver and those 
> systems with the NIST leapsecond file, either via ftp or Autokey, 
> handled the lurch correctly. On the other hand, the EndRun CDMA/NTP 
> server took about five minutes to lurch.
> 
> Dave

My Spectracom 8170 did *not* handle the leapsecond correctly, and a 
reading of the manual after the fact indicates that it wasn't meant to:

"Once the Time Sync light is on the clock will keep UTC time. The 
display will be changed when 3 consecutive good compares are received 
that do not agree with the display data. This will happen when the leap 
second is inserted."


It updated by holding for a second at 00:03:59.

The algorithm apparently ignores the leapsecond flag in the timecode, 
and works as follows: at 00:01:00, WWVB tells the clock that it is a 
second fast.  At 00:02:00 and 00:03:00 that is confirmed.  The display 
updates at 00:03:59.

I'm not sure why it waited until the end of the third minute, rather 
than the beginning, to make the change, but that's what happened. 
(timestamp extract at the bottom of 
http://www.febo.com/time-freq/leapsecond-2005/index.html).

John
_______________________________________________
questions mailing list
questions@lists.ntp.isc.org
https://lists.ntp.isc.org/mailman/listinfo/questions

David L. Mills wrote:

> Rob,
>
> I can confirm that the Spectracom GPS and WWVB receivers, Arbiter GPS 
> receiver, TrueTime NTS-200 GPS/NTP server, WWV/H audio driver and 
> those systems with the NIST leapsecond file, either via ftp or 
> Autokey, handled the lurch correctly. On the other hand, the EndRun 
> CDMA/NTP server took about five minutes to lurch.
>
> Dave
>
> Rob van der Putten wrote:
>
>> Hi there
>>
>>
>> "Richard B. Gilbert" wrote:
>>
>>
>>> It's not quite what you asked for but:
>>>
>>> Publishers of Computer Time Synchronization Software
>>> <http://tf.nist.gov/timefreq/general/softwarelist.htm>
>>>
>>> and
>>>
>>> Manufacturers of Time and Frequency Receivers
>>> <http://tf.nist.gov/timefreq/general/receiverlist.htm>
>>
>>
>>
>> Comments on which of these actually handled the leap second correctly 
>> would
>> be nice.
>>
>>
>> Regards,
>> Rob
>
Where can I get the leap second file by ftp?  I've looked on the NIST 
web site and failed to find it.   They display the leap second 
information but I don't see a link to where it's available for 
download.  Getting it by autokey is not an option; I'm behind a NAT 
firewall/router.

I found this.

ftp://hpiers.obspm.fr/iers/bul/bulc/TimeSteps.history

Paul

Richard B. Gilbert wrote:
> Where can I get the leap second file by ftp?  I've looked on the NIST
> web site and failed to find it.   They display the leap second
> information but I don't see a link to where it's available for
> download.  Getting it by autokey is not an option; I'm behind a NAT
> firewall/router.

The file is available at
ftp://time.nist.gov/pub/

Filename: leap-seconds.nnnnnnnnnn
where nnnnnnnnnn is a kind of "serial number" derived from a time stamp.

The current name of the file is: leap-seconds.3331497600

This file must be copied to the crypto directory configured for ntpd, and
inside that directory a link must created which points to that file. The
standard name for the link is ntpkey_leap, however, this can be overridden
by a configuration parameter. 

So currently it should look like this:
ntpkey_leap -> leap-seconds.3331497600


Martin
-- 
Martin Burnicki

Meinberg Funkuhren
Bad Pyrmont
Germany

Please consider adding this information to, say, a "Leap Seconds" page, at
the end of the current list of things at http://ntp.isc.org/Support/ .

H

alkruse@gmail.com (Alan Kruse) writes:

> Hello,
> 
> 
> 
> Does anyone know of a comprehensive list of time synchronization hardware
> and software?

As comprehensive as the Internet, or as comprehensive as a Google search?

Regards,
Ulrich