Re: [time-nuts] Comparing PPS from 2 GPS units

2012-12-21 Thread Bob Camp
Hi

The other question would be - what libraries (if any) are used by the code? If 
any are they windows compatible?

Bob

On Dec 21, 2012, at 2:16 AM, Hal Murray hmur...@megapathdsl.net wrote:

 Can you create an executable for windows?
 
 I know next to nothing about Windows.  (and don't have access to any Windows 
 machines)
 
 Others have reported that Python works on Windows.
 
 If you give me a few input/output samples, I'll try to write some python code 
 to do the translation.  If I get it working, I expect there will be somebody 
 on the list who can fix the top-level stuff to work correctly on Windows 
 and/or describe the recipe that's needed for setup.
 
 
 -- 
 These are my opinions.  I hate spam.
 
 
 
 
 ___
 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.


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


Re: [time-nuts] Comparing PPS from 2 GPS units

2012-12-21 Thread Jim Lux

On 12/20/12 11:16 PM, Hal Murray wrote:

Can you create an executable for windows?


I know next to nothing about Windows.  (and don't have access to any Windows
machines)

Others have reported that Python works on Windows.



I use python all the time on Windows (and unchanged from Python running 
on a Mac or Linux box).


As a practical matter, I use ActiveState ActivePython, but there's 
several pythons for windows here

http://www.python.org/getit/windows/

For windows,after installing python, if you have your xyz.py file, you 
just double click on it, and it runs like any other program.




If you give me a few input/output samples, I'll try to write some python code
to do the translation.  If I get it working, I expect there will be somebody
on the list who can fix the top-level stuff to work correctly on Windows
and/or describe the recipe that's needed for setup.





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


Re: [time-nuts] Comparing PPS from 2 GPS units

2012-12-20 Thread Said Jackson
Hal,

Can you create an executable for windows?

Thanks,
Said

Sent from my iPad

On Dec 14, 2012, at 8:47 PM, Hal Murray hmur...@megapathdsl.net wrote:

 
 saidj...@aol.com said:
 Time-Nuts, anyone willing to write this for the benefit of all? 
 
 Does python run on Windows?  If so, give me samples of input data and what 
 you want as output.
 
 
 -- 
 These are my opinions.  I hate spam.
 
 
 
 
 ___
 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.

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


Re: [time-nuts] Comparing PPS from 2 GPS units

2012-12-20 Thread Sarah White
On 12/21/2012 1:52 AM, Said Jackson wrote:
 Can you create an executable for windows?

 Thanks,
 Said

python is a script-type language which runs on top of the python engine
(almost similar to how java programs run on a java engine)

... to answer your question: yep, you can download here:

http://sourceforge.net/projects/pywin32/files/pywin32/Build%20218/

Most software written for python is usually targeted for 2.7 and/or 3.2,
but you can try some other version if you're wanting to risk it.

hope this helps,
Sarah

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


Re: [time-nuts] Comparing PPS from 2 GPS units

2012-12-20 Thread Hal Murray
 Can you create an executable for windows?

I know next to nothing about Windows.  (and don't have access to any Windows 
machines)

Others have reported that Python works on Windows.

If you give me a few input/output samples, I'll try to write some python code 
to do the translation.  If I get it working, I expect there will be somebody 
on the list who can fix the top-level stuff to work correctly on Windows 
and/or describe the recipe that's needed for setup.


-- 
These are my opinions.  I hate spam.




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


Re: [time-nuts] Comparing PPS from 2 GPS units

2012-12-18 Thread Gerhard Hoffmann

Am 18.12.2012 03:01, schrieb David:

That is the stuff but Tektronix had some with an even smaller
diameter.  It would be nice to have a new source as I would hate to
cannibalize oscilloscopes for it.


Could be Sage Wireline. Also used for couplers and RF power amps.

http://www.google.de/url?sa=trct=jq=sage%20wirelinesource=webcd=9cad=rjaved=0CHwQFjAIurl=http%3A%2F%2Fwww.wtel.com.cn%2Fmanageweb%2Fwebedit%2Fuploadfile%2FSage%2520Catalog%2520Products%25202010.pdfei=mCbQUMy3FMTKsgbs64HYDAusg=AFQjCNGNWELj8YsRHE8scZewoWT_MnrMiA

(I wonder if this monster link works)

regards, Gerhard



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


Re: [time-nuts] Comparing PPS from 2 GPS units

2012-12-18 Thread REEVES Paul
I think not Wireline. That has a rather 'loose' twist coupling between the two 
internal lines. The cable is probably purpose designed for use in delay lines 
and actually did have a helically wound inner conductor. In a previous life 
working for a bit of Marconi that made tv camera systems we used this stuff for 
video equalisation networks and similar. Not sure it is still made as all the 
video processing is digital nowadays..   I might have some stashed away but 
it would take a LOT of finding :-)

regards,
Paul G8GJA

-Original Message-
From: time-nuts-boun...@febo.com [mailto:time-nuts-boun...@febo.com] On Behalf 
Of Gerhard Hoffmann
Sent: 18 December 2012 08:24
To: time-nuts@febo.com
Subject: Re: [time-nuts] Comparing PPS from 2 GPS units

Am 18.12.2012 03:01, schrieb David:
 That is the stuff but Tektronix had some with an even smaller
 diameter.  It would be nice to have a new source as I would hate to
 cannibalize oscilloscopes for it.

Could be Sage Wireline. Also used for couplers and RF power amps.

http://www.google.de/url?sa=trct=jq=sage%20wirelinesource=webcd=9cad=rjaved=0CHwQFjAIurl=http%3A%2F%2Fwww.wtel.com.cn%2Fmanageweb%2Fwebedit%2Fuploadfile%2FSage%2520Catalog%2520Products%25202010.pdfei=mCbQUMy3FMTKsgbs64HYDAusg=AFQjCNGNWELj8YsRHE8scZewoWT_MnrMiA

(I wonder if this monster link works)

regards, Gerhard



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

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


Re: [time-nuts] Comparing PPS from 2 GPS units

2012-12-18 Thread Jim Lux

On 12/18/12 12:23 AM, Gerhard Hoffmann wrote:

Am 18.12.2012 03:01, schrieb David:

That is the stuff but Tektronix had some with an even smaller
diameter.  It would be nice to have a new source as I would hate to
cannibalize oscilloscopes for it.


Could be Sage Wireline. Also used for couplers and RF power amps.

http://www.google.de/url?sa=trct=jq=sage%20wirelinesource=webcd=9cad=rjaved=0CHwQFjAIurl=http%3A%2F%2Fwww.wtel.com.cn%2Fmanageweb%2Fwebedit%2Fuploadfile%2FSage%2520Catalog%2520Products%25202010.pdfei=mCbQUMy3FMTKsgbs64HYDAusg=AFQjCNGNWELj8YsRHE8scZewoWT_MnrMiA



Horrible redirection/copy link from China

Sage is part of Spectrum Microwave now:
http://www.spectrummicrowave.com/pdf/wirelineguide.pdf

But they're not making delay line to my knowledge, more precision 
twisted pair and such for couplers.






(I wonder if this monster link works)

regards, Gerhard



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




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


Re: [time-nuts] Comparing PPS from 2 GPS units

2012-12-18 Thread Jim Lux

On 12/17/12 11:21 PM, Hal Murray wrote:

Cond. Material  Magnet Wire Helix
(What is magnet wire, and what does helix mean and how does it effect
coax?)



Magnet wire is enamelled wire (usually copper).


I'm familiar with that usage, but I don't know why it's interesting in the
context of coax.

I think the key idea is that the insulation is thin so you can get lots of
turns/inch in a transformer.

I don't understand what a helix is in coax, or rather I don't appreciate
the numbers.  I'd guess that the center conductor is constructed as a helix
and that increases the inductance/meter by a whole lot, or something like
that.  But isn't there a sqrt in there?



That is exactly what is done.. a *very tiny* wire is wound in a helix 
around a core (sometimes ferrous) that forms the center conductor of the 
coaxial cable, so it has huge L per length.


And yes, 1/sqrt(LC) is the propagation velocity







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


Re: [time-nuts] Comparing PPS from 2 GPS units

2012-12-17 Thread Hal Murray

 A fifth solution is to use a pulse delay generator like a DG535. I use this
 to create high-resolution early/late 1PPS sync pulses. They show up on eBay,
 but aren't cheap. For bargains, watch for older model programmable pulse
 delay generators by BNC (Berkeley Nucleonics Corporation).

Thanks.  Those are more $$$ than I'm interested in right now, but might be a 
useful tool sometime in the future.

Another approach is to use a scope: trigger on one PPS and adjust the delay 
(which might be negative) and sweep speed so you can see the other PPS 
signal.  Maybe I'll play with this to see what sort of results I can get.


 Lastly, there are cute little delay boxes (www.ebay.com/itm/150962422699)
 that might work. Not sure how stable they are at the ns level. But it would
 be fun to measure. If someone opens one of these please tell us if it's a
 coil of wire, some kind of LRC filter delay, or if they use those Dallas
 delay chips. Which is another solution for you -- google or eBay search for:
 silicon delay line. 

You can make a reasonable delay line by using the lumped circuit 
approximation for the L and C for the appropriate impedance transmission 
line.  I assume that's what's in the delay boxes.  I should try that 
sometime.  Thanks for the reminder.

The delay chips I've looked at before used gate delays.  I think they were 
Motorola rather than Dallas.  I just poked at a few Maxim data sheets.  I 
didn't find out how they implemented the delays.

I think some of the clock recovery chips tune delays by tweaking the 
threshold voltage.


-- 
These are my opinions.  I hate spam.




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


Re: [time-nuts] Comparing PPS from 2 GPS units

2012-12-17 Thread David
On Mon, 17 Dec 2012 10:19:43 -0800, Hal Murray
hmur...@megapathdsl.net wrote:


 A fifth solution is to use a pulse delay generator like a DG535. I use this
 to create high-resolution early/late 1PPS sync pulses. They show up on eBay,
 but aren't cheap. For bargains, watch for older model programmable pulse
 delay generators by BNC (Berkeley Nucleonics Corporation).

Thanks.  Those are more $$$ than I'm interested in right now, but might be a 
useful tool sometime in the future.

Another approach is to use a scope: trigger on one PPS and adjust the delay 
(which might be negative) and sweep speed so you can see the other PPS 
signal.  Maybe I'll play with this to see what sort of results I can get.


 Lastly, there are cute little delay boxes (www.ebay.com/itm/150962422699)
 that might work. Not sure how stable they are at the ns level. But it would
 be fun to measure. If someone opens one of these please tell us if it's a
 coil of wire, some kind of LRC filter delay, or if they use those Dallas
 delay chips. Which is another solution for you -- google or eBay search for:
 silicon delay line. 

You can make a reasonable delay line by using the lumped circuit 
approximation for the L and C for the appropriate impedance transmission 
line.  I assume that's what's in the delay boxes.  I should try that 
sometime.  Thanks for the reminder.

The delay chips I've looked at before used gate delays.  I think they were 
Motorola rather than Dallas.  I just poked at a few Maxim data sheets.  I 
didn't find out how they implemented the delays.

I think some of the clock recovery chips tune delays by tweaking the 
threshold voltage.

I have been testing just using adjustable RC delays into a logic gate
to generate pretrigger pulses for sampling oscilloscopes.  Accuracy
depends on a complete reset of the capacitor and tracking between the
RC charge voltage and gate threshold voltage.  Worst cast jitter for
TTL has been in the 100s of picoseconds range because of supply
voltage sensitivity.  Different families of TTL and CMOS logic all
performed about the same.

Here is the jitter measurement that came from the RC logic gate delay
test:

http://www.banishedsouls.org/c2df3757f1/PG506/PDJ%20lolcat.jpg

Much better is to use a differential comparator or differential input
ECL which solves the threshold variation errors and a fast (it really
isn't all that fast) ramp generator with a precision reset.  The
differential input allows the ramp rate and threshold voltage to be
linked allowing ratiometric operation to reject power supply or
reference voltage variation and noise.

My next pretrigger generator is going the differential comparator or
differential ECL route with a fast ramp and precision reset.  I expect
jitter to be significantly better than 10s of picoseconds for delays
up to about 100 nanoseconds.  If I get down to 10 picoseconds of
jitter, I will be happy since I have no real way to measure much below
that.

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


Re: [time-nuts] Comparing PPS from 2 GPS units

2012-12-17 Thread Bob Camp
Hi

With R-C delay generators, temperature coefficient is likely to be an issue. 
NPO will get you to 30 ppm/C. Most resistors will be up in the 50 or so ppm / C 
range. On top of that you have the contributions of what ever strays might be 
running around. 

If you are trying to set up say a 1 us delay, you will get ~ 50 ps per degree C 
in your delay. That's a lot .

Bob

On Dec 17, 2012, at 1:56 PM, David davidwh...@gmail.com wrote:

 On Mon, 17 Dec 2012 10:19:43 -0800, Hal Murray
 hmur...@megapathdsl.net wrote:
 
 
 A fifth solution is to use a pulse delay generator like a DG535. I use this
 to create high-resolution early/late 1PPS sync pulses. They show up on eBay,
 but aren't cheap. For bargains, watch for older model programmable pulse
 delay generators by BNC (Berkeley Nucleonics Corporation).
 
 Thanks.  Those are more $$$ than I'm interested in right now, but might be a 
 useful tool sometime in the future.
 
 Another approach is to use a scope: trigger on one PPS and adjust the delay 
 (which might be negative) and sweep speed so you can see the other PPS 
 signal.  Maybe I'll play with this to see what sort of results I can get.
 
 
 Lastly, there are cute little delay boxes (www.ebay.com/itm/150962422699)
 that might work. Not sure how stable they are at the ns level. But it would
 be fun to measure. If someone opens one of these please tell us if it's a
 coil of wire, some kind of LRC filter delay, or if they use those Dallas
 delay chips. Which is another solution for you -- google or eBay search for:
 silicon delay line. 
 
 You can make a reasonable delay line by using the lumped circuit 
 approximation for the L and C for the appropriate impedance transmission 
 line.  I assume that's what's in the delay boxes.  I should try that 
 sometime.  Thanks for the reminder.
 
 The delay chips I've looked at before used gate delays.  I think they were 
 Motorola rather than Dallas.  I just poked at a few Maxim data sheets.  I 
 didn't find out how they implemented the delays.
 
 I think some of the clock recovery chips tune delays by tweaking the 
 threshold voltage.
 
 I have been testing just using adjustable RC delays into a logic gate
 to generate pretrigger pulses for sampling oscilloscopes.  Accuracy
 depends on a complete reset of the capacitor and tracking between the
 RC charge voltage and gate threshold voltage.  Worst cast jitter for
 TTL has been in the 100s of picoseconds range because of supply
 voltage sensitivity.  Different families of TTL and CMOS logic all
 performed about the same.
 
 Here is the jitter measurement that came from the RC logic gate delay
 test:
 
 http://www.banishedsouls.org/c2df3757f1/PG506/PDJ%20lolcat.jpg
 
 Much better is to use a differential comparator or differential input
 ECL which solves the threshold variation errors and a fast (it really
 isn't all that fast) ramp generator with a precision reset.  The
 differential input allows the ramp rate and threshold voltage to be
 linked allowing ratiometric operation to reject power supply or
 reference voltage variation and noise.
 
 My next pretrigger generator is going the differential comparator or
 differential ECL route with a fast ramp and precision reset.  I expect
 jitter to be significantly better than 10s of picoseconds for delays
 up to about 100 nanoseconds.  If I get down to 10 picoseconds of
 jitter, I will be happy since I have no real way to measure much below
 that.
 
 ___
 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.


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


Re: [time-nuts] Comparing PPS from 2 GPS units

2012-12-17 Thread David
You would not want to do this for long delays obviously.  A digital
counter with the delay used as a vernier would be more appropriate
there.  That gets complicated fast if the input is asynchronous.

Analog first order compensation of the temperature coefficient is
straightforward using the same techniques that are used for voltage to
frequency converters.  Unfortunately, polystyrene capacitors are no
longer produced.  Digital calibration might be easier to design and
would be a good idea for verification of performance anyway.

I wonder what the temperature coefficient is of the Maxim's
programmable delay lines.  I do not see it in their datasheets.  The
On semiconductor one I checked is greater than 1000ppm/C but its
maximum delay is 12.5 nanoseconds.

On Mon, 17 Dec 2012 14:04:54 -0500, Bob Camp li...@rtty.us wrote:

Hi

With R-C delay generators, temperature coefficient is likely to be an issue. 
NPO will get you to 30 ppm/C. Most resistors will be up in the 50 or so ppm / 
C range. On top of that you have the contributions of what ever strays might 
be running around. 

If you are trying to set up say a 1 us delay, you will get ~ 50 ps per degree 
C in your delay. That's a lot .

Bob

On Dec 17, 2012, at 1:56 PM, David davidwh...@gmail.com wrote:

 On Mon, 17 Dec 2012 10:19:43 -0800, Hal Murray
 hmur...@megapathdsl.net wrote:
 
 
 A fifth solution is to use a pulse delay generator like a DG535. I use this
 to create high-resolution early/late 1PPS sync pulses. They show up on 
 eBay,
 but aren't cheap. For bargains, watch for older model programmable pulse
 delay generators by BNC (Berkeley Nucleonics Corporation).
 
 Thanks.  Those are more $$$ than I'm interested in right now, but might be 
 a 
 useful tool sometime in the future.
 
 Another approach is to use a scope: trigger on one PPS and adjust the delay 
 (which might be negative) and sweep speed so you can see the other PPS 
 signal.  Maybe I'll play with this to see what sort of results I can get.
 
 
 Lastly, there are cute little delay boxes (www.ebay.com/itm/150962422699)
 that might work. Not sure how stable they are at the ns level. But it would
 be fun to measure. If someone opens one of these please tell us if it's a
 coil of wire, some kind of LRC filter delay, or if they use those Dallas
 delay chips. Which is another solution for you -- google or eBay search 
 for:
 silicon delay line. 
 
 You can make a reasonable delay line by using the lumped circuit 
 approximation for the L and C for the appropriate impedance transmission 
 line.  I assume that's what's in the delay boxes.  I should try that 
 sometime.  Thanks for the reminder.
 
 The delay chips I've looked at before used gate delays.  I think they were 
 Motorola rather than Dallas.  I just poked at a few Maxim data sheets.  I 
 didn't find out how they implemented the delays.
 
 I think some of the clock recovery chips tune delays by tweaking the 
 threshold voltage.
 
 I have been testing just using adjustable RC delays into a logic gate
 to generate pretrigger pulses for sampling oscilloscopes.  Accuracy
 depends on a complete reset of the capacitor and tracking between the
 RC charge voltage and gate threshold voltage.  Worst cast jitter for
 TTL has been in the 100s of picoseconds range because of supply
 voltage sensitivity.  Different families of TTL and CMOS logic all
 performed about the same.
 
 Here is the jitter measurement that came from the RC logic gate delay
 test:
 
 http://www.banishedsouls.org/c2df3757f1/PG506/PDJ%20lolcat.jpg
 
 Much better is to use a differential comparator or differential input
 ECL which solves the threshold variation errors and a fast (it really
 isn't all that fast) ramp generator with a precision reset.  The
 differential input allows the ramp rate and threshold voltage to be
 linked allowing ratiometric operation to reject power supply or
 reference voltage variation and noise.
 
 My next pretrigger generator is going the differential comparator or
 differential ECL route with a fast ramp and precision reset.  I expect
 jitter to be significantly better than 10s of picoseconds for delays
 up to about 100 nanoseconds.  If I get down to 10 picoseconds of
 jitter, I will be happy since I have no real way to measure much below
 that.
 
 ___
 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.


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

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


Re: [time-nuts] Comparing PPS from 2 GPS units

2012-12-17 Thread M. Simon
Nice pulse delay generator:

http://www.edn.com/file/14660-Figure_1.pdf

The article that goes with it:

http://www.edn.com/design/analog/4323671/Dual-flip-flop-forms-simple-delayed-pulse-generator


The delay is analog - charging a capacitor until it crosses a threshold. So I 
don't know if it is good enough. But I did find it interesting. The order of 
the delay is 1 to 250 uSec. Faster parts would get you into shorter delays. 

If you had two of these operating on a common trigger...

Simon


Engineering is the art of making what you want from what you can get at a 
profit.




 From: David davidwh...@gmail.com
To: Discussion of precise time and frequency measurement time-nuts@febo.com 
Sent: Monday, December 17, 2012 6:56 PM
Subject: Re: [time-nuts] Comparing PPS from 2 GPS units
 
On Mon, 17 Dec 2012 10:19:43 -0800, Hal Murray
hmur...@megapathdsl.net wrote:


 A fifth solution is to use a pulse delay generator like a DG535. I use this
 to create high-resolution early/late 1PPS sync pulses. They show up on eBay,
 but aren't cheap. For bargains, watch for older model programmable pulse
 delay generators by BNC (Berkeley Nucleonics Corporation).

Thanks.  Those are more $$$ than I'm interested in right now, but might be a 
useful tool sometime in the future.

Another approach is to use a scope: trigger on one PPS and adjust the delay 
(which might be negative) and sweep speed so you can see the other PPS 
signal.  Maybe I'll play with this to see what sort of results I can get.


 Lastly, there are cute little delay boxes (www.ebay.com/itm/150962422699)
 that might work. Not sure how stable they are at the ns level. But it would
 be fun to measure. If someone opens one of these please tell us if it's a
 coil of wire, some kind of LRC filter delay, or if they use those Dallas
 delay chips. Which is another solution for you -- google or eBay search for:
 silicon delay line. 

You can make a reasonable delay line by using the lumped circuit 
approximation for the L and C for the appropriate impedance transmission 
line.  I assume that's what's in the delay boxes.  I should try that 
sometime.  Thanks for the reminder.

The delay chips I've looked at before used gate delays.  I think they were 
Motorola rather than Dallas.  I just poked at a few Maxim data sheets.  I 
didn't find out how they implemented the delays.

I think some of the clock recovery chips tune delays by tweaking the 
threshold voltage.

I have been testing just using adjustable RC delays into a logic gate
to generate pretrigger pulses for sampling oscilloscopes.  Accuracy
depends on a complete reset of the capacitor and tracking between the
RC charge voltage and gate threshold voltage.  Worst cast jitter for
TTL has been in the 100s of picoseconds range because of supply
voltage sensitivity.  Different families of TTL and CMOS logic all
performed about the same.

Here is the jitter measurement that came from the RC logic gate delay
test:

http://www.banishedsouls.org/c2df3757f1/PG506/PDJ%20lolcat.jpg

Much better is to use a differential comparator or differential input
ECL which solves the threshold variation errors and a fast (it really
isn't all that fast) ramp generator with a precision reset.  The
differential input allows the ramp rate and threshold voltage to be
linked allowing ratiometric operation to reject power supply or
reference voltage variation and noise.

My next pretrigger generator is going the differential comparator or
differential ECL route with a fast ramp and precision reset.  I expect
jitter to be significantly better than 10s of picoseconds for delays
up to about 100 nanoseconds.  If I get down to 10 picoseconds of
jitter, I will be happy since I have no real way to measure much below
that.

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



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


Re: [time-nuts] Comparing PPS from 2 GPS units

2012-12-17 Thread Bob Camp
Hi

I believe you will find that NPO's are your best bet by far for short delays.

The R's and C's on a simple semi are going to have some pretty major tempco's. 
If they go with a fancy process they can change that. Normally to keep things 
cheap they use the simple process.

Bob

On Dec 17, 2012, at 2:55 PM, David davidwh...@gmail.com wrote:

 You would not want to do this for long delays obviously.  A digital
 counter with the delay used as a vernier would be more appropriate
 there.  That gets complicated fast if the input is asynchronous.
 
 Analog first order compensation of the temperature coefficient is
 straightforward using the same techniques that are used for voltage to
 frequency converters.  Unfortunately, polystyrene capacitors are no
 longer produced.  Digital calibration might be easier to design and
 would be a good idea for verification of performance anyway.
 
 I wonder what the temperature coefficient is of the Maxim's
 programmable delay lines.  I do not see it in their datasheets.  The
 On semiconductor one I checked is greater than 1000ppm/C but its
 maximum delay is 12.5 nanoseconds.
 
 On Mon, 17 Dec 2012 14:04:54 -0500, Bob Camp li...@rtty.us wrote:
 
 Hi
 
 With R-C delay generators, temperature coefficient is likely to be an issue. 
 NPO will get you to 30 ppm/C. Most resistors will be up in the 50 or so ppm 
 / C range. On top of that you have the contributions of what ever strays 
 might be running around. 
 
 If you are trying to set up say a 1 us delay, you will get ~ 50 ps per 
 degree C in your delay. That's a lot .
 
 Bob
 
 On Dec 17, 2012, at 1:56 PM, David davidwh...@gmail.com wrote:
 
 On Mon, 17 Dec 2012 10:19:43 -0800, Hal Murray
 hmur...@megapathdsl.net wrote:
 
 
 A fifth solution is to use a pulse delay generator like a DG535. I use 
 this
 to create high-resolution early/late 1PPS sync pulses. They show up on 
 eBay,
 but aren't cheap. For bargains, watch for older model programmable pulse
 delay generators by BNC (Berkeley Nucleonics Corporation).
 
 Thanks.  Those are more $$$ than I'm interested in right now, but might be 
 a 
 useful tool sometime in the future.
 
 Another approach is to use a scope: trigger on one PPS and adjust the 
 delay 
 (which might be negative) and sweep speed so you can see the other PPS 
 signal.  Maybe I'll play with this to see what sort of results I can get.
 
 
 Lastly, there are cute little delay boxes (www.ebay.com/itm/150962422699)
 that might work. Not sure how stable they are at the ns level. But it 
 would
 be fun to measure. If someone opens one of these please tell us if it's a
 coil of wire, some kind of LRC filter delay, or if they use those Dallas
 delay chips. Which is another solution for you -- google or eBay search 
 for:
 silicon delay line. 
 
 You can make a reasonable delay line by using the lumped circuit 
 approximation for the L and C for the appropriate impedance transmission 
 line.  I assume that's what's in the delay boxes.  I should try that 
 sometime.  Thanks for the reminder.
 
 The delay chips I've looked at before used gate delays.  I think they were 
 Motorola rather than Dallas.  I just poked at a few Maxim data sheets.  I 
 didn't find out how they implemented the delays.
 
 I think some of the clock recovery chips tune delays by tweaking the 
 threshold voltage.
 
 I have been testing just using adjustable RC delays into a logic gate
 to generate pretrigger pulses for sampling oscilloscopes.  Accuracy
 depends on a complete reset of the capacitor and tracking between the
 RC charge voltage and gate threshold voltage.  Worst cast jitter for
 TTL has been in the 100s of picoseconds range because of supply
 voltage sensitivity.  Different families of TTL and CMOS logic all
 performed about the same.
 
 Here is the jitter measurement that came from the RC logic gate delay
 test:
 
 http://www.banishedsouls.org/c2df3757f1/PG506/PDJ%20lolcat.jpg
 
 Much better is to use a differential comparator or differential input
 ECL which solves the threshold variation errors and a fast (it really
 isn't all that fast) ramp generator with a precision reset.  The
 differential input allows the ramp rate and threshold voltage to be
 linked allowing ratiometric operation to reject power supply or
 reference voltage variation and noise.
 
 My next pretrigger generator is going the differential comparator or
 differential ECL route with a fast ramp and precision reset.  I expect
 jitter to be significantly better than 10s of picoseconds for delays
 up to about 100 nanoseconds.  If I get down to 10 picoseconds of
 jitter, I will be happy since I have no real way to measure much below
 that.
 
 ___
 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.
 
 
 ___
 time-nuts mailing list -- time-nuts@febo.com
 To 

Re: [time-nuts] Comparing PPS from 2 GPS units

2012-12-17 Thread Hal Murray

li...@rtty.us said:
 If you are trying to set up say a 1 us delay, you will get ~ 50 ps per
 degree C in your delay. That's a lot . 

A while ago, t...@leapsecond.com said:
 A long delay cable is fine too. If these are timing receivers you probably
 don't need more than 100 ns of delay, once you figure out which receiver is
 ahead of the other. The cable tempco is low enough not to worry about. 

100 ns is 50-100 feet.  That's a reasonable length to work with.  But I was 
curious about the temperature coefficient.  Google found this:
  http://www.hepl.hiroshima-u.ac.jp/phx/notes/cable/cable.html
which says:
# Belden 8240 (solid) shows a temperature coefficient of around 
-0.252ps/m/deg in a temperature range between -20 and 30 deg. The coefficient 
becomes steeper beyond 30 deg.
# Belden 8219 (foam) shows a larger temperature coefficient of around -0.352 
ps/m/deg than that of 8240 in the similar temperature range. The coefficient 
becomes steeper beyond 30 deg, but less steeper than that of 8240.
# Fujikura RG58-A/U shows the smallest temperature coefficient of around 
-0.152 ps/m/deg, but in a narrow temperature range between -10 and 20 deg. 
The coefficient beyond 20 deg is much steeper than the others.

To pick round numbers, 30 meters and 3 C and 0.25 ps/m/C gives 25 ps.


-- 
These are my opinions.  I hate spam.




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


Re: [time-nuts] Comparing PPS from 2 GPS units

2012-12-17 Thread Bruce Griffiths
Its actually a relatively low performance implementation of a classic 
technique.
The ramp capacitor reset switch (a saturated transistor) has a 
relatively slow turnoff and poorly defined reset voltage.


For shorter time delays lower capacitance current source and reset 
devices are required.


Decoupling of the current sensing device in the control loop from the 
current source device emitter is desirable.


ECL delay chips using this technique complete with a DAC to set the 
comparator threshold used to be available.


A classic reset switch uses a current driven pair of matched shottky 
diodes to ensure fast switching coupled with a relatively low offset 
voltage.


Techniques to produce stable longer delays:

1) Use a stable (phase locked) gated oscillator to produce a well 
defined long delay using pulse counting together with a triggered ramp + 
DAC + comparator for fine adjustment.

The HP5359A delay generator is an example of this technique.

2) Use a synchroniser plus counter for the coarse delay followed by a 
triggered ramp + DAC and comparator.
The synchroniser delay is measured and the result used to adjust the 
fine delay to compensate for the variable synchroniser delay.
Analog techniques where the fine delay ramp is stopped and held by the 
synchroniser outpt and then resumed by the digital delay output 
transition have also been used.



Bruce

M. Simon wrote:

Nice pulse delay generator:

http://www.edn.com/file/14660-Figure_1.pdf

The article that goes with it:

http://www.edn.com/design/analog/4323671/Dual-flip-flop-forms-simple-delayed-pulse-generator


The delay is analog - charging a capacitor until it crosses a threshold. So I 
don't know if it is good enough. But I did find it interesting. The order of 
the delay is 1 to 250 uSec. Faster parts would get you into shorter delays.

If you had two of these operating on a common trigger...

Simon


Engineering is the art of making what you want from what you can get at a 
profit.



   


From: Daviddavidwh...@gmail.com
To: Discussion of precise time and frequency measurementtime-nuts@febo.com
Sent: Monday, December 17, 2012 6:56 PM
Subject: Re: [time-nuts] Comparing PPS from 2 GPS units

On Mon, 17 Dec 2012 10:19:43 -0800, Hal Murray
hmur...@megapathdsl.net  wrote:

 
   

A fifth solution is to use a pulse delay generator like a DG535. I use this
to create high-resolution early/late 1PPS sync pulses. They show up on eBay,
but aren't cheap. For bargains, watch for older model programmable pulse
delay generators by BNC (Berkeley Nucleonics Corporation).
 

Thanks.  Those are more $$$ than I'm interested in right now, but might be a
useful tool sometime in the future.

Another approach is to use a scope: trigger on one PPS and adjust the delay
(which might be negative) and sweep speed so you can see the other PPS
signal.  Maybe I'll play with this to see what sort of results I can get.


   

Lastly, there are cute little delay boxes (www.ebay.com/itm/150962422699)
that might work. Not sure how stable they are at the ns level. But it would
be fun to measure. If someone opens one of these please tell us if it's a
coil of wire, some kind of LRC filter delay, or if they use those Dallas
delay chips. Which is another solution for you -- google or eBay search for:
silicon delay line.
 

You can make a reasonable delay line by using the lumped circuit
approximation for the L and C for the appropriate impedance transmission
line.  I assume that's what's in the delay boxes.  I should try that
sometime.  Thanks for the reminder.

The delay chips I've looked at before used gate delays.  I think they were
Motorola rather than Dallas.  I just poked at a few Maxim data sheets.  I
didn't find out how they implemented the delays.

I think some of the clock recovery chips tune delays by tweaking the
threshold voltage.
   

I have been testing just using adjustable RC delays into a logic gate
to generate pretrigger pulses for sampling oscilloscopes.  Accuracy
depends on a complete reset of the capacitor and tracking between the
RC charge voltage and gate threshold voltage.  Worst cast jitter for
TTL has been in the 100s of picoseconds range because of supply
voltage sensitivity.  Different families of TTL and CMOS logic all
performed about the same.

Here is the jitter measurement that came from the RC logic gate delay
test:

http://www.banishedsouls.org/c2df3757f1/PG506/PDJ%20lolcat.jpg

Much better is to use a differential comparator or differential input
ECL which solves the threshold variation errors and a fast (it really
isn't all that fast) ramp generator with a precision reset.  The
differential input allows the ramp rate and threshold voltage to be
linked allowing ratiometric operation to reject power supply or
reference voltage variation and noise.

My next pretrigger generator is going the differential comparator or
differential ECL route with a fast ramp and precision reset.  I

Re: [time-nuts] Comparing PPS from 2 GPS units

2012-12-17 Thread Gerhard Hoffmann

Am 17.12.2012 19:56, schrieb David:



My next pretrigger generator is going the differential comparator or
differential ECL route with a fast ramp and precision reset.  I expect
jitter to be significantly better than 10s of picoseconds for delays
up to about 100 nanoseconds.  If I get down to 10 picoseconds of
jitter, I will be happy since I have no real way to measure much below
that.



That should be easy to do. I did a trigger pulse  delay for a
54750A scope. You need abt. 25 nsec delay to see the trigger event.
I did it with ooold 10K ECL I still had around and a few meters of
semi rigid cable. The semi rigid is surprisingly compact when wound
on a piece of plastic tube.

There was not much difference when watching the output of an
ADCMP580 comparator, via trigger delay or via internal trigger
and waiting a few clocks with the built-in delay.

The ADCMP580 is a fine chip, btw. You get a lot of speed for
not too much money. (digikey)

I will rebuild the trigger delay over xmas, this time with
CML to remove most of a systematic error in my scope setup.

CML is much more friendly than ECL/PECL from a probing
point of view. No need to carry Vtt to the scope and have
a problematic bias tee there, or shifting the supplies
until all happens to fit...

regards, Gerhard


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


Re: [time-nuts] Comparing PPS from 2 GPS units

2012-12-17 Thread Bob Camp
Hi

The nice thing about a spool of coax is that it's got a bit of thermal mass. It 
will average out a lot of minor temperature ups and downs. 

Bob

On Dec 17, 2012, at 4:34 PM, Hal Murray hmur...@megapathdsl.net wrote:

 
 li...@rtty.us said:
 If you are trying to set up say a 1 us delay, you will get ~ 50 ps per
 degree C in your delay. That's a lot . 
 
 A while ago, t...@leapsecond.com said:
 A long delay cable is fine too. If these are timing receivers you probably
 don't need more than 100 ns of delay, once you figure out which receiver is
 ahead of the other. The cable tempco is low enough not to worry about. 
 
 100 ns is 50-100 feet.  That's a reasonable length to work with.  But I was 
 curious about the temperature coefficient.  Google found this:
  http://www.hepl.hiroshima-u.ac.jp/phx/notes/cable/cable.html
 which says:
 # Belden 8240 (solid) shows a temperature coefficient of around 
 -0.252ps/m/deg in a temperature range between -20 and 30 deg. The coefficient 
 becomes steeper beyond 30 deg.
 # Belden 8219 (foam) shows a larger temperature coefficient of around -0.352 
 ps/m/deg than that of 8240 in the similar temperature range. The coefficient 
 becomes steeper beyond 30 deg, but less steeper than that of 8240.
 # Fujikura RG58-A/U shows the smallest temperature coefficient of around 
 -0.152 ps/m/deg, but in a narrow temperature range between -10 and 20 deg. 
 The coefficient beyond 20 deg is much steeper than the others.
 
 To pick round numbers, 30 meters and 3 C and 0.25 ps/m/C gives 25 ps.
 
 
 -- 
 These are my opinions.  I hate spam.
 
 
 
 
 ___
 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.


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


Re: [time-nuts] Comparing PPS from 2 GPS units

2012-12-17 Thread David
I wish there was an source for helically wound shielded differential
transmission line like the type used in later analog oscilloscopes.
The only place I know where to find it is oscilloscope part mules.

Essentially it was transmission line with a ridiculously low velocity
factor.  It is great for building instant digital delay lines up to
the low 10s of nanoseconds range in a small space.

On Mon, 17 Dec 2012 20:04:15 -0500, Bob Camp li...@rtty.us wrote:

Hi

The nice thing about a spool of coax is that it's got a bit of thermal mass. 
It will average out a lot of minor temperature ups and downs. 

Bob

On Dec 17, 2012, at 4:34 PM, Hal Murray hmur...@megapathdsl.net wrote:

 
 li...@rtty.us said:
 If you are trying to set up say a 1 us delay, you will get ~ 50 ps per
 degree C in your delay. That's a lot . 
 
 A while ago, t...@leapsecond.com said:
 A long delay cable is fine too. If these are timing receivers you probably
 don't need more than 100 ns of delay, once you figure out which receiver is
 ahead of the other. The cable tempco is low enough not to worry about. 
 
 100 ns is 50-100 feet.  That's a reasonable length to work with.  But I was 
 curious about the temperature coefficient.  Google found this:
  http://www.hepl.hiroshima-u.ac.jp/phx/notes/cable/cable.html
 which says:
 # Belden 8240 (solid) shows a temperature coefficient of around 
 -0.252ps/m/deg in a temperature range between -20 and 30 deg. The 
 coefficient 
 becomes steeper beyond 30 deg.
 # Belden 8219 (foam) shows a larger temperature coefficient of around -0.352 
 ps/m/deg than that of 8240 in the similar temperature range. The coefficient 
 becomes steeper beyond 30 deg, but less steeper than that of 8240.
 # Fujikura RG58-A/U shows the smallest temperature coefficient of around 
 -0.152 ps/m/deg, but in a narrow temperature range between -10 and 20 deg. 
 The coefficient beyond 20 deg is much steeper than the others.
 
 To pick round numbers, 30 meters and 3 C and 0.25 ps/m/C gives 25 ps.

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


Re: [time-nuts] Comparing PPS from 2 GPS units

2012-12-17 Thread Daniel Mendes


Like this?

http://www.ebay.com/itm/Tektronix-Delay-Line-for-475-Oscilloscope-New-/290824098279?pt=LH_DefaultDomain_0hash=item43b67791e7

Em 17/12/2012 23:39, David escreveu:

I wish there was an source for helically wound shielded differential
transmission line like the type used in later analog oscilloscopes.
The only place I know where to find it is oscilloscope part mules.

Essentially it was transmission line with a ridiculously low velocity
factor.  It is great for building instant digital delay lines up to
the low 10s of nanoseconds range in a small space.

On Mon, 17 Dec 2012 20:04:15 -0500, Bob Camp li...@rtty.us wrote:


Hi

The nice thing about a spool of coax is that it's got a bit of thermal mass. It 
will average out a lot of minor temperature ups and downs.

Bob

On Dec 17, 2012, at 4:34 PM, Hal Murray hmur...@megapathdsl.net wrote:


li...@rtty.us said:

If you are trying to set up say a 1 us delay, you will get ~ 50 ps per
degree C in your delay. That's a lot .

A while ago, t...@leapsecond.com said:

A long delay cable is fine too. If these are timing receivers you probably
don't need more than 100 ns of delay, once you figure out which receiver is
ahead of the other. The cable tempco is low enough not to worry about.

100 ns is 50-100 feet.  That's a reasonable length to work with.  But I was
curious about the temperature coefficient.  Google found this:
  http://www.hepl.hiroshima-u.ac.jp/phx/notes/cable/cable.html
which says:
# Belden 8240 (solid) shows a temperature coefficient of around
-0.252ps/m/deg in a temperature range between -20 and 30 deg. The coefficient
becomes steeper beyond 30 deg.
# Belden 8219 (foam) shows a larger temperature coefficient of around -0.352
ps/m/deg than that of 8240 in the similar temperature range. The coefficient
becomes steeper beyond 30 deg, but less steeper than that of 8240.
# Fujikura RG58-A/U shows the smallest temperature coefficient of around
-0.152 ps/m/deg, but in a narrow temperature range between -10 and 20 deg.
The coefficient beyond 20 deg is much steeper than the others.

To pick round numbers, 30 meters and 3 C and 0.25 ps/m/C gives 25 ps.

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



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


Re: [time-nuts] Comparing PPS from 2 GPS units

2012-12-17 Thread Bob Camp
Hi

At some point the whole get it onto the board / get it off the board thing 
becomes the main issue. Then it's easier to just make the delay line part of 
the PC layout.

Bob

On Dec 17, 2012, at 8:39 PM, David davidwh...@gmail.com wrote:

 I wish there was an source for helically wound shielded differential
 transmission line like the type used in later analog oscilloscopes.
 The only place I know where to find it is oscilloscope part mules.
 
 Essentially it was transmission line with a ridiculously low velocity
 factor.  It is great for building instant digital delay lines up to
 the low 10s of nanoseconds range in a small space.
 
 On Mon, 17 Dec 2012 20:04:15 -0500, Bob Camp li...@rtty.us wrote:
 
 Hi
 
 The nice thing about a spool of coax is that it's got a bit of thermal mass. 
 It will average out a lot of minor temperature ups and downs. 
 
 Bob
 
 On Dec 17, 2012, at 4:34 PM, Hal Murray hmur...@megapathdsl.net wrote:
 
 
 li...@rtty.us said:
 If you are trying to set up say a 1 us delay, you will get ~ 50 ps per
 degree C in your delay. That's a lot . 
 
 A while ago, t...@leapsecond.com said:
 A long delay cable is fine too. If these are timing receivers you probably
 don't need more than 100 ns of delay, once you figure out which receiver is
 ahead of the other. The cable tempco is low enough not to worry about. 
 
 100 ns is 50-100 feet.  That's a reasonable length to work with.  But I was 
 curious about the temperature coefficient.  Google found this:
 http://www.hepl.hiroshima-u.ac.jp/phx/notes/cable/cable.html
 which says:
 # Belden 8240 (solid) shows a temperature coefficient of around 
 -0.252ps/m/deg in a temperature range between -20 and 30 deg. The 
 coefficient 
 becomes steeper beyond 30 deg.
 # Belden 8219 (foam) shows a larger temperature coefficient of around 
 -0.352 
 ps/m/deg than that of 8240 in the similar temperature range. The 
 coefficient 
 becomes steeper beyond 30 deg, but less steeper than that of 8240.
 # Fujikura RG58-A/U shows the smallest temperature coefficient of around 
 -0.152 ps/m/deg, but in a narrow temperature range between -10 and 20 deg. 
 The coefficient beyond 20 deg is much steeper than the others.
 
 To pick round numbers, 30 meters and 3 C and 0.25 ps/m/C gives 25 ps.
 
 ___
 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.


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


Re: [time-nuts] Comparing PPS from 2 GPS units

2012-12-17 Thread David
That is the stuff but Tektronix had some with an even smaller
diameter.  It would be nice to have a new source as I would hate to
cannibalize oscilloscopes for it.

On Mon, 17 Dec 2012 23:43:21 -0200, Daniel Mendes dmend...@gmail.com
wrote:

Like this?

http://www.ebay.com/itm/Tektronix-Delay-Line-for-475-Oscilloscope-New-/290824098279?pt=LH_DefaultDomain_0hash=item43b67791e7

Em 17/12/2012 23:39, David escreveu:
 I wish there was an source for helically wound shielded differential
 transmission line like the type used in later analog oscilloscopes.
 The only place I know where to find it is oscilloscope part mules.

 Essentially it was transmission line with a ridiculously low velocity
 factor.  It is great for building instant digital delay lines up to
 the low 10s of nanoseconds range in a small space.

 On Mon, 17 Dec 2012 20:04:15 -0500, Bob Camp li...@rtty.us wrote:

 Hi

 The nice thing about a spool of coax is that it's got a bit of thermal 
 mass. It will average out a lot of minor temperature ups and downs.

 Bob

 On Dec 17, 2012, at 4:34 PM, Hal Murray hmur...@megapathdsl.net wrote:

 li...@rtty.us said:
 If you are trying to set up say a 1 us delay, you will get ~ 50 ps per
 degree C in your delay. That's a lot .
 A while ago, t...@leapsecond.com said:
 A long delay cable is fine too. If these are timing receivers you probably
 don't need more than 100 ns of delay, once you figure out which receiver 
 is
 ahead of the other. The cable tempco is low enough not to worry about.
 100 ns is 50-100 feet.  That's a reasonable length to work with.  But I was
 curious about the temperature coefficient.  Google found this:
   http://www.hepl.hiroshima-u.ac.jp/phx/notes/cable/cable.html
 which says:
 # Belden 8240 (solid) shows a temperature coefficient of around
 -0.252ps/m/deg in a temperature range between -20 and 30 deg. The 
 coefficient
 becomes steeper beyond 30 deg.
 # Belden 8219 (foam) shows a larger temperature coefficient of around 
 -0.352
 ps/m/deg than that of 8240 in the similar temperature range. The 
 coefficient
 becomes steeper beyond 30 deg, but less steeper than that of 8240.
 # Fujikura RG58-A/U shows the smallest temperature coefficient of around
 -0.152 ps/m/deg, but in a narrow temperature range between -10 and 20 deg.
 The coefficient beyond 20 deg is much steeper than the others.

 To pick round numbers, 30 meters and 3 C and 0.25 ps/m/C gives 25 ps.
 ___
 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.


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

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


Re: [time-nuts] Comparing PPS from 2 GPS units

2012-12-17 Thread David
I have seen the small diameter, about like RG-174, delay cable used
for patching PC boards after the fact.  That is how I know it exists.
:)

I just have not found a source for it.

On Mon, 17 Dec 2012 20:47:34 -0500, Bob Camp li...@rtty.us wrote:

Hi

At some point the whole get it onto the board / get it off the board thing 
becomes the main issue. Then it's easier to just make the delay line part of 
the PC layout.

Bob

On Dec 17, 2012, at 8:39 PM, David davidwh...@gmail.com wrote:

 I wish there was an source for helically wound shielded differential
 transmission line like the type used in later analog oscilloscopes.
 The only place I know where to find it is oscilloscope part mules.
 
 Essentially it was transmission line with a ridiculously low velocity
 factor.  It is great for building instant digital delay lines up to
 the low 10s of nanoseconds range in a small space.
 
 On Mon, 17 Dec 2012 20:04:15 -0500, Bob Camp li...@rtty.us wrote:
 
 Hi
 
 The nice thing about a spool of coax is that it's got a bit of thermal 
 mass. It will average out a lot of minor temperature ups and downs. 
 
 Bob
 
 On Dec 17, 2012, at 4:34 PM, Hal Murray hmur...@megapathdsl.net wrote:
 
 
 li...@rtty.us said:
 If you are trying to set up say a 1 us delay, you will get ~ 50 ps per
 degree C in your delay. That's a lot . 
 
 A while ago, t...@leapsecond.com said:
 A long delay cable is fine too. If these are timing receivers you probably
 don't need more than 100 ns of delay, once you figure out which receiver 
 is
 ahead of the other. The cable tempco is low enough not to worry about. 
 
 100 ns is 50-100 feet.  That's a reasonable length to work with.  But I 
 was 
 curious about the temperature coefficient.  Google found this:
 http://www.hepl.hiroshima-u.ac.jp/phx/notes/cable/cable.html
 which says:
 # Belden 8240 (solid) shows a temperature coefficient of around 
 -0.252ps/m/deg in a temperature range between -20 and 30 deg. The 
 coefficient 
 becomes steeper beyond 30 deg.
 # Belden 8219 (foam) shows a larger temperature coefficient of around 
 -0.352 
 ps/m/deg than that of 8240 in the similar temperature range. The 
 coefficient 
 becomes steeper beyond 30 deg, but less steeper than that of 8240.
 # Fujikura RG58-A/U shows the smallest temperature coefficient of around 
 -0.152 ps/m/deg, but in a narrow temperature range between -10 and 20 deg. 
 The coefficient beyond 20 deg is much steeper than the others.
 
 To pick round numbers, 30 meters and 3 C and 0.25 ps/m/C gives 25 ps.

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


Re: [time-nuts] Comparing PPS from 2 GPS units

2012-12-17 Thread Jim Lux

On 12/17/12 5:39 PM, David wrote:

I wish there was an source for helically wound shielded differential
transmission line like the type used in later analog oscilloscopes.
The only place I know where to find it is oscilloscope part mules.


You mean RG65
http://www.awcwire.com/ProductSpec.aspx?id=M17/34-RG65-Coaxial-Cable
or RG186
http://www.awcwire.com/ProductSpec.aspx?id=RG186-Coaxial-Cable


there's a place in Nevada (Reno, I think) that makes that stuff.. it's a 
helically loaded coaxial delay line.  I was looking for it a few years 
ago for a radar target simulator for Phoenix.


http://www.allenavionics.com/Info_Srv/SpecifyingDelayLinesPage2.htm


There's also a magnetostrictive delay line...


These days, for RF/Radar purposes, people either digitize or use SAW or 
BAW devices.




Essentially it was transmission line with a ridiculously low velocity
factor.  It is great for building instant digital delay lines up to
the low 10s of nanoseconds range in a small space.

On Mon, 17 Dec 2012 20:04:15 -0500, Bob Camp li...@rtty.us wrote:


Hi

The nice thing about a spool of coax is that it's got a bit of thermal mass. It 
will average out a lot of minor temperature ups and downs.

Bob

On Dec 17, 2012, at 4:34 PM, Hal Murray hmur...@megapathdsl.net wrote:



li...@rtty.us said:

If you are trying to set up say a 1 us delay, you will get ~ 50 ps per
degree C in your delay. That's a lot .


A while ago, t...@leapsecond.com said:

A long delay cable is fine too. If these are timing receivers you probably
don't need more than 100 ns of delay, once you figure out which receiver is
ahead of the other. The cable tempco is low enough not to worry about.


100 ns is 50-100 feet.  That's a reasonable length to work with.  But I was
curious about the temperature coefficient.  Google found this:
  http://www.hepl.hiroshima-u.ac.jp/phx/notes/cable/cable.html
which says:
# Belden 8240 (solid) shows a temperature coefficient of around
-0.252ps/m/deg in a temperature range between -20 and 30 deg. The coefficient
becomes steeper beyond 30 deg.
# Belden 8219 (foam) shows a larger temperature coefficient of around -0.352
ps/m/deg than that of 8240 in the similar temperature range. The coefficient
becomes steeper beyond 30 deg, but less steeper than that of 8240.
# Fujikura RG58-A/U shows the smallest temperature coefficient of around
-0.152 ps/m/deg, but in a narrow temperature range between -10 and 20 deg.
The coefficient beyond 20 deg is much steeper than the others.

To pick round numbers, 30 meters and 3 C and 0.25 ps/m/C gives 25 ps.


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




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


Re: [time-nuts] Comparing PPS from 2 GPS units

2012-12-17 Thread Hal Murray

jim...@earthlink.net said:
 You mean RG65 http://www.awcwire.com/ProductSpec.aspx?id=M17/
 34-RG65-Coaxial-Cable or RG186 http://www.awcwire.com/ProductSpec.aspx?id=RG1
 86-Coaxial-Cable 

Interesting stuff.  Thanks.

RG-65 says no longer available.  It also says:
  Coaxial Delay Line 0.15 uSec/ft
(Am I having troubles counting zeros, or is that seriously slow?)
  Nom. Imp. 950
  Vel. of Prop. 2 (no units)
  Cond. MaterialMagnet Wire Helix
(What is magnet wire, and what does helix mean and how does it effect 
coax?)


RG186 says:
  Shield Material   Magnet Wire   [What does that mean?]
  Nom. Imp. 1000

The cable on scope probes (at least fancy ones) has a tiny conductor.  I 
think that translates into high impedance.


-- 
These are my opinions.  I hate spam.




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


Re: [time-nuts] Comparing PPS from 2 GPS units

2012-12-17 Thread Jim Lux

On 12/17/12 9:40 PM, Hal Murray wrote:


jim...@earthlink.net said:

You mean RG65 http://www.awcwire.com/ProductSpec.aspx?id=M17/
34-RG65-Coaxial-Cable or RG186 http://www.awcwire.com/ProductSpec.aspx?id=RG1
86-Coaxial-Cable


Interesting stuff.  Thanks.

RG-65 says no longer available.  It also says:
   Coaxial Delay Line 0.15 uSec/ft
(Am I having troubles counting zeros, or is that seriously slow?)

Yes, seriously slow.. 150 ns/ft, vs 1ns/ft in free space..



   Nom. Imp.950
   Vel. of Prop.2 (no units)
   Cond. Material   Magnet Wire Helix
(What is magnet wire, and what does helix mean and how does it effect
coax?)


RG186 says:
   Shield Material  Magnet Wire   [What does that mean?]
   Nom. Imp.1000

The cable on scope probes (at least fancy ones) has a tiny conductor.  I
think that translates into high impedance.





No.. this stuff has a helically wound center conductor (so the L per 
unit length is very high).. impedance is sqrt (L/C) so the Z is high 
(1000 ohms).. prop velocity is 1/sqrt(LC), so big L means slow prop..


This stuff is incredibly lossy..

Some of it has the center conductor wound around a soft iron core wire 
to increase the inductance.









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


Re: [time-nuts] Comparing PPS from 2 GPS units

2012-12-17 Thread Bruce Griffiths

Hal Murray wrote:

jim...@earthlink.net said:
   

You mean RG65 http://www.awcwire.com/ProductSpec.aspx?id=M17/
34-RG65-Coaxial-Cable or RG186 http://www.awcwire.com/ProductSpec.aspx?id=RG1
86-Coaxial-Cable
 

Interesting stuff.  Thanks.

RG-65 says no longer available.  It also says:
   Coaxial Delay Line 0.15 uSec/ft
(Am I having troubles counting zeros, or is that seriously slow?)
   Nom. Imp.950
   Vel. of Prop.2 (no units)
   Cond. Material   Magnet Wire Helix
(What is magnet wire, and what does helix mean and how does it effect
coax?)

   

Magnet wire is enamelled wire (usually copper).

RG186 says:
   Shield Material  Magnet Wire   [What does that mean?]
   Nom. Imp.1000

The cable on scope probes (at least fancy ones) has a tiny conductor.  I
think that translates into high impedance.


   

Bruce

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


Re: [time-nuts] Comparing PPS from 2 GPS units

2012-12-17 Thread Hal Murray
Cond. MaterialMagnet Wire Helix
 (What is magnet wire, and what does helix mean and how does it effect
 coax?)

 Magnet wire is enamelled wire (usually copper).

I'm familiar with that usage, but I don't know why it's interesting in the 
context of coax.

I think the key idea is that the insulation is thin so you can get lots of 
turns/inch in a transformer.

I don't understand what a helix is in coax, or rather I don't appreciate 
the numbers.  I'd guess that the center conductor is constructed as a helix 
and that increases the inductance/meter by a whole lot, or something like 
that.  But isn't there a sqrt in there?


-- 
These are my opinions.  I hate spam.




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


Re: [time-nuts] Comparing PPS from 2 GPS units

2012-12-14 Thread SAIDJACK
Hi Tom,
 
but they could have achieved the same exact result by using scientific  
notation such as:
 
2.3E-010
 
or:
 
2.30E-010
 
or:
 
23E-011
 
to note the higher internal resolution in the later case.
 
I realize that one can easily parse these raw outputs, if one can  write 
python or C etc quickly, but I always find myself doing search and  replace: 
'* u' with '0E-06 in Word etc..
 
Also I don't happen to have a 1us long and accurate delay line, and I have  
to measure two pulses very close to each other, so I have no real choice in 
the  matter at this time. The jitter can be up to +/-1us, so I need that 
1us  delay to keep the values positive.
 
It would be good if the programmers would have added options to select the  
output format, and how to count time intervals close to zero when going  
negative. This should have been very easy to add in the counter's  software.
 
Maybe there is a Windows executable out there that can parse raw 53132A  
counter log files, recognize what the data is, and turn them into  proper 
scientific notation as well as handling the 0.999,999,999  second issue, that 
can then be directly read by programs such as  Excel, Plotter, etc?
 
Time-Nuts, anyone willing to write this for the benefit of all?
 
bye,
Said
 
 
In a message dated 12/13/2012 22:55:42 Pacific Standard Time,  
t...@leapsecond.com writes:

  Absolutely horrible to parse, these guys should have heard of scientific 
  
 notation. Not sure who programmed that unit, or if there is a  firmware  
 upgrade that gives proper numbers.

They are  more proper than you think. Do you remember one of the first 
lessons in  high-school science class: scientific measurements have both value 
and  precision. Thus 2.3 is not the same as 2.30 which is not the same as 
2.300.  Precision is important. When the 53132A adds * it conveys to the user 
that  precision is  missing.

/tvb


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


Re: [time-nuts] Comparing PPS from 2 GPS units

2012-12-14 Thread Hal Murray

saidj...@aol.com said:
 Time-Nuts, anyone willing to write this for the benefit of all? 

Does python run on Windows?  If so, give me samples of input data and what 
you want as output.


-- 
These are my opinions.  I hate spam.




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


Re: [time-nuts] Comparing PPS from 2 GPS units

2012-12-14 Thread Bill Dailey
Yes it does.

Sent from my iPad

On Dec 14, 2012, at 10:47 PM, Hal Murray hmur...@megapathdsl.net wrote:

 
 saidj...@aol.com said:
 Time-Nuts, anyone willing to write this for the benefit of all? 
 
 Does python run on Windows?  If so, give me samples of input data and what 
 you want as output.
 
 
 -- 
 These are my opinions.  I hate spam.
 
 
 
 
 ___
 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.

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


Re: [time-nuts] Comparing PPS from 2 GPS units

2012-12-14 Thread Jim Lux

On 12/14/12 8:47 PM, Hal Murray wrote:


saidj...@aol.com said:

Time-Nuts, anyone willing to write this for the benefit of all?


Does python run on Windows?  If so, give me samples of input data and what
you want as output.




Sure.. there's several flavors.. I use Active Python

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


[time-nuts] Comparing PPS from 2 GPS units

2012-12-13 Thread Hal Murray

Suppose I want to compare the PPS outputs of 2 GPS units.  The problem is 
that I don't know which one will happen first.

If I feed them into the start/stop inputs of a typical timer/freq box, I 
don't know which is which.  If I get them wrong, the answer will be 
0.99xx seconds rather than the -0.00xx that I want.

Is there a simple solution for this?

My straw man is to use the antenna cable delay setting to offset one of the 
PPS pulses a long way.

Plan B would be a physical delay unit.  But they are probably temperature 
sensitive, and I'm not setup to keep anything at a constant temperature.

Do any of the counter/timer boxes have a mode for this?  If so, is there a 
buzzword I've overlooked?


-- 
These are my opinions.  I hate spam.




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


Re: [time-nuts] Comparing PPS from 2 GPS units

2012-12-13 Thread lists
They make frequency difference meters. I never used one, but it seems to me a 
frequency difference meter would just use the two input signals to toggle up 
and down respectively on a counter, then display the result over a fixed period.

Would this do what you want?

--Original Message--
From: Hal Murray
Sender: time-nuts-boun...@febo.com
To: time-nuts@febo.com
ReplyTo: Discussion of precise time and frequency measurement
Subject: [time-nuts] Comparing PPS from 2 GPS units
Sent: Dec 13, 2012 1:57 AM


Suppose I want to compare the PPS outputs of 2 GPS units.  The problem is 
that I don't know which one will happen first.

If I feed them into the start/stop inputs of a typical timer/freq box, I 
don't know which is which.  If I get them wrong, the answer will be 
0.99xx seconds rather than the -0.00xx that I want.

Is there a simple solution for this?

My straw man is to use the antenna cable delay setting to offset one of the 
PPS pulses a long way.

Plan B would be a physical delay unit.  But they are probably temperature 
sensitive, and I'm not setup to keep anything at a constant temperature.

Do any of the counter/timer boxes have a mode for this?  If so, is there a 
buzzword I've overlooked?


-- 
These are my opinions.  I hate spam.




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

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


Re: [time-nuts] Comparing PPS from 2 GPS units

2012-12-13 Thread Bob Camp
Hi

The easy way to take care of the problem is to program one of them with a cable 
delay of around 500 ns. The GPS should not be outside +/-100 ns, so that's 
plenty of room for a start / stop to occur. Of course that assumes that the GPS 
has a programable cable delay setting. 

A 500 foot spool of cheap coax from the local big box store would be the other 
answer. You may need to fiddle a little with the terminations on it. Some of 
the cheap coax really isn't quite the impedance you would think from the 75 
ohm coax label on it ….

Bob

On Dec 13, 2012, at 4:57 AM, Hal Murray hmur...@megapathdsl.net wrote:

 
 Suppose I want to compare the PPS outputs of 2 GPS units.  The problem is 
 that I don't know which one will happen first.
 
 If I feed them into the start/stop inputs of a typical timer/freq box, I 
 don't know which is which.  If I get them wrong, the answer will be 
 0.99xx seconds rather than the -0.00xx that I want.
 
 Is there a simple solution for this?
 
 My straw man is to use the antenna cable delay setting to offset one of the 
 PPS pulses a long way.
 
 Plan B would be a physical delay unit.  But they are probably temperature 
 sensitive, and I'm not setup to keep anything at a constant temperature.
 
 Do any of the counter/timer boxes have a mode for this?  If so, is there a 
 buzzword I've overlooked?
 
 
 -- 
 These are my opinions.  I hate spam.
 
 
 
 
 ___
 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.


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


Re: [time-nuts] Comparing PPS from 2 GPS units

2012-12-13 Thread David
If the trailing edge of one of the pulses is reliable, you could
measure from the starting edge of one pulse to the trailing edge of
the other pulse.

It is not impossible to make an adjustable but accurate pulse delay
using a comparator or maybe a gate.  How accurate does your
measurement need to be?

Setting the cable delay like Bob suggests would be the easiest.

On Thu, 13 Dec 2012 01:57:34 -0800, Hal Murray
hmur...@megapathdsl.net wrote:

Suppose I want to compare the PPS outputs of 2 GPS units.  The problem is 
that I don't know which one will happen first.

If I feed them into the start/stop inputs of a typical timer/freq box, I 
don't know which is which.  If I get them wrong, the answer will be 
0.99xx seconds rather than the -0.00xx that I want.

Is there a simple solution for this?

My straw man is to use the antenna cable delay setting to offset one of the 
PPS pulses a long way.

Plan B would be a physical delay unit.  But they are probably temperature 
sensitive, and I'm not setup to keep anything at a constant temperature.

Do any of the counter/timer boxes have a mode for this?  If so, is there a 
buzzword I've overlooked?

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


Re: [time-nuts] Comparing PPS from 2 GPS units

2012-12-13 Thread Tom Van Baak
Hi Hal,

This happens to me too. The solution I usually use is to adjust the cable delay 
parameter. I find it convenient sometimes to advance the 1PPS by 1 microsecond. 
Kind of like at the tone, the time will be, rather than at the tone, the 
time was. Give up on at the tone, the time is.

The other solution is to use two (N) counters. Connect a clean (OCXO+divider is 
ok) 1 Hz signal to all start channel inputs. Each GPS 1PPS then goes to a stop 
channel; one per counter. From the raw data, you can then calculate all 
pair-wise combinations of N GPS receivers. The inaccuracy of the OCXO drops out 
of the calculations.

A third solution is to use a time-stamping counter (e.g., Pendulum CNT-91). In 
this case the order of events doesn't matter. You can calculate whatever you 
want from the raw timestamp data of all pulses received.

A long delay cable is fine too. If these are timing receivers you probably 
don't need more than 100 ns of delay, once you figure out which receiver is 
ahead of the other. The cable tempco is low enough not to worry about.

A fifth solution is to use a pulse delay generator like a DG535. I use this to 
create high-resolution early/late 1PPS sync pulses. They show up on eBay, but 
aren't cheap. For bargains, watch for older model programmable pulse delay 
generators by BNC (Berkeley Nucleonics Corporation).

Lastly, there are cute little delay boxes (www.ebay.com/itm/150962422699) that 
might work. Not sure how stable they are at the ns level. But it would be fun 
to measure. If someone opens one of these please tell us if it's a coil of 
wire, some kind of LRC filter delay, or if they use those Dallas delay chips. 
Which is another solution for you -- google or eBay search for: silicon delay 
line.

/tvb

- Original Message - 
From: Hal Murray hmur...@megapathdsl.net
To: time-nuts@febo.com
Sent: Thursday, December 13, 2012 1:57 AM
Subject: [time-nuts] Comparing PPS from 2 GPS units


 
 Suppose I want to compare the PPS outputs of 2 GPS units.  The problem is 
 that I don't know which one will happen first.
 
 If I feed them into the start/stop inputs of a typical timer/freq box, I 
 don't know which is which.  If I get them wrong, the answer will be 
 0.99xx seconds rather than the -0.00xx that I want.
 
 Is there a simple solution for this?
 
 My straw man is to use the antenna cable delay setting to offset one of the 
 PPS pulses a long way.
 
 Plan B would be a physical delay unit.  But they are probably temperature 
 sensitive, and I'm not setup to keep anything at a constant temperature.
 
 Do any of the counter/timer boxes have a mode for this?  If so, is there a 
 buzzword I've overlooked?
 
 
 -- 
 These are my opinions.  I hate spam.



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


Re: [time-nuts] Comparing PPS from 2 GPS units

2012-12-13 Thread Robert LaJeunesse
The indicated delay box is an unpowered device intended for timing composite 
video and fine-tuning for color burst phase match. As such they are analog in 
and out, require / expect defined source and load impedances (typically 75 
Ohms), are slightly lossy, and 100% passive. I suspect they are pure 
LC (ignoring the fact that all real inductors have some R as well).  I would 
expect stability in the low ns range, as more than a few degrees of color 
subcarrier shift shows up on NTSC.

Bob LaJeunesse



From: Tom Van Baak t...@leapsecond.com
To: Discussion of precise time and frequency measurement time-nuts@febo.com
Sent: Thu, December 13, 2012 12:56:17 PM
Subject: Re: [time-nuts] Comparing PPS from 2 GPS units

Lastly, there are cute little delay boxes (www.ebay.com/itm/150962422699) that 
might work. Not sure how stable they are at the ns level. But it would be fun 
to 
measure. If someone opens one of these please tell us if it's a coil of wire, 
some kind of LRC filter delay, or if they use those Dallas delay chips. Which 
is 
another solution for you -- google or eBay search for: silicon delay line.

/tvb
___
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.


Re: [time-nuts] Comparing PPS from 2 GPS units

2012-12-13 Thread timenuts
On Dec 13, 2012, at 4:57 AM, Hal Murray hmur...@megapathdsl.net wrote:
 Suppose I want to compare the PPS outputs of 2 GPS units.  The problem is
 that I don't know which one will happen first.

 If I feed them into the start/stop inputs of a typical timer/freq box, I
 don't know which is which.  If I get them wrong, the answer will be
 0.99xx seconds rather than the -0.00xx that I want.

 [...]
 
 Do any of the counter/timer boxes have a mode for this?  If so, is there
 a buzzword I've overlooked?

Counters like the Agilent 53230 actually WILL output negative delays 
in this case as long as the delta is still small. This is a quite useful 
feature in such cases...


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


Re: [time-nuts] Comparing PPS from 2 GPS units

2012-12-13 Thread David
On Fri, 14 Dec 2012 00:06:15 +0100, timen...@triplespark.net wrote:

On Dec 13, 2012, at 4:57 AM, Hal Murray hmur...@megapathdsl.net wrote:
 Suppose I want to compare the PPS outputs of 2 GPS units.  The problem is
 that I don't know which one will happen first.

 If I feed them into the start/stop inputs of a typical timer/freq box, I
 don't know which is which.  If I get them wrong, the answer will be
 0.99xx seconds rather than the -0.00xx that I want.

 [...]
 
 Do any of the counter/timer boxes have a mode for this?  If so, is there
 a buzzword I've overlooked?

Counters like the Agilent 53230 actually WILL output negative delays 
in this case as long as the delta is still small. This is a quite useful 
feature in such cases...

I was thinking along those lines but as far as I can tell from the
manual, the Racal Dana 1991 and 1992 only measure backwards to -2
nanoseconds which I have just verified with a 50 nanosecond rise time
pulse and fiddling with the A channel and B channel trigger levels in
common mode.  I remember seeing the same thing when using a 2
nanosecond calibrated delay coaxial patch cable.

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


Re: [time-nuts] Comparing PPS from 2 GPS units

2012-12-13 Thread SAIDJACK
Hi anonymous,
 
the 53132A only does that for a couple of nanoseconds. Then it jumps to a  
stupid value such as:
 
 
0.004 us
-0.002 us
0.999,999,993 s
 
It get's even better when the counter decides it doesn't have enough  
resolution in frequency mode:
 
2,3** u
 
Absolutely horrible to parse, these guys should have heard of scientific  
notation. Not sure who programmed that unit, or if there is a firmware  
upgrade that gives proper numbers.
 
bye,
Said
 
 
In a message dated 12/13/2012 15:07:50 Pacific Standard Time,  
timen...@triplespark.net writes:

Counters  like the Agilent 53230 actually WILL output negative delays 
in this case  as long as the delta is still small. This is a quite useful 
feature in  such cases...


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


Re: [time-nuts] Comparing PPS from 2 GPS units

2012-12-13 Thread Tom Van Baak
Hi Said,

 the 53132A only does that for a couple of nanoseconds. Then it jumps to a  
 stupid value such as:
 
 0.004 us
 -0.002 us
 0.999,999,993 s

It looks like you were measuring a 1PPS pulse that was very close to the 1PPS 
reference. As Hal noted when he started this thread, this is tricky.

But the results you're seeing from the 53132A are fine. The RS232 time interval 
output of these counters is either s for seconds or us for microseconds. 
These counters also use thousands separators. It's easy on the eye; trivial to 
parse too. Or you can use GPIB and get the data in other formats. I would not 
call it stupid.

What you're seeing in this case is phase wrap. Your small TI numbers just went 
over the boundary and now your tiny delta is 1.0 seconds minus a tiny delta; 
hence the 0.3 number. It's not the counter's fault. It's also an 
indication that you have missed one sample. The counter is doing the right 
thing. See previous posting on how to properly deal with this.

 It get's even better when the counter decides it doesn't have enough  
 resolution in frequency mode:
 
 2,3** u

This is actually one of my favorite features of the counter. It shows how 
experienced the hp engineers who designed it were. The * are correct; they 
are digit precision place holders. This counter, unlike most others, keeps 
track of resolution and precision and does not report digits that aren't valid.

 Absolutely horrible to parse, these guys should have heard of scientific  
 notation. Not sure who programmed that unit, or if there is a firmware  
 upgrade that gives proper numbers.

They are more proper than you think. Do you remember one of the first lessons 
in high-school science class: scientific measurements have both value and 
precision. Thus 2.3 is not the same as 2.30 which is not the same as 2.300. 
Precision is important. When the 53132A adds * it conveys to the user that 
precision is missing.

/tvb


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