Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!mit-eddie!bbn!apple!sun-barr!texsun!texbell!vector!telecom-gateway From: vern@zebra.uucp Newsgroups: comp.dcom.telecom Subject: Re: Radio Time Sources Message-ID: Date: 20 May 89 19:33:01 GMT Sender: news@vector.Dallas.TX.US Lines: 31 Approved: telecom-request@vector.dallas.tx.us X-Submissions-To: telecom@eecs.nwu.edu X-Administrivia-To: telecom-request@vector.dallas.tx.us X-TELECOM-Digest: volume 9, issue 172, message 5 of 6 In article , @cs.utexas.edu:marcus@ osf.osf.org (Mark Roman) writes: > I am trying to get some information on radio clocks, specifically > the kind used to provide a reliable standard time for a LAN. I have been > recommended to Precision Standard Time Inc. in Fremont, CA. They make a > dandy clock called the Time Source, which is perfect for my needs. > It's a radio receiver tuned to WWV in CO, which puts out serial data > on an RS232 port. This data, as you might've guessed, is the decoded > time according to the NBS. Try calling the National Bureau of Standards at Boulder, CO. They have digital time available on 303-494-4774 at 300/1200 baud. Type an 'H' immediately after connecting for a blurb about the format and accuracy. The blurb tells how you can get the time to a couple of milli-seconds at your location. They calculate the round-trip propagation time and adjust their timing accordingly. Don't worry about excessive time charges, they disconnect after 50+- secs. so that your call will always be less tha one minute. This also makes the 8 or 10 lines available for more users. The 1200 baud message has more information such as Daylight Time change dates, Julian date etc. but the 300 baud is more accurate. (2-3 ms vs. 5-6 ms). Good Luck. Vernon C. Hoxie {ncar,nbires,boulder,isis}!scicom!zebra!vern 3975 W. 29th Ave. voice: 303-477-1780 Denver, Colo., 80212 uucp: 303-455-2670