time-nuts@lists.febo.com

Discussion of precise time and frequency measurement

View all threads

Re: [time-nuts] GPSDO Alternatives

E
EWKehren@aol.com
Thu, Dec 6, 2012 7:38 PM

Paul
I agree. That is my main frustration, lot of talk no results. The good part
of time nuts is that I have made some very good contacts that share my
interest  of actually building some things and results are great.
Remember the Loran simulator?

Bert Kehren

In a message dated 12/6/2012 1:17:14 P.M. Eastern Standard Time,
paulswedb@gmail.com writes:

Boy do I  have to agree. uProcs by the dozens and with all kinds of
counters
onboard.
I think it was Bob who said none of thats the  challenge.
It is the phase comparison method and a stable D/A converter and  reference.

From what I have seen and I could be dead wrong here the on  board uprocs

have D/As but the quality is simply OK.
The other comment  is that whoever writes the software gets to choose the
software and  everything else. Its actually not really democratic at all.
Cause we will  all use it if its reasonably good. ;-)
If I do it it will be basic! Though  it will run at very high speeds. Now
someone should be jumping in with  Forth real soon now.
Last tidbit the Rasberry is a pretty interesting  widget and there had been
a thread about a time server. Was looking forward  to the results. Nothing
ever  happened.
Regards
Paul
WB8TSL

On Thu, Dec 6, 2012 at 1:00 PM,  Bob Camp lists@rtty.us wrote:

Hi

It's a  rare microcontroller these days that does not come with a free
tool
chain. Same goes for the debugger. Most MCU lines have family  members

with

similarly low (or lower) prices and good availability.  They pretty much

all

either work with a crystal two caps and a  resistor. Most will run fine

with

none of the above on the internal  clock.

Bob

-----Original Message-----
From: time-nuts-bounces@febo.com [mailto:time-nuts-bounces@febo.com]  On
Behalf Of Dale J. Robertson
Sent: Thursday, December 06,  2012 12:45 PM
To: time-nuts@febo.com
Subject: Re: [time-nuts]  GPSDO Alternatives

Arduino is Dirt Cheap!
At it's  cheapest it is just an atmel AVR, a crystal, 2 caps and a

resistor

with the arduino bootloader programmed into it. Easily obtainable from
several sources for 5 bucks or so. All the code, toolchain etc. (the
ecosystem as it were) is free. it's real easy to put one together on a
piece

of perfboard. If you're gonna put the phase detector,  dividers etc.
together

anyway there's really no need  to clutter things up with some ginormous
commercial arduino  board.
Dale

-----Original Message-----
From:  Keenan Tims
Sent: Thursday, December 06, 2012 10:38 AM
To:  time-nuts@febo.com
Subject: Re: [time-nuts] GPSDO  Alternatives

As a lurker, I just want to chime in and say that  I for one would love
to see an open-source GPSDO implementation. There  are quite a few open
hardware designs out there, but as Bob suggests,  all the interesting
bits are tied up in the closed-source software  they run. And most of
them are no longer maintained, meaning it's  getting hard to find parts.

I've thought on designing a  hardware platform to support a GPSDO as
well, but don't have the  time-nut or control theory skills (or
equipment) necessary to make the  software any good. My hope at the time
was that a build it and they  will come approach would solve those
problems, but I haven't had time  to make that gamble.

As far as uP choice, Arduino's only  saving grace is the pool of existing
'developers' in the amateur  community for it - but that's perhaps a big
deal here. It's expensive,  doesn't include debug hardware, and is slow
with not many peripherals.  I'd second the STM32 ARM Cortex platform, or
suggest MSP430 if you  want to stay cheap and slow.

Keenan
VE7XEN

On 2012-12-06 1:28 AM, Chris Albertson wrote:

On Wed, Dec 5, 2012 at 2:50 PM, SAIDJACK@aol.com wrote:

If there is one thing I learned, it is that one is  never finished
improving
the software.  That is why we are time-nuts I guess.

This is  the reason I suggested using the Arduino.  It is so easy to
program
that MANY people will be able to contribute.  That  is my goal, a GPSDO
that
can be a "living project"  that is not dependent on one or a few

experts.

I'd like to see a  budget of well under $100, again so that more people

can

contribute and experiment.

A design that can evolve  will have just about any performance people

want.

So don't worry about if it is 1E-12 or 1E-15.  Just make it

transparent

and easy to understand and modify.


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.


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.

Paul I agree. That is my main frustration, lot of talk no results. The good part of time nuts is that I have made some very good contacts that share my interest of actually building some things and results are great. Remember the Loran simulator? Bert Kehren In a message dated 12/6/2012 1:17:14 P.M. Eastern Standard Time, paulswedb@gmail.com writes: Boy do I have to agree. uProcs by the dozens and with all kinds of counters onboard. I think it was Bob who said none of thats the challenge. It is the phase comparison method and a stable D/A converter and reference. >From what I have seen and I could be dead wrong here the on board uprocs have D/As but the quality is simply OK. The other comment is that whoever writes the software gets to choose the software and everything else. Its actually not really democratic at all. Cause we will all use it if its reasonably good. ;-) If I do it it will be basic! Though it will run at very high speeds. Now someone should be jumping in with Forth real soon now. Last tidbit the Rasberry is a pretty interesting widget and there had been a thread about a time server. Was looking forward to the results. Nothing ever happened. Regards Paul WB8TSL On Thu, Dec 6, 2012 at 1:00 PM, Bob Camp <lists@rtty.us> wrote: > Hi > > It's a rare microcontroller these days that does *not* come with a free > tool > chain. Same goes for the debugger. Most MCU lines have family members with > similarly low (or lower) prices and good availability. They pretty much all > either work with a crystal two caps and a resistor. Most will run fine with > none of the above on the internal clock. > > Bob > > -----Original Message----- > From: time-nuts-bounces@febo.com [mailto:time-nuts-bounces@febo.com] On > Behalf Of Dale J. Robertson > Sent: Thursday, December 06, 2012 12:45 PM > To: time-nuts@febo.com > Subject: Re: [time-nuts] GPSDO Alternatives > > Arduino is Dirt Cheap! > At it's cheapest it is just an atmel AVR, a crystal, 2 caps and a resistor > with the arduino bootloader programmed into it. Easily obtainable from > several sources for 5 bucks or so. All the code, toolchain etc. (the > ecosystem as it were) is free. it's real easy to put one together on a > piece > > of perfboard. If you're gonna put the phase detector, dividers etc. > together > > anyway there's really no need to clutter things up with some ginormous > commercial arduino board. > Dale > > -----Original Message----- > From: Keenan Tims > Sent: Thursday, December 06, 2012 10:38 AM > To: time-nuts@febo.com > Subject: Re: [time-nuts] GPSDO Alternatives > > As a lurker, I just want to chime in and say that I for one would love > to see an open-source GPSDO implementation. There are quite a few open > hardware designs out there, but as Bob suggests, all the interesting > bits are tied up in the closed-source software they run. And most of > them are no longer maintained, meaning it's getting hard to find parts. > > I've thought on designing a hardware platform to support a GPSDO as > well, but don't have the time-nut or control theory skills (or > equipment) necessary to make the software any good. My hope at the time > was that a build it and they will come approach would solve those > problems, but I haven't had time to make that gamble. > > As far as uP choice, Arduino's only saving grace is the pool of existing > 'developers' in the amateur community for it - but that's perhaps a big > deal here. It's expensive, doesn't include debug hardware, and is slow > with not many peripherals. I'd second the STM32 ARM Cortex platform, or > suggest MSP430 if you want to stay cheap and slow. > > Keenan > VE7XEN > > On 2012-12-06 1:28 AM, Chris Albertson wrote: > > On Wed, Dec 5, 2012 at 2:50 PM, <SAIDJACK@aol.com> wrote: > >> > >> If there is one thing I learned, it is that one is never finished > >> improving > >> the software. That is why we are time-nuts I guess. > >> > > This is the reason I suggested using the Arduino. It is so easy to > > program > > that MANY people will be able to contribute. That is my goal, a GPSDO > > that > > can be a "living project" that is not dependent on one or a few experts. > > I'd like to see a budget of well under $100, again so that more people > can > > contribute and experiment. > > > > A design that can evolve will have just about any performance people > want. > > So don't worry about if it is 1E-12 or 1E-15. Just make it transparent > > and easy to understand and modify. > > > > > _______________________________________________ > 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. > _______________________________________________ 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.
D
dlewis6767
Thu, Dec 6, 2012 8:21 PM

I'm excited, for sure.

I've got a whole box of goodies over here I bought full of the Arduino uP
and a ton of its 'shields'.  Been collecting, so-to-speak.

I just new I could use it for a, down-and-dirty GPSDO.  The Trimble Lassen
looks good down to 20ns UTC (I got two for $10); then add a cheap datum
ocxo; coupled that with the Arduino.  VoilĂ .

I can't wait, ..and you guys are reinforcing that just because its' cheap
won't mean it won't work.

-Don


From: EWKehren@aol.com
Sent: Thursday, December 06, 2012 1:38 PM
To: time-nuts@febo.com
Subject: Re: [time-nuts] GPSDO Alternatives

Paul
I agree. That is my main frustration, lot of talk no results. The good
part
of time nuts is that I have made some very good contacts that share my
interest  of actually building some things and results are great.
Remember the Loran simulator?

Bert Kehren

In a message dated 12/6/2012 1:17:14 P.M. Eastern Standard Time,
paulswedb@gmail.com writes:

Boy do I  have to agree. uProcs by the dozens and with all kinds of
counters
onboard.
I think it was Bob who said none of thats the  challenge.
It is the phase comparison method and a stable D/A converter and
reference.
From what I have seen and I could be dead wrong here the on  board uprocs
have D/As but the quality is simply OK.
The other comment  is that whoever writes the software gets to choose the
software and  everything else. Its actually not really democratic at all.
Cause we will  all use it if its reasonably good. ;-)
If I do it it will be basic! Though  it will run at very high speeds. Now
someone should be jumping in with  Forth real soon now.
Last tidbit the Rasberry is a pretty interesting  widget and there had
been
a thread about a time server. Was looking forward  to the results. Nothing
ever  happened.
Regards
Paul
WB8TSL

On Thu, Dec 6, 2012 at 1:00 PM,  Bob Camp lists@rtty.us wrote:

Hi

It's a  rare microcontroller these days that does not come with a free
tool
chain. Same goes for the debugger. Most MCU lines have family  members

with

similarly low (or lower) prices and good availability.  They pretty much

all

either work with a crystal two caps and a  resistor. Most will run fine

with

none of the above on the internal  clock.

Bob

-----Original Message-----
From: time-nuts-bounces@febo.com [mailto:time-nuts-bounces@febo.com]  On
Behalf Of Dale J. Robertson
Sent: Thursday, December 06,  2012 12:45 PM
To: time-nuts@febo.com
Subject: Re: [time-nuts]  GPSDO Alternatives

Arduino is Dirt Cheap!
At it's  cheapest it is just an atmel AVR, a crystal, 2 caps and a

resistor

with the arduino bootloader programmed into it. Easily obtainable from
several sources for 5 bucks or so. All the code, toolchain etc. (the
ecosystem as it were) is free. it's real easy to put one together on a
piece

of perfboard. If you're gonna put the phase detector,  dividers etc.
together

anyway there's really no need  to clutter things up with some ginormous
commercial arduino  board.
Dale

-----Original Message-----
From:  Keenan Tims
Sent: Thursday, December 06, 2012 10:38 AM
To:  time-nuts@febo.com
Subject: Re: [time-nuts] GPSDO  Alternatives

As a lurker, I just want to chime in and say that  I for one would love
to see an open-source GPSDO implementation. There  are quite a few open
hardware designs out there, but as Bob suggests,  all the interesting
bits are tied up in the closed-source software  they run. And most of
them are no longer maintained, meaning it's  getting hard to find parts.

I've thought on designing a  hardware platform to support a GPSDO as
well, but don't have the  time-nut or control theory skills (or
equipment) necessary to make the  software any good. My hope at the time
was that a build it and they  will come approach would solve those
problems, but I haven't had time  to make that gamble.

As far as uP choice, Arduino's only  saving grace is the pool of existing
'developers' in the amateur  community for it - but that's perhaps a big
deal here. It's expensive,  doesn't include debug hardware, and is slow
with not many peripherals.  I'd second the STM32 ARM Cortex platform, or
suggest MSP430 if you  want to stay cheap and slow.

Keenan
VE7XEN

On 2012-12-06 1:28 AM, Chris Albertson wrote:

On Wed, Dec 5, 2012 at 2:50 PM, SAIDJACK@aol.com wrote:

If there is one thing I learned, it is that one is  never finished
improving
the software.  That is why we are time-nuts I guess.

This is  the reason I suggested using the Arduino.  It is so easy to
program
that MANY people will be able to contribute.  That  is my goal, a GPSDO
that
can be a "living project"  that is not dependent on one or a few

experts.

I'd like to see a  budget of well under $100, again so that more people

can

contribute and experiment.

A design that can evolve  will have just about any performance people

want.

So don't worry about if it is 1E-12 or 1E-15.  Just make it

transparent

and easy to understand and modify.


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.


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.

I'm excited, for sure. I've got a whole box of goodies over here I bought full of the Arduino uP and a ton of its 'shields'. Been collecting, so-to-speak. I just new I could use it for a, down-and-dirty GPSDO. The Trimble Lassen looks good down to 20ns UTC (I got two for $10); then add a cheap datum ocxo; coupled that with the Arduino. VoilĂ . I can't wait, ..and you guys are reinforcing that just because its' cheap won't mean it won't work. -Don -------------------------------------------------- From: <EWKehren@aol.com> Sent: Thursday, December 06, 2012 1:38 PM To: <time-nuts@febo.com> Subject: Re: [time-nuts] GPSDO Alternatives > Paul > I agree. That is my main frustration, lot of talk no results. The good > part > of time nuts is that I have made some very good contacts that share my > interest of actually building some things and results are great. > Remember the Loran simulator? > > Bert Kehren > > > In a message dated 12/6/2012 1:17:14 P.M. Eastern Standard Time, > paulswedb@gmail.com writes: > > Boy do I have to agree. uProcs by the dozens and with all kinds of > counters > onboard. > I think it was Bob who said none of thats the challenge. > It is the phase comparison method and a stable D/A converter and > reference. > From what I have seen and I could be dead wrong here the on board uprocs > have D/As but the quality is simply OK. > The other comment is that whoever writes the software gets to choose the > software and everything else. Its actually not really democratic at all. > Cause we will all use it if its reasonably good. ;-) > If I do it it will be basic! Though it will run at very high speeds. Now > someone should be jumping in with Forth real soon now. > Last tidbit the Rasberry is a pretty interesting widget and there had > been > a thread about a time server. Was looking forward to the results. Nothing > ever happened. > Regards > Paul > WB8TSL > > On Thu, Dec 6, 2012 at 1:00 PM, Bob Camp <lists@rtty.us> wrote: > >> Hi >> >> It's a rare microcontroller these days that does *not* come with a free >> tool >> chain. Same goes for the debugger. Most MCU lines have family members > with >> similarly low (or lower) prices and good availability. They pretty much > all >> either work with a crystal two caps and a resistor. Most will run fine > with >> none of the above on the internal clock. >> >> Bob >> >> -----Original Message----- >> From: time-nuts-bounces@febo.com [mailto:time-nuts-bounces@febo.com] On >> Behalf Of Dale J. Robertson >> Sent: Thursday, December 06, 2012 12:45 PM >> To: time-nuts@febo.com >> Subject: Re: [time-nuts] GPSDO Alternatives >> >> Arduino is Dirt Cheap! >> At it's cheapest it is just an atmel AVR, a crystal, 2 caps and a > resistor >> with the arduino bootloader programmed into it. Easily obtainable from >> several sources for 5 bucks or so. All the code, toolchain etc. (the >> ecosystem as it were) is free. it's real easy to put one together on a >> piece >> >> of perfboard. If you're gonna put the phase detector, dividers etc. >> together >> >> anyway there's really no need to clutter things up with some ginormous >> commercial arduino board. >> Dale >> >> -----Original Message----- >> From: Keenan Tims >> Sent: Thursday, December 06, 2012 10:38 AM >> To: time-nuts@febo.com >> Subject: Re: [time-nuts] GPSDO Alternatives >> >> As a lurker, I just want to chime in and say that I for one would love >> to see an open-source GPSDO implementation. There are quite a few open >> hardware designs out there, but as Bob suggests, all the interesting >> bits are tied up in the closed-source software they run. And most of >> them are no longer maintained, meaning it's getting hard to find parts. >> >> I've thought on designing a hardware platform to support a GPSDO as >> well, but don't have the time-nut or control theory skills (or >> equipment) necessary to make the software any good. My hope at the time >> was that a build it and they will come approach would solve those >> problems, but I haven't had time to make that gamble. >> >> As far as uP choice, Arduino's only saving grace is the pool of existing >> 'developers' in the amateur community for it - but that's perhaps a big >> deal here. It's expensive, doesn't include debug hardware, and is slow >> with not many peripherals. I'd second the STM32 ARM Cortex platform, or >> suggest MSP430 if you want to stay cheap and slow. >> >> Keenan >> VE7XEN >> >> On 2012-12-06 1:28 AM, Chris Albertson wrote: >> > On Wed, Dec 5, 2012 at 2:50 PM, <SAIDJACK@aol.com> wrote: >> >> >> >> If there is one thing I learned, it is that one is never finished >> >> improving >> >> the software. That is why we are time-nuts I guess. >> >> >> > This is the reason I suggested using the Arduino. It is so easy to >> > program >> > that MANY people will be able to contribute. That is my goal, a GPSDO >> > that >> > can be a "living project" that is not dependent on one or a few > experts. >> > I'd like to see a budget of well under $100, again so that more people >> can >> > contribute and experiment. >> > >> > A design that can evolve will have just about any performance people >> want. >> > So don't worry about if it is 1E-12 or 1E-15. Just make it > transparent >> > and easy to understand and modify. >> > >> >> >> _______________________________________________ >> 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. >> > _______________________________________________ > 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.
CP
Charles P. Steinmetz
Thu, Dec 6, 2012 9:35 PM

Don wrote:

you guys are reinforcing that just because its' cheap won't mean it
won't work.

Of course it doesn't.  But keep in mind that "working" spans several
orders of magnitude in this area, and what one needs to design and
build depends on what degree of "working" one needs to support the
uses to which the finished standard will be put.  First, there is
performance during normal operation (good, continuous satellite
tracking) -- ADEV at all taus of interest, PN at all offsets of
interest, distortion and spurs, residual AM, stability over
temperature, PPS jitter, etc.  Then, there is performance with poor
satellite visibility, and finally performance in holdover (no
satellite visibility) for however long one needs it (if one needs it
at all, which many amateurs may not).  For some, there will be power
consumption issues.  There may also be issues of interfacing to
monitoring devices, both simple (e.g., LCD status displays) and
sophisticated (e.g., computer running Lady Heather or Z38xx).  Does
it need to work with existing programs, or is writing a new
monitoring program part of the project?  Then there are the
construction issues.  Does it need to be assembled entirely from
connectorized modules, no soldering required?  Or capable of being
thrown together on a scrap of perfboard?  Or will a PC card be
designed?  If so, can it use SMT parts?  How adaptable must it be,
particularly in accommodating different oscillators?  Does it need to
support rubidium oscillators as well as quartz?  Etc., etc., etc.

Thunderbolt and Z38xx commercial GPSDOs are plentiful and relatively
affordable, so they are natural benchmarks for any DIY project.

From my perspective, the most interesting development would be an
offer by someone with a very well equipped lab to test any DIY GPSDO
with a consistent protocol and publish the results.  That way, we
could all see how the various approaches compare with respect to the
characteristics that are most important to each of us.

Best regards,

Charles

Don wrote: >you guys are reinforcing that just because its' cheap won't mean it >won't work. Of course it doesn't. But keep in mind that "working" spans several orders of magnitude in this area, and what one needs to design and build depends on what degree of "working" one needs to support the uses to which the finished standard will be put. First, there is performance during normal operation (good, continuous satellite tracking) -- ADEV at all taus of interest, PN at all offsets of interest, distortion and spurs, residual AM, stability over temperature, PPS jitter, etc. Then, there is performance with poor satellite visibility, and finally performance in holdover (no satellite visibility) for however long one needs it (if one needs it at all, which many amateurs may not). For some, there will be power consumption issues. There may also be issues of interfacing to monitoring devices, both simple (e.g., LCD status displays) and sophisticated (e.g., computer running Lady Heather or Z38xx). Does it need to work with existing programs, or is writing a new monitoring program part of the project? Then there are the construction issues. Does it need to be assembled entirely from connectorized modules, no soldering required? Or capable of being thrown together on a scrap of perfboard? Or will a PC card be designed? If so, can it use SMT parts? How adaptable must it be, particularly in accommodating different oscillators? Does it need to support rubidium oscillators as well as quartz? Etc., etc., etc. Thunderbolt and Z38xx commercial GPSDOs are plentiful and relatively affordable, so they are natural benchmarks for any DIY project. From my perspective, the most interesting development would be an offer by someone with a very well equipped lab to test any DIY GPSDO with a consistent protocol and publish the results. That way, we could all see how the various approaches compare with respect to the characteristics that are most important to each of us. Best regards, Charles
BC
Bob Camp
Thu, Dec 6, 2012 9:56 PM

Hi

The single best thing about a TBolt is Lady Heather.

Consider how many years it's taken to get it to where it is today. Consider
how many people have worked extensively on it. It's a wonderful thing to
have available.

Could you make a homebrew gizmo look "just like a TBolt"? Sure you could. It
might well take you forever to do all the reverse engineering, validation,
and testing, but it can be done. I'd guess it would take less time to
re-write a version of LH from scratch....


Another thing to consider:

Z3801's got scrapped out, flooded the market, and the price went to "real
good". The supply dried up and prices climbed. This took years.

TBolts went through the same cycle. Again over a time period of many years.

In both cases you had a long time to look at them and make a decision about
weather you wanted one or not. It was never a "buy it this week or they are
gone" thing.

These aren't the only things that will ever get scrapped. There's something
somewhere in the world that's going to get junked. Some sort of GPSDO will
flood the market in the future. It will be around for many years at low
prices.

What ever you do as a project needs to be pretty good to survive the
competition. Otherwise it'll die before anybody ever sees one.

Bob

-----Original Message-----
From: time-nuts-bounces@febo.com [mailto:time-nuts-bounces@febo.com] On
Behalf Of Charles P. Steinmetz
Sent: Thursday, December 06, 2012 4:36 PM
To: Discussion of precise time and frequency measurement
Subject: Re: [time-nuts] GPSDO Alternatives

Don wrote:

you guys are reinforcing that just because its' cheap won't mean it
won't work.

Of course it doesn't.  But keep in mind that "working" spans several
orders of magnitude in this area, and what one needs to design and
build depends on what degree of "working" one needs to support the
uses to which the finished standard will be put.  First, there is
performance during normal operation (good, continuous satellite
tracking) -- ADEV at all taus of interest, PN at all offsets of
interest, distortion and spurs, residual AM, stability over
temperature, PPS jitter, etc.  Then, there is performance with poor
satellite visibility, and finally performance in holdover (no
satellite visibility) for however long one needs it (if one needs it
at all, which many amateurs may not).  For some, there will be power
consumption issues.  There may also be issues of interfacing to
monitoring devices, both simple (e.g., LCD status displays) and
sophisticated (e.g., computer running Lady Heather or Z38xx).  Does
it need to work with existing programs, or is writing a new
monitoring program part of the project?  Then there are the
construction issues.  Does it need to be assembled entirely from
connectorized modules, no soldering required?  Or capable of being
thrown together on a scrap of perfboard?  Or will a PC card be
designed?  If so, can it use SMT parts?  How adaptable must it be,
particularly in accommodating different oscillators?  Does it need to
support rubidium oscillators as well as quartz?  Etc., etc., etc.

Thunderbolt and Z38xx commercial GPSDOs are plentiful and relatively
affordable, so they are natural benchmarks for any DIY project.

From my perspective, the most interesting development would be an
offer by someone with a very well equipped lab to test any DIY GPSDO
with a consistent protocol and publish the results.  That way, we
could all see how the various approaches compare with respect to the
characteristics that are most important to each of us.

Best regards,

Charles


time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to
https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.

Hi The single best thing about a TBolt is Lady Heather. Consider how many years it's taken to get it to where it is today. Consider how many people have worked extensively on it. It's a wonderful thing to have available. Could you make a homebrew gizmo look "just like a TBolt"? Sure you could. It might well take you forever to do all the reverse engineering, validation, and testing, but it can be done. I'd guess it would take less time to re-write a version of LH from scratch.... ------ Another thing to consider: Z3801's got scrapped out, flooded the market, and the price went to "real good". The supply dried up and prices climbed. This took years. TBolts went through the same cycle. Again over a time period of many years. In both cases you had a long time to look at them and make a decision about weather you wanted one or not. It was never a "buy it this week or they are gone" thing. These aren't the only things that will ever get scrapped. There's something somewhere in the world that's going to get junked. Some sort of GPSDO will flood the market in the future. It will be around for many years at low prices. What ever you do as a project needs to be pretty good to survive the competition. Otherwise it'll die before anybody ever sees one. Bob -----Original Message----- From: time-nuts-bounces@febo.com [mailto:time-nuts-bounces@febo.com] On Behalf Of Charles P. Steinmetz Sent: Thursday, December 06, 2012 4:36 PM To: Discussion of precise time and frequency measurement Subject: Re: [time-nuts] GPSDO Alternatives Don wrote: >you guys are reinforcing that just because its' cheap won't mean it >won't work. Of course it doesn't. But keep in mind that "working" spans several orders of magnitude in this area, and what one needs to design and build depends on what degree of "working" one needs to support the uses to which the finished standard will be put. First, there is performance during normal operation (good, continuous satellite tracking) -- ADEV at all taus of interest, PN at all offsets of interest, distortion and spurs, residual AM, stability over temperature, PPS jitter, etc. Then, there is performance with poor satellite visibility, and finally performance in holdover (no satellite visibility) for however long one needs it (if one needs it at all, which many amateurs may not). For some, there will be power consumption issues. There may also be issues of interfacing to monitoring devices, both simple (e.g., LCD status displays) and sophisticated (e.g., computer running Lady Heather or Z38xx). Does it need to work with existing programs, or is writing a new monitoring program part of the project? Then there are the construction issues. Does it need to be assembled entirely from connectorized modules, no soldering required? Or capable of being thrown together on a scrap of perfboard? Or will a PC card be designed? If so, can it use SMT parts? How adaptable must it be, particularly in accommodating different oscillators? Does it need to support rubidium oscillators as well as quartz? Etc., etc., etc. Thunderbolt and Z38xx commercial GPSDOs are plentiful and relatively affordable, so they are natural benchmarks for any DIY project. From my perspective, the most interesting development would be an offer by someone with a very well equipped lab to test any DIY GPSDO with a consistent protocol and publish the results. That way, we could all see how the various approaches compare with respect to the characteristics that are most important to each of us. Best regards, Charles _______________________________________________ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
JA
John Ackermann N8UR
Thu, Dec 6, 2012 10:17 PM

On 12/6/2012 4:35 PM, Charles P. Steinmetz wrote:

From my perspective, the most interesting development would be an offer
by someone with a very well equipped lab to test any DIY GPSDO with a
consistent protocol and publish the results.  That way, we could all see
how the various approaches compare with respect to the characteristics
that are most important to each of us.

This is interesting, and I could bite -- for a limited definition of
"very well equipped."

What's really interesting, though, is the idea that collectively we
might develop some standard measurement protocols that would be
reproducible in a number of (amateur) labs.

John

On 12/6/2012 4:35 PM, Charles P. Steinmetz wrote: > From my perspective, the most interesting development would be an offer > by someone with a very well equipped lab to test any DIY GPSDO with a > consistent protocol and publish the results. That way, we could all see > how the various approaches compare with respect to the characteristics > that are most important to each of us. This is interesting, and I could bite -- for a limited definition of "very well equipped." What's *really* interesting, though, is the idea that collectively we might develop some standard measurement protocols that would be reproducible in a number of (amateur) labs. John
JL
Jim Lux
Fri, Dec 7, 2012 2:06 PM

On 12/6/12 1:56 PM, Bob Camp wrote:

Hi

The single best thing about a TBolt is Lady Heather.

Consider how many years it's taken to get it to where it is today. Consider
how many people have worked extensively on it. It's a wonderful thing to
have available.

Could you make a homebrew gizmo look "just like a TBolt"? Sure you could. It
might well take you forever to do all the reverse engineering, validation,
and testing, but it can be done. I'd guess it would take less time to
re-write a version of LH from scratch....

Of course, the process of experimenting and trying to duplicate the
Tbolt is fairly educational.  It touches a lot of interesting areas in
RF design and metrology, as well as software algorithms.  One might do
it for the same reason that someone builds a fusor in their garage.
There are easier ways to get neutrons, but building a fusor is a nice
combination of learning about high vacuum, high voltage, nuclear physics
and metrology, etc.

Both are a heck of a lot cheaper than building and flying a CubeSat, for
instance.

On 12/6/12 1:56 PM, Bob Camp wrote: > Hi > > The single best thing about a TBolt is Lady Heather. > > Consider how many years it's taken to get it to where it is today. Consider > how many people have worked extensively on it. It's a wonderful thing to > have available. > > Could you make a homebrew gizmo look "just like a TBolt"? Sure you could. It > might well take you forever to do all the reverse engineering, validation, > and testing, but it can be done. I'd guess it would take less time to > re-write a version of LH from scratch.... Of course, the process of experimenting and trying to duplicate the Tbolt is fairly educational. It touches a lot of interesting areas in RF design and metrology, as well as software algorithms. One might do it for the same reason that someone builds a fusor in their garage. There are easier ways to get neutrons, but building a fusor is a nice combination of learning about high vacuum, high voltage, nuclear physics and metrology, etc. Both are a heck of a lot cheaper than building and flying a CubeSat, for instance.
CP
Charles P. Steinmetz
Fri, Dec 7, 2012 10:50 PM

John wrote:

What's really interesting, though, is the idea that collectively
we might develop some standard measurement protocols that would be
reproducible in a number of (amateur) labs.

I agree, but I didn't dare to dream so large when I wrote:

From my perspective, the most interesting development would be an offer
by someone with a very well equipped lab to test any DIY GPSDO with a
consistent protocol and publish the results.  That way, we could all see
how the various approaches compare with respect to the characteristics
that are most important to each of us.

At bottom, any such testing requires (i) a comparison standard at
least as good (and hopefully at least somewhat better) than the DUT
at all taus and offsets (which may, in reality, be several standards,
each doing part of that job), (ii) a reliable TIC (and, potentially
usefully, frequency counter) that can exploit the stability of the
comparison standard, and (iii) the capability to process the raw data
to produce meaningful information.  [Additionally, to characterize
poor-signal behavior one would presumably use attenuators and a
well-situated antenna.  Some may not have good antenna sites to begin
with, and in any case, it would be hard to standardize the signal
strength between locations.]

My thoughts were (1) for many (most?) of the people who would want to
build a DIY GPSDO, it would likely be their first "really good"
standard, and therefore their best; and (2) the range of
TICs/frequency counters owned by the target base is so wide, and
covers such a large range of capabilities (to say nothing of whether
any given counter is in good repair and being used to best
advantage), that obtaining comparable results from one amateur lab to
another would be just as much if not more dependent on the individual
counters involved than on the GPSDOs under test.

However, that is no reason not to push forward with standardized
measurement protocols, which would focus all of us on what the
relevant desiderata are and how to measure them.

Best regards,

Charles

John wrote: >What's *really* interesting, though, is the idea that collectively >we might develop some standard measurement protocols that would be >reproducible in a number of (amateur) labs. I agree, but I didn't dare to dream so large when I wrote: >> From my perspective, the most interesting development would be an offer >>by someone with a very well equipped lab to test any DIY GPSDO with a >>consistent protocol and publish the results. That way, we could all see >>how the various approaches compare with respect to the characteristics >>that are most important to each of us. At bottom, any such testing requires (i) a comparison standard at least as good (and hopefully at least somewhat better) than the DUT at all taus and offsets (which may, in reality, be several standards, each doing part of that job), (ii) a reliable TIC (and, potentially usefully, frequency counter) that can exploit the stability of the comparison standard, and (iii) the capability to process the raw data to produce meaningful information. [Additionally, to characterize poor-signal behavior one would presumably use attenuators and a well-situated antenna. Some may not have good antenna sites to begin with, and in any case, it would be hard to standardize the signal strength between locations.] My thoughts were (1) for many (most?) of the people who would want to build a DIY GPSDO, it would likely be their first "really good" standard, and therefore their best; and (2) the range of TICs/frequency counters owned by the target base is so wide, and covers such a large range of capabilities (to say nothing of whether any given counter is in good repair and being used to best advantage), that obtaining comparable results from one amateur lab to another would be just as much if not more dependent on the individual counters involved than on the GPSDOs under test. However, that is no reason not to push forward with standardized measurement protocols, which would focus all of us on what the relevant desiderata are and how to measure them. Best regards, Charles
D
David
Sat, Dec 8, 2012 2:38 AM

On Fri, 07 Dec 2012 17:50:55 -0500, "Charles P. Steinmetz"
charles_steinmetz@lavabit.com wrote:

John wrote:

What's really interesting, though, is the idea that collectively
we might develop some standard measurement protocols that would be
reproducible in a number of (amateur) labs.

I agree, but I didn't dare to dream so large when I wrote:

From my perspective, the most interesting development would be an offer
by someone with a very well equipped lab to test any DIY GPSDO with a
consistent protocol and publish the results.  That way, we could all see
how the various approaches compare with respect to the characteristics
that are most important to each of us.

At bottom, any such testing requires (i) a comparison standard at
least as good (and hopefully at least somewhat better) than the DUT
at all taus and offsets (which may, in reality, be several standards,
each doing part of that job), (ii) a reliable TIC (and, potentially
usefully, frequency counter) that can exploit the stability of the
comparison standard, and (iii) the capability to process the raw data
to produce meaningful information.  [Additionally, to characterize
poor-signal behavior one would presumably use attenuators and a
well-situated antenna.  Some may not have good antenna sites to begin
with, and in any case, it would be hard to standardize the signal
strength between locations.]

My thoughts were (1) for many (most?) of the people who would want to
build a DIY GPSDO, it would likely be their first "really good"
standard, and therefore their best; and (2) the range of
TICs/frequency counters owned by the target base is so wide, and
covers such a large range of capabilities (to say nothing of whether
any given counter is in good repair and being used to best
advantage), that obtaining comparable results from one amateur lab to
another would be just as much if not more dependent on the individual
counters involved than on the GPSDOs under test.

However, that is no reason not to push forward with standardized
measurement protocols, which would focus all of us on what the
relevant desiderata are and how to measure them.

For myself:

  1. My current lack a comparison standard is the reason I would design
    and build a GPSDO.  At best I might buy a used rubidium oscillator at
    some point.  People talk about good deals on Thunderbolts but I have
    yet to see one.  It seems peak Thunderbolt passed before I was
    seriously looking.

  2. So far my best universal counter is a rebuilt Racal Dana 1992 with
    a TCXO but it lacks GPIB.  It might be easier and cheaper for me to
    duplicate my GPSDO phase detector and add a counter chain and trigger
    so it can make and report its own time interval measurements against a
    secondary asynchronous source but that would hardly be reproducible by
    a third party.

  3. I am less interested in this since I will be at the mercy of
    whatever timing GPS I use and my current antenna environment.

On Fri, 07 Dec 2012 17:50:55 -0500, "Charles P. Steinmetz" <charles_steinmetz@lavabit.com> wrote: >John wrote: > >>What's *really* interesting, though, is the idea that collectively >>we might develop some standard measurement protocols that would be >>reproducible in a number of (amateur) labs. > >I agree, but I didn't dare to dream so large when I wrote: > >>> From my perspective, the most interesting development would be an offer >>>by someone with a very well equipped lab to test any DIY GPSDO with a >>>consistent protocol and publish the results. That way, we could all see >>>how the various approaches compare with respect to the characteristics >>>that are most important to each of us. > >At bottom, any such testing requires (i) a comparison standard at >least as good (and hopefully at least somewhat better) than the DUT >at all taus and offsets (which may, in reality, be several standards, >each doing part of that job), (ii) a reliable TIC (and, potentially >usefully, frequency counter) that can exploit the stability of the >comparison standard, and (iii) the capability to process the raw data >to produce meaningful information. [Additionally, to characterize >poor-signal behavior one would presumably use attenuators and a >well-situated antenna. Some may not have good antenna sites to begin >with, and in any case, it would be hard to standardize the signal >strength between locations.] > >My thoughts were (1) for many (most?) of the people who would want to >build a DIY GPSDO, it would likely be their first "really good" >standard, and therefore their best; and (2) the range of >TICs/frequency counters owned by the target base is so wide, and >covers such a large range of capabilities (to say nothing of whether >any given counter is in good repair and being used to best >advantage), that obtaining comparable results from one amateur lab to >another would be just as much if not more dependent on the individual >counters involved than on the GPSDOs under test. > >However, that is no reason not to push forward with standardized >measurement protocols, which would focus all of us on what the >relevant desiderata are and how to measure them. For myself: 1. My current lack a comparison standard is the reason I would design and build a GPSDO. At best I might buy a used rubidium oscillator at some point. People talk about good deals on Thunderbolts but I have yet to see one. It seems peak Thunderbolt passed before I was seriously looking. 2. So far my best universal counter is a rebuilt Racal Dana 1992 with a TCXO but it lacks GPIB. It might be easier and cheaper for me to duplicate my GPSDO phase detector and add a counter chain and trigger so it can make and report its own time interval measurements against a secondary asynchronous source but that would hardly be reproducible by a third party. 3. I am less interested in this since I will be at the mercy of whatever timing GPS I use and my current antenna environment.