Chris writes:
For most users I think that is reasonable. It's just not what one
expects to read on a Time Nuts list. Here we expect to see posting
from true nut-cases who want microsecond just because they can do it.
But how can you verify microsecond accuracy on Windows? Even the OS
only
On Mon, Mar 25, 2013 at 9:46 PM, Hal Murray hmur...@megapathdsl.net wrote:
albertson.ch...@gmail.com said:
I think you can get Windows to run at the few milliseconds of error range
with the standard NTP distribution.
I don't think I've seen anything that bad, but it's easy to be off by 100s
On Mon, Mar 25, 2013 at 10:56 PM, Anthony G. Atkielski
anth...@atkielski.com wrote:
Chris writes:
For most users I think that is reasonable. It's just not what one
expects to read on a Time Nuts list. Here we expect to see posting
from true nut-cases who want microsecond just because they
From: Anthony G. Atkielski
[]
I've been using the standard NTP client in Windows XP for ages, and it
works just fine. I tried third-party stuff. It was just more work for
no apparent gain. The XP desktop is synchronized with my NTP server
perfectly within the limits of my perception, so there is
From: Anthony G. Atkielski
[]
But how can you verify microsecond accuracy on Windows? Even the OS only has
10 ms resolution for the system clock.
[]
Anthony
===
Anthony,
I appreciate that your needs don't include accurate PC time, but for the
record
On Tue, 26 Mar 2013 05:05:26 +0100, Anthony G. Atkielski
anth...@atkielski.com wrote:
Dan (I think) writes:
Because, up until today, windows time did what I needed it to do. It may
still, if the fault turns out to be network related.
In reality, it's more software to learn to administer, and
davidwh...@gmail.com said:
I have had trouble with the built in XP NTP client where it fails silently
so I usually install Tardis which keeps an easy to read log which includes
performance data.
One of the problems with timekeeping is the load on the servers.
The standard ntpd package tries
Hi
One very important thing to consider when looking at this design - it was done
in the era of selective availability. That provided a lot dither all by it's
self.
Bob
On Mar 25, 2013, at 10:05 PM, Richard H McCorkle mccor...@ptialaska.net
wrote:
Bob,
You are preaching to the choir and
On Mon, Mar 25, 2013 at 11:16 PM, Tom Van Baak t...@leapsecond.com wrote:
Both edges of the 24MHz clock gating pulse are asynchronous with respect
to the signal being gated.
Metastability can result with clock pulse widths that lie within a
critical range.
Bruce
I don't disagree with your
On Tue, Mar 26, 2013 at 12:41 AM, Hal Murray hmur...@megapathdsl.net wrote:
davidwh...@gmail.com said:
I have had trouble with the built in XP NTP client where it fails silently
so I usually install Tardis which keeps an easy to read log which includes
performance data.
One of the problems
I think using satellite Dave's plot routines is the way to tweak NTP. If you
update too often, you can see the disturbance. This isn't a scientific
solution, but a practical one.
___
time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to
I should of been clearer, Thanks for your comments.
final configuration is:
OCXO as a 10 MHz reference to the 106.5 MHz PLL then the DB6NT
multiplier chain for the LO.
All of the stability I need for a contest weekend.
Stan, W1LE
On 3/26/2013 1:21 AM, Rex wrote:
Please tell us if I am
On 3/26/2013 2:43 AM, time-nuts-requ...@febo.com wrote:
albertson.ch...@gmail.com said:
I think you can get Windows to run at the few milliseconds of error range
with the standard NTP distribution.
I don't think I've seen anything that bad, but it's easy to be off by 100s of
ms if I download
On 3/26/2013 7:21 PM, Dan Kemppainen wrote:
Keep in mind, we are after all, taking about windows. An operating
system that IS NOT real time operating system. (You think it is, try
move a continuous stream of a few 6+ MBytes/Sec data to it!)
Well, the Perseus SDR, when set to its maximum
within network latency of around a second or so
A second is a long time/distance for a packet.
The measured round trip time from California to Maine is under 100 ms.
Sanity check: The US is 3000 miles east-west. A mile is 5000 feet. The
speed of light is 1 ft/ns in vacuum. So that's
Hi
All the stability and likely 20 to 30 db better phase noise. Probably 40 to 60
db better spurs / crud.
Bob
On Mar 26, 2013, at 12:31 PM, Stan, W1LE stanw...@verizon.net wrote:
I should of been clearer, Thanks for your comments.
final configuration is:
OCXO as a 10 MHz reference to
Hi
The worst case (this time) are errors in the bottom 5 bits. The software will
treat them as valid data. That assumes things stay simple. You are looking a
counter that wraps around a lot of times….
Bob
On Mar 26, 2013, at 7:33 AM, Javier Serrano javier.serrano.par...@gmail.com
wrote:
On
On Tue, Mar 26, 2013 at 07:39:51PM +0100, Alberto di Bene wrote:
On 3/26/2013 7:21 PM, Dan Kemppainen wrote:
Keep in mind, we are after all, taking about windows. An operating
system that IS NOT real time operating system. (You think it is, try
move a continuous stream of a few 6+ MBytes/Sec
Just to add to to this, I recently had a partial power outage and one of my
better OCXO's (a Datum 1000) lost power for a day or so. After being powered
back up for approx 24 hours the frequency error was well under one part per
billion. This is more than accurate enough for any of my
19 matches
Mail list logo
