NS
Nick Sayer
Mon, Sep 12, 2016 6:41 PM
I was talking with someone at AD about a question I had about one of their TinyDACs when they mentioned their HMC1031 chip. It looks like the ideal building block for a clean-up oscillator.
It struck me just a touch later that the Venus838LPx-T has by default a 10 MHz output that’s phase locked to GPS time. It’s not good quality, but I wonder if it’s good enough to be the reference for this particular chip. They do talk about the ability to be driven by a “noisy” or "jittery” reference.
I think I’m going to take a crack at an OH300 GPSDO based on this design concept. Actually, first I’m going to actually try to quantify the jitter on the 10 MHz output from the Venus. From the HMC1031 datasheet it appears that if it’s not confined to a ±3 ns corridor that the lock indicator may not work (or work well). That would be a bummer.
I can foresee a GPSDO with the miniDIN 4 jack presenting the PPS and serial I/O from the GPS module and two LEDs on the front - the “FIX” LED from the GPS module and the lock LED from the PLL along with two BNC jacks. It would have some downsides. For one, I believe in the absence of GPS reception, it wouldn’t be able to properly hold-over at all. But it’ll be interesting to see if it can work as well as the micro-controller driven variant does.
I was talking with someone at AD about a question I had about one of their TinyDACs when they mentioned their HMC1031 chip. It looks like the ideal building block for a clean-up oscillator.
It struck me just a touch later that the Venus838LPx-T has by default a 10 MHz output that’s phase locked to GPS time. It’s not good quality, but I wonder if it’s good enough to be the reference for this particular chip. They do talk about the ability to be driven by a “noisy” or "jittery” reference.
I think I’m going to take a crack at an OH300 GPSDO based on this design concept. Actually, first I’m going to actually try to quantify the jitter on the 10 MHz output from the Venus. From the HMC1031 datasheet it appears that if it’s not confined to a ±3 ns corridor that the lock indicator may not work (or work well). That would be a bummer.
I can foresee a GPSDO with the miniDIN 4 jack presenting the PPS and serial I/O from the GPS module and two LEDs on the front - the “FIX” LED from the GPS module and the lock LED from the PLL along with two BNC jacks. It would have some downsides. For one, I believe in the absence of GPS reception, it wouldn’t be able to properly hold-over at all. But it’ll be interesting to see if it can work as well as the micro-controller driven variant does.
TS
Tim Shoppa
Mon, Sep 12, 2016 7:06 PM
You know Nick, the loop time constant typically used with the HMC1031 loop
filter is typically 5 milliseconds. I'm sure some bigger R's and C's can
used for a longer time constant, and I'm sure that'll help clean up the
awful 10MHz output of the Venus838LPx-T. But it is hardly what I'd call a
"GPSDO".
Tim N3QE
On Mon, Sep 12, 2016 at 2:41 PM, Nick Sayer via time-nuts <
time-nuts@febo.com> wrote:
I was talking with someone at AD about a question I had about one of their
TinyDACs when they mentioned their HMC1031 chip. It looks like the ideal
building block for a clean-up oscillator.
It struck me just a touch later that the Venus838LPx-T has by default a 10
MHz output that’s phase locked to GPS time. It’s not good quality, but I
wonder if it’s good enough to be the reference for this particular chip.
They do talk about the ability to be driven by a “noisy” or "jittery”
reference.
I think I’m going to take a crack at an OH300 GPSDO based on this design
concept. Actually, first I’m going to actually try to quantify the jitter
on the 10 MHz output from the Venus. From the HMC1031 datasheet it appears
that if it’s not confined to a ±3 ns corridor that the lock indicator may
not work (or work well). That would be a bummer.
I can foresee a GPSDO with the miniDIN 4 jack presenting the PPS and
serial I/O from the GPS module and two LEDs on the front - the “FIX” LED
from the GPS module and the lock LED from the PLL along with two BNC jacks.
It would have some downsides. For one, I believe in the absence of GPS
reception, it wouldn’t be able to properly hold-over at all. But it’ll be
interesting to see if it can work as well as the micro-controller driven
variant does.
time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to https://www.febo.com/cgi-bin/
mailman/listinfo/time-nuts
and follow the instructions there.
You know Nick, the loop time constant typically used with the HMC1031 loop
filter is typically 5 milliseconds. I'm sure some bigger R's and C's can
used for a longer time constant, and I'm sure that'll help clean up the
awful 10MHz output of the Venus838LPx-T. But it is hardly what I'd call a
"GPSDO".
Tim N3QE
On Mon, Sep 12, 2016 at 2:41 PM, Nick Sayer via time-nuts <
time-nuts@febo.com> wrote:
> I was talking with someone at AD about a question I had about one of their
> TinyDACs when they mentioned their HMC1031 chip. It looks like the ideal
> building block for a clean-up oscillator.
>
> It struck me just a touch later that the Venus838LPx-T has by default a 10
> MHz output that’s phase locked to GPS time. It’s not good quality, but I
> wonder if it’s good enough to be the reference for this particular chip.
> They do talk about the ability to be driven by a “noisy” or "jittery”
> reference.
>
> I think I’m going to take a crack at an OH300 GPSDO based on this design
> concept. Actually, first I’m going to actually try to quantify the jitter
> on the 10 MHz output from the Venus. From the HMC1031 datasheet it appears
> that if it’s not confined to a ±3 ns corridor that the lock indicator may
> not work (or work well). That would be a bummer.
>
> I can foresee a GPSDO with the miniDIN 4 jack presenting the PPS and
> serial I/O from the GPS module and two LEDs on the front - the “FIX” LED
> from the GPS module and the lock LED from the PLL along with two BNC jacks.
> It would have some downsides. For one, I believe in the absence of GPS
> reception, it wouldn’t be able to properly hold-over at all. But it’ll be
> interesting to see if it can work as well as the micro-controller driven
> variant does.
> _______________________________________________
> time-nuts mailing list -- time-nuts@febo.com
> To unsubscribe, go to https://www.febo.com/cgi-bin/
> mailman/listinfo/time-nuts
> and follow the instructions there.
>
BC
Bob Camp
Mon, Sep 12, 2016 8:01 PM
Hi
The noise performance of the HMC1031 close in is pretty horrible. It’s actually worse than the GPS signal noise. In a normal GPSDO the idea is to use an oscillator that is cleaner at 0.01 to 10 Hz than the GPS.
Bob
On Sep 12, 2016, at 2:41 PM, Nick Sayer via time-nuts time-nuts@febo.com wrote:
I was talking with someone at AD about a question I had about one of their TinyDACs when they mentioned their HMC1031 chip. It looks like the ideal building block for a clean-up oscillator.
It struck me just a touch later that the Venus838LPx-T has by default a 10 MHz output that’s phase locked to GPS time. It’s not good quality, but I wonder if it’s good enough to be the reference for this particular chip. They do talk about the ability to be driven by a “noisy” or "jittery” reference.
I think I’m going to take a crack at an OH300 GPSDO based on this design concept. Actually, first I’m going to actually try to quantify the jitter on the 10 MHz output from the Venus. From the HMC1031 datasheet it appears that if it’s not confined to a ±3 ns corridor that the lock indicator may not work (or work well). That would be a bummer.
I can foresee a GPSDO with the miniDIN 4 jack presenting the PPS and serial I/O from the GPS module and two LEDs on the front - the “FIX” LED from the GPS module and the lock LED from the PLL along with two BNC jacks. It would have some downsides. For one, I believe in the absence of GPS reception, it wouldn’t be able to properly hold-over at all. But it’ll be interesting to see if it can work as well as the micro-controller driven variant does.
time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.
Hi
The noise performance of the HMC1031 close in is pretty horrible. It’s actually *worse* than the GPS signal noise. In a normal GPSDO the idea is to use an oscillator that is cleaner at 0.01 to 10 Hz than the GPS.
Bob
> On Sep 12, 2016, at 2:41 PM, Nick Sayer via time-nuts <time-nuts@febo.com> wrote:
>
> I was talking with someone at AD about a question I had about one of their TinyDACs when they mentioned their HMC1031 chip. It looks like the ideal building block for a clean-up oscillator.
>
> It struck me just a touch later that the Venus838LPx-T has by default a 10 MHz output that’s phase locked to GPS time. It’s not good quality, but I wonder if it’s good enough to be the reference for this particular chip. They do talk about the ability to be driven by a “noisy” or "jittery” reference.
>
> I think I’m going to take a crack at an OH300 GPSDO based on this design concept. Actually, first I’m going to actually try to quantify the jitter on the 10 MHz output from the Venus. From the HMC1031 datasheet it appears that if it’s not confined to a ±3 ns corridor that the lock indicator may not work (or work well). That would be a bummer.
>
> I can foresee a GPSDO with the miniDIN 4 jack presenting the PPS and serial I/O from the GPS module and two LEDs on the front - the “FIX” LED from the GPS module and the lock LED from the PLL along with two BNC jacks. It would have some downsides. For one, I believe in the absence of GPS reception, it wouldn’t be able to properly hold-over at all. But it’ll be interesting to see if it can work as well as the micro-controller driven variant does.
> _______________________________________________
> time-nuts mailing list -- time-nuts@febo.com
> To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
> and follow the instructions there.
CS
Charles Steinmetz
Mon, Sep 12, 2016 8:27 PM
You know Nick, the loop time constant typically used with the HMC1031 loop
filter is typically 5 milliseconds. I'm sure some bigger R's and C's can
used for a longer time constant, and I'm sure that'll help clean up the
awful 10MHz output of the Venus838LPx-T. But it is hardly what I'd call a
"GPSDO".
One point that may not be obvious to people thinking of designing GPSDOs
is this: The requirement for a very long time constant control loop
(hundreds to thousands of seconds) has nothing to do with the frequency
of the reference signal from the GPS (that is, it is not due to the
reference being a 1PPS signal). Rather, it is determined by the tau at
which the stability of the GPS signal becomes better than the stability
of the local oscillator (generally an OCXO). Unless the designer
chooses a very bad local oscillator, this will be in the region of tau =
100-10kS (maybe only 20-50S if using a TCXO instead of an OCXO).
The stability of any higher-frequency signal from a GPS that does not
have a disciplined, high-stability LO (e.g., 10kHz in the case of the
obsolete Navman Jupiter GPS receivers, or 10MHz in the case of the
Venus) will be no better than the stability of the PPS, so the
high-stability local oscillator you add will still need to be
disciplined with the same slow loop you would use with PPS discipline if
you want the sort of results time-nuts expect from a GPSDO.
Best regards,
Charles
Tim wrote:
> You know Nick, the loop time constant typically used with the HMC1031 loop
> filter is typically 5 milliseconds. I'm sure some bigger R's and C's can
> used for a longer time constant, and I'm sure that'll help clean up the
> awful 10MHz output of the Venus838LPx-T. But it is hardly what I'd call a
> "GPSDO".
One point that may not be obvious to people thinking of designing GPSDOs
is this: The requirement for a very long time constant control loop
(hundreds to thousands of seconds) has nothing to do with the frequency
of the reference signal from the GPS (that is, it is not due to the
reference being a 1PPS signal). Rather, it is determined by the tau at
which the stability of the GPS signal becomes better than the stability
of the local oscillator (generally an OCXO). Unless the designer
chooses a very bad local oscillator, this will be in the region of tau =
100-10kS (maybe only 20-50S if using a TCXO instead of an OCXO).
The stability of any higher-frequency signal from a GPS that does not
have a disciplined, high-stability LO (e.g., 10kHz in the case of the
obsolete Navman Jupiter GPS receivers, or 10MHz in the case of the
Venus) will be no better than the stability of the PPS, so the
high-stability local oscillator you add will still need to be
disciplined with the same slow loop you would use with PPS discipline if
you want the sort of results time-nuts expect from a GPSDO.
Best regards,
Charles
NS
Nick Sayer
Mon, Sep 12, 2016 8:31 PM
On Sep 12, 2016, at 1:01 PM, Bob Camp kb8tq@n1k.org wrote:
Hi
The noise performance of the HMC1031 close in is pretty horrible. It’s actually worse than the GPS signal noise. In a normal GPSDO the idea is to use an oscillator that is cleaner at 0.01 to 10 Hz than the GPS.
I don’t see where you get that.
To generate the phase noise figures (8,9,11,12) they used a Crystek CVHD-950. I don’t think it necessarily follows that a better quality OCXO can’t do better than that, does it?
On Sep 12, 2016, at 2:41 PM, Nick Sayer via time-nuts time-nuts@febo.com wrote:
I was talking with someone at AD about a question I had about one of their TinyDACs when they mentioned their HMC1031 chip. It looks like the ideal building block for a clean-up oscillator.
It struck me just a touch later that the Venus838LPx-T has by default a 10 MHz output that’s phase locked to GPS time. It’s not good quality, but I wonder if it’s good enough to be the reference for this particular chip. They do talk about the ability to be driven by a “noisy” or "jittery” reference.
I think I’m going to take a crack at an OH300 GPSDO based on this design concept. Actually, first I’m going to actually try to quantify the jitter on the 10 MHz output from the Venus. From the HMC1031 datasheet it appears that if it’s not confined to a ±3 ns corridor that the lock indicator may not work (or work well). That would be a bummer.
I can foresee a GPSDO with the miniDIN 4 jack presenting the PPS and serial I/O from the GPS module and two LEDs on the front - the “FIX” LED from the GPS module and the lock LED from the PLL along with two BNC jacks. It would have some downsides. For one, I believe in the absence of GPS reception, it wouldn’t be able to properly hold-over at all. But it’ll be interesting to see if it can work as well as the micro-controller driven variant does.
time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.
> On Sep 12, 2016, at 1:01 PM, Bob Camp <kb8tq@n1k.org> wrote:
>
> Hi
>
> The noise performance of the HMC1031 close in is pretty horrible. It’s actually *worse* than the GPS signal noise. In a normal GPSDO the idea is to use an oscillator that is cleaner at 0.01 to 10 Hz than the GPS.
I don’t see where you get that.
To generate the phase noise figures (8,9,11,12) they used a Crystek CVHD-950. I don’t think it necessarily follows that a better quality OCXO can’t do better than that, does it?
>
> Bob
>
>
>> On Sep 12, 2016, at 2:41 PM, Nick Sayer via time-nuts <time-nuts@febo.com> wrote:
>>
>> I was talking with someone at AD about a question I had about one of their TinyDACs when they mentioned their HMC1031 chip. It looks like the ideal building block for a clean-up oscillator.
>>
>> It struck me just a touch later that the Venus838LPx-T has by default a 10 MHz output that’s phase locked to GPS time. It’s not good quality, but I wonder if it’s good enough to be the reference for this particular chip. They do talk about the ability to be driven by a “noisy” or "jittery” reference.
>>
>> I think I’m going to take a crack at an OH300 GPSDO based on this design concept. Actually, first I’m going to actually try to quantify the jitter on the 10 MHz output from the Venus. From the HMC1031 datasheet it appears that if it’s not confined to a ±3 ns corridor that the lock indicator may not work (or work well). That would be a bummer.
>>
>> I can foresee a GPSDO with the miniDIN 4 jack presenting the PPS and serial I/O from the GPS module and two LEDs on the front - the “FIX” LED from the GPS module and the lock LED from the PLL along with two BNC jacks. It would have some downsides. For one, I believe in the absence of GPS reception, it wouldn’t be able to properly hold-over at all. But it’ll be interesting to see if it can work as well as the micro-controller driven variant does.
>> _______________________________________________
>> time-nuts mailing list -- time-nuts@febo.com
>> To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
>> and follow the instructions there.
>
NS
Nick Sayer
Mon, Sep 12, 2016 8:47 PM
You know Nick, the loop time constant typically used with the HMC1031 loop
filter is typically 5 milliseconds. I'm sure some bigger R's and C's can
used for a longer time constant, and I'm sure that'll help clean up the
awful 10MHz output of the Venus838LPx-T. But it is hardly what I'd call a
"GPSDO".
One point that may not be obvious to people thinking of designing GPSDOs is this: The requirement for a very long time constant control loop (hundreds to thousands of seconds) has nothing to do with the frequency of the reference signal from the GPS (that is, it is not due to the reference being a 1PPS signal). Rather, it is determined by the tau at which the stability of the GPS signal becomes better than the stability of the local oscillator (generally an OCXO). Unless the designer chooses a very bad local oscillator, this will be in the region of tau = 100-10kS (maybe only 20-50S if using a TCXO instead of an OCXO).
The stability of any higher-frequency signal from a GPS that does not have a disciplined, high-stability LO (e.g., 10kHz in the case of the obsolete Navman Jupiter GPS receivers, or 10MHz in the case of the Venus) will be no better than the stability of the PPS, so the high-stability local oscillator you add will still need to be disciplined with the same slow loop you would use with PPS discipline if you want the sort of results time-nuts expect from a GPSDO.
Ok. Is it the case that the loop filter bandwidth is related to the time constant? Are there methods for minimizing the loop filter bandwidth that might be useful here? I would hazard a guess that obtaining >100s of TC equivalent in pure hardware would be at best difficult. At the same time, it seems like having a microcontroller act as an averager in software between an ADC and a DAC would be just silly.
Jim Miller's 10 kHz GPSDO that’s been referenced here has either solved this problem, or the 10 kHz output of the Jupiter is substantially better than the Venus’ 10 MHz output, or the design doesn’t give the results time-nuts expect from a GPSDO. Which of those applies?
> On Sep 12, 2016, at 1:27 PM, Charles Steinmetz <csteinmetz@yandex.com> wrote:
>
> Tim wrote:
>
>> You know Nick, the loop time constant typically used with the HMC1031 loop
>> filter is typically 5 milliseconds. I'm sure some bigger R's and C's can
>> used for a longer time constant, and I'm sure that'll help clean up the
>> awful 10MHz output of the Venus838LPx-T. But it is hardly what I'd call a
>> "GPSDO".
>
> One point that may not be obvious to people thinking of designing GPSDOs is this: The requirement for a very long time constant control loop (hundreds to thousands of seconds) has nothing to do with the frequency of the reference signal from the GPS (that is, it is not due to the reference being a 1PPS signal). Rather, it is determined by the tau at which the stability of the GPS signal becomes better than the stability of the local oscillator (generally an OCXO). Unless the designer chooses a very bad local oscillator, this will be in the region of tau = 100-10kS (maybe only 20-50S if using a TCXO instead of an OCXO).
>
> The stability of any higher-frequency signal from a GPS that does not have a disciplined, high-stability LO (e.g., 10kHz in the case of the obsolete Navman Jupiter GPS receivers, or 10MHz in the case of the Venus) will be no better than the stability of the PPS, so the high-stability local oscillator you add will still need to be disciplined with the same slow loop you would use with PPS discipline if you want the sort of results time-nuts expect from a GPSDO.
Ok. Is it the case that the loop filter bandwidth is related to the time constant? Are there methods for minimizing the loop filter bandwidth that might be useful here? I would hazard a guess that obtaining >100s of TC equivalent in pure hardware would be at best difficult. At the same time, it seems like having a microcontroller act as an averager in software between an ADC and a DAC would be just silly.
Jim Miller's 10 kHz GPSDO that’s been referenced here has either solved this problem, or the 10 kHz output of the Jupiter is substantially better than the Venus’ 10 MHz output, or the design doesn’t give the results time-nuts expect from a GPSDO. Which of those applies?
>
> Best regards,
>
> Charles
>
>
> _______________________________________________
> time-nuts mailing list -- time-nuts@febo.com
> To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
> and follow the instructions there.
BS
Bob Stewart
Mon, Sep 12, 2016 9:00 PM
Nick said:
"Jim Miller's 10 kHz GPSDO that’s been referenced here has either solved this problem, or the 10 kHz output of the Jupiter is substantially better than the Venus’ 10 MHz output, or the design doesn’t give the results time-nuts expect from a GPSDO. Which of those applies?"
Hi Nick,
You have to be very careful about the receiver you select. I think it's the case that the Jupiter's internal oscillator is phase locked to the GPS signal. In that case, you can use the output from the receiver to directly drive a PLL giving a high quality 10MHz or whatever you like. But, the low cost receivers on the market now, including those from Ublox, do not phase lock their oscillators to the GPS signal. In the case of Ublox, they specifically say that the quantization value is only available for the 1PPS output. So, yes, you can get a 10KHz pulse train from a Ublox or any other modern inexpensive GPS receiver, but it will suffer from whatever quantization error the manufacturer specifies.
bob
-----------------------------------------------------------------
AE6RV.com
GFS GPSDO list:
groups.yahoo.com/neo/groups/GFS-GPSDOs/info
Nick said:
"Jim Miller's 10 kHz GPSDO that’s been referenced here has either solved this problem, or the 10 kHz output of the Jupiter is substantially better than the Venus’ 10 MHz output, or the design doesn’t give the results time-nuts expect from a GPSDO. Which of those applies?"
Hi Nick,
You have to be very careful about the receiver you select. I think it's the case that the Jupiter's internal oscillator is phase locked to the GPS signal. In that case, you can use the output from the receiver to directly drive a PLL giving a high quality 10MHz or whatever you like. But, the low cost receivers on the market now, including those from Ublox, do not phase lock their oscillators to the GPS signal. In the case of Ublox, they specifically say that the quantization value is only available for the 1PPS output. So, yes, you can get a 10KHz pulse train from a Ublox or any other modern inexpensive GPS receiver, but it will suffer from whatever quantization error the manufacturer specifies.
bob
-----------------------------------------------------------------
AE6RV.com
GFS GPSDO list:
groups.yahoo.com/neo/groups/GFS-GPSDOs/info
CS
Charles Steinmetz
Mon, Sep 12, 2016 10:15 PM
Ok. Is it the case that the loop filter bandwidth is related to the time constant?
They are two ways of expressing the same thing, with the proviso that TC
applies strictly only to first-order, linear time-invariant systems --
in electronics, circuits with with one real pole.
T = RC, where "T" is the time constant and "R" and "C" are resistor and
capacitor values.
So, a single-pole LP filter consisting of a series 10k resistor and a
shunt 100nF capacitor has T = .001 seconds (=1mS). Its frequency
response (i.e., the -3dB or "corner" frequency) is given by:
f = 1/(2 x pi x T), or 159.16 Hz.
Checking, we note that the reactance of a capacitor is given by x =
-1/(2 x pi x f x C). When f = 159.16 Hz, the reactance of a 100nF
capacitor is -10k ohms, which is the value that produces a -3dB response
of 159.16 Hz in the LP filter with a 10k resistor.
Jim Miller's 10 kHz GPSDO that’s been referenced here has either solved this problem, or the 10 kHz output of the Jupiter is substantially better than the Venus’ 10 MHz output, or the design doesn’t give the results time-nuts expect from a GPSDO. Which of those applies?
I have no idea how the Jupiter generates its 10k output -- it was
speculation on my part that its stability must be no better than the
PPS. I have not looked at the Miller circuit for a long time (also,
note that Mr. Miller published at least two different GPSDO designs, so
one also has to be careful to know which one is under discussion). I
recall that I did not have much hope that the better of the two would
give TN-quality results, and was very surprised to find that when Tom
tested one, it performed quite well (although, the loop time constant
was clearly way too low -- as it is in the Tbolt with factory default
settings). I suppose the answer to the question is to be found in ADEV
plots of the Jupiter's 10kHz output. Perhaps there are some already
published on the web?
There was some discussion of this on the list back in mid-February 2008.
Best regards,
Charles
Nick wrote:
> Ok. Is it the case that the loop filter bandwidth is related to the time constant?
They are two ways of expressing the same thing, with the proviso that TC
applies strictly only to first-order, linear time-invariant systems --
in electronics, circuits with with one real pole.
T = RC, where "T" is the time constant and "R" and "C" are resistor and
capacitor values.
So, a single-pole LP filter consisting of a series 10k resistor and a
shunt 100nF capacitor has T = .001 seconds (=1mS). Its frequency
response (i.e., the -3dB or "corner" frequency) is given by:
f = 1/(2 x pi x T), or 159.16 Hz.
Checking, we note that the reactance of a capacitor is given by x =
-1/(2 x pi x f x C). When f = 159.16 Hz, the reactance of a 100nF
capacitor is -10k ohms, which is the value that produces a -3dB response
of 159.16 Hz in the LP filter with a 10k resistor.
> Jim Miller's 10 kHz GPSDO that’s been referenced here has either solved this problem, or the 10 kHz output of the Jupiter is substantially better than the Venus’ 10 MHz output, or the design doesn’t give the results time-nuts expect from a GPSDO. Which of those applies?
I have no idea how the Jupiter generates its 10k output -- it was
speculation on my part that its stability must be no better than the
PPS. I have not looked at the Miller circuit for a long time (also,
note that Mr. Miller published at least two different GPSDO designs, so
one also has to be careful to know which one is under discussion). I
recall that I did not have much hope that the better of the two would
give TN-quality results, and was very surprised to find that when Tom
tested one, it performed quite well (although, the loop time constant
was clearly way too low -- as it is in the Tbolt with factory default
settings). I suppose the answer to the question is to be found in ADEV
plots of the Jupiter's 10kHz output. Perhaps there are some already
published on the web?
There was some discussion of this on the list back in mid-February 2008.
Best regards,
Charles
B_
Bryan _
Mon, Sep 12, 2016 10:37 PM
From the Jupiter-T TU60-D120 datasheet
Figure 1-3 (next page) shows the typical 1PPS performance of the Jupiter-T GPS receiver. The 10 kHz output is also available from the receiver and is phase coherent with the 1PPS signal. This output is made available for functions such as phase locking of crystal oscillators, frequency synthesisers, and similar applications.
-=Bryan=-
Date: Mon, 12 Sep 2016 21:00:51 +0000
From: bob@evoria.net
To: nsayer@kfu.com; time-nuts@febo.com
Subject: Re: [time-nuts] A new take on the all-hardware GPSDO concept
Nick said:
"Jim Miller's 10 kHz GPSDO that’s been referenced here has either solved this problem, or the 10 kHz output of the Jupiter is substantially better than the Venus’ 10 MHz output, or the design doesn’t give the results time-nuts expect from a GPSDO. Which of those applies?"
Hi Nick,
You have to be very careful about the receiver you select. I think it's the case that the Jupiter's internal oscillator is phase locked to the GPS signal. In that case, you can use the output from the receiver to directly drive a PLL giving a high quality 10MHz or whatever you like. But, the low cost receivers on the market now, including those from Ublox, do not phase lock their oscillators to the GPS signal. In the case of Ublox, they specifically say that the quantization value is only available for the 1PPS output. So, yes, you can get a 10KHz pulse train from a Ublox or any other modern inexpensive GPS receiver, but it will suffer from whatever quantization error the manufacturer specifies.
bob
AE6RV.com
GFS GPSDO list:
groups.yahoo.com/neo/groups/GFS-GPSDOs/info
time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.
>From the Jupiter-T TU60-D120 datasheet
Figure 1-3 (next page) shows the typical 1PPS performance of the Jupiter-T GPS receiver. The 10 kHz output is also available from the receiver and is phase coherent with the 1PPS signal. This output is made available for functions such as phase locking of crystal oscillators, frequency synthesisers, and similar applications.
-=Bryan=-
> Date: Mon, 12 Sep 2016 21:00:51 +0000
> From: bob@evoria.net
> To: nsayer@kfu.com; time-nuts@febo.com
> Subject: Re: [time-nuts] A new take on the all-hardware GPSDO concept
>
> Nick said:
> "Jim Miller's 10 kHz GPSDO that’s been referenced here has either solved this problem, or the 10 kHz output of the Jupiter is substantially better than the Venus’ 10 MHz output, or the design doesn’t give the results time-nuts expect from a GPSDO. Which of those applies?"
> Hi Nick,
> You have to be very careful about the receiver you select. I think it's the case that the Jupiter's internal oscillator is phase locked to the GPS signal. In that case, you can use the output from the receiver to directly drive a PLL giving a high quality 10MHz or whatever you like. But, the low cost receivers on the market now, including those from Ublox, do not phase lock their oscillators to the GPS signal. In the case of Ublox, they specifically say that the quantization value is only available for the 1PPS output. So, yes, you can get a 10KHz pulse train from a Ublox or any other modern inexpensive GPS receiver, but it will suffer from whatever quantization error the manufacturer specifies.
>
> bob
> -----------------------------------------------------------------
> AE6RV.com
>
> GFS GPSDO list:
> groups.yahoo.com/neo/groups/GFS-GPSDOs/info
>
>
>
> _______________________________________________
> time-nuts mailing list -- time-nuts@febo.com
> To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
> and follow the instructions there.
CS
Charles Steinmetz
Mon, Sep 12, 2016 11:57 PM
From the Jupiter-T TU60-D120 datasheet
Figure 1-3 (next page) shows the typical 1PPS performance of the Jupiter-T GPS receiver. The 10 kHz output is also available from the receiver and is phase coherent with the 1PPS signal. This output is made available for functions such as phase locking of crystal oscillators, frequency synthesisers, and similar applications.
Yes, but.... The devil is in the details.
The fact that one thing is phase-locked to another does not necessarily
mean it puts out a good, clean signal. At short time scales (tau less
than ~100 seconds), the PPS signal from any GPS receiver is noisy. At
tau = 1second, it is shockingly noisy (~5e-9), and it decreases by a
nominal factor of 10 per decade as the averaging time (tau) is made
longer. By tau = 1000 seconds, it is pretty respectable (~2e-12 if the
GPS rx designers did their job well).
So, the trick is to use the noisy source (GPS) to discipline the clean
source (OCXO) very gently and very slowly. That way, the OCXO remains
in control of the output at short tau (< 100 to 1000 seconds), while it
is kept on-frequency over the long term by the GPS. This requires a PLL
control loop with a very long time constant (equivalently, a very low
cutoff frequency, in the microHertz to milliHertz region). It is not
practical to build analog filters with time constants that long, so one
must design a digital filter (far from impossible, but not the sort of
thing most hobbyist GPSDO designers are willing to undertake).
If you use a control loop with a short time constant, then the quiet
OXCO just follows the noisy reference source and doesn't improve anything.
If a GPS rx puts out a phase-locked audio or RF frequency (10kHz or
10MHz in the examples we've been discussing), the question becomes
whether that output has better stability (lower jitter) over short
averaging times than the PPS. The usual way to do this would be to use
a clean local oscillator disciplined in a very slow loop -- the same
thing discussed above, only at 10kHz rather than 10MHz. To my
knowledge, the Jupiter receivers don't have internal OCXOs devoted to
this, so if the 10kHz output really does have better stability at short
tau than the PPS, it isn't exactly obvious how the designers did it.
Presumably, they would need a very high-Q resonator of some sort.
Best regards,
Charles
Bryan wrote:
> From the Jupiter-T TU60-D120 datasheet
> Figure 1-3 (next page) shows the typical 1PPS performance of the Jupiter-T GPS receiver. The 10 kHz output is also available from the receiver and is phase coherent with the 1PPS signal. This output is made available for functions such as phase locking of crystal oscillators, frequency synthesisers, and similar applications.
Yes, but.... The devil is in the details.
The fact that one thing is phase-locked to another does not necessarily
mean it puts out a good, clean signal. At short time scales (tau less
than ~100 seconds), the PPS signal from any GPS receiver is noisy. At
tau = 1second, it is shockingly noisy (~5e-9), and it decreases by a
nominal factor of 10 per decade as the averaging time (tau) is made
longer. By tau = 1000 seconds, it is pretty respectable (~2e-12 if the
GPS rx designers did their job well).
So, the trick is to use the noisy source (GPS) to discipline the clean
source (OCXO) very gently and very slowly. That way, the OCXO remains
in control of the output at short tau (< 100 to 1000 seconds), while it
is kept on-frequency over the long term by the GPS. This requires a PLL
control loop with a very long time constant (equivalently, a very low
cutoff frequency, in the microHertz to milliHertz region). It is not
practical to build analog filters with time constants that long, so one
must design a digital filter (far from impossible, but not the sort of
thing most hobbyist GPSDO designers are willing to undertake).
If you use a control loop with a short time constant, then the quiet
OXCO just follows the noisy reference source and doesn't improve anything.
If a GPS rx puts out a phase-locked audio or RF frequency (10kHz or
10MHz in the examples we've been discussing), the question becomes
whether that output has better stability (lower jitter) over short
averaging times than the PPS. The usual way to do this would be to use
a clean local oscillator disciplined in a very slow loop -- the same
thing discussed above, only at 10kHz rather than 10MHz. To my
knowledge, the Jupiter receivers don't have internal OCXOs devoted to
this, so if the 10kHz output really does have better stability at short
tau than the PPS, it isn't exactly obvious how the designers did it.
Presumably, they would need a very high-Q resonator of *some* sort.
Best regards,
Charles