On 11/3/2012 5:32 AM, Sarah White wrote:
So, at or around 1981 (the year I was born) there was a cool concept.
IBM was selling personal computers (IBM-PC compatible later became a
thing) and by the time I was old enough to operate a modem, I had one
myself. Life was good.
Wonder if there is
Dear Sarah,
Good morning. I just returned home from a long and difficult customer data
center migration. I thought of sharing that I feel the same way as you do
regarding your thread. Things should always behave like a Mac or Linux, in
which if there is a glitch, the OS responsible party jumps
Sarah,
I am having a hard time understanding your problem. Or at least what you see as
a problem. I am not sure what you are really complaining about here ? Is it
the
daylight change ? Or is it a dual boot problem which would suggest you do not
have some settings in their rightful place ?
On 11/3/2012 8:02 AM, Edgardo Molina wrote:
Dear Sarah,
Good morning. I just returned home from a long and difficult customer data
center migration. I thought of sharing that I feel the same way as you do
regarding your thread. Things should always behave like a Mac or Linux, in
which if
Microsoft also does updates regarding the day daylight savings time changes,
similar to that Apple message.
I suspect I'm not following this thread correctly. What I got from the orignal
thread is Microsoft will thunk the RTC during the switchover. I'm going to
make it a point to insure NTP is
On 11/3/2012 8:26 AM, WB6BNQ wrote:
Sarah,
I am having a hard time understanding your problem. Or at least what you see
as
a problem. I am not sure what you are really complaining about here ? Is it
the
daylight change ? Or is it a dual boot problem which would suggest you do not
-Original Message-
From: Sarah White
[]
Seeing as I'm in the process of installing a hardware refclock (trimble
thunderbolt connected via serial port) for my NTP, it is highly
problematic and potentially error-prone for microsoft's OS to touch the
bios hardware clock AT ALL.
I'm
On 11/3/2012 9:18 AM, David J Taylor wrote:
-Original Message- From: Sarah White
[]
Seeing as I'm in the process of installing a hardware refclock (trimble
thunderbolt connected via serial port) for my NTP, it is highly
problematic and potentially error-prone for microsoft's OS to
Windows actually CHANGES the RTC at DST changover, rather than let it tick
montinically, and adjust the offset.
This is what is bad ...
Dave
Regards,
David Partridge
-Original Message-
From: time-nuts-boun...@febo.com [mailto:time-nuts-boun...@febo.com] On Behalf
Of
-Original Message-
From: Sarah White
Sent: Saturday, November 03, 2012 9:49 AM
Thanks so much David...
Really. Thanks. I feel alot better now.
Regardless of documented issues on:
http://www.cl.cam.ac.uk/~mgk25/mswish/ut-rtc.html
(quote) The numerous past malfunctions of Microsoft
On 11/3/2012 11:31 AM, David J Taylor wrote:
-Original Message- From: Sarah White
Sent: Saturday, November 03, 2012 9:49 AM
Thanks so much David...
Really. Thanks. I feel alot better now.
Regardless of documented issues on:
http://www.cl.cam.ac.uk/~mgk25/mswish/ut-rtc.html
Thank you for the interesting information. Now, the time has come to
look for an adequate counter - anyone who has experience with the HP
53132A and the SR620? If they both where at - say 1000 USD - what would
you prefer for the job of phase measurement? I've read about that
massive single
-Original Message-
From: Sarah White
Great, thanks for the loopstats.
For the included loopstats, I believe Alta was among the ones on which
you were running windows 7 + NTP... Would you mind confirming which
setting you have for your timezone? (since I'm reasonably certain I know
what
On 11/03/2012 03:10 PM, Volker Esper wrote:
Thank you for the interesting information. Now, the time has come to
look for an adequate counter - anyone who has experience with the HP
53132A and the SR620? If they both where at - say 1000 USD - what would
you prefer for the job of phase
On 11/03/2012 05:05 AM, Sarah White wrote:
Seeing as I'm in the process of installing a hardware refclock (trimble
thunderbolt connected via serial port) for my NTP, it is highly
problematic and potentially error-prone for microsoft's OS to touch the
bios hardware clock AT ALL.
Just in case it
On Fri, Nov 2, 2012 at 10:32 PM, Sarah White kuze...@gmail.com wrote:
So, at or around 1981 (the year I was born) there was a cool concept.
IBM was selling personal computers (IBM-PC compatible later became a
thing) and by the time I was old enough to operate a modem, I had one
myself. Life
On 11/3/2012 3:12 PM, David J Taylor wrote:
-Original Message- From: Sarah White
Great, thanks for the loopstats.
For the included loopstats, I believe Alta was among the ones on which
you were running windows 7 + NTP... Would you mind confirming which
setting you have for your
On 11/3/12 8:50 AM, Chris Albertson wrote:
On Fri, Nov 2, 2012 at 10:32 PM, Sarah White kuze...@gmail.com wrote:
So, at or around 1981 (the year I was born) there was a cool concept.
IBM was selling personal computers (IBM-PC compatible later became a
thing) and by the time I was old enough to
I've acquired an EIP 545A counter which seems to be in decent shape.
In reading through the service manual there is a reference to option 14,
a high resolution mode that increases gate time to 10 seconds.
As far as I can tell, this doesn't appear to be an add-on board. Anyone
know the details?
Try asking on the EIP_Microwave Yahoo Group.
Best,
-John
===
I've acquired an EIP 545A counter which seems to be in decent shape.
In reading through the service manual there is a reference to option 14,
a high resolution mode that increases gate time to 10 seconds.
As far
Hi Magnus;
I hope this is not to far off thread. Has anyone in the group done real world
measurements of single shot res, and jitter on the new Agilent and
Tektronix/Pendulum counters compared to the SR620 and Agilent 53132A. I would
imagine that counter designs would be an area that really
Hi
Both counters have their weak points long term. On the balance I think the 620
should last longer. The 620 is the higher resolution of the two. The 620
normally comes with a bit better reference. Both are supported by various Time
Nut software packages. Both do GPIB and serial i/o. The 620
Hi
The 620 is still pretty good (when tuned up). It certainly beats the Pendulum's
on a single shot basis. The 53230 is spec'd to be as good as the 620. I suspect
it meets or exceeds it's stated specs.
Bob
On Nov 3, 2012, at 12:58 PM, Tom Knox act...@hotmail.com wrote:
Hi Magnus;
I hope
On 11/3/2012 6:32 AM, Sarah White wrote:
/Wonder if there is any sensible way to petition microsoft to fix this
stupid mistake dating back to the DOS era. Windows 8 / metro is out now,
and I can't bloody stand the changes. Would be nice if windows 7 had an
update to fix this issue:
Hi
Possibly because they run multiple very large / very expensive software
packages that are Windows only items.
Bob
On Nov 3, 2012, at 11:50 AM, Chris Albertson albertson.ch...@gmail.com wrote:
On Fri, Nov 2, 2012 at 10:32 PM, Sarah White kuze...@gmail.com wrote:
So, at or around 1981
And remember how late they were to network support?
I had a computer store at that time and sold a lot of Artisoft LANtastic
kits because Win3.1 did not have network support. I believe it was
slipstreamed in 3.11.
Most of my installations were so several machines in an office could share a
Hi Tom,
On 11/03/2012 05:58 PM, Tom Knox wrote:
Hi Magnus;
I hope this is not to far off thread. Has anyone in the group done
real world measurements of single shot res, and jitter on the new
Agilent and Tektronix/Pendulum counters compared to the SR620 and
Agilent 53132A. I would imagine that
On Sat, Nov 3, 2012 at 9:24 AM, Jim Lux jim...@earthlink.net wrote:
On 11/3/12 8:50 AM, Chris Albertson wrote:
That is the root cause of all Window's problems. The company was run be a
chief software architect who technically very ignorant and lacked any
formal education in the subject.
On 11/3/2012 6:31 PM, Orin Eman wrote:
There was also OS/2...
The best OpSys ever killed by IBM itself, as an internal, confidential,
report
indicated that developing middleware for Windows NT could produce much more
revenues than continuing to develop OS/2...
So they decided to let it
Hi Bob
I didn't expect something to be tunable in the counter (except for the
oscillator) - what is it that has to be calibrated?
Thanks
Volker
Am 03.11.2012 18:04, schrieb Bob Camp:
Hi
The 620 is still pretty good (when tuned up). It certainly beats the Pendulum's
on a single shot
Hi
There is a fairly elaborate alignment procedure for the 620. It's been reported
in great detail here on the list. The counter definitely does better after you
go through the full process.
Bob
On Nov 3, 2012, at 3:42 PM, Volker Esper ail...@t-online.de wrote:
Hi Bob
I didn't expect
Hi Bob
What is it, that limits a counters life, are you speaking of typical
counter specific failures or do you just mean the common wearout?
Sorry, I know those are no smart questions - but my heart is thumping
when I think of the price and the long way it has to go over the sea...
Hi
In the case of the 53132, the power supply seems to be the weak link. Out of
maybe a hundred or so in the fleet, we see maybe one or two die each month. On
the SR620 the power supply also seems to go from time to time. Both have the
normal keyboard and display issues, but those can be
Reykjavík, Iceland is UTC+0 without summer time changes.
Brent
On 11/3/2012 9:55 AM, Sarah White wrote:
P.S. Seems strange that the only two options for a UTC+0 timezone are
London, Dublin or Casablanca (neither of which are year-round UTC)
... I'll try to remember to point this out to the
Ah, ok, that helps. Meanwhile, I've found the manual and the schematics,
and it seems to be possible, to get a died power supply back running.
Thanks a lot!
Volker
Am 03.11.2012 21:36, schrieb Bob Camp:
Hi
In the case of the 53132, the power supply seems to be the weak link. Out of
Great, your answere gives me hope, that the calibration procedure can be
done at my home :-)
Thank you!
Volker
Am 03.11.2012 21:08, schrieb Bob Camp:
Hi
There is a fairly elaborate alignment procedure for the 620. It's been reported
in great detail here on the list. The counter definitely
Folks,
Given that slew rate is so critical, why do we distribute sine waves and
perform the zero-crossing detection at every target instrument?
david
Trigger jitter is the noise at the trigger point. it's a combination
of thermal noise and the slew-rate at the trigger points. It is often
On 11/03/2012 09:36 PM, Bob Camp wrote:
Hi
In the case of the 53132, the power supply seems to be the weak link. Out of
maybe a hundred or so in the fleet, we see maybe one or two die each month. On
the SR620 the power supply also seems to go from time to time. Both have the
normal keyboard
David,
On 11/03/2012 10:44 PM, David Hooke wrote:
Folks,
Given that slew rate is so critical, why do we distribute sine waves and
perform the zero-crossing detection at every target instrument?
... or rather, why do we design our input stages so they are so
slew-rate sensitive?
Sine isn't
Usually you don't need a BVA to test the single-shot capability of a
counter: a length (say 50nS) of good RF coaxial cable and your preferred
OCXO/Rb/GPSDO should be enough.
On Sat, Nov 3, 2012 at 11:14 PM, Magnus Danielson
mag...@rubidium.dyndns.org wrote:
On 11/03/2012 09:36 PM, Bob Camp
Hi
If you have a sine wave, it gets into everything. You can identify it and take
it out of your data.
If you have a broad band uber-fast high level pules, it gets into everything.
Identifying it's impact and taking it out of the data - not so easy.
That may sound a bit crazy. I've actually
Hi
The relay *can* be replaced. Not so much with the input amp. If it goes, you
lost the counter. The displays also die from time to time. Like the relay, they
can be replaced.
Bob
On Nov 3, 2012, at 6:14 PM, Magnus Danielson mag...@rubidium.dyndns.org wrote:
On 11/03/2012 09:36 PM, Bob
This has probably already been posted more than once, but if anyone
is still looking for a description of the new WWVB modulation scheme:
http://tf.boulder.nist.gov/general/pdf/2651.pdf (Sept. 2012)
Best regards,
Charles
___
time-nuts mailing
david wrote:
Given that slew rate is so critical, why do we distribute sine waves
and perform the zero-crossing detection at every target instrument?
Magnus made some good points in response to your question. To
elaborate a bit: it is much easier to provide a friendly transmission
The below is correct but a simpler way to say it is this:
A square wave contains the fundamental frequency plus every odd harmonic
up to infinity. A sine wave contains only the fundamental frequency.
It is the up to infinity part that causes all the trouble. And yes it
really does go to
Of course you can't have a perfect square wave! That would imply zero
transition time and since frequency is inverse to time that implies infinitely
high frequency bandwidth is required to achieve that perfect square wave.
Getting a square wave with a fast enough slew rate between high and
On 11/04/2012 01:13 AM, Peter Gottlieb wrote:
Of course you can't have a perfect square wave! That would imply zero
transition time
... oh, THAT would be useful! :D No trigger point jitter!
... and it would be a hell to contain within the cables and connectors
we have, as they leak a lot as
47 matches
Mail list logo
