time-nuts@lists.febo.com

Discussion of precise time and frequency measurement

View all threads

TIC resolution impact on GPSDO's performance

UB
Ulrich Bangert
Sun, Dec 24, 2006 2:40 PM

Hi folks,

I am starting a new thread because this topic ist still discussed very
controversial. I hope this posting helps to get more insight. What
follows is by no means to be understood as an act of personal
aggression. Nevertheless I will phrase my point of view as clear as
possible. I suggest that you have a look at the attached pdf now.

First obey the dotted blue line. This is the Allan plot for a HP10811
OCXO as a typical example for what a lot of us have at hand. The
undotted blue line indicates the lowest ADEV that is reached anywhere
between 10 and 1000 s.

While it is not necessary for the understanding of the further
discussion you might want to know WHY the Allan plot has this banana
like looking: Within an oscillator an number of DIFFERENT noise
processes are active and play a part in the overall noise that the
oscillator emits. Some of these processes have the property that they
tend to cancel themselves a bit when averaged over a certain time,
others do not. The minimum of the ADEV must be considered as being
located at the averaging time where further averaging leeds to no more
improvement in noise and where the other noise processes (mainly
environmental sesibilities) that do not tend to cancel start to overrule
the scene.

While the Allan plots of different OCXOs are not identical they look all
very similar. My FTS1200 may start at 1E-12 @ 1 s and be in the range of
some parts in 1E-13 up to 1000 s. Also its ascending slope is not as
steep as the HP's one. Nevertheless it looks pretty similar. In contrast
to that the Allan plot of a simple xtal oscillator is also a banana but
may be located 4 orders of magnitude above the HP's one.

Now look to the yellow line. This is the Allan plot for a Motorola M12+
receiver if we squeeze ALL available time information out of it, i.e.
when we apply the sawtooth correction value to the 1pps. The plot starts
at 2E-9 @ 1 s and has a slope which is little bit smaller in magnitude
than -1.

Note one thing: The sawtooth correction value of the M12+ is an integer
multiple of 1 nanosecond. To make full use of this 1 ns correction
resolution it should be clear that we need to measure the receivers's 1
pps with at least the same resolution. Bruce has already pointed out a
number of times that if we want to neglect the influence of sheer
resolution at all at this point even a few ps timing resolution need not
be considered an overshot.

Clearly we see the crossing point with the OCXO's Allan plot located
between 1000 and 2000 s. Although I have already stressed it a lot in
the last days let us consider again what needs to be done it we are
going to marry this receiver with this OCXO in a GPSDO. What would
happen when we set the regulation loop's time constant to say 100 s?
Setting the loop time constant to a certain value means as much as:
Starting from that time the receiver more and more overrules the OCXO.

But then: At 100 s the ADEV of the receiver is more than an order of
magnitude worse than that of the OCXO ALONE! If we allow the receiver to
overrule the OCXO at a loop time constant of 100 s the Allan plot for
the OUTPUT of the frequency standard at 100 s will be dominated by the
receiver which will give us an inferior result than if it were dominated
by the OCXO! 100 s is not a good loop time constant!

Whats the story with a loop time constant of say 10000 s? The
argumentation is pretty much the same as for 100 s but with a role
reversal between receiver and OCXO. For the 10000 s the OCXO's ADEV is
an order of magnitude worse that that of the receiver. If we allow the
receiver to enter the scene that late the Allan plot for the OUTPUT of
the standard will be dominated by the OCXO at 10000 s which will give us
an inferior result than if it were dominated by the receiver. 10000 s is
not a good loop time constant!

For the most of you it will already now be kind of evident that the
crossing point defines the magical value that we have to set the loop
time constant to but this fact can be formulated with a bit more of
scientifical preciseness: At no observation time tau will it be possible
to have an ADEV at the OUTPUT of the standard that is lower then BOTH
Allan plots at this tau. Where should its origin come from? The very
best we can do for any tau is to find the lower of the two Allan plots
for this tau and to choose the according source as the instance that
shall dominate the standard's output at this tau. From there it is only
a small step to notice that below the crossing point the OCXO's Allan
plot is lower and above it the receiver's Allan plot is lower and that
we really have identified the crossing point as the correct loop time
constant. TVB has pointed out that marginal errors in setting the loop
time constant will not prevent the circuit to work as a frequency
standard. However this may go hand in hand with a loss in precision may
it be marginal or not so why not use the correct value?

What if we had not used the sawtooth corrected values but the raw 1pps
phase data? This situation is diagrammed by the black dotted line. Again
we have to set the loop time constant according to the crossing point
which is considerably later than with the corrected values.

This alone should not bother us but let us consider its impact: Since
below the crossing point the standard OUTPUT's Allan plot is dominated
by the OCXO we are going to create a local maximum in the standard
OUTPUT's Allan plot which we should not be especially proud of. But the
more important point is: At least up to a day or more the Allan plot of
the SAW corrected data is significant BELOW that of the uncorrected data
and this can be expressed in two ways:

  1. For a given observation time tau the standard's output will exhibit
    more stability whith the corrected data

or

  1. In order to get to an certain stability of the standard's output you
    will need longer measurement times with the uncorrected data compared to
    the corrected phase data.

This discussion does NOT take into account the awkward effects of
bridge-building that make everything even worse.

What does that all mean in reality? Suppose the distance of a satellite
in an orbit around planet Mars is going to be measured up to a
resolution and precision of a few meters (!) by means of a 'time of
flight' measurement on an electromagnetic wave that is transmitted to
the satellite and answered by an transponder. What may sound like
'rocket science' for some of you this is what radio amateurs (!) of the
AMSAT hopefully will do within a timeplan of a few years! Of course the
delay introduced by the transponder alone is determined before the start
of the satellite!

With the speed of light being app. 0.3 m/ns this will involve to measure
a time interval of some thousand s (runtime forth and back for a medium
distance Earth to Mars) with some ns precision and resolution what asks
for a abt. 1E-12 relative resolution and precision. If we do not want
that our measurements are disturbed by the statistical fluctuations of
the timebase used, these fluctuations shall be less than 1E-12 at a few
thousand seconds. With a GPSDO using SAW corrected data this is achieved
at abt. 4000-5000 s. A GPSDO using uncorrected data will have
statistical fluctuations 5 times the planned measurement resolution and
precision at this tau and will not make a suitable timebase for that
purpose.

And yes, I know that the TIE RMS and the MTIE are the better suited
statistical measures for this kind of problem but I did not want to
complicate the discussion by introducing new terms. (For those
interested: Not only does my Plotter utility compute TIE RMS and MTIE
from phase data, in the case of MTIE it does it orders of magnitude
faster than Stable32 due to a modern binary matrix de-composition
algorithm). In case you did not know: Plotter can be downloaded for free
from

http://www.ulrich-bangert.de/plotter.zip

Even for the uncorrected data we had assumed that we had measured them
with a TIC resolution small enough to neglect the effects of
quantization. What happens if the TIC in use has a quantization interval
that is in the order of the effect being measured or even bigger? If we
were measuring an infinite stable and jitter-free signal with a TIC
having a quantization interval of 41.6 ns (as in the case in the Shera
design) we will introduce statistical fluctuation sheer due to the
quantization and nothing else that are diagrammed by the red dotted
line.

The vertical distance to the yellow line (stability using SAW corrected
phase data) is almost an order of magnitude! And please don't mistake
the red dotted line with the overall result of measuring the raw phase
data with 41.6 ns quantization interval! It shows the effect of
quantization ALONE! Computing the real noise to be expected when
measureing the receiver's pps would involve to compute the RMS sum of
BOTH the receiver's noise and the quantization noise resulting in a line
that is located even adverse compared to the red line!

Brooks Shera's argument that he may average over raw phase data measured
with his 41.6 ns quantization to remove noise is correct! Indeed, the
red line may serve him as an (a bit too optimistic) estimation on how
long to average for a given noise level. His misconception has its roots
in the false conclusion that when averaging does remove noise it is
pretty much EQUIVALENT to using sawtooth corrected data. THAT is NOT
true!

Compare the red and the yellow line: Whenever the red line has reached a
certain noise level, the yellow line has reached the same noise level in
1/10 the time. Or argument the other way around: Surely a Shera standard
can reach a stability level of 1E-12 (We leave questions of DAC
resolution and/or tempcos of parts and solder joints(!) out of the
discussion. They can only make things worse) But consider at what
observation times tau this is possible: 40000-50000 s. Not to be used
for the Mars ranging where we need this stability at 4000 s! Where the
Shera design needs to get by heavy averaging a design using SAW
corrected values gets in 1/10 the time due to using less noisier input
data! Got the clue?

This is ONLY due to the 41.6 ns quantization interval and that is the
reason why Bruce and I insist on the proposition that the noise
introduced by the 41.6 ns quantization interval is the dominant one in
the Shera design and that this noise is a factor 10-20 worse than that
of the best receivers available today.

I leave it to your own judgement whether claims like

In most cases you can... Forget the quantization error.

or

In summary, it appears that 1pps sawtooth/bridge noise can be ignored

for a

GPSDO.

are consistent with the laws of physics and mathematics.

Hey Brooks, you are an fantastic engineer but claims like this are not
worth to leave your mouth!

Best regards and a Merry Christmas for everyone in the group
Ulrich Bangert, DF6JB

Hi folks, I am starting a new thread because this topic ist still discussed very controversial. I hope this posting helps to get more insight. What follows is by no means to be understood as an act of personal aggression. Nevertheless I will phrase my point of view as clear as possible. I suggest that you have a look at the attached pdf now. First obey the dotted blue line. This is the Allan plot for a HP10811 OCXO as a typical example for what a lot of us have at hand. The undotted blue line indicates the lowest ADEV that is reached anywhere between 10 and 1000 s. While it is not necessary for the understanding of the further discussion you might want to know WHY the Allan plot has this banana like looking: Within an oscillator an number of DIFFERENT noise processes are active and play a part in the overall noise that the oscillator emits. Some of these processes have the property that they tend to cancel themselves a bit when averaged over a certain time, others do not. The minimum of the ADEV must be considered as being located at the averaging time where further averaging leeds to no more improvement in noise and where the other noise processes (mainly environmental sesibilities) that do not tend to cancel start to overrule the scene. While the Allan plots of different OCXOs are not identical they look all very similar. My FTS1200 may start at 1E-12 @ 1 s and be in the range of some parts in 1E-13 up to 1000 s. Also its ascending slope is not as steep as the HP's one. Nevertheless it looks pretty similar. In contrast to that the Allan plot of a simple xtal oscillator is also a banana but may be located 4 orders of magnitude above the HP's one. Now look to the yellow line. This is the Allan plot for a Motorola M12+ receiver if we squeeze ALL available time information out of it, i.e. when we apply the sawtooth correction value to the 1pps. The plot starts at 2E-9 @ 1 s and has a slope which is little bit smaller in magnitude than -1. Note one thing: The sawtooth correction value of the M12+ is an integer multiple of 1 nanosecond. To make full use of this 1 ns correction resolution it should be clear that we need to measure the receivers's 1 pps with at least the same resolution. Bruce has already pointed out a number of times that if we want to neglect the influence of sheer resolution at all at this point even a few ps timing resolution need not be considered an overshot. Clearly we see the crossing point with the OCXO's Allan plot located between 1000 and 2000 s. Although I have already stressed it a lot in the last days let us consider again what needs to be done it we are going to marry this receiver with this OCXO in a GPSDO. What would happen when we set the regulation loop's time constant to say 100 s? Setting the loop time constant to a certain value means as much as: Starting from that time the receiver more and more overrules the OCXO. But then: At 100 s the ADEV of the receiver is more than an order of magnitude worse than that of the OCXO ALONE! If we allow the receiver to overrule the OCXO at a loop time constant of 100 s the Allan plot for the OUTPUT of the frequency standard at 100 s will be dominated by the receiver which will give us an inferior result than if it were dominated by the OCXO! 100 s is not a good loop time constant! Whats the story with a loop time constant of say 10000 s? The argumentation is pretty much the same as for 100 s but with a role reversal between receiver and OCXO. For the 10000 s the OCXO's ADEV is an order of magnitude worse that that of the receiver. If we allow the receiver to enter the scene that late the Allan plot for the OUTPUT of the standard will be dominated by the OCXO at 10000 s which will give us an inferior result than if it were dominated by the receiver. 10000 s is not a good loop time constant! For the most of you it will already now be kind of evident that the crossing point defines the magical value that we have to set the loop time constant to but this fact can be formulated with a bit more of scientifical preciseness: At no observation time tau will it be possible to have an ADEV at the OUTPUT of the standard that is lower then BOTH Allan plots at this tau. Where should its origin come from? The very best we can do for any tau is to find the lower of the two Allan plots for this tau and to choose the according source as the instance that shall dominate the standard's output at this tau. From there it is only a small step to notice that below the crossing point the OCXO's Allan plot is lower and above it the receiver's Allan plot is lower and that we really have identified the crossing point as the correct loop time constant. TVB has pointed out that marginal errors in setting the loop time constant will not prevent the circuit to work as a frequency standard. However this may go hand in hand with a loss in precision may it be marginal or not so why not use the correct value? What if we had not used the sawtooth corrected values but the raw 1pps phase data? This situation is diagrammed by the black dotted line. Again we have to set the loop time constant according to the crossing point which is considerably later than with the corrected values. This alone should not bother us but let us consider its impact: Since below the crossing point the standard OUTPUT's Allan plot is dominated by the OCXO we are going to create a local maximum in the standard OUTPUT's Allan plot which we should not be especially proud of. But the more important point is: At least up to a day or more the Allan plot of the SAW corrected data is significant BELOW that of the uncorrected data and this can be expressed in two ways: 1) For a given observation time tau the standard's output will exhibit more stability whith the corrected data or 2) In order to get to an certain stability of the standard's output you will need longer measurement times with the uncorrected data compared to the corrected phase data. This discussion does NOT take into account the awkward effects of bridge-building that make everything even worse. What does that all mean in reality? Suppose the distance of a satellite in an orbit around planet Mars is going to be measured up to a resolution and precision of a few meters (!) by means of a 'time of flight' measurement on an electromagnetic wave that is transmitted to the satellite and answered by an transponder. What may sound like 'rocket science' for some of you this is what radio amateurs (!) of the AMSAT hopefully will do within a timeplan of a few years! Of course the delay introduced by the transponder alone is determined before the start of the satellite! With the speed of light being app. 0.3 m/ns this will involve to measure a time interval of some thousand s (runtime forth and back for a medium distance Earth to Mars) with some ns precision and resolution what asks for a abt. 1E-12 relative resolution and precision. If we do not want that our measurements are disturbed by the statistical fluctuations of the timebase used, these fluctuations shall be less than 1E-12 at a few thousand seconds. With a GPSDO using SAW corrected data this is achieved at abt. 4000-5000 s. A GPSDO using uncorrected data will have statistical fluctuations 5 times the planned measurement resolution and precision at this tau and will not make a suitable timebase for that purpose. And yes, I know that the TIE RMS and the MTIE are the better suited statistical measures for this kind of problem but I did not want to complicate the discussion by introducing new terms. (For those interested: Not only does my Plotter utility compute TIE RMS and MTIE from phase data, in the case of MTIE it does it orders of magnitude faster than Stable32 due to a modern binary matrix de-composition algorithm). In case you did not know: Plotter can be downloaded for free from http://www.ulrich-bangert.de/plotter.zip Even for the uncorrected data we had assumed that we had measured them with a TIC resolution small enough to neglect the effects of quantization. What happens if the TIC in use has a quantization interval that is in the order of the effect being measured or even bigger? If we were measuring an infinite stable and jitter-free signal with a TIC having a quantization interval of 41.6 ns (as in the case in the Shera design) we will introduce statistical fluctuation sheer due to the quantization and nothing else that are diagrammed by the red dotted line. The vertical distance to the yellow line (stability using SAW corrected phase data) is almost an order of magnitude! And please don't mistake the red dotted line with the overall result of measuring the raw phase data with 41.6 ns quantization interval! It shows the effect of quantization ALONE! Computing the real noise to be expected when measureing the receiver's pps would involve to compute the RMS sum of BOTH the receiver's noise and the quantization noise resulting in a line that is located even adverse compared to the red line! Brooks Shera's argument that he may average over raw phase data measured with his 41.6 ns quantization to remove noise is correct! Indeed, the red line may serve him as an (a bit too optimistic) estimation on how long to average for a given noise level. His misconception has its roots in the false conclusion that when averaging does remove noise it is pretty much EQUIVALENT to using sawtooth corrected data. THAT is NOT true! Compare the red and the yellow line: Whenever the red line has reached a certain noise level, the yellow line has reached the same noise level in 1/10 the time. Or argument the other way around: Surely a Shera standard can reach a stability level of 1E-12 (We leave questions of DAC resolution and/or tempcos of parts and solder joints(!) out of the discussion. They can only make things worse) But consider at what observation times tau this is possible: 40000-50000 s. Not to be used for the Mars ranging where we need this stability at 4000 s! Where the Shera design needs to get by heavy averaging a design using SAW corrected values gets in 1/10 the time due to using less noisier input data! Got the clue? This is ONLY due to the 41.6 ns quantization interval and that is the reason why Bruce and I insist on the proposition that the noise introduced by the 41.6 ns quantization interval is the dominant one in the Shera design and that this noise is a factor 10-20 worse than that of the best receivers available today. I leave it to your own judgement whether claims like > In most cases you can... Forget the quantization error. or > In summary, it appears that 1pps sawtooth/bridge noise can be ignored for a > GPSDO. are consistent with the laws of physics and mathematics. Hey Brooks, you are an fantastic engineer but claims like this are not worth to leave your mouth! Best regards and a Merry Christmas for everyone in the group Ulrich Bangert, DF6JB
TV
Tom Van Baak
Sun, Dec 24, 2006 11:03 PM

Hi Ulrich,

Thanks for your note on TIC resolution and the very
nice plot you attached. Here are some comments:

  1. Could you clarify for us what points in your plot
    are real measured data and what points, if any, are
    simulated?

  2. Have you looked into why your Comparison.pdf
    plot doesn't have the same look as SigmaTauBoth
    (photo_gallery_44.html)?

Do both represent the same thing (M12/sawtooth
vs. M12/corrected) or did I misunderstand one of
them. Because they do seem to have a different
look.

The red and black lines are parallel while black
and yellow appear to merge (like chopsticks).

But the horizon point (where the lines meet) for the
SigmaTauBoth plot is around tau 1 day while the
horizon point for Comparison.pdf, as best I can tell,
is around tau 10^8 seconds (about 1000 days).

  1. For the sake of contrast, and to make your plot
    even better, would you be able to add another OCXO
    or two?

For example, perhaps add one that performs closer
to the 10811 spec (e.g. drift rate of 5e-10/day) and
one that is a lesser grade, an Ovenaire or CTS class
of OCXO or TCXO with short-term stability in the -10's
and drift rate in the -9's. I can provide the data if you
need it.

Perhaps other readers can suggest their own OCXO
or Rb.

  1. I'm wondering if you could conclude something
    interesting if your plot separated the OCXO issue,
    from the GPS engine issue, from the TIC issue
    rather than lumping the GPS and TIC together into
    one line.

For example, in addition to different examples of
OCXO (low, medium, and high-performance) and
different GPS engines (e.g., Oncore VP, M12 with
sawtooth, M12/corrected), do you think you could
you also add different TIC resolutions?

For example, HP 53131 (500 ps) vs. 53132 (150 ps)
vs. 5334 (2 ns) vs. 5370 and SRS 620 (25 ps). You
can also add Shera (42?ns) and Jackson (8?ns).

Perhaps other readers can suggest different ones.

I'll have a few more comments later.

/tvb

Hi Ulrich, Thanks for your note on TIC resolution and the very nice plot you attached. Here are some comments: 1. Could you clarify for us what points in your plot are real measured data and what points, if any, are simulated? 2. Have you looked into why your Comparison.pdf plot doesn't have the same look as SigmaTauBoth (photo_gallery_44.html)? Do both represent the same thing (M12/sawtooth vs. M12/corrected) or did I misunderstand one of them. Because they do seem to have a different look. The red and black lines are parallel while black and yellow appear to merge (like chopsticks). But the horizon point (where the lines meet) for the SigmaTauBoth plot is around tau 1 day while the horizon point for Comparison.pdf, as best I can tell, is around tau 10^8 seconds (about 1000 days). 3. For the sake of contrast, and to make your plot even better, would you be able to add another OCXO or two? For example, perhaps add one that performs closer to the 10811 spec (e.g. drift rate of 5e-10/day) and one that is a lesser grade, an Ovenaire or CTS class of OCXO or TCXO with short-term stability in the -10's and drift rate in the -9's. I can provide the data if you need it. Perhaps other readers can suggest their own OCXO or Rb. 4. I'm wondering if you could conclude something interesting if your plot separated the OCXO issue, from the GPS engine issue, from the TIC issue rather than lumping the GPS and TIC together into one line. For example, in addition to different examples of OCXO (low, medium, and high-performance) and different GPS engines (e.g., Oncore VP, M12 with sawtooth, M12/corrected), do you think you could you also add different TIC resolutions? For example, HP 53131 (500 ps) vs. 53132 (150 ps) vs. 5334 (2 ns) vs. 5370 and SRS 620 (25 ps). You can also add Shera (42?ns) and Jackson (8?ns). Perhaps other readers can suggest different ones. I'll have a few more comments later. /tvb
PK
Poul-Henning Kamp
Sun, Dec 24, 2006 11:51 PM

In message 000001c72769$8363beb0$03b2fea9@athlon, "Ulrich Bangert" writes:

For the most of you it will already now be kind of evident that the
crossing point defines the magical value that we have to set the loop
time constant to but this fact can be formulated with a bit more of
scientifical preciseness: At no observation time tau will it be possible
to have an ADEV at the OUTPUT of the standard that is lower then BOTH
Allan plots at this tau.

This is not true in general, but does hold true for the example you
have chosen.  The exact requirement for truthfullness is that the
noise-processes of your two sources must be uncorrelated.

What if we had not used the sawtooth corrected values but the raw 1pps
phase data?

Your black line is bogus in the usual "teacher's bad example way".

We know that the hardware PPS signal from gps is phasemodulated
with a +/- N ns signal which has a box distribution and upper
frequency limit of 2 Hz and which, subject to temperature stability
and hanging bridges, has no significant frequency components below
< 1/500s.

It follows readily for this, that only teachers trying to show a
bad example would use the PPS signal for tau > 500 second without
filtering the higher frequencies out, one way or another.

(In the initial capture phase, no filtering should be used to get
the best possible frequency response of the PLL, in the "grab" phase
where the integrator is clamped, a simple exponential average should
be used.  Once lock has been aquired, linear regression offers a
useful zero-latency filtering model.)

Your black line should have reflected this.

But your further argument has trouble as well.

No causal algorithm can allow you to implement:

if (tau < N)
	use OCXO
else
	use GPS

For some interval of tau, both sources will affect the result, if
you do post-factum disciplines (ie: paper clocks) you can do it a
lot closer to optimal, but the statistics gets increasingly nasty
and the age of your data will approach infinity as the fidelity
increases.

But most fatal to your message: you look at the wrong kind of stats
for this particular kind of discipline.

When you discipline an frequency source (OCXO, Rb, Cs) to a phase
source (GPS, Loran-C, WWV, DCF77, NTP etc), you have to decide for
which parameter you (optimize your) discipline:

Minimum phase offset.
Minimum frequency offset.
Best phase stability.
Best frequency stability.
Best holdover performance in phase.
Best holdover performance in frequency.

All I have heard about here so far, is the first and a few cases
of the second kind, and neither of those shows their performance
particularly well on an ADEV plot.

And most amateurs even forget to deal with quartz frequency jumps
and other 'point-like' upsets.

The theory behind a PLL is really no different from a PID temperature
regulation, and I highly recommend people read up on those because
they are generally explained much better than when PLL's are the
subject.

Before you get any good ideas: note that our measurement noise
(jitter/resolution) only for very long tau permits meaningful use
of the D(ifferential) term.  It is possible to use a hysteresis on
the D term to catch frequency jumps in the xtal, but it is of dubious
advantage compared to just detecting and resetting the PLL).

A less significant difference from PID regulations is higher order
integrals:  They are not useful for temperature regulation, but if
you want to get really nasty with your PLL, you can add another
term to model the frequency drift, and another one to model the
change in frequency drift and another one to model the change in the
change of the frequency drift and ... (you get the idea).

Be aware that floating point is necessary and that rounding errors
will mess you up if you are not very careful with your sums and
differences.

I can highly recommend writing a small program or big spreadsheet
to simulate a PLL so you can play with the coefficients and get a
feel for the dynamics by watching plots of the phase and frequency
deltas and ADEV etc.

Merry X-mas!

Poul-Henning

--
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 <000001c72769$8363beb0$03b2fea9@athlon>, "Ulrich Bangert" writes: >For the most of you it will already now be kind of evident that the >crossing point defines the magical value that we have to set the loop >time constant to but this fact can be formulated with a bit more of >scientifical preciseness: At no observation time tau will it be possible >to have an ADEV at the OUTPUT of the standard that is lower then BOTH >Allan plots at this tau. This is not true in general, but does hold true for the example you have chosen. The exact requirement for truthfullness is that the noise-processes of your two sources must be uncorrelated. >What if we had not used the sawtooth corrected values but the raw 1pps >phase data? Your black line is bogus in the usual "teacher's bad example way". We know that the hardware PPS signal from gps is phasemodulated with a +/- N ns signal which has a box distribution and upper frequency limit of 2 Hz and which, subject to temperature stability and hanging bridges, has no significant frequency components below < 1/500s. It follows readily for this, that only teachers trying to show a bad example would use the PPS signal for tau > 500 second without filtering the higher frequencies out, one way or another. (In the initial capture phase, no filtering should be used to get the best possible frequency response of the PLL, in the "grab" phase where the integrator is clamped, a simple exponential average should be used. Once lock has been aquired, linear regression offers a useful zero-latency filtering model.) Your black line should have reflected this. But your further argument has trouble as well. No causal algorithm can allow you to implement: if (tau < N) use OCXO else use GPS For some interval of tau, both sources will affect the result, if you do post-factum disciplines (ie: paper clocks) you can do it a lot closer to optimal, but the statistics gets increasingly nasty and the age of your data will approach infinity as the fidelity increases. But most fatal to your message: you look at the wrong kind of stats for this particular kind of discipline. When you discipline an frequency source (OCXO, Rb, Cs) to a phase source (GPS, Loran-C, WWV, DCF77, NTP etc), you have to decide for which parameter you (optimize your) discipline: Minimum phase offset. Minimum frequency offset. Best phase stability. Best frequency stability. Best holdover performance in phase. Best holdover performance in frequency. All I have heard about here so far, is the first and a few cases of the second kind, and neither of those shows their performance particularly well on an ADEV plot. And most amateurs even forget to deal with quartz frequency jumps and other 'point-like' upsets. The theory behind a PLL is really no different from a PID temperature regulation, and I highly recommend people read up on those because they are generally explained much better than when PLL's are the subject. Before you get any good ideas: note that our measurement noise (jitter/resolution) only for very long tau permits meaningful use of the D(ifferential) term. It is possible to use a hysteresis on the D term to catch frequency jumps in the xtal, but it is of dubious advantage compared to just detecting and resetting the PLL). A less significant difference from PID regulations is higher order integrals: They are not useful for temperature regulation, but if you want to get really nasty with your PLL, you can add another term to model the frequency drift, and another one to model the change in frequency drift and another one to model the change in the change of the frequency drift and ... (you get the idea). Be aware that floating point is necessary and that rounding errors will mess you up if you are not very careful with your sums and differences. I can highly recommend writing a small program or big spreadsheet to simulate a PLL so you can play with the coefficients and get a feel for the dynamics by watching plots of the phase and frequency deltas and ADEV etc. Merry X-mas! Poul-Henning -- 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.
DB
Dr Bruce Griffiths
Mon, Dec 25, 2006 12:37 AM

Poul-Henning Kamp wrote:

In message 000001c72769$8363beb0$03b2fea9@athlon, "Ulrich Bangert" writes:

For the most of you it will already now be kind of evident that the
crossing point defines the magical value that we have to set the loop
time constant to but this fact can be formulated with a bit more of
scientifical preciseness: At no observation time tau will it be possible
to have an ADEV at the OUTPUT of the standard that is lower then BOTH
Allan plots at this tau.

This is not true in general, but does hold true for the example you
have chosen.  The exact requirement for truthfullness is that the
noise-processes of your two sources must be uncorrelated.

What if we had not used the sawtooth corrected values but the raw 1pps
phase data?

Your black line is bogus in the usual "teacher's bad example way".

We know that the hardware PPS signal from gps is phasemodulated
with a +/- N ns signal which has a box distribution and upper
frequency limit of 2 Hz and which, subject to temperature stability
and hanging bridges, has no significant frequency components below
< 1/500s.

Has this been established by actual measurement?
Ignoring the combined effects of quantisation and coherence would not
seem to be very sensible.

It follows readily for this, that only teachers trying to show a
bad example would use the PPS signal for tau > 500 second without
filtering the higher frequencies out, one way or another.

(In the initial capture phase, no filtering should be used to get
the best possible frequency response of the PLL, in the "grab" phase
where the integrator is clamped, a simple exponential average should
be used.  Once lock has been aquired, linear regression offers a
useful zero-latency filtering model.)

Your black line should have reflected this.

But your further argument has trouble as well.

No causal algorithm can allow you to implement:

if (tau < N)
	use OCXO
else
	use GPS

For some interval of tau, both sources will affect the result, if
you do post-factum disciplines (ie: paper clocks) you can do it a
lot closer to optimal, but the statistics gets increasingly nasty
and the age of your data will approach infinity as the fidelity
increases.

But most fatal to your message: you look at the wrong kind of stats
for this particular kind of discipline.

When you discipline an frequency source (OCXO, Rb, Cs) to a phase
source (GPS, Loran-C, WWV, DCF77, NTP etc), you have to decide for
which parameter you (optimize your) discipline:

Minimum phase offset.
Minimum frequency offset.
Best phase stability.
Best frequency stability.
Best holdover performance in phase.
Best holdover performance in frequency.

All I have heard about here so far, is the first and a few cases
of the second kind, and neither of those shows their performance
particularly well on an ADEV plot.

And most amateurs even forget to deal with quartz frequency jumps
and other 'point-like' upsets.

The theory behind a PLL is really no different from a PID temperature
regulation, and I highly recommend people read up on those because
they are generally explained much better than when PLL's are the
subject.

Before you get any good ideas: note that our measurement noise
(jitter/resolution) only for very long tau permits meaningful use
of the D(ifferential) term.  It is possible to use a hysteresis on
the D term to catch frequency jumps in the xtal, but it is of dubious
advantage compared to just detecting and resetting the PLL).

A less significant difference from PID regulations is higher order
integrals:  They are not useful for temperature regulation,

This is not true, using a second integrator in a crystal oscillator
temperature regulation loop can be very effective, as indicated in the
following paper:
A LOW-PROFILE HIGH-PERFORMANCE CRYSTAL OSCILLATOR FOR TIMEKEEPING
APPLICATIONS
R. K. Karlquist**, L. S. Cutler**, E. M. Ingman*, J. L. Johnson**, and
T. Parisek*
available at:
http://www.karlquist.com/osc.pdf

but if
you want to get really nasty with your PLL, you can add another
term to model the frequency drift, and another one to model the
change in frequency drift and another one to model the change in the
change of the frequency drift and ... (you get the idea).

Be aware that floating point is necessary and that rounding errors
will mess you up if you are not very careful with your sums and
differences.

I can highly recommend writing a small program or big spreadsheet
to simulate a PLL so you can play with the coefficients and get a
feel for the dynamics by watching plots of the phase and frequency
deltas and ADEV etc.

Merry X-mas!

Poul-Henning

Poul-Henning

One correction and a query

Bruce

Poul-Henning Kamp wrote: > In message <000001c72769$8363beb0$03b2fea9@athlon>, "Ulrich Bangert" writes: > > >> For the most of you it will already now be kind of evident that the >> crossing point defines the magical value that we have to set the loop >> time constant to but this fact can be formulated with a bit more of >> scientifical preciseness: At no observation time tau will it be possible >> to have an ADEV at the OUTPUT of the standard that is lower then BOTH >> Allan plots at this tau. >> > > This is not true in general, but does hold true for the example you > have chosen. The exact requirement for truthfullness is that the > noise-processes of your two sources must be uncorrelated. > > >> What if we had not used the sawtooth corrected values but the raw 1pps >> phase data? >> > > Your black line is bogus in the usual "teacher's bad example way". > > We know that the hardware PPS signal from gps is phasemodulated > with a +/- N ns signal which has a box distribution and upper > frequency limit of 2 Hz and which, subject to temperature stability > and hanging bridges, has no significant frequency components below > < 1/500s. > > Has this been established by actual measurement? Ignoring the combined effects of quantisation and coherence would not seem to be very sensible. > It follows readily for this, that only teachers trying to show a > bad example would use the PPS signal for tau > 500 second without > filtering the higher frequencies out, one way or another. > > (In the initial capture phase, no filtering should be used to get > the best possible frequency response of the PLL, in the "grab" phase > where the integrator is clamped, a simple exponential average should > be used. Once lock has been aquired, linear regression offers a > useful zero-latency filtering model.) > > Your black line should have reflected this. > > > But your further argument has trouble as well. > > No causal algorithm can allow you to implement: > > if (tau < N) > use OCXO > else > use GPS > > For some interval of tau, both sources will affect the result, if > you do post-factum disciplines (ie: paper clocks) you can do it a > lot closer to optimal, but the statistics gets increasingly nasty > and the age of your data will approach infinity as the fidelity > increases. > > But most fatal to your message: you look at the wrong kind of stats > for this particular kind of discipline. > > When you discipline an frequency source (OCXO, Rb, Cs) to a phase > source (GPS, Loran-C, WWV, DCF77, NTP etc), you have to decide for > which parameter you (optimize your) discipline: > > Minimum phase offset. > Minimum frequency offset. > Best phase stability. > Best frequency stability. > Best holdover performance in phase. > Best holdover performance in frequency. > > All I have heard about here so far, is the first and a few cases > of the second kind, and neither of those shows their performance > particularly well on an ADEV plot. > > And most amateurs even forget to deal with quartz frequency jumps > and other 'point-like' upsets. > > The theory behind a PLL is really no different from a PID temperature > regulation, and I highly recommend people read up on those because > they are generally explained much better than when PLL's are the > subject. > > Before you get any good ideas: note that our measurement noise > (jitter/resolution) only for very long tau permits meaningful use > of the D(ifferential) term. It is possible to use a hysteresis on > the D term to catch frequency jumps in the xtal, but it is of dubious > advantage compared to just detecting and resetting the PLL). > > A less significant difference from PID regulations is higher order > integrals: They are not useful for temperature regulation, This is not true, using a second integrator in a crystal oscillator temperature regulation loop can be very effective, as indicated in the following paper: A LOW-PROFILE HIGH-PERFORMANCE CRYSTAL OSCILLATOR FOR TIMEKEEPING APPLICATIONS R. K. Karlquist**, L. S. Cutler**, E. M. Ingman*, J. L. Johnson**, and T. Parisek* available at: http://www.karlquist.com/osc.pdf > but if > you want to get really nasty with your PLL, you can add another > term to model the frequency drift, and another one to model the > change in frequency drift and another one to model the change in the > change of the frequency drift and ... (you get the idea). > > Be aware that floating point is necessary and that rounding errors > will mess you up if you are not very careful with your sums and > differences. > > I can highly recommend writing a small program or big spreadsheet > to simulate a PLL so you can play with the coefficients and get a > feel for the dynamics by watching plots of the phase and frequency > deltas and ADEV etc. > > Merry X-mas! > > Poul-Henning > > Poul-Henning One correction and a query Bruce
DB
Dr Bruce Griffiths
Mon, Dec 25, 2006 5:02 AM

Poul-Henning Kamp wrote:

In message 000001c72769$8363beb0$03b2fea9@athlon, "Ulrich Bangert" writes:

For the most of you it will already now be kind of evident that the
crossing point defines the magical value that we have to set the loop
time constant to but this fact can be formulated with a bit more of
scientifical preciseness: At no observation time tau will it be possible
to have an ADEV at the OUTPUT of the standard that is lower then BOTH
Allan plots at this tau.

This is not true in general, but does hold true for the example you
have chosen.  The exact requirement for truthfullness is that the
noise-processes of your two sources must be uncorrelated.

What if we had not used the sawtooth corrected values but the raw 1pps
phase data?

Your black line is bogus in the usual "teacher's bad example way".

We know that the hardware PPS signal from gps is phasemodulated
with a +/- N ns signal which has a box distribution and upper
frequency limit of 2 Hz and which, subject to temperature stability
and hanging bridges, has no significant frequency components below
< 1/500s.

How can this be true?
The PPS output rate is 1Hz!
Are you saying there is significant wideband noise on the 1 PPS output?
Is that lower frequency limit 0.002Hz?

It follows readily for this, that only teachers trying to show a
bad example would use the PPS signal for tau > 500 second without
filtering the higher frequencies out, one way or another.

(In the initial capture phase, no filtering should be used to get
the best possible frequency response of the PLL, in the "grab" phase
where the integrator is clamped, a simple exponential average should
be used.  Once lock has been aquired, linear regression offers a
useful zero-latency filtering model.)

Your black line should have reflected this.

But your further argument has trouble as well.

No causal algorithm can allow you to implement:

if (tau < N)
	use OCXO
else
	use GPS

For some interval of tau, both sources will affect the result, if
you do post-factum disciplines (ie: paper clocks) you can do it a
lot closer to optimal, but the statistics gets increasingly nasty
and the age of your data will approach infinity as the fidelity
increases.

But most fatal to your message: you look at the wrong kind of stats
for this particular kind of discipline.

When you discipline an frequency source (OCXO, Rb, Cs) to a phase
source (GPS, Loran-C, WWV, DCF77, NTP etc), you have to decide for
which parameter you (optimize your) discipline:

Minimum phase offset.
Minimum frequency offset.
Best phase stability.
Best frequency stability.
Best holdover performance in phase.
Best holdover performance in frequency.

All I have heard about here so far, is the first and a few cases
of the second kind, and neither of those shows their performance
particularly well on an ADEV plot.

And most amateurs even forget to deal with quartz frequency jumps
and other 'point-like' upsets.

The theory behind a PLL is really no different from a PID temperature
regulation, and I highly recommend people read up on those because
they are generally explained much better than when PLL's are the
subject.

Before you get any good ideas: note that our measurement noise
(jitter/resolution) only for very long tau permits meaningful use
of the D(ifferential) term.  It is possible to use a hysteresis on
the D term to catch frequency jumps in the xtal, but it is of dubious
advantage compared to just detecting and resetting the PLL).

A less significant difference from PID regulations is higher order
integrals:  They are not useful for temperature regulation, but if
you want to get really nasty with your PLL, you can add another
term to model the frequency drift, and another one to model the
change in frequency drift and another one to model the change in the
change of the frequency drift and ... (you get the idea).

Be aware that floating point is necessary and that rounding errors
will mess you up if you are not very careful with your sums and
differences.

I can highly recommend writing a small program or big spreadsheet
to simulate a PLL so you can play with the coefficients and get a
feel for the dynamics by watching plots of the phase and frequency
deltas and ADEV etc.

Merry X-mas!

Poul-Henning

Bruce

Poul-Henning Kamp wrote: > In message <000001c72769$8363beb0$03b2fea9@athlon>, "Ulrich Bangert" writes: > > >> For the most of you it will already now be kind of evident that the >> crossing point defines the magical value that we have to set the loop >> time constant to but this fact can be formulated with a bit more of >> scientifical preciseness: At no observation time tau will it be possible >> to have an ADEV at the OUTPUT of the standard that is lower then BOTH >> Allan plots at this tau. >> > > This is not true in general, but does hold true for the example you > have chosen. The exact requirement for truthfullness is that the > noise-processes of your two sources must be uncorrelated. > > >> What if we had not used the sawtooth corrected values but the raw 1pps >> phase data? >> > > Your black line is bogus in the usual "teacher's bad example way". > > We know that the hardware PPS signal from gps is phasemodulated > with a +/- N ns signal which has a box distribution and upper > frequency limit of 2 Hz and which, subject to temperature stability > and hanging bridges, has no significant frequency components below > < 1/500s. > How can this be true? The PPS output rate is 1Hz! Are you saying there is significant wideband noise on the 1 PPS output? Is that lower frequency limit 0.002Hz? > It follows readily for this, that only teachers trying to show a > bad example would use the PPS signal for tau > 500 second without > filtering the higher frequencies out, one way or another. > > (In the initial capture phase, no filtering should be used to get > the best possible frequency response of the PLL, in the "grab" phase > where the integrator is clamped, a simple exponential average should > be used. Once lock has been aquired, linear regression offers a > useful zero-latency filtering model.) > > Your black line should have reflected this. > > > But your further argument has trouble as well. > > No causal algorithm can allow you to implement: > > if (tau < N) > use OCXO > else > use GPS > > For some interval of tau, both sources will affect the result, if > you do post-factum disciplines (ie: paper clocks) you can do it a > lot closer to optimal, but the statistics gets increasingly nasty > and the age of your data will approach infinity as the fidelity > increases. > > But most fatal to your message: you look at the wrong kind of stats > for this particular kind of discipline. > > When you discipline an frequency source (OCXO, Rb, Cs) to a phase > source (GPS, Loran-C, WWV, DCF77, NTP etc), you have to decide for > which parameter you (optimize your) discipline: > > Minimum phase offset. > Minimum frequency offset. > Best phase stability. > Best frequency stability. > Best holdover performance in phase. > Best holdover performance in frequency. > > All I have heard about here so far, is the first and a few cases > of the second kind, and neither of those shows their performance > particularly well on an ADEV plot. > > And most amateurs even forget to deal with quartz frequency jumps > and other 'point-like' upsets. > > The theory behind a PLL is really no different from a PID temperature > regulation, and I highly recommend people read up on those because > they are generally explained much better than when PLL's are the > subject. > > Before you get any good ideas: note that our measurement noise > (jitter/resolution) only for very long tau permits meaningful use > of the D(ifferential) term. It is possible to use a hysteresis on > the D term to catch frequency jumps in the xtal, but it is of dubious > advantage compared to just detecting and resetting the PLL). > > A less significant difference from PID regulations is higher order > integrals: They are not useful for temperature regulation, but if > you want to get really nasty with your PLL, you can add another > term to model the frequency drift, and another one to model the > change in frequency drift and another one to model the change in the > change of the frequency drift and ... (you get the idea). > > Be aware that floating point is necessary and that rounding errors > will mess you up if you are not very careful with your sums and > differences. > > I can highly recommend writing a small program or big spreadsheet > to simulate a PLL so you can play with the coefficients and get a > feel for the dynamics by watching plots of the phase and frequency > deltas and ADEV etc. > > Merry X-mas! > > Poul-Henning > > Bruce
PK
Poul-Henning Kamp
Mon, Dec 25, 2006 9:26 AM

In message 458F5B82.8000501@xtra.co.nz, Dr Bruce Griffiths writes:

We know that the hardware PPS signal from gps is phasemodulated
with a +/- N ns signal which has a box distribution and upper
frequency limit of 2 Hz and which, subject to temperature stability
and hanging bridges, has no significant frequency components below
< 1/500s.

How can this be true?
The PPS output rate is 1Hz!
Are you saying there is significant wideband noise on the 1 PPS output?
Is that lower frequency limit 0.002Hz?

I'm talking about the negative sawtooth signal (as available in
the serial data stream) which is phase modulated onto the ideal
1PPS signal as received by the GPS receiver.

BTW, as you probably already guessed, 2 Hz should be read as .5 Hz
(It's the Nyquist limit thing).

--
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 <458F5B82.8000501@xtra.co.nz>, Dr Bruce Griffiths writes: >> We know that the hardware PPS signal from gps is phasemodulated >> with a +/- N ns signal which has a box distribution and upper >> frequency limit of 2 Hz and which, subject to temperature stability >> and hanging bridges, has no significant frequency components below >> < 1/500s. >> >How can this be true? >The PPS output rate is 1Hz! >Are you saying there is significant wideband noise on the 1 PPS output? >Is that lower frequency limit 0.002Hz? I'm talking about the negative sawtooth signal (as available in the serial data stream) which is phase modulated onto the ideal 1PPS signal as received by the GPS receiver. BTW, as you probably already guessed, 2 Hz should be read as .5 Hz (It's the Nyquist limit thing). -- 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.
PK
Poul-Henning Kamp
Mon, Dec 25, 2006 9:32 AM

In message 458F1D50.3000707@xtra.co.nz, Dr Bruce Griffiths writes:

We know that the hardware PPS signal from gps is phasemodulated
with a +/- N ns signal which has a box distribution and upper
frequency limit of 2 Hz and which, subject to temperature stability
and hanging bridges, has no significant frequency components below
< 1/500s.

Has this been established by actual measurement?

With the caveat that I wrote 2Hz instead of 0.5Hz (Nyquist thing)
this follows directly from signals theory.

Running a FFT over the negative sawtooth values is an interesting
exercise, in particlar of you collect a weeks worth of data or more.

Ignoring the combined effects of quantisation and coherence would not
seem to be very sensible.

A quantum of 1ns is not a concern if the attack point for the PLL
is on the order of hours.

I'm not sure what coherence you are talking about here, the
negative sawtooth signal is not coherent with anything as far
as we know.

A less significant difference from PID regulations is higher order
integrals:  They are not useful for temperature regulation,

This is not true, using a second integrator in a crystal oscillator
temperature regulation loop can be very effective, as indicated in the
following paper:

That does make sense, I was only talking about more normal
temperature regulations (water tanks, process chemicals etc).

--
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 <458F1D50.3000707@xtra.co.nz>, Dr Bruce Griffiths writes: >> We know that the hardware PPS signal from gps is phasemodulated >> with a +/- N ns signal which has a box distribution and upper >> frequency limit of 2 Hz and which, subject to temperature stability >> and hanging bridges, has no significant frequency components below >> < 1/500s. >> >Has this been established by actual measurement? With the caveat that I wrote 2Hz instead of 0.5Hz (Nyquist thing) this follows directly from signals theory. Running a FFT over the negative sawtooth values is an interesting exercise, in particlar of you collect a weeks worth of data or more. >Ignoring the combined effects of quantisation and coherence would not >seem to be very sensible. A quantum of 1ns is not a concern if the attack point for the PLL is on the order of hours. I'm not sure what coherence you are talking about here, the negative sawtooth signal is not coherent with anything as far as we know. >> A less significant difference from PID regulations is higher order >> integrals: They are not useful for temperature regulation, >This is not true, using a second integrator in a crystal oscillator >temperature regulation loop can be very effective, as indicated in the >following paper: That does make sense, I was only talking about more normal temperature regulations (water tanks, process chemicals etc). -- 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.
UB
Ulrich Bangert
Mon, Dec 25, 2006 1:34 PM

Hi Tom,

  1. Could you clarify for us what points in your plot
    are real measured data and what points, if any, are
    simulated?

the red line is a simulated computed noise due to the 41.6 ns
quantization errors. The HP10811 plot is made up of two parts. One for
taus up to a few 100 s where I measured it against my FTS1200 having
significantly lower ADEV in that range. A second part for longer taus as
measured inside the open loop of my GPSDO. i.e. against sawtooth
corrected pps. The two gps lines are from a closed loop measurement.

  1. Have you looked into why your Comparison.pdf
    plot doesn't have the same look as SigmaTauBoth
    (photo_gallery_44.html)?

I noticed that too and I have no explanation for that. Since I had the
raw data that lead to photo_gallery_44.html no more at hand I had to use
different raw data to construct the pdf in my posting.

But the horizon point (where the lines meet) for the
SigmaTauBoth plot is around tau 1 day while the horizon point
for Comparison.pdf, as best I can tell, is around tau 10^8
seconds (about 1000 days).

I would like this problem to get cleared for myself too. I am going to
start some new measurements. While it is a problem worth to discuss: If
it were like you say would that not backup my argumentation because it
would draw the yellow line even a bit lower due to the changed slope and
so increase the distance to the red line?

  1. For the sake of contrast, and to make your plot
    even better, would you be able to add another OCXO
    or two?

Yesterday i spend some hours into improving my Plotter utility to make
that possible. Otherwise I would not have been able to generate the plot
of my posting. If you want to send me data then

a) send me raw phase data so that I compute the statistics on my own

or

b) if you send me statistical data give them a look similar to

Tau       Overlapping Allan Deviation
1.00000000000000E+00 1.18508991343051E-09
2.00000000000000E+00 1.00418275497165E-09
4.00000000000000E+00 4.94116108301216E-10
8.00000000000000E+00 2.54210080584921E-10
1.60000000000000E+01 1.32077950356112E-10
3.20000000000000E+01 7.12770070677926E-11
6.40000000000000E+01 4.01265021949822E-11
1.28000000000000E+02 2.40645383337377E-11
2.56000000000000E+02 1.24198310130885E-11
5.12000000000000E+02 6.61924079416740E-12
1.02400000000000E+03 3.39639264963695E-12
2.04800000000000E+03 1.60459982080177E-12
4.09600000000000E+03 8.34317107123469E-13
8.19200000000000E+03 4.23896023761579E-13
1.63840000000000E+04 2.18096321206837E-13
3.27680000000000E+04 1.00382297277920E-13
6.55360000000000E+04 5.27984014158743E-14

The headerline is needed. Any number of columns is allowed. The number
format need not exactly be that way.

  1. I'm wondering if you could conclude something
    interesting if your plot separated the OCXO issue,
    from the GPS engine issue, from the TIC issue
    rather than lumping the GPS and TIC together into
    one line.

While you are correct that I lump GPS and TIC into one line, we all must
live with that. Because once you make a measurement you have already
lumped the TIC resolution into your data. The only thing that we can do
about is to make the TIC resolution sufficiently small. My GPS data is
measured with 110 ps resolution. The left part of the hp10811 plot has
been measured with 1e-13 @ 1 s resolution.

For example, HP 53131 (500 ps) vs. 53132 (150 ps)
vs. 5334 (2 ns) vs. 5370 and SRS 620 (25 ps). You
can also add Shera (42?ns) and Jackson (8?ns).

As long as the TIC resolution is small against the jitter of the signal
to be measured we will hardly see anything of its influence in an
(lumped) Allan plot. As long as GPS is concerned (even sawtooth
corrected) this is the reason why we live so well with our HP5370s, our
HP53131/2s and our SR620s with the HP53131 being a bit on the boarder.
The 5334's 2 ns reolution and anything that will clearly document itself
in the Allan plots. As for the Shera design: The red line IS an a bit
too optimictic estimation for this case.

I am a bit disappointed that i seem to have failed to make clear the
true tenor of my posting: That the TIC resolution kind of 'modulates'
the measurement results and that this modulation can become the dominant
one depending on the signal's properties and the modulation amplitude.

Best regards
Ulrich Bangert, DF6JB

-----Ursprüngliche Nachricht-----
Von: time-nuts-bounces@febo.com
[mailto:time-nuts-bounces@febo.com] Im Auftrag von Tom Van Baak
Gesendet: Montag, 25. Dezember 2006 00:03
An: Discussion of precise time and frequency measurement
Betreff: Re: [time-nuts] TIC resolution impact on GPSDO's performance

Hi Ulrich,

Thanks for your note on TIC resolution and the very
nice plot you attached. Here are some comments:

  1. Could you clarify for us what points in your plot
    are real measured data and what points, if any, are
    simulated?

  2. Have you looked into why your Comparison.pdf
    plot doesn't have the same look as SigmaTauBoth
    (photo_gallery_44.html)?

Do both represent the same thing (M12/sawtooth
vs. M12/corrected) or did I misunderstand one of
them. Because they do seem to have a different
look.

The red and black lines are parallel while black
and yellow appear to merge (like chopsticks).

But the horizon point (where the lines meet) for the
SigmaTauBoth plot is around tau 1 day while the horizon point
for Comparison.pdf, as best I can tell, is around tau 10^8
seconds (about 1000 days).

  1. For the sake of contrast, and to make your plot
    even better, would you be able to add another OCXO
    or two?

For example, perhaps add one that performs closer
to the 10811 spec (e.g. drift rate of 5e-10/day) and
one that is a lesser grade, an Ovenaire or CTS class
of OCXO or TCXO with short-term stability in the -10's
and drift rate in the -9's. I can provide the data if you
need it.

Perhaps other readers can suggest their own OCXO
or Rb.

  1. I'm wondering if you could conclude something
    interesting if your plot separated the OCXO issue,
    from the GPS engine issue, from the TIC issue
    rather than lumping the GPS and TIC together into
    one line.

For example, in addition to different examples of
OCXO (low, medium, and high-performance) and
different GPS engines (e.g., Oncore VP, M12 with
sawtooth, M12/corrected), do you think you could
you also add different TIC resolutions?

For example, HP 53131 (500 ps) vs. 53132 (150 ps)
vs. 5334 (2 ns) vs. 5370 and SRS 620 (25 ps). You
can also add Shera (42?ns) and Jackson (8?ns).

Perhaps other readers can suggest different ones.

I'll have a few more comments later.

/tvb


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

Hi Tom, > 1. Could you clarify for us what points in your plot > are real measured data and what points, if any, are > simulated? the red line is a simulated computed noise due to the 41.6 ns quantization errors. The HP10811 plot is made up of two parts. One for taus up to a few 100 s where I measured it against my FTS1200 having significantly lower ADEV in that range. A second part for longer taus as measured inside the open loop of my GPSDO. i.e. against sawtooth corrected pps. The two gps lines are from a closed loop measurement. > 2. Have you looked into why your Comparison.pdf > plot doesn't have the same look as SigmaTauBoth > (photo_gallery_44.html)? I noticed that too and I have no explanation for that. Since I had the raw data that lead to photo_gallery_44.html no more at hand I had to use different raw data to construct the pdf in my posting. > But the horizon point (where the lines meet) for the > SigmaTauBoth plot is around tau 1 day while the horizon point > for Comparison.pdf, as best I can tell, is around tau 10^8 > seconds (about 1000 days). I would like this problem to get cleared for myself too. I am going to start some new measurements. While it is a problem worth to discuss: If it were like you say would that not backup my argumentation because it would draw the yellow line even a bit lower due to the changed slope and so increase the distance to the red line? > 3. For the sake of contrast, and to make your plot > even better, would you be able to add another OCXO > or two? Yesterday i spend some hours into improving my Plotter utility to make that possible. Otherwise I would not have been able to generate the plot of my posting. If you want to send me data then a) send me raw phase data so that I compute the statistics on my own or b) if you send me statistical data give them a look similar to Tau Overlapping Allan Deviation 1.00000000000000E+00 1.18508991343051E-09 2.00000000000000E+00 1.00418275497165E-09 4.00000000000000E+00 4.94116108301216E-10 8.00000000000000E+00 2.54210080584921E-10 1.60000000000000E+01 1.32077950356112E-10 3.20000000000000E+01 7.12770070677926E-11 6.40000000000000E+01 4.01265021949822E-11 1.28000000000000E+02 2.40645383337377E-11 2.56000000000000E+02 1.24198310130885E-11 5.12000000000000E+02 6.61924079416740E-12 1.02400000000000E+03 3.39639264963695E-12 2.04800000000000E+03 1.60459982080177E-12 4.09600000000000E+03 8.34317107123469E-13 8.19200000000000E+03 4.23896023761579E-13 1.63840000000000E+04 2.18096321206837E-13 3.27680000000000E+04 1.00382297277920E-13 6.55360000000000E+04 5.27984014158743E-14 The headerline is needed. Any number of columns is allowed. The number format need not exactly be that way. > 4. I'm wondering if you could conclude something > interesting if your plot separated the OCXO issue, > from the GPS engine issue, from the TIC issue > rather than lumping the GPS and TIC together into > one line. While you are correct that I lump GPS and TIC into one line, we all must live with that. Because once you make a measurement you have already lumped the TIC resolution into your data. The only thing that we can do about is to make the TIC resolution sufficiently small. My GPS data is measured with 110 ps resolution. The left part of the hp10811 plot has been measured with 1e-13 @ 1 s resolution. > For example, HP 53131 (500 ps) vs. 53132 (150 ps) > vs. 5334 (2 ns) vs. 5370 and SRS 620 (25 ps). You > can also add Shera (42?ns) and Jackson (8?ns). As long as the TIC resolution is small against the jitter of the signal to be measured we will hardly see anything of its influence in an (lumped) Allan plot. As long as GPS is concerned (even sawtooth corrected) this is the reason why we live so well with our HP5370s, our HP53131/2s and our SR620s with the HP53131 being a bit on the boarder. The 5334's 2 ns reolution and anything that will clearly document itself in the Allan plots. As for the Shera design: The red line IS an a bit too optimictic estimation for this case. I am a bit disappointed that i seem to have failed to make clear the true tenor of my posting: That the TIC resolution kind of 'modulates' the measurement results and that this modulation can become the dominant one depending on the signal's properties and the modulation amplitude. Best regards Ulrich Bangert, DF6JB > -----Ursprüngliche Nachricht----- > Von: time-nuts-bounces@febo.com > [mailto:time-nuts-bounces@febo.com] Im Auftrag von Tom Van Baak > Gesendet: Montag, 25. Dezember 2006 00:03 > An: Discussion of precise time and frequency measurement > Betreff: Re: [time-nuts] TIC resolution impact on GPSDO's performance > > > Hi Ulrich, > > Thanks for your note on TIC resolution and the very > nice plot you attached. Here are some comments: > > 1. Could you clarify for us what points in your plot > are real measured data and what points, if any, are > simulated? > > 2. Have you looked into why your Comparison.pdf > plot doesn't have the same look as SigmaTauBoth > (photo_gallery_44.html)? > > Do both represent the same thing (M12/sawtooth > vs. M12/corrected) or did I misunderstand one of > them. Because they do seem to have a different > look. > > The red and black lines are parallel while black > and yellow appear to merge (like chopsticks). > > But the horizon point (where the lines meet) for the > SigmaTauBoth plot is around tau 1 day while the horizon point > for Comparison.pdf, as best I can tell, is around tau 10^8 > seconds (about 1000 days). > > 3. For the sake of contrast, and to make your plot > even better, would you be able to add another OCXO > or two? > > For example, perhaps add one that performs closer > to the 10811 spec (e.g. drift rate of 5e-10/day) and > one that is a lesser grade, an Ovenaire or CTS class > of OCXO or TCXO with short-term stability in the -10's > and drift rate in the -9's. I can provide the data if you > need it. > > Perhaps other readers can suggest their own OCXO > or Rb. > > 4. I'm wondering if you could conclude something > interesting if your plot separated the OCXO issue, > from the GPS engine issue, from the TIC issue > rather than lumping the GPS and TIC together into > one line. > > For example, in addition to different examples of > OCXO (low, medium, and high-performance) and > different GPS engines (e.g., Oncore VP, M12 with > sawtooth, M12/corrected), do you think you could > you also add different TIC resolutions? > > For example, HP 53131 (500 ps) vs. 53132 (150 ps) > vs. 5334 (2 ns) vs. 5370 and SRS 620 (25 ps). You > can also add Shera (42?ns) and Jackson (8?ns). > > Perhaps other readers can suggest different ones. > > I'll have a few more comments later. > > /tvb > > > > _______________________________________________ > time-nuts mailing list > time-nuts@febo.com > https://www.febo.com/cgi-> bin/mailman/listinfo/time-nuts >
UB
Ulrich Bangert
Mon, Dec 25, 2006 2:17 PM

Poul,

Your black line is bogus in the usual "teacher's bad example way".

We know that the hardware PPS signal from gps is
phasemodulated with a +/- N ns signal which has a box
distribution and upper frequency limit of 2 Hz and which,
subject to temperature stability and hanging bridges, has no
significant frequency components below < 1/500s.

It follows readily for this, that only teachers trying to
show a bad example would use the PPS signal for tau > 500
second without filtering the higher frequencies out, one way
or another.

I am not talking now about 2 vs. 0.5 Hz. It is the rest of your argument
that asks too much from me. Can you elaborate on that? I have no idea of
what you are talking about!

No causal algorithm can allow you to implement:

if (tau < N)
	use OCXO
else
	use GPS

Come on, Poul! I have carefully tried to avoid such interpretation by
using terms like "starts to dominate" and so.

But most fatal to your message: you look at the wrong kind of
stats for this particular kind of discipline.

Being still adaptive I wait for people who explain it to me.

When you discipline an frequency source (OCXO, Rb, Cs) to a
phase source (GPS, Loran-C, WWV, DCF77, NTP etc), you have to
decide for which parameter you (optimize your) discipline:

Minimum phase offset.
Minimum frequency offset.
Best phase stability.
Best frequency stability.
Best holdover performance in phase.
Best holdover performance in frequency.

All I have heard about here so far, is the first and a few
cases of the second kind, and neither of those shows their
performance particularly well on an ADEV plot.

I agree completely to you that anything concerning holdover is neglected
in the discussion but may this be due to the fact that holdover
performance is the least important one in amateur use?

In my own GPSDO i discipline the LO's pps to have a MAXIMUM phase offset
of 500 ms against the receiver's pps. That avoids lots of ambiguity
problems and leaves the widest phase measurement range to make the loop
even lock when the OCXO is initially far apart its setpoint.

Otherwise you are correct that one can optimize for different
parameters. This gives immediate rise for the following publications:

  1. A guide to discipline your frequency source to a phase source with
    minimum phase offset

  2. A guide to disipline  your frequency source to a phase source with
    minimum frequency offset

  3. A guide to discipline your frequency source to a phase source with
    best phase stability

  4. A guide to discipline your frequency source to a phase source with
    best frequency stability

If you can deliver or send some links: I will surely devour stuff like
this!

Best Regards
Ulrich Bangert, DF6JB

-----Ursprüngliche Nachricht-----
Von: time-nuts-bounces@febo.com
[mailto:time-nuts-bounces@febo.com] Im Auftrag von Poul-Henning Kamp
Gesendet: Montag, 25. Dezember 2006 00:51
An: Discussion of precise time and frequency measurement
Betreff: Re: [time-nuts] TIC resolution impact on GPSDO's performance

In message 000001c72769$8363beb0$03b2fea9@athlon, "Ulrich
Bangert" writes:

For the most of you it will already now be kind of evident that the
crossing point defines the magical value that we have to set

the loop

time constant to but this fact can be formulated with a bit more of
scientifical preciseness: At no observation time tau will it be
possible to have an ADEV at the OUTPUT of the standard that is lower
then BOTH Allan plots at this tau.

This is not true in general, but does hold true for the
example you have chosen.  The exact requirement for
truthfullness is that the noise-processes of your two sources
must be uncorrelated.

What if we had not used the sawtooth corrected values but

the raw 1pps

phase data?

Your black line is bogus in the usual "teacher's bad example way".

We know that the hardware PPS signal from gps is
phasemodulated with a +/- N ns signal which has a box
distribution and upper frequency limit of 2 Hz and which,
subject to temperature stability and hanging bridges, has no
significant frequency components below < 1/500s.

It follows readily for this, that only teachers trying to
show a bad example would use the PPS signal for tau > 500
second without filtering the higher frequencies out, one way
or another.

(In the initial capture phase, no filtering should be used to
get the best possible frequency response of the PLL, in the
"grab" phase where the integrator is clamped, a simple
exponential average should be used.  Once lock has been
aquired, linear regression offers a useful zero-latency
filtering model.)

Your black line should have reflected this.

But your further argument has trouble as well.

No causal algorithm can allow you to implement:

if (tau < N)
	use OCXO
else
	use GPS

For some interval of tau, both sources will affect the
result, if you do post-factum disciplines (ie: paper clocks)
you can do it a lot closer to optimal, but the statistics
gets increasingly nasty and the age of your data will
approach infinity as the fidelity increases.

But most fatal to your message: you look at the wrong kind of
stats for this particular kind of discipline.

When you discipline an frequency source (OCXO, Rb, Cs) to a
phase source (GPS, Loran-C, WWV, DCF77, NTP etc), you have to
decide for which parameter you (optimize your) discipline:

Minimum phase offset.
Minimum frequency offset.
Best phase stability.
Best frequency stability.
Best holdover performance in phase.
Best holdover performance in frequency.

All I have heard about here so far, is the first and a few
cases of the second kind, and neither of those shows their
performance particularly well on an ADEV plot.

And most amateurs even forget to deal with quartz frequency
jumps and other 'point-like' upsets.

The theory behind a PLL is really no different from a PID
temperature regulation, and I highly recommend people read up
on those because they are generally explained much better
than when PLL's are the subject.

Before you get any good ideas: note that our measurement noise
(jitter/resolution) only for very long tau permits meaningful
use of the D(ifferential) term.  It is possible to use a
hysteresis on the D term to catch frequency jumps in the
xtal, but it is of dubious advantage compared to just
detecting and resetting the PLL).

A less significant difference from PID regulations is higher order
integrals:  They are not useful for temperature regulation,
but if you want to get really nasty with your PLL, you can
add another term to model the frequency drift, and another
one to model the change in frequency drift and another one to
model the change in the change of the frequency drift and ...
(you get the idea).

Be aware that floating point is necessary and that rounding
errors will mess you up if you are not very careful with your
sums and differences.

I can highly recommend writing a small program or big
spreadsheet to simulate a PLL so you can play with the
coefficients and get a feel for the dynamics by watching
plots of the phase and frequency deltas and ADEV etc.

Merry X-mas!

Poul-Henning

--
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.


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

Poul, > Your black line is bogus in the usual "teacher's bad example way". > > We know that the hardware PPS signal from gps is > phasemodulated with a +/- N ns signal which has a box > distribution and upper frequency limit of 2 Hz and which, > subject to temperature stability and hanging bridges, has no > significant frequency components below < 1/500s. > > It follows readily for this, that only teachers trying to > show a bad example would use the PPS signal for tau > 500 > second without filtering the higher frequencies out, one way > or another. I am not talking now about 2 vs. 0.5 Hz. It is the rest of your argument that asks too much from me. Can you elaborate on that? I have no idea of what you are talking about! > No causal algorithm can allow you to implement: > > if (tau < N) > use OCXO > else > use GPS > Come on, Poul! I have carefully tried to avoid such interpretation by using terms like "starts to dominate" and so. > But most fatal to your message: you look at the wrong kind of > stats for this particular kind of discipline. Being still adaptive I wait for people who explain it to me. > When you discipline an frequency source (OCXO, Rb, Cs) to a > phase source (GPS, Loran-C, WWV, DCF77, NTP etc), you have to > decide for which parameter you (optimize your) discipline: > > Minimum phase offset. > Minimum frequency offset. > Best phase stability. > Best frequency stability. > Best holdover performance in phase. > Best holdover performance in frequency. > > All I have heard about here so far, is the first and a few > cases of the second kind, and neither of those shows their > performance particularly well on an ADEV plot. I agree completely to you that anything concerning holdover is neglected in the discussion but may this be due to the fact that holdover performance is the least important one in amateur use? In my own GPSDO i discipline the LO's pps to have a MAXIMUM phase offset of 500 ms against the receiver's pps. That avoids lots of ambiguity problems and leaves the widest phase measurement range to make the loop even lock when the OCXO is initially far apart its setpoint. Otherwise you are correct that one can optimize for different parameters. This gives immediate rise for the following publications: 1) A guide to discipline your frequency source to a phase source with minimum phase offset 2) A guide to disipline your frequency source to a phase source with minimum frequency offset 3) A guide to discipline your frequency source to a phase source with best phase stability 1) A guide to discipline your frequency source to a phase source with best frequency stability If you can deliver or send some links: I will surely devour stuff like this! Best Regards Ulrich Bangert, DF6JB > -----Ursprüngliche Nachricht----- > Von: time-nuts-bounces@febo.com > [mailto:time-nuts-bounces@febo.com] Im Auftrag von Poul-Henning Kamp > Gesendet: Montag, 25. Dezember 2006 00:51 > An: Discussion of precise time and frequency measurement > Betreff: Re: [time-nuts] TIC resolution impact on GPSDO's performance > > > In message <000001c72769$8363beb0$03b2fea9@athlon>, "Ulrich > Bangert" writes: > > >For the most of you it will already now be kind of evident that the > >crossing point defines the magical value that we have to set > the loop > >time constant to but this fact can be formulated with a bit more of > >scientifical preciseness: At no observation time tau will it be > >possible to have an ADEV at the OUTPUT of the standard that is lower > >then BOTH Allan plots at this tau. > > This is not true in general, but does hold true for the > example you have chosen. The exact requirement for > truthfullness is that the noise-processes of your two sources > must be uncorrelated. > > >What if we had not used the sawtooth corrected values but > the raw 1pps > >phase data? > > Your black line is bogus in the usual "teacher's bad example way". > > We know that the hardware PPS signal from gps is > phasemodulated with a +/- N ns signal which has a box > distribution and upper frequency limit of 2 Hz and which, > subject to temperature stability and hanging bridges, has no > significant frequency components below < 1/500s. > > It follows readily for this, that only teachers trying to > show a bad example would use the PPS signal for tau > 500 > second without filtering the higher frequencies out, one way > or another. > > (In the initial capture phase, no filtering should be used to > get the best possible frequency response of the PLL, in the > "grab" phase where the integrator is clamped, a simple > exponential average should be used. Once lock has been > aquired, linear regression offers a useful zero-latency > filtering model.) > > Your black line should have reflected this. > > > But your further argument has trouble as well. > > No causal algorithm can allow you to implement: > > if (tau < N) > use OCXO > else > use GPS > > For some interval of tau, both sources will affect the > result, if you do post-factum disciplines (ie: paper clocks) > you can do it a lot closer to optimal, but the statistics > gets increasingly nasty and the age of your data will > approach infinity as the fidelity increases. > > But most fatal to your message: you look at the wrong kind of > stats for this particular kind of discipline. > > When you discipline an frequency source (OCXO, Rb, Cs) to a > phase source (GPS, Loran-C, WWV, DCF77, NTP etc), you have to > decide for which parameter you (optimize your) discipline: > > Minimum phase offset. > Minimum frequency offset. > Best phase stability. > Best frequency stability. > Best holdover performance in phase. > Best holdover performance in frequency. > > All I have heard about here so far, is the first and a few > cases of the second kind, and neither of those shows their > performance particularly well on an ADEV plot. > > And most amateurs even forget to deal with quartz frequency > jumps and other 'point-like' upsets. > > The theory behind a PLL is really no different from a PID > temperature regulation, and I highly recommend people read up > on those because they are generally explained much better > than when PLL's are the subject. > > Before you get any good ideas: note that our measurement noise > (jitter/resolution) only for very long tau permits meaningful > use of the D(ifferential) term. It is possible to use a > hysteresis on the D term to catch frequency jumps in the > xtal, but it is of dubious advantage compared to just > detecting and resetting the PLL). > > A less significant difference from PID regulations is higher order > integrals: They are not useful for temperature regulation, > but if you want to get really nasty with your PLL, you can > add another term to model the frequency drift, and another > one to model the change in frequency drift and another one to > model the change in the change of the frequency drift and ... > (you get the idea). > > Be aware that floating point is necessary and that rounding > errors will mess you up if you are not very careful with your > sums and differences. > > I can highly recommend writing a small program or big > spreadsheet to simulate a PLL so you can play with the > coefficients and get a feel for the dynamics by watching > plots of the phase and frequency deltas and ADEV etc. > > Merry X-mas! > > Poul-Henning > > -- > 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. > > _______________________________________________ > time-nuts mailing list > time-nuts@febo.com > https://www.febo.com/cgi-> bin/mailman/listinfo/time-nuts >
DB
Dr Bruce Griffiths
Mon, Dec 25, 2006 10:46 PM

Poul-Henning

Poul-Henning Kamp wrote:

In message 458F1D50.3000707@xtra.co.nz, Dr Bruce Griffiths writes:

We know that the hardware PPS signal from gps is phasemodulated
with a +/- N ns signal which has a box distribution and upper
frequency limit of 2 Hz and which, subject to temperature stability
and hanging bridges, has no significant frequency components below
< 1/500s.

The sawtooth error is certainly not entirely random, there would appear
to be a strong correlation between the errors for adjacent pulses.

Has this been established by actual measurement?

With the caveat that I wrote 2Hz instead of 0.5Hz (Nyquist thing)
this follows directly from signals theory.

Running a FFT over the negative sawtooth values is an interesting
exercise, in particlar of you collect a weeks worth of data or more.

Ignoring the combined effects of quantisation and coherence would not
seem to be very sensible.

A quantum of 1ns is not a concern if the attack point for the PLL
is on the order of hours.

This statement is only true when one is disciplining or monitoring
relatively with sufficiently large frequency and/or phase instabilities.
When one wishes to discipline an Oscilloquartz 8607 OCXO for example
every nanosecond or fraction thereof matters.
If the appropriate timing receiver (not an M12+, or M12M) is used an
Allan variance less than 2E-13 is possible from  1s < tau < IE6 sec for
the disciplined OCXO.

I'm not sure what coherence you are talking about here, the
negative sawtooth signal is not coherent with anything as far
as we know.

Its not the coherence of the sawtooth but the coherence between the
oscillator clocking the timer used to position the PPS signal and the
frequency of the PPS signal itself.

Bruce

Poul-Henning Poul-Henning Kamp wrote: > In message <458F1D50.3000707@xtra.co.nz>, Dr Bruce Griffiths writes: > > >>> We know that the hardware PPS signal from gps is phasemodulated >>> with a +/- N ns signal which has a box distribution and upper >>> frequency limit of 2 Hz and which, subject to temperature stability >>> and hanging bridges, has no significant frequency components below >>> < 1/500s. >>> The sawtooth error is certainly not entirely random, there would appear to be a strong correlation between the errors for adjacent pulses. >>> >>> >> Has this been established by actual measurement? >> > > With the caveat that I wrote 2Hz instead of 0.5Hz (Nyquist thing) > this follows directly from signals theory. > > Running a FFT over the negative sawtooth values is an interesting > exercise, in particlar of you collect a weeks worth of data or more. > > >> Ignoring the combined effects of quantisation and coherence would not >> seem to be very sensible. >> > > A quantum of 1ns is not a concern if the attack point for the PLL > is on the order of hours. > > This statement is only true when one is disciplining or monitoring relatively with sufficiently large frequency and/or phase instabilities. When one wishes to discipline an Oscilloquartz 8607 OCXO for example every nanosecond or fraction thereof matters. If the appropriate timing receiver (not an M12+, or M12M) is used an Allan variance less than 2E-13 is possible from 1s < tau < IE6 sec for the disciplined OCXO. > I'm not sure what coherence you are talking about here, the > negative sawtooth signal is not coherent with anything as far > as we know. > > Its not the coherence of the sawtooth but the coherence between the oscillator clocking the timer used to position the PPS signal and the frequency of the PPS signal itself. Bruce