David,
The problem is that they start in sync and over the course of a day drift
that far apart despite having NTP running. We're not sure why NTP isn't
correcting it along the way. Though at this point, we are looking at a
firmware bug.
Thanks!
Bob
===
Bob,
OK, now I understand: you are not interested in anything less than 100K
seconds with your 1nS counter. Taking samples every 100K seconds from very
stable sources with a 1nS counter hides the entire step between (for
example) a 1E-14 and 2E-14. You can't see 1.1E-14, 1.2E-14, 1.3E-14 but,
yes, you
Hi
Yes, that's it exactly.
I knew we must be talking about to different things...
Bob
-Original Message-
From: time-nuts-boun...@febo.com [mailto:time-nuts-boun...@febo.com] On
Behalf Of Azelio Boriani
Sent: Friday, October 05, 2012 5:25 AM
To: Discussion of precise time and frequency
Very nice experiment on oscillator coupling:
http://blogs.discovermagazine.com/cosmicvariance/2012/10/01/you-are-getting-sleeepy/
Quite time-nuts style, I would say.
Marco IK1ODO
___
time-nuts mailing list -- time-nuts@febo.com
To unsubscribe,
Hi,
A long time ago (~1955), when mechanical watches were the only sort on
the market, and pocket watch (onions) were not only a curiosity, I
remember seeing in watchmaker showcase several of them suspended by
their ring on little hooks, and the coupling was enough to make the
oscillate in
That is his point.
Initial time comes from MB clock.
System (OS) time is set from that at boot.
During NTP startup for a client it is normal to do a ntpdate to hard
set the OS clock (direct one time set).
From there ntpd would track and adjust.
HOWEVER, there are limits to how much ntpd will
bow...@gmail.com said:
The problem is that they start in sync and over the course of a day drift
that far apart despite having NTP running. We're not sure why NTP isn't
correcting it along the way. Though at this point, we are looking at a
firmware bug.
I wouldn't think of it as two systems
On 10/05/2012 08:23 PM, Christopher Brown wrote:
That is his point.
Initial time comes from MB clock.
System (OS) time is set from that at boot.
During NTP startup for a client it is normal to do a ntpdate to hard
set the OS clock (direct one time set).
From there ntpd would track and
Comments inline.
On Oct 5, 2012, at 18:26, Hal Murray hmur...@megapathdsl.net wrote:
bow...@gmail.com said:
The problem is that they start in sync and over the course of a day drift
that far apart despite having NTP running. We're not sure why NTP isn't
correcting it along the way.
Hmmm - was just poking through leapsecond.com's /pages section.
Noticed a folder 'csac' dated Oct 3, 2012.
Guessing there will be some plots/test results in a little bit??
Early xmas?
Brent
On Thu, Oct 4, 2012 at 12:21 PM, Azelio Boriani
azelio.bori...@screen.it wrote:
Just sold. It was not
Alberto,
I have been reading the time-nuts archives and ran across a Feb 25, 2006
post where you mention you coded a GPSDO for an Atmel AT90s8535. Is
that code still available and could I please get a copy of it. Also, if
you have a schematic I would like to see same if possible.
Thanks,
Hmmm - was just poking through leapsecond.com's /pages section.
Noticed a folder 'csac' dated Oct 3, 2012.
Guessing there will be some plots/test results in a little bit??
Early xmas?
Brent
Brent,
Yes, I added that folder a few days ago when Kevin mentioned the CSAC GPSDO.
The data
12 matches
Mail list logo
