[time-nuts] TCVCXO Adjustment
artgodwin at gmail.com
Thu Apr 12 19:48:11 EDT 2018
Why not put a GPS receiver in it ? It won't always get a lock, but if it
gets accurate time every few weeks it can do the long-term tweaking someone
suggested in the watch thread (call in to the watch repair two weeks
apart). Except it can be done more or less EVERY two weeks.
I agree, a phone app is also a way to implement the time code generator.
But there's a lot to be said for a self-contained box for some jobs, and
the hassle of linking it to a phone or PC can be avoided for $10 on the
BOM. It doesn't even need to be a 'good' one - the TCXO is going to keep it
accurate enough over the months you can spend tracking the error.
On Thu, Apr 12, 2018 at 11:21 PM, Chris Caudle <chris at chriscaudle.org>
> On Tue, April 10, 2018 8:12 pm, Bob kb8tq wrote:
> > Since your typical PC does not have anything in it that is accurate to
> > ppm, you still need something as a reference to compare things to.
> > A GPS module or a GPSDO are probably the easiest things to get ahold of.
> Catching up on some of the time-nuts traffic, some of the messages about
> GPS API on phones make me wonder if a phone would not be a better option
> for a typical non-time-nut user than a PC. Setting up a GPS receiver with
> PPS output with a modern PC that does not have a RS232 port available can
> be pretty tricky (you would probably be starting with a bare circuit board
> rather than a nicely packaged GPS device for starters), so maybe a phone
> with GPS built in that lets you grab raw time data would be a better setup
> for a user with limited experience setting up time measurement systems.
> Or maybe a GPS Arduino shield and build a calibration system from a second
> Multiple possibilities that are hard to rule out until the hard
> performance limits are defined.
> Chris Caudle
> time-nuts mailing list -- time-nuts at febo.com
> To unsubscribe, go to https://www.febo.com/cgi-bin/
> and follow the instructions there.
More information about the time-nuts