Hi,
On 2020-03-03 09:48, Matthias Welwarsky wrote:
> On Dienstag, 3. März 2020 09:25:13 CET Dana Whitlow wrote:
>> Matthias,
>>
>> You said that the LPRO has a pulling range of 4 PPM. Really? I
>> would think that 4PPB would be much more likely for a Rb.
> Yes, sorry, typing mistake. The user
On Dienstag, 3. März 2020 09:25:13 CET Dana Whitlow wrote:
> Matthias,
>
> You said that the LPRO has a pulling range of 4 PPM. Really? I
> would think that 4PPB would be much more likely for a Rb.
Yes, sorry, typing mistake. The user guide says "more then +/- 1.5E-9", I
found it more in the
Matthias,
You said that the LPRO has a pulling range of 4 PPM. Really? I
would think that 4PPB would be much more likely for a Rb.
Dana
On Mon, Mar 2, 2020 at 3:21 PM Matthias Welwarsky
wrote:
> On Montag, 2. März 2020 18:32:44 CET Skip Withrow wrote:
> [...]
> > The Thunderbolt DAC steps
On Montag, 2. März 2020 22:20:48 CET Matthias Welwarsky wrote:
> On Montag, 2. März 2020 18:32:44 CET Skip Withrow wrote:
> With a reasonably stable PPS from a timing receiver, just looking at the DAC
> movements, it should not be a problem to have a MDEV of 1e-14'ish for
> tau=1s. The LPRO
On Montag, 2. März 2020 18:32:44 CET Skip Withrow wrote:
[...]
> The Thunderbolt DAC steps in 10uV steps IIRC. And it steps its DAC
> voltage every second. With GPS signals jumping around you can still
> (will) end up with poorer short term performance than if the Rb was
> left to its own
Hi
So backing up a bit:
What are you trying to do?
GPS signals by their nature are noisy short term. They get better the longer
you stretch out the observation time. If you are running a single band /
uncorrected
GPS ( = most GPSDO’s and most GPS modules) you will hit a bunch of issues
Hello Mike,
Replacing the OCXO in a Thunderbolt (or one of the many telecom
cousins) is very easy to do. Just yank out the OCXO, hook the
Thunderbolt EFC to the Rubidium EFC (the Thunderbolt range is 0-6V),
and hook the Rb 10MHz where the OCXO 10MHz went.
That is the easy part. Understanding
You should log the PRS10's PPS timestamps with a computer, I'm sure you will be
surprised by what you see.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice
Hi
I'm doing it. I've taken PRS-10 which has PPS IN feature and fed it with PPS
from Trimble. It is still work in progress but the mechanism works. Time
constant of the PRS-10 is set to very long time (8 hours?) from factory when
signal is present on PPS-10.
Problem I'm encountering
In message
, Dana
Whitlow writes:
>Probably the easiest solution would be to feed 1 PPS from the T'bolt into a
>full-featured
>PRS-10 Rb, then fiddle with the loop parameters in the PRS-10 to best suit
>your needs.
Been there, tried that, not a good idea.
The PPS input of the
It is very simple to do. Warren did it I think seven years ago and we have done
it repeatedly in the last 4 years. Take the EFC that goes to the OCXO to the C
field control and Tbolt can determine and automatically adjust to frequency per
Volt. You can also adjust the time constant. Tbolt is
Probably the easiest solution would be to feed 1 PPS from the T'bolt into a
full-featured
PRS-10 Rb, then fiddle with the loop parameters in the PRS-10 to best suit
your needs.
Unfortunately, I'm told that most of the surplus PRS-10s have been stripped
of this capability.
But a new PRS-10 *does*
Hello, Time-Nutters--
Is it possible to add/combine/mate a rubidium osc to a Trimble
Thunderbolt GPSDO?
Have there been any examples of this that I could use as a guide?
Thanks for any info/feedback on this!!
Mike Baker
Gainesville/Micanopy
Florida USA
***
13 matches
Mail list logo
