Telco's know exactly what time it is. Although, frequency is much
more important than time. Central Offices use either Rb or Cs for a
Time Freq. standard. They need to keep all the trunk signals in
perfect sync to keep from loosing bits.
Cell sites generally use GPSDO's. Either OXCO or
Ah, the hazards of e-mail.
Glenn says, As for the blind leading the blind, AFAIK many
people on this list make their living designing/building/
selling precise timing products.
I never meant to say that the blind led the blind. Nor did
I comment on anyone's ability to use precision timing
[telcos]
They need to keep all the trunk signals in perfect sync to keep from
loosing bits.
That's not quite right.
You won't drop bits if the trunk is (slightly) faster than the source. I
think the protocols for encapsulating T1s in T3s and such have a slot for
that so telco-X can
From: xaos [EMAIL PROTECTED]
Subject: Re: [time-nuts] Progress of my HP Z3801A -- Ooops!
Date: Tue, 29 Aug 2006 18:42:45 -0400
Message-ID: [EMAIL PROTECTED]
Magnus,
George,
Arghhh... I forgot to include it in the build script.
It is there now as version 2.0.3. I double-checked and the file
On Wed, August 30, 2006 22:23, Magnus Danielson said:
The current state is on:
http://rubidium.dyndns.org/gpsdata/
Should this
Satellites(Tracking/Visible): 6/3
be read as; Tracking 6 SVs, 3 more should be visable over the 10 deg
horizon mask, but are not used now?
From: [EMAIL PROTECTED]
Subject: Re: [time-nuts] Progress of my HP Z3801A -- Ooops!
Date: Wed, 30 Aug 2006 22:59:07 +0200 (CEST)
Message-ID: [EMAIL PROTECTED]
On Wed, August 30, 2006 22:23, Magnus Danielson said:
The current state is on:
http://rubidium.dyndns.org/gpsdata/
Should this
First,
Ah, much better. After batteling the perl package hell (i.e. finding the
exact right Debian package that will make it tick) I now have it
running, but
now I need to figure out how to make it tick on automatic. I also
commented out
the cd /opt/ntp/timelord/shm || exit line from the G1
___
time-nuts mailing list
time-nuts@febo.com
https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
Hal Murray wrote:
[telcos]
They need to keep all the trunk signals in perfect sync to keep from
loosing bits.
That's not quite right.
You won't drop bits if the trunk is (slightly) faster than the source. I
think the protocols for encapsulating T1s in T3s and such have a slot for
I have observed that some cell phones set their clock when you power
them up, and others set it at regular time. Some automatically change
time zone as you travel and some don't, maybe due to the same process.
Didier KO4BB
Glenn wrote:
_Most_ cell phones set their time to network time.
CDMA phones have their clocks set by the system, as they require more precise
synchronization of not only the data stream bit timing, but also the
synchronization of the psuedo random key streams. These are used for syncing up
the Walsh codes as well as security encryption key functions.
Daun
Mangus,
Now, to the more problematic issue of time delay between
:SYST:STAT? invocation and receiver response.
I just wish that the information in the :SYSTEM:STATUS?
command was available separately.
Much of it is. I have reverse-engineered the actual SCPI command structure,
but
Any real ideas on how to make it work in coordination with NTP?
ntpd has a lot of logging. If you turn on clockstats you will get the info
from your refclocks, mostly a line with a timestamp and the raw data, like this:
53978 3319.033 127.127.26.1 T220060831005520339
53978 3383.033
Much of it is. I have reverse-engineered the actual SCPI command
structure, but I haven't had time to test them all. Besides, I
actually found an error in my analysis and haven't had time to fix it.
What did you uncover that wasn't in the manual?
--
The suespammers.org mail server is
Hal Murray writes:
Much of it is. I have reverse-engineered the actual SCPI command
structure, but I haven't had time to test them all. Besides, I
actually found an error in my analysis and haven't had time to fix it.
What did you uncover that wasn't in the manual?
Good explanation!
Daun
N8ASB
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of David I. Emery
Sent: Thursday, August 31, 2006 12:01 AM
To: Discussion of precise time and frequency measurement
Subject: Re: [time-nuts] Time syncing question
On Wed, Aug 30,
16 matches
Mail list logo
