time-nuts@lists.febo.com

Discussion of precise time and frequency measurement

View all threads

Re: [time-nuts] The VE2ZAZ GPSDO

BK
Brian Kirby
Mon, Oct 23, 2006 5:02 AM

John Ackermann N8UR wrote:

The few experiments I've done indicate that there isn't that much
sample-to-sample jitter in a divider built up out of a reasonable-length
string of 74HC390 dividers, but the temperature stability is horrible.

John

We'll, its time to break out some heaters and ovens....!  Brian N4FMN

John Ackermann N8UR wrote: > The few experiments I've done indicate that there isn't that much > sample-to-sample jitter in a divider built up out of a reasonable-length > string of 74HC390 dividers, but the temperature stability is horrible. > > John > > We'll, its time to break out some heaters and ovens....! Brian N4FMN
DB
Dr Bruce Griffiths
Mon, Oct 23, 2006 5:06 AM

Didier Juges wrote:

Dr Bruce Griffiths wrote:

Didier Juges wrote:

Dr Bruce Griffiths wrote:

Didier Juges wrote:

Dr Bruce Griffiths wrote:

In principle this measurement could be made with a time interval counter:
PPS -> START
delayed 10KHz -> STOP

Vary the delay and watch the jitter jump when the leading edge of the
PPS signal occurs during the 10KHz burst which was phase coherent with
the previous PPS pulse.
The only problem is finding a suitable variable delay device with
sufficiently low (<=1ns??) jitter.

The delay device can be triggered by the 1 PPS, then will drive the ARM
input of the counter, so as long as the delay device's jitter  is less
than the 10 kHz period, if we adjust the delay to 0.99985 second
(between the last 2 periods of 10 kHz before the 1 PPS), then the TI
counter will START on the last 10 kHz pulse before the pps, and STOP on
the 1 PPS.
Tek has some time delay generators in the TM-500 and 7000 plug-in
series. I knew one day I would need one of those, I now know why :-)

Didier


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

Since the HP5370 arm input is high impedance(1 Megohm) and its input
range lies betwen -2V and +2V its desirable to drive it from a back
terminated source with an amplitude of 2V or less to avoid overdriving
(the comparators are better behaved if the input signal remains within
the specified range) the input and ensure that the pulse at the ARM is
relatively clean and reflection free. A suitable buffer can be built
using 3 74AC04 inverters as depicted below: The 74AC04 inverters load
currents are well within the specified limits even if the buffer output
is shorted to ground. Thus the driver should have a long service life.
ARM driver

Bruce


The trigger levels on the 5370 are strange. The normal inputs have
trigger levels that can be adjusted between -1.5 and +0.6 V or something
like that.
I am not sure where that is coming from.
For the ARM input, if someone is going to drive it with long coax
cables, the best would be a 50 ohm termination right at the instrument's
input.
The schematic did not make it, but I believe I understand what you mean:
3 gates with common input, each output has a 150 ohm series resistor and
the outputs (far end of the resistors) are tied together, to provide a
good 50 ohm drive to the cable. A series capacitor would probably be
recommended to center the signal around ground (assuming it's 50% duty
cycle).

Didier


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

Didier

The trigger level limits are derived from the input amplifier and
trigger circuit characteristics for the START and STOP inputs.

The ARM input feeds directly (via a 1X FET buffer) to an  ECL comparator
((MC1651).
This comparator has an NPN longtailed pair input stage the
characteristics of which determines the usable input signal range.
Driving an amplifier or comparator input stage into saturation degrades
its timing characteristics somewhat.

Bruce

I understand that the levels are what they are due to the use of ECL
logic, I was wondering from a user's perspective, was the 5370 intended
to be used only with ECL logic circuits? I am surprised that they did
not design a trigger range that included at least the "old" normal TTL
levels 0 to 5V. TTL was very common when the 5370 was designed (it uses
a lot of it internally, not so much in the timing circuits though)

Didier


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

The 5370 STOP and ARM inputs can cope with 5V TTL/CMOS levels if used
with the 10X input attenuators.

The high input impedance HP5363 time interval probes allow a much wider
-10V to +10V input range.

The ARM input has no built in attenuator, however you can use an
external attenuator with it.

Neither CMOS nor TTL were intended to drive 50 ohm loads so a high
impedance probe was usually required.
It is possible to use resistors designed into the circuit to create very
wide bandwidth 10:1 or 20: probes when driving a 50 ohm instrument.

Bruce

Didier Juges wrote: > Dr Bruce Griffiths wrote: > >> Didier Juges wrote: >> >> >>> Dr Bruce Griffiths wrote: >>> >>> >>> >>>> Didier Juges wrote: >>>> >>>> >>>> >>>> >>>>> Dr Bruce Griffiths wrote: >>>>> >>>>> >>>>> >>>>> >>>>> >>>>>> In principle this measurement could be made with a time interval counter: >>>>>> PPS -> START >>>>>> delayed 10KHz -> STOP >>>>>> >>>>>> Vary the delay and watch the jitter jump when the leading edge of the >>>>>> PPS signal occurs during the 10KHz burst which was phase coherent with >>>>>> the previous PPS pulse. >>>>>> The only problem is finding a suitable variable delay device with >>>>>> sufficiently low (<=1ns??) jitter. >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>> The delay device can be triggered by the 1 PPS, then will drive the ARM >>>>> input of the counter, so as long as the delay device's jitter is less >>>>> than the 10 kHz period, if we adjust the delay to 0.99985 second >>>>> (between the last 2 periods of 10 kHz before the 1 PPS), then the TI >>>>> counter will START on the last 10 kHz pulse before the pps, and STOP on >>>>> the 1 PPS. >>>>> Tek has some time delay generators in the TM-500 and 7000 plug-in >>>>> series. I knew one day I would need one of those, I now know why :-) >>>>> >>>>> Didier >>>>> >>>>> >>>>> _______________________________________________ >>>>> time-nuts mailing list >>>>> time-nuts@febo.com >>>>> https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>> Since the HP5370 arm input is high impedance(1 Megohm) and its input >>>> range lies betwen -2V and +2V its desirable to drive it from a back >>>> terminated source with an amplitude of 2V or less to avoid overdriving >>>> (the comparators are better behaved if the input signal remains within >>>> the specified range) the input and ensure that the pulse at the ARM is >>>> relatively clean and reflection free. A suitable buffer can be built >>>> using 3 74AC04 inverters as depicted below: The 74AC04 inverters load >>>> currents are well within the specified limits even if the buffer output >>>> is shorted to ground. Thus the driver should have a long service life. >>>> ARM driver >>>> >>>> >>>> Bruce >>>> ________________ >>>> >>>> >>>> >>> The trigger levels on the 5370 are strange. The normal inputs have >>> trigger levels that can be adjusted between -1.5 and +0.6 V or something >>> like that. >>> I am not sure where that is coming from. >>> For the ARM input, if someone is going to drive it with long coax >>> cables, the best would be a 50 ohm termination right at the instrument's >>> input. >>> The schematic did not make it, but I believe I understand what you mean: >>> 3 gates with common input, each output has a 150 ohm series resistor and >>> the outputs (far end of the resistors) are tied together, to provide a >>> good 50 ohm drive to the cable. A series capacitor would probably be >>> recommended to center the signal around ground (assuming it's 50% duty >>> cycle). >>> >>> Didier >>> _______________________________________________ >>> time-nuts mailing list >>> time-nuts@febo.com >>> https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts >>> >>> >>> >>> >> Didier >> >> The trigger level limits are derived from the input amplifier and >> trigger circuit characteristics for the START and STOP inputs. >> >> The ARM input feeds directly (via a 1X FET buffer) to an ECL comparator >> ((MC1651). >> This comparator has an NPN longtailed pair input stage the >> characteristics of which determines the usable input signal range. >> Driving an amplifier or comparator input stage into saturation degrades >> its timing characteristics somewhat. >> >> Bruce >> >> >> > I understand that the levels are what they are due to the use of ECL > logic, I was wondering from a user's perspective, was the 5370 intended > to be used only with ECL logic circuits? I am surprised that they did > not design a trigger range that included at least the "old" normal TTL > levels 0 to 5V. TTL was very common when the 5370 was designed (it uses > a lot of it internally, not so much in the timing circuits though) > > Didier > > _______________________________________________ > time-nuts mailing list > time-nuts@febo.com > https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts > > The 5370 STOP and ARM inputs can cope with 5V TTL/CMOS levels if used with the 10X input attenuators. The high input impedance HP5363 time interval probes allow a much wider -10V to +10V input range. The ARM input has no built in attenuator, however you can use an external attenuator with it. Neither CMOS nor TTL were intended to drive 50 ohm loads so a high impedance probe was usually required. It is possible to use resistors designed into the circuit to create very wide bandwidth 10:1 or 20: probes when driving a 50 ohm instrument. Bruce
UB
Ulrich Bangert
Mon, Oct 23, 2006 5:28 PM

Didier,

I need to find the best way to go from the 10 MHz sinewave to the
divider, probably through an LM119 comparator with modest
hysteresis.

the Datum LPRO User's Guide / Installation Guide discusses some methods
of sine to square wave conversion in terms of lowest phase noise.

Since you were originally asking for Allan Deviation i would like to
advertise again my free PLOTTER software which does what ALAVAR does but
more nicely + many things more. Since it does not simply open the input
file but first makes a copy to a "working file" you may even work with
it on files in that a different program is currently sampling data, so
you don't have to wait to the end of data acquistion but may get
intermediate results at any time.

When you put forward your questions about measuring Allan deviation i
saw that it were all the right & intelligent questions and perhaps this
is the reason why so many people are willing to enlighten you. I wish I
had known time nuts when i was in the same state of mind as you. Would
have saved me years of learning it the hard way!

73 de Ulrich, DF6JB

-----Ursprüngliche Nachricht-----
Von: time-nuts-bounces@febo.com
[mailto:time-nuts-bounces@febo.com] Im Auftrag von Didier Juges
Gesendet: Montag, 23. Oktober 2006 06:03
An: Discussion of precise time and frequency measurement
Betreff: Re: [time-nuts] How to measure Allan Deviation?

Bruce,

Thanks for the reminder. That was my intention. I was
planning to use a
74HC74, and whatever dividers I can get my hands on. I am not looking
forward to daisy chain seven 7490s, so I will probably try something
else. With the D flip-flop, the dividers don't really matter,
as long as
the delay is below 100nS.
I need to find the best way to go from the 10 MHz sinewave to the
divider, probably through an LM119 comparator with modest
hysteresis. The need for a low jitter divider is the same for
the GPS disciplined
oscillator, so I should be able to reuse the divider for my frequency
standard.

Thanks

Didier

Dr Bruce Griffiths wrote:

Didier

If you are going to use a PPS divider to divide the oscillator
frequency
down to 1Hz, you will need to measure the inherent jitter

of the divider

to ensure that it doesn't degrade the measurement

resolution. It may be

necessary to resynchronise the divided output using a fast

D flipflop to

reduce the inherent divider jitter to less than the 20ps

resolution of

the 5370.

Bruce


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

Didier, > I need to find the best way to go from the 10 MHz sinewave to the > divider, probably through an LM119 comparator with modest > hysteresis. the Datum LPRO User's Guide / Installation Guide discusses some methods of sine to square wave conversion in terms of lowest phase noise. Since you were originally asking for Allan Deviation i would like to advertise again my free PLOTTER software which does what ALAVAR does but more nicely + many things more. Since it does not simply open the input file but first makes a copy to a "working file" you may even work with it on files in that a different program is currently sampling data, so you don't have to wait to the end of data acquistion but may get intermediate results at any time. When you put forward your questions about measuring Allan deviation i saw that it were all the right & intelligent questions and perhaps this is the reason why so many people are willing to enlighten you. I wish I had known time nuts when i was in the same state of mind as you. Would have saved me years of learning it the hard way! 73 de Ulrich, DF6JB > -----Ursprüngliche Nachricht----- > Von: time-nuts-bounces@febo.com > [mailto:time-nuts-bounces@febo.com] Im Auftrag von Didier Juges > Gesendet: Montag, 23. Oktober 2006 06:03 > An: Discussion of precise time and frequency measurement > Betreff: Re: [time-nuts] How to measure Allan Deviation? > > > Bruce, > > Thanks for the reminder. That was my intention. I was > planning to use a > 74HC74, and whatever dividers I can get my hands on. I am not looking > forward to daisy chain seven 7490s, so I will probably try something > else. With the D flip-flop, the dividers don't really matter, > as long as > the delay is below 100nS. > I need to find the best way to go from the 10 MHz sinewave to the > divider, probably through an LM119 comparator with modest > hysteresis. The need for a low jitter divider is the same for > the GPS disciplined > oscillator, so I should be able to reuse the divider for my frequency > standard. > > Thanks > > Didier > > Dr Bruce Griffiths wrote: > > Didier > > > > If you are going to use a PPS divider to divide the oscillator > > frequency > > down to 1Hz, you will need to measure the inherent jitter > of the divider > > to ensure that it doesn't degrade the measurement > resolution. It may be > > necessary to resynchronise the divided output using a fast > D flipflop to > > reduce the inherent divider jitter to less than the 20ps > resolution of > > the 5370. > > > > Bruce > > > > > _______________________________________________ > time-nuts mailing list > time-nuts@febo.com > https://www.febo.com/cgi-> bin/mailman/listinfo/time-nuts >
TV
Tom Van Baak
Mon, Oct 23, 2006 5:46 PM

Didier,

I've been out of town and I see a flurry of postings to
your original query about Allan deviation. It sounds
like your goal is to measure the stability of various
oscillators that you have lying around?

First, your 5370 or any other TIC (Time Interval Counter)
will be adequate for this. I'd suggest using a 'scope on
the input channel(s) to make sure your signal and trigger
levels are what you think they are. Outliers or high 5370
STDEV is a hint of poor triggering.

It sounds like you have the computer data logging part
solved. Most ADEV tools take accumulated phase
difference data; just the data that a 5370 in TI mode
will generate.

Second, your Jupiter GPS board, or any other sub-100 ns
GPS timing board, will work fine. Use the 1PPS output.

You don't have to build a GPSDO in order to make the
measurements that you want! In fact, it may only get
in the way. Instead, consider these two points.

  1. For short-term stability tests, just make a set of
    quick pair-wise measurements between stand-alone
    oscillators at short gate-times. If they are close in
    frequency, or can be made close in frequency, then
    the 5370 built-in STDEV statistic is useful in real-time
    (use an N or 10 or 100). If not, collect raw phase data
    and run it through your favorite ADEV tool.

This method should work fine for fractions of a second
to 10s or 100s of seconds.

The good and bad pairs will be obvious; in a matter of
minutes you can tell which one or two oscillators are
the best, short-term.

Remember that your measurements are the RMS sum
of both oscillators and the counter itself so there will be
limits to the resolution, especially visible at short times.

  1. For long-term stability measurements, one at a time,
    compare your oscillators against the raw GPS 1PPS,
    collect phase data, and run it through your ADEV tool.

To avoid phase wrap-around, depending on the frequency
offsets, you may need to divide the 5/10 MHz oscillator
down to at least the kHz range, or the obvious 1PPS, to
get clean phase measurements.

Let the GPS 1PPS be the start channel. For this sort
of long-term measurement any TTL/CMOS homebrew
divider will work (the jitter and tempco are in the noise).

It's OK to average the samples down by 100 to 1000
to reduce the volume of data you collect or process.
I often use something around 300 (5 minutes).

This will give you frequency offset, mid- to long-term
stability, and frequency drift information. A couple of
hours or days of data per oscillator should be sufficient.

Again, you don't need to build a GPSDO for any of this.

/tvb

Didier, I've been out of town and I see a flurry of postings to your original query about Allan deviation. It sounds like your goal is to measure the stability of various oscillators that you have lying around? First, your 5370 or any other TIC (Time Interval Counter) will be adequate for this. I'd suggest using a 'scope on the input channel(s) to make sure your signal and trigger levels are what you think they are. Outliers or high 5370 STDEV is a hint of poor triggering. It sounds like you have the computer data logging part solved. Most ADEV tools take accumulated phase difference data; just the data that a 5370 in TI mode will generate. Second, your Jupiter GPS board, or any other sub-100 ns GPS timing board, will work fine. Use the 1PPS output. You don't have to build a GPSDO in order to make the measurements that you want! In fact, it may only get in the way. Instead, consider these two points. 1) For short-term stability tests, just make a set of quick pair-wise measurements between stand-alone oscillators at short gate-times. If they are close in frequency, or can be made close in frequency, then the 5370 built-in STDEV statistic is useful in real-time (use an N or 10 or 100). If not, collect raw phase data and run it through your favorite ADEV tool. This method should work fine for fractions of a second to 10s or 100s of seconds. The good and bad pairs will be obvious; in a matter of minutes you can tell which one or two oscillators are the best, short-term. Remember that your measurements are the RMS sum of both oscillators and the counter itself so there will be limits to the resolution, especially visible at short times. 2) For long-term stability measurements, one at a time, compare your oscillators against the raw GPS 1PPS, collect phase data, and run it through your ADEV tool. To avoid phase wrap-around, depending on the frequency offsets, you may need to divide the 5/10 MHz oscillator down to at least the kHz range, or the obvious 1PPS, to get clean phase measurements. Let the GPS 1PPS be the start channel. For this sort of long-term measurement any TTL/CMOS homebrew divider will work (the jitter and tempco are in the noise). It's OK to average the samples down by 100 to 1000 to reduce the volume of data you collect or process. I often use something around 300 (5 minutes). This will give you frequency offset, mid- to long-term stability, and frequency drift information. A couple of hours or days of data per oscillator should be sufficient. Again, you don't need to build a GPSDO for any of this. /tvb
DB
Dr Bruce Griffiths
Mon, Oct 23, 2006 9:52 PM

Tom Van Baak wrote:

Didier,

I've been out of town and I see a flurry of postings to
your original query about Allan deviation. It sounds
like your goal is to measure the stability of various
oscillators that you have lying around?

First, your 5370 or any other TIC (Time Interval Counter)
will be adequate for this. I'd suggest using a 'scope on
the input channel(s) to make sure your signal and trigger
levels are what you think they are. Outliers or high 5370
STDEV is a hint of poor triggering.

It sounds like you have the computer data logging part
solved. Most ADEV tools take accumulated phase
difference data; just the data that a 5370 in TI mode
will generate.

Second, your Jupiter GPS board, or any other sub-100 ns
GPS timing board, will work fine. Use the 1PPS output.

You don't have to build a GPSDO in order to make the
measurements that you want! In fact, it may only get
in the way. Instead, consider these two points.

  1. For short-term stability tests, just make a set of
    quick pair-wise measurements between stand-alone
    oscillators at short gate-times. If they are close in
    frequency, or can be made close in frequency, then
    the 5370 built-in STDEV statistic is useful in real-time
    (use an N or 10 or 100). If not, collect raw phase data
    and run it through your favorite ADEV tool.

This method should work fine for fractions of a second
to 10s or 100s of seconds.

The good and bad pairs will be obvious; in a matter of
minutes you can tell which one or two oscillators are
the best, short-term.

Remember that your measurements are the RMS sum
of both oscillators and the counter itself so there will be
limits to the resolution, especially visible at short times.

  1. For long-term stability measurements, one at a time,
    compare your oscillators against the raw GPS 1PPS,
    collect phase data, and run it through your ADEV tool.

To avoid phase wrap-around, depending on the frequency
offsets, you may need to divide the 5/10 MHz oscillator
down to at least the kHz range, or the obvious 1PPS, to
get clean phase measurements.

Let the GPS 1PPS be the start channel. For this sort
of long-term measurement any TTL/CMOS homebrew
divider will work (the jitter and tempco are in the noise).

It's OK to average the samples down by 100 to 1000
to reduce the volume of data you collect or process.
I often use something around 300 (5 minutes).

This will give you frequency offset, mid- to long-term
stability, and frequency drift information. A couple of
hours or days of data per oscillator should be sufficient.

Again, you don't need to build a GPSDO for any of this.

/tvb


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

Tom

In comparing 2 oscillators do you mean

  1. Connecting one oscillator to the FREQ STD input at the rear of the
    5370A, selecting the external timebase and connecting the other
    oscillator to the Front panel FREQ/PERIOD input and then selecting
    frequency measurement which in effect gives the frequency ratio of the 2
    oscillators?

OR

  1. Connecting the 2 oscillators to the LO and RF ports of a mixer,
    lowpass filtering the mixer output and measuring the beat frequency?

If the temperature varies over a large range whilst collecting PPS
timing data, any old divider will not suffice as particularly with a
CMOS ripple counter (eg cascaded 74HC390's) the propagation delay
(tempco ~ 0.4%/K) will vary significantly as will the receiver delay.

Bruce

Tom Van Baak wrote: > Didier, > > I've been out of town and I see a flurry of postings to > your original query about Allan deviation. It sounds > like your goal is to measure the stability of various > oscillators that you have lying around? > > First, your 5370 or any other TIC (Time Interval Counter) > will be adequate for this. I'd suggest using a 'scope on > the input channel(s) to make sure your signal and trigger > levels are what you think they are. Outliers or high 5370 > STDEV is a hint of poor triggering. > > It sounds like you have the computer data logging part > solved. Most ADEV tools take accumulated phase > difference data; just the data that a 5370 in TI mode > will generate. > > Second, your Jupiter GPS board, or any other sub-100 ns > GPS timing board, will work fine. Use the 1PPS output. > > > You don't have to build a GPSDO in order to make the > measurements that you want! In fact, it may only get > in the way. Instead, consider these two points. > > 1) For short-term stability tests, just make a set of > quick pair-wise measurements between stand-alone > oscillators at short gate-times. If they are close in > frequency, or can be made close in frequency, then > the 5370 built-in STDEV statistic is useful in real-time > (use an N or 10 or 100). If not, collect raw phase data > and run it through your favorite ADEV tool. > > This method should work fine for fractions of a second > to 10s or 100s of seconds. > > The good and bad pairs will be obvious; in a matter of > minutes you can tell which one or two oscillators are > the best, short-term. > > Remember that your measurements are the RMS sum > of both oscillators and the counter itself so there will be > limits to the resolution, especially visible at short times. > > 2) For long-term stability measurements, one at a time, > compare your oscillators against the raw GPS 1PPS, > collect phase data, and run it through your ADEV tool. > > To avoid phase wrap-around, depending on the frequency > offsets, you may need to divide the 5/10 MHz oscillator > down to at least the kHz range, or the obvious 1PPS, to > get clean phase measurements. > > Let the GPS 1PPS be the start channel. For this sort > of long-term measurement any TTL/CMOS homebrew > divider will work (the jitter and tempco are in the noise). > > It's OK to average the samples down by 100 to 1000 > to reduce the volume of data you collect or process. > I often use something around 300 (5 minutes). > > This will give you frequency offset, mid- to long-term > stability, and frequency drift information. A couple of > hours or days of data per oscillator should be sufficient. > > Again, you don't need to build a GPSDO for any of this. > > /tvb > > > _______________________________________________ > time-nuts mailing list > time-nuts@febo.com > https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts > > Tom In comparing 2 oscillators do you mean 1) Connecting one oscillator to the FREQ STD input at the rear of the 5370A, selecting the external timebase and connecting the other oscillator to the Front panel FREQ/PERIOD input and then selecting frequency measurement which in effect gives the frequency ratio of the 2 oscillators? OR 2) Connecting the 2 oscillators to the LO and RF ports of a mixer, lowpass filtering the mixer output and measuring the beat frequency? If the temperature varies over a large range whilst collecting PPS timing data, any old divider will not suffice as particularly with a CMOS ripple counter (eg cascaded 74HC390's) the propagation delay (tempco ~ 0.4%/K) will vary significantly as will the receiver delay. Bruce
MD
Magnus Danielson
Mon, Oct 23, 2006 10:22 PM

From: Dr Bruce Griffiths bruce.griffiths@xtra.co.nz
Subject: Re: [time-nuts] How to measure Allan Deviation?
Date: Tue, 24 Oct 2006 10:52:21 +1300
Message-ID: 453D3995.8080004@xtra.co.nz

Tom

Hi Bruce,

In comparing 2 oscillators do you mean

  1. Connecting one oscillator to the FREQ STD input at the rear of the
    5370A, selecting the external timebase and connecting the other
    oscillator to the Front panel FREQ/PERIOD input and then selecting
    frequency measurement which in effect gives the frequency ratio of the 2
    oscillators?

I have advocated this approach, but nobody seemed to care.

OR

  1. Connecting the 2 oscillators to the LO and RF ports of a mixer,
    lowpass filtering the mixer output and measuring the beat frequency?

Could potentially cause very long cycles which could mean unknown amounts of
wrap in the counters time-counter. Unless you ensure them to be sufficiently
offtuned so it is a very small risk.

Actually, I think he meant:

  1. Connect the two oscillators to start and stop channels and measure the TI
    results.

If the temperature varies over a large range whilst collecting PPS
timing data, any old divider will not suffice as particularly with a
CMOS ripple counter (eg cascaded 74HC390's) the propagation delay
(tempco ~ 0.4%/K) will vary significantly as will the receiver delay.

You will handle that to a high degree by a synchronising D-flip-flop clocked
with the input clock and taking the divided PPS for input. Then most effort is
on that one alone.

Cheers,
Magnus

From: Dr Bruce Griffiths <bruce.griffiths@xtra.co.nz> Subject: Re: [time-nuts] How to measure Allan Deviation? Date: Tue, 24 Oct 2006 10:52:21 +1300 Message-ID: <453D3995.8080004@xtra.co.nz> > Tom Hi Bruce, > In comparing 2 oscillators do you mean > > 1) Connecting one oscillator to the FREQ STD input at the rear of the > 5370A, selecting the external timebase and connecting the other > oscillator to the Front panel FREQ/PERIOD input and then selecting > frequency measurement which in effect gives the frequency ratio of the 2 > oscillators? I have advocated this approach, but nobody seemed to care. > OR > > 2) Connecting the 2 oscillators to the LO and RF ports of a mixer, > lowpass filtering the mixer output and measuring the beat frequency? Could potentially cause very long cycles which could mean unknown amounts of wrap in the counters time-counter. Unless you ensure them to be sufficiently offtuned so it is a very small risk. Actually, I think he meant: 0) Connect the two oscillators to start and stop channels and measure the TI results. > If the temperature varies over a large range whilst collecting PPS > timing data, any old divider will not suffice as particularly with a > CMOS ripple counter (eg cascaded 74HC390's) the propagation delay > (tempco ~ 0.4%/K) will vary significantly as will the receiver delay. You will handle that to a high degree by a synchronising D-flip-flop clocked with the input clock and taking the divided PPS for input. Then most effort is on that one alone. Cheers, Magnus
DJ
Didier Juges
Tue, Oct 24, 2006 1:20 AM

Hi Ulrich,

comments are embedded:

Ulrich Bangert wrote:

the Datum LPRO User's Guide / Installation Guide discusses some methods
of sine to square wave conversion in terms of lowest phase noise.

This is good to know. Do you have any suggestion how I might get a copy
of the relevant pages of the manual?

Since you were originally asking for Allan Deviation i would like to
advertise again my free PLOTTER software which does what ALAVAR does but
more nicely + many things more. Since it does not simply open the input
file but first makes a copy to a "working file" you may even work with
it on files in that a different program is currently sampling data, so
you don't have to wait to the end of data acquistion but may get
intermediate results at any time.

That sounds like a great feature, nothing worse than stopping a long
test period just to see if the data is any good, even though I should
get the same result by copying the log in progress in a temp file using
conventional methods. Your program saves the step and makes it that much
more convenient. I will download it. I will make sure my program does
not buffer too much data before flushing to the file, so that I get as
much of the data that is available for analysis.

When you put forward your questions about measuring Allan deviation i
saw that it were all the right & intelligent questions and perhaps this
is the reason why so many people are willing to enlighten you. I wish I
had known time nuts when i was in the same state of mind as you. Would
have saved me years of learning it the hard way!

Thank you. I am amazed at the amount and quality of support I got. I
intend to organize all the contributions in a web page. It seems like I
was not the only one with these questions, but everyone else was afraid
to ask :-)

73 de Ulrich, DF6JB

73, de Didier KO4BB

Hi Ulrich, comments are embedded: Ulrich Bangert wrote: > the Datum LPRO User's Guide / Installation Guide discusses some methods > of sine to square wave conversion in terms of lowest phase noise. > > This is good to know. Do you have any suggestion how I might get a copy of the relevant pages of the manual? > Since you were originally asking for Allan Deviation i would like to > advertise again my free PLOTTER software which does what ALAVAR does but > more nicely + many things more. Since it does not simply open the input > file but first makes a copy to a "working file" you may even work with > it on files in that a different program is currently sampling data, so > you don't have to wait to the end of data acquistion but may get > intermediate results at any time. > > That sounds like a great feature, nothing worse than stopping a long test period just to see if the data is any good, even though I should get the same result by copying the log in progress in a temp file using conventional methods. Your program saves the step and makes it that much more convenient. I will download it. I will make sure my program does not buffer too much data before flushing to the file, so that I get as much of the data that is available for analysis. > When you put forward your questions about measuring Allan deviation i > saw that it were all the right & intelligent questions and perhaps this > is the reason why so many people are willing to enlighten you. I wish I > had known time nuts when i was in the same state of mind as you. Would > have saved me years of learning it the hard way! > > Thank you. I am amazed at the amount and quality of support I got. I intend to organize all the contributions in a web page. It seems like I was not the only one with these questions, but everyone else was afraid to ask :-) > 73 de Ulrich, DF6JB > 73, de Didier KO4BB
DB
Dr Bruce Griffiths
Tue, Oct 24, 2006 1:37 AM

Didier Juges wrote:

Hi Ulrich,

comments are embedded:

Ulrich Bangert wrote:

the Datum LPRO User's Guide / Installation Guide discusses some methods
of sine to square wave conversion in terms of lowest phase noise.

This is good to know. Do you have any suggestion how I might get a copy
of the relevant pages of the manual?

Since you were originally asking for Allan Deviation i would like to
advertise again my free PLOTTER software which does what ALAVAR does but
more nicely + many things more. Since it does not simply open the input
file but first makes a copy to a "working file" you may even work with
it on files in that a different program is currently sampling data, so
you don't have to wait to the end of data acquistion but may get
intermediate results at any time.

That sounds like a great feature, nothing worse than stopping a long
test period just to see if the data is any good, even though I should
get the same result by copying the log in progress in a temp file using
conventional methods. Your program saves the step and makes it that much
more convenient. I will download it. I will make sure my program does
not buffer too much data before flushing to the file, so that I get as
much of the data that is available for analysis.

When you put forward your questions about measuring Allan deviation i
saw that it were all the right & intelligent questions and perhaps this
is the reason why so many people are willing to enlighten you. I wish I
had known time nuts when i was in the same state of mind as you. Would
have saved me years of learning it the hard way!

Thank you. I am amazed at the amount and quality of support I got. I
intend to organize all the contributions in a web page. It seems like I
was not the only one with these questions, but everyone else was afraid
to ask :-)

73 de Ulrich, DF6JB

Didier

You may also find this useful

http://www.wenzel.com/documents/waveform.html

There are some other items that may be of interest at:

http://www.wenzel.com/documents/library.html

Though you may not want to build the water barometer!!

Bruce

Didier Juges wrote: > Hi Ulrich, > > comments are embedded: > > Ulrich Bangert wrote: > >> the Datum LPRO User's Guide / Installation Guide discusses some methods >> of sine to square wave conversion in terms of lowest phase noise. >> >> >> > This is good to know. Do you have any suggestion how I might get a copy > of the relevant pages of the manual? > >> Since you were originally asking for Allan Deviation i would like to >> advertise again my free PLOTTER software which does what ALAVAR does but >> more nicely + many things more. Since it does not simply open the input >> file but first makes a copy to a "working file" you may even work with >> it on files in that a different program is currently sampling data, so >> you don't have to wait to the end of data acquistion but may get >> intermediate results at any time. >> >> >> > That sounds like a great feature, nothing worse than stopping a long > test period just to see if the data is any good, even though I should > get the same result by copying the log in progress in a temp file using > conventional methods. Your program saves the step and makes it that much > more convenient. I will download it. I will make sure my program does > not buffer too much data before flushing to the file, so that I get as > much of the data that is available for analysis. > >> When you put forward your questions about measuring Allan deviation i >> saw that it were all the right & intelligent questions and perhaps this >> is the reason why so many people are willing to enlighten you. I wish I >> had known time nuts when i was in the same state of mind as you. Would >> have saved me years of learning it the hard way! >> >> >> > Thank you. I am amazed at the amount and quality of support I got. I > intend to organize all the contributions in a web page. It seems like I > was not the only one with these questions, but everyone else was afraid > to ask :-) > >> 73 de Ulrich, DF6JB >> >> > 73, de Didier KO4BB > > > _______________________________________________ > time-nuts mailing list > time-nuts@febo.com > https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts > > Didier You may also find this useful http://www.wenzel.com/documents/waveform.html There are some other items that may be of interest at: http://www.wenzel.com/documents/library.html Though you may not want to build the water barometer!! Bruce
DB
Dr Bruce Griffiths
Tue, Oct 24, 2006 1:51 AM

Didier

Did you get my comment on HP5370A differential linearity errors.
It made it to the list but I didn't receive a bounced copy.

Bruce

Didier Did you get my comment on HP5370A differential linearity errors. It made it to the list but I didn't receive a bounced copy. Bruce
DJ
Didier Juges
Tue, Oct 24, 2006 2:15 AM

Hi Tom,

comments are embedded:

Tom Van Baak wrote:

Didier,

I've been out of town and I see a flurry of postings to
your original query about Allan deviation. It sounds
like your goal is to measure the stability of various
oscillators that you have lying around?

That's what happens when you go on vacation :-) and the answer is yes...

First, your 5370 or any other TIC (Time Interval Counter)
will be adequate for this. I'd suggest using a 'scope on
the input channel(s) to make sure your signal and trigger
levels are what you think they are. Outliers or high 5370
STDEV is a hint of poor triggering.

I do not understand the signal on the rear trigger outputs. At the
moment, I have a single 10 MHz sine signal fed to the START channel, and
the 5370 is set to  TI, MEAN, SAMPLE SIZE 1, + TI ONLY, START channel
triggers on rise and STOP channel triggers on fall, and START COM is
selected. The instrument displays about 60 nS (fairly stable, 150 ps
jitter) or so at the moment. The rear  START trigger shows a negative
going pulse (400uS wide, at 62 mS rep rate), with the rising edge
(positive going) synchronous with the 10 MHz signal and the phase is
adjustable using the STOP trigger level! When I trigger the scope on
the falling edge of the START trigger output, the 10 MHz signal seems to
drift, and the trigger setting has no effect, except that if adjusted
too far, the instrument stops updating the display.

Apparently, the START trigger adjustment has no effect on the timing of
the rear START trigger output, but will cause the display to freeze if
the START trigger is set to either extreme, even though the START
trigger output on the rear does not change.

The STOP trigger output works the opposite: it responds to the START
trigger level. Could it be that the outputs are reversed on my instrument?

I am not sure this is a complete description, and maybe there is an
obvious answer that I am missing, but I am perplexed.

It sounds like you have the computer data logging part
solved. Most ADEV tools take accumulated phase
difference data; just the data that a 5370 in TI mode
will generate.

It seems simple, but it would help to have a short sample file suitable
to feed into your favorite ADEV program just to make sure I have the
format right. It seems like I will be trying AlaVar and Plotter.

Second, your Jupiter GPS board, or any other sub-100 ns
GPS timing board, will work fine. Use the 1PPS output.

Good, thanks

You don't have to build a GPSDO in order to make the
measurements that you want! In fact, it may only get
in the way. Instead, consider these two points.

  1. For short-term stability tests, just make a set of
    quick pair-wise measurements between stand-alone
    oscillators at short gate-times. If they are close in
    frequency, or can be made close in frequency, then
    the 5370 built-in STDEV statistic is useful in real-time
    (use an N or 10 or 100). If not, collect raw phase data
    and run it through your favorite ADEV tool.

I guess I could collect the STDEV values via GPIB and plot them.

This method should work fine for fractions of a second
to 10s or 100s of seconds.

The good and bad pairs will be obvious; in a matter of
minutes you can tell which one or two oscillators are
the best, short-term.

Remember that your measurements are the RMS sum
of both oscillators and the counter itself so there will be
limits to the resolution, especially visible at short times.

  1. For long-term stability measurements, one at a time,
    compare your oscillators against the raw GPS 1PPS,
    collect phase data, and run it through your ADEV tool.

To avoid phase wrap-around, depending on the frequency
offsets, you may need to divide the 5/10 MHz oscillator
down to at least the kHz range, or the obvious 1PPS, to
get clean phase measurements.

Let the GPS 1PPS be the start channel. For this sort
of long-term measurement any TTL/CMOS homebrew
divider will work (the jitter and tempco are in the noise).

If I understand correctly, if I use the 1 PPS as the start channel, I
only need to divide the 10 MHz down to something like 1 or 10 kHz,
depending on the observation window and the frequency difference.
Someone else offered the same trick, so it sounds like a good idea.

It's OK to average the samples down by 100 to 1000
to reduce the volume of data you collect or process.
I often use something around 300 (5 minutes).

There seems to be a common agreement about that.

This will give you frequency offset, mid- to long-term
stability, and frequency drift information. A couple of
hours or days of data per oscillator should be sufficient.

I like that better than weeks or months. At least, I am sure it will be
a while before I am at the point of having to collect data for months
before I can tell my oscillators apart...

Again, you don't need to build a GPSDO for any of this.

/tvb

Thanks a bunch, but the whole point of this is to pick the best OCXO to
make a GPSDO :-)

Didier

Hi Tom, comments are embedded: Tom Van Baak wrote: > Didier, > > I've been out of town and I see a flurry of postings to > your original query about Allan deviation. It sounds > like your goal is to measure the stability of various > oscillators that you have lying around? > That's what happens when you go on vacation :-) and the answer is yes... > First, your 5370 or any other TIC (Time Interval Counter) > will be adequate for this. I'd suggest using a 'scope on > the input channel(s) to make sure your signal and trigger > levels are what you think they are. Outliers or high 5370 > STDEV is a hint of poor triggering. > I do not understand the signal on the rear trigger outputs. At the moment, I have a single 10 MHz sine signal fed to the START channel, and the 5370 is set to TI, MEAN, SAMPLE SIZE 1, + TI ONLY, START channel triggers on rise and STOP channel triggers on fall, and START COM is selected. The instrument displays about 60 nS (fairly stable, 150 ps jitter) or so at the moment. The rear START trigger shows a negative going pulse (400uS wide, at 62 mS rep rate), with the rising edge (positive going) synchronous with the 10 MHz signal and the phase is adjustable using the *STOP* trigger level! When I trigger the scope on the falling edge of the START trigger output, the 10 MHz signal seems to drift, and the trigger setting has no effect, except that if adjusted too far, the instrument stops updating the display. Apparently, the START trigger adjustment has no effect on the timing of the rear START trigger output, but will cause the display to freeze if the START trigger is set to either extreme, even though the START trigger output on the rear does not change. The STOP trigger output works the opposite: it responds to the START trigger level. Could it be that the outputs are reversed on my instrument? I am not sure this is a complete description, and maybe there is an obvious answer that I am missing, but I am perplexed. > It sounds like you have the computer data logging part > solved. Most ADEV tools take accumulated phase > difference data; just the data that a 5370 in TI mode > will generate. > It seems simple, but it would help to have a short sample file suitable to feed into your favorite ADEV program just to make sure I have the format right. It seems like I will be trying AlaVar and Plotter. > Second, your Jupiter GPS board, or any other sub-100 ns > GPS timing board, will work fine. Use the 1PPS output. > Good, thanks > You don't have to build a GPSDO in order to make the > measurements that you want! In fact, it may only get > in the way. Instead, consider these two points. > > 1) For short-term stability tests, just make a set of > quick pair-wise measurements between stand-alone > oscillators at short gate-times. If they are close in > frequency, or can be made close in frequency, then > the 5370 built-in STDEV statistic is useful in real-time > (use an N or 10 or 100). If not, collect raw phase data > and run it through your favorite ADEV tool. > I guess I could collect the STDEV values via GPIB and plot them. > This method should work fine for fractions of a second > to 10s or 100s of seconds. > > The good and bad pairs will be obvious; in a matter of > minutes you can tell which one or two oscillators are > the best, short-term. > > Remember that your measurements are the RMS sum > of both oscillators and the counter itself so there will be > limits to the resolution, especially visible at short times. > > 2) For long-term stability measurements, one at a time, > compare your oscillators against the raw GPS 1PPS, > collect phase data, and run it through your ADEV tool. > > To avoid phase wrap-around, depending on the frequency > offsets, you may need to divide the 5/10 MHz oscillator > down to at least the kHz range, or the obvious 1PPS, to > get clean phase measurements. > > Let the GPS 1PPS be the start channel. For this sort > of long-term measurement any TTL/CMOS homebrew > divider will work (the jitter and tempco are in the noise). > If I understand correctly, if I use the 1 PPS as the start channel, I only need to divide the 10 MHz down to something like 1 or 10 kHz, depending on the observation window and the frequency difference. Someone else offered the same trick, so it sounds like a good idea. > It's OK to average the samples down by 100 to 1000 > to reduce the volume of data you collect or process. > I often use something around 300 (5 minutes). > There seems to be a common agreement about that. > This will give you frequency offset, mid- to long-term > stability, and frequency drift information. A couple of > hours or days of data per oscillator should be sufficient. > I like that better than weeks or months. At least, I am sure it will be a while before I am at the point of having to collect data for months before I can tell my oscillators apart... > Again, you don't need to build a GPSDO for any of this. > > /tvb > Thanks a bunch, but the whole point of this is to pick the best OCXO to make a GPSDO :-) Didier