time-nuts@lists.febo.com

Discussion of precise time and frequency measurement

View all threads

Fine print on HP 5334B

HM
Hal Murray
Thu, Feb 22, 2007 8:10 PM

(Interesting timing given the SR620 discussion.)

I'm (finally) getting my GPIB gizmo working.

I have a HP 5334B running off its (good) internal osc looking at the output
of a Z3801A.  Assuming the Z3801A is stable, this is a backwards way of
looking at the internal osc.  (There is a shared in/out connector for the
internal clock, so I can't see the internal osc if I feed it an ext
reference.)

I left it running for a night with the mostly default setup and 100 cycle
averaging.  I think the default gate time is 0.3 seconds.  Answers ranged
from:
F  +9.999999330E+06
F  +9.999999333E+06

I've had this setup running for several weeks.  The bottom digit doesn't fit
on the display, so I never noticed there was anything interesting going on
down there.  The 100 cycle averaging has a button on the front panel.
Without it, the display is one digit shorter.

Yesterday, I got it running with a single 60 second gate.  Now it's wobbling
between:
F  +9.999999339E+06
F  +9.999999340E+06

I was a bit surprised there is such a difference.  Is this all obvious to
anybody who has carefully read the manual?

Of course, now that I think about it, averaging frequency measurements seems
less helpful that simply using a longer measurement time.  But I'm still
surprised the answers were so different.

Another quirk I noticed.  They truncate rather than round for the display on
the front panel.  9.999999339 shows up as 9.99999933 rather than 9.99999934

Is there anything else like this I should watch out for?  Does anybody have a
quick summary on how to get good results or traps to avoid?

--
These are my opinions, not necessarily my employer's.  I hate spam.

(Interesting timing given the SR620 discussion.) I'm (finally) getting my GPIB gizmo working. I have a HP 5334B running off its (good) internal osc looking at the output of a Z3801A. Assuming the Z3801A is stable, this is a backwards way of looking at the internal osc. (There is a shared in/out connector for the internal clock, so I can't see the internal osc if I feed it an ext reference.) I left it running for a night with the mostly default setup and 100 cycle averaging. I think the default gate time is 0.3 seconds. Answers ranged from: F +9.999999330E+06 F +9.999999333E+06 I've had this setup running for several weeks. The bottom digit doesn't fit on the display, so I never noticed there was anything interesting going on down there. The 100 cycle averaging has a button on the front panel. Without it, the display is one digit shorter. Yesterday, I got it running with a single 60 second gate. Now it's wobbling between: F +9.999999339E+06 F +9.999999340E+06 I was a bit surprised there is such a difference. Is this all obvious to anybody who has carefully read the manual? Of course, now that I think about it, averaging frequency measurements seems less helpful that simply using a longer measurement time. But I'm still surprised the answers were so different. Another quirk I noticed. They truncate rather than round for the display on the front panel. 9.999999339 shows up as 9.99999933 rather than 9.99999934 Is there anything else like this I should watch out for? Does anybody have a quick summary on how to get good results or traps to avoid? -- These are my opinions, not necessarily my employer's. I hate spam.
JM
John Miles
Thu, Feb 22, 2007 8:29 PM

What do people observe on their 5370A/Bs?  After warmup, I tend to see a
bias of about +0.0005 Hz, or 5E-11, when observing its own 10 MHz source.
There is some occasional random waffling on the order of about +/- 0.001 Hz
but for the most part it reads close to 10.000 000 000 5.

I have never been able to calibrate the interpolators (specifically the
anticoincidence adjustment) in these counters, due to lack of a
vernier-adjustable pulse generator.  When I was going through one last week,
I just left the anticoincidence pot in the middle of its range, and couldn't
see any ill effects from doing so.  The manual is not that great at
describing exactly what this adjustment does.

-- john, KE5FX

-----Original Message-----
From: time-nuts-bounces@febo.com [mailto:time-nuts-bounces@febo.com]On
Behalf Of Hal Murray
Sent: Thursday, February 22, 2007 12:10 PM
To: time-nuts@febo.com
Subject: [time-nuts] Fine print on HP 5334B

(Interesting timing given the SR620 discussion.)

I'm (finally) getting my GPIB gizmo working.

I have a HP 5334B running off its (good) internal osc looking at
the output
of a Z3801A.  Assuming the Z3801A is stable, this is a backwards way of
looking at the internal osc.  (There is a shared in/out connector for the
internal clock, so I can't see the internal osc if I feed it an ext
reference.)

I left it running for a night with the mostly default setup and 100 cycle
averaging.  I think the default gate time is 0.3 seconds.  Answers ranged
from:
F  +9.999999330E+06
F  +9.999999333E+06

What do people observe on their 5370A/Bs? After warmup, I tend to see a bias of about +0.0005 Hz, or 5E-11, when observing its own 10 MHz source. There is some occasional random waffling on the order of about +/- 0.001 Hz but for the most part it reads close to 10.000 000 000 5. I have never been able to calibrate the interpolators (specifically the anticoincidence adjustment) in these counters, due to lack of a vernier-adjustable pulse generator. When I was going through one last week, I just left the anticoincidence pot in the middle of its range, and couldn't see any ill effects from doing so. The manual is not that great at describing exactly what this adjustment does. -- john, KE5FX > -----Original Message----- > From: time-nuts-bounces@febo.com [mailto:time-nuts-bounces@febo.com]On > Behalf Of Hal Murray > Sent: Thursday, February 22, 2007 12:10 PM > To: time-nuts@febo.com > Subject: [time-nuts] Fine print on HP 5334B > > > (Interesting timing given the SR620 discussion.) > > I'm (finally) getting my GPIB gizmo working. > > I have a HP 5334B running off its (good) internal osc looking at > the output > of a Z3801A. Assuming the Z3801A is stable, this is a backwards way of > looking at the internal osc. (There is a shared in/out connector for the > internal clock, so I can't see the internal osc if I feed it an ext > reference.) > > I left it running for a night with the mostly default setup and 100 cycle > averaging. I think the default gate time is 0.3 seconds. Answers ranged > from: > F +9.999999330E+06 > F +9.999999333E+06 >
JM
John Miles
Thu, Feb 22, 2007 8:34 PM

That was with an external 10 MHz source with both rear-panel reference and
front-panel Ch B inputs fed from a passive 4:1 splitter, by the way.
Feeding the EXT reference output directly to Ch B through a 6' cable results
in an average reading much closer to exactly 10 MHz.

-- john, KE5FX

-----Original Message-----
From: time-nuts-bounces@febo.com [mailto:time-nuts-bounces@febo.com]On
Behalf Of John Miles
Sent: Thursday, February 22, 2007 12:30 PM
To: Discussion of precise time and frequency measurement
Subject: Re: [time-nuts] Fine print on HP 5334B

What do people observe on their 5370A/Bs?  After warmup, I tend to see a
bias of about +0.0005 Hz, or 5E-11, when observing its own 10 MHz source.
There is some occasional random waffling on the order of about
+/- 0.001 Hz
but for the most part it reads close to 10.000 000 000 5.

I have never been able to calibrate the interpolators (specifically the
anticoincidence adjustment) in these counters, due to lack of a
vernier-adjustable pulse generator.  When I was going through one
last week,
I just left the anticoincidence pot in the middle of its range,
and couldn't
see any ill effects from doing so.  The manual is not that great at
describing exactly what this adjustment does.

-- john, KE5FX

That was with an external 10 MHz source with both rear-panel reference and front-panel Ch B inputs fed from a passive 4:1 splitter, by the way. Feeding the EXT reference output directly to Ch B through a 6' cable results in an average reading much closer to exactly 10 MHz. -- john, KE5FX > -----Original Message----- > From: time-nuts-bounces@febo.com [mailto:time-nuts-bounces@febo.com]On > Behalf Of John Miles > Sent: Thursday, February 22, 2007 12:30 PM > To: Discussion of precise time and frequency measurement > Subject: Re: [time-nuts] Fine print on HP 5334B > > > What do people observe on their 5370A/Bs? After warmup, I tend to see a > bias of about +0.0005 Hz, or 5E-11, when observing its own 10 MHz source. > There is some occasional random waffling on the order of about > +/- 0.001 Hz > but for the most part it reads close to 10.000 000 000 5. > > I have never been able to calibrate the interpolators (specifically the > anticoincidence adjustment) in these counters, due to lack of a > vernier-adjustable pulse generator. When I was going through one > last week, > I just left the anticoincidence pot in the middle of its range, > and couldn't > see any ill effects from doing so. The manual is not that great at > describing exactly what this adjustment does. > > -- john, KE5FX > >
DI
David I. Emery
Thu, Feb 22, 2007 9:16 PM

On Thu, Feb 22, 2007 at 12:29:35PM -0800, John Miles wrote:

What do people observe on their 5370A/Bs?  After warmup, I tend to see a
bias of about +0.0005 Hz, or 5E-11, when observing its own 10 MHz source.
There is some occasional random waffling on the order of about +/- 0.001 Hz
but for the most part it reads close to 10.000 000 000 5.

I have never been able to calibrate the interpolators (specifically the
anticoincidence adjustment) in these counters, due to lack of a
vernier-adjustable pulse generator.  When I was going through one last week,
I just left the anticoincidence pot in the middle of its range, and couldn't
see any ill effects from doing so.  The manual is not that great at
describing exactly what this adjustment does.

-- john, KE5FX

Mine is off more (or was until it died a couple of weeks ago).   But

I have yet to attempt the full cal procedure for reasons similar to yours.

I did find that using GPSDO 10 mhz the error was quite stable

(always reading low in my case, not high) but apparently just barely within
the spec in the manual.

--
Dave Emery N1PRE,  die@dieconsulting.com  DIE Consulting, Weston, Mass 02493
"An empty zombie mind with a forlorn barely readable weatherbeaten
'For Rent' sign still vainly flapping outside on the weed encrusted pole - in
celebration of what could have been, but wasn't and is not to be now either."

On Thu, Feb 22, 2007 at 12:29:35PM -0800, John Miles wrote: > What do people observe on their 5370A/Bs? After warmup, I tend to see a > bias of about +0.0005 Hz, or 5E-11, when observing its own 10 MHz source. > There is some occasional random waffling on the order of about +/- 0.001 Hz > but for the most part it reads close to 10.000 000 000 5. > > I have never been able to calibrate the interpolators (specifically the > anticoincidence adjustment) in these counters, due to lack of a > vernier-adjustable pulse generator. When I was going through one last week, > I just left the anticoincidence pot in the middle of its range, and couldn't > see any ill effects from doing so. The manual is not that great at > describing exactly what this adjustment does. > > -- john, KE5FX Mine is off more (or was until it died a couple of weeks ago). But I have yet to attempt the full cal procedure for reasons similar to yours. I did find that using GPSDO 10 mhz the error was quite stable (always reading low in my case, not high) but apparently just barely within the spec in the manual. -- Dave Emery N1PRE, die@dieconsulting.com DIE Consulting, Weston, Mass 02493 "An empty zombie mind with a forlorn barely readable weatherbeaten 'For Rent' sign still vainly flapping outside on the weed encrusted pole - in celebration of what could have been, but wasn't and is not to be now either."
DB
Dr Bruce Griffiths
Thu, Feb 22, 2007 9:19 PM

John Miles wrote:

What do people observe on their 5370A/Bs?  After warmup, I tend to see a
bias of about +0.0005 Hz, or 5E-11, when observing its own 10 MHz source.
There is some occasional random waffling on the order of about +/- 0.001 Hz
but for the most part it reads close to 10.000 000 000 5.

I have never been able to calibrate the interpolators (specifically the
anticoincidence adjustment) in these counters, due to lack of a
vernier-adjustable pulse generator.  When I was going through one last week,
I just left the anticoincidence pot in the middle of its range, and couldn't
see any ill effects from doing so.  The manual is not that great at
describing exactly what this adjustment does.

-- john, KE5FX

-----Original Message-----
From: time-nuts-bounces@febo.com [mailto:time-nuts-bounces@febo.com]On
Behalf Of Hal Murray
Sent: Thursday, February 22, 2007 12:10 PM
To: time-nuts@febo.com
Subject: [time-nuts] Fine print on HP 5334B

(Interesting timing given the SR620 discussion.)

I'm (finally) getting my GPIB gizmo working.

I have a HP 5334B running off its (good) internal osc looking at
the output
of a Z3801A.  Assuming the Z3801A is stable, this is a backwards way of
looking at the internal osc.  (There is a shared in/out connector for the
internal clock, so I can't see the internal osc if I feed it an ext
reference.)

I left it running for a night with the mostly default setup and 100 cycle
averaging.  I think the default gate time is 0.3 seconds.  Answers ranged
from:
F  +9.999999330E+06
F  +9.999999333E+06

John

Connecting the frequency output to the Frequency/period input (set to 50
ohm) with a 1m double screened RG58 cable displays a frequency of
10.000000004 with rms fluctuations of about 2 in the last digit.  This
occurs right at start before any warmup with an HP5370A that doesn't
have an HP10811 or equivalent internal oscillator. oscillator.

Bruce

John Miles wrote: > What do people observe on their 5370A/Bs? After warmup, I tend to see a > bias of about +0.0005 Hz, or 5E-11, when observing its own 10 MHz source. > There is some occasional random waffling on the order of about +/- 0.001 Hz > but for the most part it reads close to 10.000 000 000 5. > > I have never been able to calibrate the interpolators (specifically the > anticoincidence adjustment) in these counters, due to lack of a > vernier-adjustable pulse generator. When I was going through one last week, > I just left the anticoincidence pot in the middle of its range, and couldn't > see any ill effects from doing so. The manual is not that great at > describing exactly what this adjustment does. > > -- john, KE5FX > > > >> -----Original Message----- >> From: time-nuts-bounces@febo.com [mailto:time-nuts-bounces@febo.com]On >> Behalf Of Hal Murray >> Sent: Thursday, February 22, 2007 12:10 PM >> To: time-nuts@febo.com >> Subject: [time-nuts] Fine print on HP 5334B >> >> >> (Interesting timing given the SR620 discussion.) >> >> I'm (finally) getting my GPIB gizmo working. >> >> I have a HP 5334B running off its (good) internal osc looking at >> the output >> of a Z3801A. Assuming the Z3801A is stable, this is a backwards way of >> looking at the internal osc. (There is a shared in/out connector for the >> internal clock, so I can't see the internal osc if I feed it an ext >> reference.) >> >> I left it running for a night with the mostly default setup and 100 cycle >> averaging. I think the default gate time is 0.3 seconds. Answers ranged >> from: >> F +9.999999330E+06 >> F +9.999999333E+06 >> >> > > > _______________________________________________ > time-nuts mailing list > time-nuts@febo.com > https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts > > John Connecting the frequency output to the Frequency/period input (set to 50 ohm) with a 1m double screened RG58 cable displays a frequency of 10.000000004 with rms fluctuations of about 2 in the last digit. This occurs right at start before any warmup with an HP5370A that doesn't have an HP10811 or equivalent internal oscillator. oscillator. Bruce
RK
Rick Karlquist
Thu, Feb 22, 2007 10:14 PM

It's worth keeping in mind a couple of things:

  1. The firmware in the 5334B is identical to the 5334A except
    for an extremely minor change to accommodate a different modulus
    in the C channel.

  2. The entire program has to fit into 2KB (two thousand and
    forty eight bytes) of ROM, and was written in assembly language and/or
    machine language and is understandable only to its author (Ken T.)
    It uses every last byte of memory.  The 2KB limit is due to
    the legacy, discontinued microprocessor that was used (long story).

  3. The interpolator has somewhat questionable accuracy when you
    get down to 12 digits.  This is hidden somewhat by the firmware,
    but if you monitor the bits the interpolator puts out, you can
    see what is going on.  To me, it is kind of amazing it works as
    well as it does considering the design.

So please lower your expectations!

If you want a really good HP counter, move up to the 53181 which
is much more modern, even being 15 years old.

Rick Karlquist N6RK
R&D Project Manager of 5334B (circa 1986)

Hal Murray wrote:

(Interesting timing given the SR620 discussion.)

I'm (finally) getting my GPIB gizmo working.

I have a HP 5334B running off its (good) internal osc looking at the
output
of a Z3801A.  Assuming the Z3801A is stable, this is a backwards way of
looking at the internal osc.  (There is a shared in/out connector for the
internal clock, so I can't see the internal osc if I feed it an ext
reference.)

I left it running for a night with the mostly default setup and 100 cycle
averaging.  I think the default gate time is 0.3 seconds.  Answers ranged
from:
F  +9.999999330E+06
F  +9.999999333E+06

I've had this setup running for several weeks.  The bottom digit doesn't
fit
on the display, so I never noticed there was anything interesting going on
down there.  The 100 cycle averaging has a button on the front panel.
Without it, the display is one digit shorter.

Yesterday, I got it running with a single 60 second gate.  Now it's
wobbling
between:
F  +9.999999339E+06
F  +9.999999340E+06

I was a bit surprised there is such a difference.  Is this all obvious to
anybody who has carefully read the manual?

Of course, now that I think about it, averaging frequency measurements
seems
less helpful that simply using a longer measurement time.  But I'm still
surprised the answers were so different.

Another quirk I noticed.  They truncate rather than round for the display
on
the front panel.  9.999999339 shows up as 9.99999933 rather than
9.99999934

Is there anything else like this I should watch out for?  Does anybody
have a
quick summary on how to get good results or traps to avoid?

--
These are my opinions, not necessarily my employer's.  I hate spam.


time-nuts mailing list
time-nuts@febo.com
https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts

It's worth keeping in mind a couple of things: 1. The firmware in the 5334B is identical to the 5334A except for an extremely minor change to accommodate a different modulus in the C channel. 2. The entire program has to fit into 2KB (two thousand and forty eight bytes) of ROM, and was written in assembly language and/or machine language and is understandable only to its author (Ken T.) It uses every last byte of memory. The 2KB limit is due to the legacy, discontinued microprocessor that was used (long story). 3. The interpolator has somewhat questionable accuracy when you get down to 12 digits. This is hidden somewhat by the firmware, but if you monitor the bits the interpolator puts out, you can see what is going on. To me, it is kind of amazing it works as well as it does considering the design. So please lower your expectations! If you want a really good HP counter, move up to the 53181 which is much more modern, even being 15 years old. Rick Karlquist N6RK R&D Project Manager of 5334B (circa 1986) Hal Murray wrote: > (Interesting timing given the SR620 discussion.) > > I'm (finally) getting my GPIB gizmo working. > > I have a HP 5334B running off its (good) internal osc looking at the > output > of a Z3801A. Assuming the Z3801A is stable, this is a backwards way of > looking at the internal osc. (There is a shared in/out connector for the > internal clock, so I can't see the internal osc if I feed it an ext > reference.) > > I left it running for a night with the mostly default setup and 100 cycle > averaging. I think the default gate time is 0.3 seconds. Answers ranged > from: > F +9.999999330E+06 > F +9.999999333E+06 > > I've had this setup running for several weeks. The bottom digit doesn't > fit > on the display, so I never noticed there was anything interesting going on > down there. The 100 cycle averaging has a button on the front panel. > Without it, the display is one digit shorter. > > Yesterday, I got it running with a single 60 second gate. Now it's > wobbling > between: > F +9.999999339E+06 > F +9.999999340E+06 > > I was a bit surprised there is such a difference. Is this all obvious to > anybody who has carefully read the manual? > > Of course, now that I think about it, averaging frequency measurements > seems > less helpful that simply using a longer measurement time. But I'm still > surprised the answers were so different. > > Another quirk I noticed. They truncate rather than round for the display > on > the front panel. 9.999999339 shows up as 9.99999933 rather than > 9.99999934 > > > Is there anything else like this I should watch out for? Does anybody > have a > quick summary on how to get good results or traps to avoid? > > -- > These are my opinions, not necessarily my employer's. I hate spam. > > > > > _______________________________________________ > time-nuts mailing list > time-nuts@febo.com > https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts > >
J
jshank
Fri, Feb 23, 2007 2:20 PM

Hi,

I check my 5370b by using the 10 MHz output and feeding it to the counter.
What I see is a fluctuation in the displayed reading of between 9.999 999
998 73 to 9.999 999 997 25.  The instrument is set for 1 s gate. Sometimes
one reading will remain for a couple of arming but usually the reading will
change between six different readings with the high and low as above.

I am assuming there is a problem with this instrument and am asking for
suggestions on what can be done to correct this problem.

Ps. this instrument has the 10811-06111 oscillator.  I have tried using the
10 MHz output from the 5370 as an external reference to a 53131A while
measuring the frequency of the 5370 10 MHz output.  After both instruments
warm up the frequency of the 5370 output is displayed on the 53131A with a 1
s gate time as 10.000 000 000  and if I increase the gate time to 10s the
reading is 10.000 000 000 0 with the reading remaining rock solid.

Thanks,

Jeff

----- Original Message -----
From: "John Miles" jmiles@pop.net
To: "Discussion of precise time and frequency measurement"
time-nuts@febo.com
Sent: Thursday, February 22, 2007 3:29 PM
Subject: Re: [time-nuts] Fine print on HP 5334B

What do people observe on their 5370A/Bs?  After warmup, I tend to see a
bias of about +0.0005 Hz, or 5E-11, when observing its own 10 MHz source.
There is some occasional random waffling on the order of about +/- 0.001
Hz
but for the most part it reads close to 10.000 000 000 5.

I have never been able to calibrate the interpolators (specifically the
anticoincidence adjustment) in these counters, due to lack of a
vernier-adjustable pulse generator.  When I was going through one last
week,
I just left the anticoincidence pot in the middle of its range, and
couldn't
see any ill effects from doing so.  The manual is not that great at
describing exactly what this adjustment does.

-- john, KE5FX

-----Original Message-----
From: time-nuts-bounces@febo.com [mailto:time-nuts-bounces@febo.com]On
Behalf Of Hal Murray
Sent: Thursday, February 22, 2007 12:10 PM
To: time-nuts@febo.com
Subject: [time-nuts] Fine print on HP 5334B

(Interesting timing given the SR620 discussion.)

I'm (finally) getting my GPIB gizmo working.

I have a HP 5334B running off its (good) internal osc looking at
the output
of a Z3801A.  Assuming the Z3801A is stable, this is a backwards way of
looking at the internal osc.  (There is a shared in/out connector for the
internal clock, so I can't see the internal osc if I feed it an ext
reference.)

I left it running for a night with the mostly default setup and 100 cycle
averaging.  I think the default gate time is 0.3 seconds.  Answers ranged
from:
F  +9.999999330E+06
F  +9.999999333E+06

Hi, I check my 5370b by using the 10 MHz output and feeding it to the counter. What I see is a fluctuation in the displayed reading of between 9.999 999 998 73 to 9.999 999 997 25. The instrument is set for 1 s gate. Sometimes one reading will remain for a couple of arming but usually the reading will change between six different readings with the high and low as above. I am assuming there is a problem with this instrument and am asking for suggestions on what can be done to correct this problem. Ps. this instrument has the 10811-06111 oscillator. I have tried using the 10 MHz output from the 5370 as an external reference to a 53131A while measuring the frequency of the 5370 10 MHz output. After both instruments warm up the frequency of the 5370 output is displayed on the 53131A with a 1 s gate time as 10.000 000 000 and if I increase the gate time to 10s the reading is 10.000 000 000 0 with the reading remaining rock solid. Thanks, Jeff ----- Original Message ----- From: "John Miles" <jmiles@pop.net> To: "Discussion of precise time and frequency measurement" <time-nuts@febo.com> Sent: Thursday, February 22, 2007 3:29 PM Subject: Re: [time-nuts] Fine print on HP 5334B > What do people observe on their 5370A/Bs? After warmup, I tend to see a > bias of about +0.0005 Hz, or 5E-11, when observing its own 10 MHz source. > There is some occasional random waffling on the order of about +/- 0.001 > Hz > but for the most part it reads close to 10.000 000 000 5. > > I have never been able to calibrate the interpolators (specifically the > anticoincidence adjustment) in these counters, due to lack of a > vernier-adjustable pulse generator. When I was going through one last > week, > I just left the anticoincidence pot in the middle of its range, and > couldn't > see any ill effects from doing so. The manual is not that great at > describing exactly what this adjustment does. > > -- john, KE5FX > > >> -----Original Message----- >> From: time-nuts-bounces@febo.com [mailto:time-nuts-bounces@febo.com]On >> Behalf Of Hal Murray >> Sent: Thursday, February 22, 2007 12:10 PM >> To: time-nuts@febo.com >> Subject: [time-nuts] Fine print on HP 5334B >> >> >> (Interesting timing given the SR620 discussion.) >> >> I'm (finally) getting my GPIB gizmo working. >> >> I have a HP 5334B running off its (good) internal osc looking at >> the output >> of a Z3801A. Assuming the Z3801A is stable, this is a backwards way of >> looking at the internal osc. (There is a shared in/out connector for the >> internal clock, so I can't see the internal osc if I feed it an ext >> reference.) >> >> I left it running for a night with the mostly default setup and 100 cycle >> averaging. I think the default gate time is 0.3 seconds. Answers ranged >> from: >> F +9.999999330E+06 >> F +9.999999333E+06 >> > > > _______________________________________________ > time-nuts mailing list > time-nuts@febo.com > https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts >
PK
Poul-Henning Kamp
Fri, Feb 23, 2007 5:43 PM

In message 003f01c75755$d2d9e340$0200a8c0@DESKTOP, "jshank" writes:

I check my 5370b by [...]

The manual is online in PDF somewhere and it has a nice and
simple to follow procedure, provided you have instruments which
are suitable substitutes what it prescribes.

--
Poul-Henning Kamp      | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG        | TCP/IP since RFC 956
FreeBSD committer      | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.

In message <003f01c75755$d2d9e340$0200a8c0@DESKTOP>, "jshank" writes: >I check my 5370b by [...] The manual is online in PDF somewhere and it has a nice and simple to follow procedure, provided you have instruments which are suitable substitutes what it prescribes. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.
DJ
Didier Juges
Fri, Feb 23, 2007 9:17 PM

Poul-Henning Kamp wrote:

In message 003f01c75755$d2d9e340$0200a8c0@DESKTOP, "jshank" writes:

I check my 5370b by [...]

The manual is online in PDF somewhere and it has a nice and
simple to follow procedure, provided you have instruments which
are suitable substitutes what it prescribes.

Service manuals (5370A and 5370B) are at
www,ko4bb.com/ham_radio/Manuals/

Didier KO4BB

Poul-Henning Kamp wrote: > In message <003f01c75755$d2d9e340$0200a8c0@DESKTOP>, "jshank" writes: > > >> I check my 5370b by [...] >> > > The manual is online in PDF somewhere and it has a nice and > simple to follow procedure, provided you have instruments which > are suitable substitutes what it prescribes. > > Service manuals (5370A and 5370B) are at www,ko4bb.com/ham_radio/Manuals/ Didier KO4BB
JG
Joseph Gray
Sat, Feb 24, 2007 1:15 AM

I just picked up a Tracor 888A Linear Phase Recorder at the local surplus
place. I thought it might be worth tinkering with, for only $7. I did some
Googling, but can't find any information on this device. Can anyone help?.

Thanks.

I just picked up a Tracor 888A Linear Phase Recorder at the local surplus place. I thought it might be worth tinkering with, for only $7. I did some Googling, but can't find any information on this device. Can anyone help?. Thanks.