Thanks to all that replied to my questions.
I have been off doing the suggestions offered and have found out some
interesting
things about my unit.
Found out that the unit I have does not allow for certain parameters to be
changed using
the command line. Argh Called SRS and talked with a
I need some guidance from the collective.
I just finished rebuilding my PRS10 lab standard and it is now using a M12+T
GPS module.
I have completed my site survey and it is now in hold position mode, TRAIM is
enabled
with 500ns alarm setting and the 1PPS is enabled during non-TRAIM alarm
You don't have a Cs reference but you have a GPS: in the long term it is
the same. By using a TIC (your preferred: HP5370B, HP5372A, SR620, PM6680,
PM6681, HP53132A, Racal 2351, Yokogawa TA720, PICTIC II, Wavecrest DTS275
[SIA3000?] and others) keep track of the GPS PPS vs. the PRS10 PPS.
On Wed,
On 05/02/2012 10:03 PM, Azelio Boriani wrote:
You don't have a Cs reference but you have a GPS: in the long term it is
the same. By using a TIC (your preferred: HP5370B, HP5372A, SR620, PM6680,
PM6681, HP53132A, Racal 2351, Yokogawa TA720, PICTIC II, Wavecrest DTS275
[SIA3000?] and others) keep
Magnus, you are correct but can I avoid to list our beloved
counters/analyzers? The time-nut main tool is the TIC.
Anyway, to correct the PPS input for the PRS10 the hardware approach is a
must: so a delay line and a microprocessor are needed. Unless the SRS can
develop a suitable software for the
Jerry, Magnus,
Considering the M12+T PPS noise, you won't need anything stellar. A
PICTIC II will do just fine... or if you trust the PRS-10 readings, run
from that.
What would make this better would to use a sawtooth-correction to PPS
delay setup, as the PRS-10 measurement resolution will
Hi Azelio,
On 05/02/2012 10:30 PM, Azelio Boriani wrote:
Magnus, you are correct but can I avoid to list our beloved
counters/analyzers? The time-nut main tool is the TIC.
Hehe, yes. But you can do great things even with a spare HP5335A for
instance. It's quite respectable with about 1 ns
I cannot believe my Guidetech GT4000 was left off your list.
Thomas Knox
Date: Wed, 2 May 2012 22:11:25 +0200
From: mag...@rubidium.dyndns.org
To: time-nuts@febo.com
Subject: Re: [time-nuts] Setting up PRS10 with M12+T GPS
On 05/02/2012 10:03 PM, Azelio Boriani wrote:
You don't have
The phase of the PPSOUT and the generated 10 MHz will probably not align
up, something which is critical to some applications.
Yes, for example the DVB-T SFN requires the PPS and 10MHz phases to be
aligned, better, not to move. This requires to slightly alter the 10MHz to
keep the PPS aligned.
my Guidetech GT4000 was left off your list.
Thomas Knox
Date: Wed, 2 May 2012 22:11:25 +0200
From: mag...@rubidium.dyndns.org
To: time-nuts@febo.com
Subject: Re: [time-nuts] Setting up PRS10 with M12+T GPS
On 05/02/2012 10:03 PM, Azelio Boriani wrote:
You don't have a Cs
Björn,
On 05/02/2012 10:54 PM, b...@lysator.liu.se wrote:
Jerry, Magnus,
Considering the M12+T PPS noise, you won't need anything stellar. A
PICTIC II will do just fine... or if you trust the PRS-10 readings, run
from that.
What would make this better would to use a sawtooth-correction to
Hi Azelio,
On 05/02/2012 11:19 PM, Azelio Boriani wrote:
The phase of the PPSOUT and the generated 10 MHz will probably not align
up,something which is critical to some applications.
Yes, for example the DVB-T SFN requires the PPS and 10MHz phases to be
aligned, better, not to move. This
The phase of the PPSOUT and the generated 10 MHz will probably not align
up, something which is critical to some applications.
Yes, for example the DVB-T SFN requires the PPS and 10MHz phases to be
aligned, better, not to move. This requires to slightly alter the 10MHz to
keep the PPS aligned.
Hi Magnus,
|---|
| |
| PRS10APRS10B |
|---PPS IN PPS OUT--PPS IN PPS OUT--|
hoping that the font doesn't mess up the
Hi Björn,
On 05/03/2012 12:01 AM, b...@lysator.liu.se wrote:
Hi Magnus,
|---|
| |
| PRS10APRS10B |
|---PPS IN PPS
Yes, all made clear.
Trigger on Ch.4, I see. You have written green: 10MHz PRS10B but it must
be A, otherwise it seems that the PPS and the 10MHz of the PRS10 are not
phase aligned. Moreover, the PRS10B seems to track the PRS10A with some
delay as the 10MHz from A spreads on more than 5nS (useful,
Magnus,
Tbolt PRS10A PRS10B
1pps --PPSIN
PPSOUT -- PPS IN
PRS10A slowly following the Tbolt (PRS10A PT8)
PRS10B quickly following the PRS10A (PRS10B PT0)
Ok?
Yes, but if this is a free-running thunderbolt (I think you said
something about that) then PT8
up PRS10 with M12+T GPS
On 05/02/2012 10:03 PM, Azelio Boriani wrote:
You don't have a Cs reference but you have a GPS: in the long term it is
the same. By using a TIC (your preferred: HP5370B, HP5372A, SR620, PM6680,
PM6681, HP53132A, Racal 2351, Yokogawa TA720, PICTIC II, Wavecrest DTS275
believe my Guidetech GT4000 was left off your list.
Thomas Knox
Date: Wed, 2 May 2012 22:11:25 +0200
From: mag...@rubidium.dyndns.org
To: time-nuts@febo.com
Subject: Re: [time-nuts] Setting up PRS10 with M12+T GPS
On 05/02/2012 10:03 PM, Azelio Boriani wrote:
You don't
Yes, all made clear.
Trigger on Ch.4, I see. You have written green: 10MHz PRS10B but it must
be A, otherwise it seems that the PPS and the 10MHz of the PRS10 are not
phase aligned. Moreover, the PRS10B seems to track the PRS10A with some
delay as the 10MHz from A spreads on more than 5nS
Hi Björn,
On 05/02/2012 11:50 PM, b...@lysator.liu.se wrote:
The phase of the PPSOUT and the generated 10 MHz will probably not align
up,something which is critical to some applications.
Yes, for example the DVB-T SFN requires the PPS and 10MHz phases to be
aligned, better, not to move. This
Maybe the 10MHz and the PPS are not exactly aligned but you can see that
the persistance of the 10MHzB (blue trace) is exactly the same of the PPS
B (red trace), so they are absolutely consistent and perfectly linked
together.
On Thu, May 3, 2012 at 12:42 AM, b...@lysator.liu.se wrote:
Yes,
Björn,
On 05/03/2012 12:30 AM, b...@lysator.liu.se wrote:
Magnus,
Tbolt PRS10A PRS10B
1pps -- PPSIN
PPSOUT -- PPS IN
PRS10A slowly following the Tbolt (PRS10A PT8)
PRS10B quickly following the PRS10A (PRS10B PT0)
Ok?
Yes, but if this is a free-running
Björn,
On 05/03/2012 12:42 AM, b...@lysator.liu.se wrote:
Yes, all made clear.
Trigger on Ch.4, I see. You have written green: 10MHz PRS10B but it must
be A, otherwise it seems that the PPS and the 10MHz of the PRS10 are not
phase aligned. Moreover, the PRS10B seems to track the PRS10A with
Björn,
On 05/03/2012 12:30 AM, b...@lysator.liu.se wrote:
Magnus,
Tbolt PRS10A PRS10B
1pps -- PPSIN
PPSOUT -- PPS IN
PRS10A slowly following the Tbolt (PRS10A PT8)
PRS10B quickly following the PRS10A (PRS10B PT0)
Ok?
Yes, but if this is a free-running
On 05/03/2012 01:09 AM, b...@lysator.liu.se wrote:
Björn,
On 05/03/2012 12:30 AM, b...@lysator.liu.se wrote:
Magnus,
Tbolt PRS10A PRS10B
1pps -- PPSIN
PPSOUT --PPS IN
PRS10A slowly following the Tbolt (PRS10A PT8)
PRS10B quickly following the PRS10A
On 5/2/2012 5:18 PM, Tom Knox wrote:
I cannot believe my Guidetech GT4000 was left off your list.
No worries. He didn't list the HP 5370A, either.
___
time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to
27 matches
Mail list logo
