Empathy List Archives

MR

Max Robinson

Thu, Oct 3, 2013 5:10 PM

Among my time nut toys is a Consumer grade GPS clock and a similar WWVB
clock. The WWVB clock consistently runs about 0.2 seconds ahead of the GPS
one. I know no one can say why without knowing the particulars of the two
clock's circuits. Just thought I'd post it for what it's worth.

Regards.

Max. K 4 O DS.

Email: max@maxsmusicplace.com

Transistor site http://www.funwithtransistors.net
Vacuum tube site: http://www.funwithtubes.net
Woodworking site
http://www.angelfire.com/electronic/funwithtubes/Woodworking/wwindex.html
Music site: http://www.maxsmusicplace.com

To subscribe to the fun with transistors group send an email to.
funwithtransistors-subscribe@yahoogroups.com

To subscribe to the fun with tubes group send an email to,
funwithtubes-subscribe@yahoogroups.com

To subscribe to the fun with wood group send a blank email to
funwithwood-subscribe@yahoogroups.com

Among my time nut toys is a Consumer grade GPS clock and a similar WWVB clock. The WWVB clock consistently runs about 0.2 seconds ahead of the GPS one. I know no one can say why without knowing the particulars of the two clock's circuits. Just thought I'd post it for what it's worth. Regards. Max. K 4 O DS. Email: max@maxsmusicplace.com Transistor site http://www.funwithtransistors.net Vacuum tube site: http://www.funwithtubes.net Woodworking site http://www.angelfire.com/electronic/funwithtubes/Woodworking/wwindex.html Music site: http://www.maxsmusicplace.com To subscribe to the fun with transistors group send an email to. funwithtransistors-subscribe@yahoogroups.com To subscribe to the fun with tubes group send an email to, funwithtubes-subscribe@yahoogroups.com To subscribe to the fun with wood group send a blank email to funwithwood-subscribe@yahoogroups.com

DJ

David J Taylor

Thu, Oct 3, 2013 6:22 PM

Among my time nut toys is a Consumer grade GPS clock and a similar WWVB
clock. The WWVB clock consistently runs about 0.2 seconds ahead of the GPS
one. I know no one can say why without knowing the particulars of the two
clock's circuits. Just thought I'd post it for what it's worth.

Regards.

Max. K 4 O DS.

---==

Max,

I see similar things here. I've always put it down to relatively poor
circuitry in the radio clock, which is why I built my NTP-controlled wall
clock!

http://www.satsignal.eu/raspberry-pi/DigitalClock.html

One radio clock is below. That particular MSF clock is actually not too
bad - visibly it's in sync with the NTP clock (which itself is within a few
microseconds of GPS time).

73,
David GM8ARV

SatSignal Software - Quality software written to your requirements
Web: http://www.satsignal.eu
Email: david-taylor@blueyonder.co.uk

Among my time nut toys is a Consumer grade GPS clock and a similar WWVB clock. The WWVB clock consistently runs about 0.2 seconds ahead of the GPS one. I know no one can say why without knowing the particulars of the two clock's circuits. Just thought I'd post it for what it's worth. Regards. Max. K 4 O DS. =================================== Max, I see similar things here. I've always put it down to relatively poor circuitry in the radio clock, which is why I built my NTP-controlled wall clock! http://www.satsignal.eu/raspberry-pi/DigitalClock.html One radio clock is below. That particular MSF clock is actually not too bad - visibly it's in sync with the NTP clock (which itself is within a few microseconds of GPS time). 73, David GM8ARV -- SatSignal Software - Quality software written to your requirements Web: http://www.satsignal.eu Email: david-taylor@blueyonder.co.uk

TK

Tom Knox

Thu, Oct 3, 2013 6:46 PM

It is all a matter of proper placement, now I know you are expecting a tirade on propagation delay and antenna placement and cable length. But actually my thought is to place them far enough apart with the WWV clock in front of your and your GPS at a 12-15 degree angle so it takes 0.2 second to look from one to the other.

Thomas Knox

From: david-taylor@blueyonder.co.uk
To: time-nuts@febo.com
Date: Thu, 3 Oct 2013 19:22:04 +0100
Subject: Re: [time-nuts] A man with two clocks...

Among my time nut toys is a Consumer grade GPS clock and a similar WWVB
clock. The WWVB clock consistently runs about 0.2 seconds ahead of the GPS
one. I know no one can say why without knowing the particulars of the two
clock's circuits. Just thought I'd post it for what it's worth.

Regards.

Max. K 4 O DS.

---==

Max,

I see similar things here. I've always put it down to relatively poor
circuitry in the radio clock, which is why I built my NTP-controlled wall
clock!

http://www.satsignal.eu/raspberry-pi/DigitalClock.html

One radio clock is below. That particular MSF clock is actually not too
bad - visibly it's in sync with the NTP clock (which itself is within a few
microseconds of GPS time).

73,
David GM8ARV

SatSignal Software - Quality software written to your requirements
Web: http://www.satsignal.eu
Email: david-taylor@blueyonder.co.uk

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.

It is all a matter of proper placement, now I know you are expecting a tirade on propagation delay and antenna placement and cable length. But actually my thought is to place them far enough apart with the WWV clock in front of your and your GPS at a 12-15 degree angle so it takes 0.2 second to look from one to the other. Thomas Knox > From: david-taylor@blueyonder.co.uk > To: time-nuts@febo.com > Date: Thu, 3 Oct 2013 19:22:04 +0100 > Subject: Re: [time-nuts] A man with two clocks... > > Among my time nut toys is a Consumer grade GPS clock and a similar WWVB > clock. The WWVB clock consistently runs about 0.2 seconds ahead of the GPS > one. I know no one can say why without knowing the particulars of the two > clock's circuits. Just thought I'd post it for what it's worth. > > Regards. > > Max. K 4 O DS. > =================================== > > Max, > > I see similar things here. I've always put it down to relatively poor > circuitry in the radio clock, which is why I built my NTP-controlled wall > clock! > > http://www.satsignal.eu/raspberry-pi/DigitalClock.html > > One radio clock is below. That particular MSF clock is actually not too > bad - visibly it's in sync with the NTP clock (which itself is within a few > microseconds of GPS time). > > 73, > David GM8ARV > -- > SatSignal Software - Quality software written to your requirements > Web: http://www.satsignal.eu > Email: david-taylor@blueyonder.co.uk > > _______________________________________________ > 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.

CG

Collins, Graham

Thu, Oct 3, 2013 7:06 PM

David,

Your raspberry-pi NTP clock is very cool.

I have put together something along the same line but is in reality just a network connected NTP disciplined clock display using an Arduino and a typical 16x2 LCD housed in a small project box.

The Arduino has a network shield and get's it power from a USB port although it could be powered by a battery or wall wart type of supply.

When it starts, the device attempts to get an IP address using DHCP. Once that is sorted it attempts to sync to my local GPS disciplined NTP server, then sets and displays it's time. It resyncs every some value between 15 and 30 minutes with the NTP server. If ever my local NTP server can't be found, it will attempt to sync to an outside NTP server on the internet. It keeps pretty good time, not "time nuts" level but is always within a few tenths of a second which is suitable for it's intended purpose.

Basic time keeping of the Arduino uses it's 16MHz crystal clock and there is some provision for adjusting in code which I have done to improve it's time keeping. I am toying with the idea of adding a 1 PPS input but just haven't gotten round to it yet.

All the bits and pieces of the code was copied from existing projects and libraries it being just a matter of finding the appropriate bits and pieces, putting them together and making changes in a few places to improve it's time keeping. It was a fun project to put together and has proven so useful in my lab that I will probably put together a couple more.

Cheers, Graham ve3gtc

---==

Max,

I see similar things here. I've always put it down to relatively poor circuitry in the radio clock, which is why I built my NTP-controlled wall clock!

http://www.satsignal.eu/raspberry-pi/DigitalClock.html

One radio clock is below. That particular MSF clock is actually not too bad - visibly it's in sync with the NTP clock (which itself is within a few microseconds of GPS time).

73,
David GM8ARV

SatSignal Software - Quality software written to your requirements
Web: http://www.satsignal.eu
Email: david-taylor@blueyonder.co.uk
.

David, Your raspberry-pi NTP clock is very cool. I have put together something along the same line but is in reality just a network connected NTP disciplined clock display using an Arduino and a typical 16x2 LCD housed in a small project box. The Arduino has a network shield and get's it power from a USB port although it could be powered by a battery or wall wart type of supply. When it starts, the device attempts to get an IP address using DHCP. Once that is sorted it attempts to sync to my local GPS disciplined NTP server, then sets and displays it's time. It resyncs every some value between 15 and 30 minutes with the NTP server. If ever my local NTP server can't be found, it will attempt to sync to an outside NTP server on the internet. It keeps pretty good time, not "time nuts" level but is always within a few tenths of a second which is suitable for it's intended purpose. Basic time keeping of the Arduino uses it's 16MHz crystal clock and there is some provision for adjusting in code which I have done to improve it's time keeping. I am toying with the idea of adding a 1 PPS input but just haven't gotten round to it yet. All the bits and pieces of the code was copied from existing projects and libraries it being just a matter of finding the appropriate bits and pieces, putting them together and making changes in a few places to improve it's time keeping. It was a fun project to put together and has proven so useful in my lab that I will probably put together a couple more. Cheers, Graham ve3gtc =================================== Max, I see similar things here. I've always put it down to relatively poor circuitry in the radio clock, which is why I built my NTP-controlled wall clock! http://www.satsignal.eu/raspberry-pi/DigitalClock.html One radio clock is below. That particular MSF clock is actually not too bad - visibly it's in sync with the NTP clock (which itself is within a few microseconds of GPS time). 73, David GM8ARV -- SatSignal Software - Quality software written to your requirements Web: http://www.satsignal.eu Email: david-taylor@blueyonder.co.uk .

PG

Phil Genera

Thu, Oct 3, 2013 10:43 PM

Is your code posted anywhere? I've been meaning to do roughly the same.

-- Phil
On Oct 3, 2013 12:07 PM, "Collins, Graham" CollinG@navcanada.ca wrote:

David,

Your raspberry-pi NTP clock is very cool.

I have put together something along the same line but is in reality just a
network connected NTP disciplined clock display using an Arduino and a
typical 16x2 LCD housed in a small project box.

The Arduino has a network shield and get's it power from a USB port
although it could be powered by a battery or wall wart type of supply.

When it starts, the device attempts to get an IP address using DHCP. Once
that is sorted it attempts to sync to my local GPS disciplined NTP server,
then sets and displays it's time. It resyncs every some value between 15
and 30 minutes with the NTP server. If ever my local NTP server can't be
found, it will attempt to sync to an outside NTP server on the internet. It
keeps pretty good time, not "time nuts" level but is always within a few
tenths of a second which is suitable for it's intended purpose.

Basic time keeping of the Arduino uses it's 16MHz crystal clock and there
is some provision for adjusting in code which I have done to improve it's
time keeping. I am toying with the idea of adding a 1 PPS input but just
haven't gotten round to it yet.

All the bits and pieces of the code was copied from existing projects and
libraries it being just a matter of finding the appropriate bits and
pieces, putting them together and making changes in a few places to improve
it's time keeping. It was a fun project to put together and has proven so
useful in my lab that I will probably put together a couple more.

Cheers, Graham ve3gtc

---==

Max,

I see similar things here. I've always put it down to relatively poor
circuitry in the radio clock, which is why I built my NTP-controlled wall
clock!

http://www.satsignal.eu/raspberry-pi/DigitalClock.html

One radio clock is below. That particular MSF clock is actually not too
bad - visibly it's in sync with the NTP clock (which itself is within a few
microseconds of GPS time).

73,
David GM8ARV

SatSignal Software - Quality software written to your requirements
Web: http://www.satsignal.eu
Email: david-taylor@blueyonder.co.uk
.

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.

Is your code posted anywhere? I've been meaning to do roughly the same. -- Phil On Oct 3, 2013 12:07 PM, "Collins, Graham" <CollinG@navcanada.ca> wrote: > David, > > Your raspberry-pi NTP clock is very cool. > > I have put together something along the same line but is in reality just a > network connected NTP disciplined clock display using an Arduino and a > typical 16x2 LCD housed in a small project box. > > The Arduino has a network shield and get's it power from a USB port > although it could be powered by a battery or wall wart type of supply. > > When it starts, the device attempts to get an IP address using DHCP. Once > that is sorted it attempts to sync to my local GPS disciplined NTP server, > then sets and displays it's time. It resyncs every some value between 15 > and 30 minutes with the NTP server. If ever my local NTP server can't be > found, it will attempt to sync to an outside NTP server on the internet. It > keeps pretty good time, not "time nuts" level but is always within a few > tenths of a second which is suitable for it's intended purpose. > > Basic time keeping of the Arduino uses it's 16MHz crystal clock and there > is some provision for adjusting in code which I have done to improve it's > time keeping. I am toying with the idea of adding a 1 PPS input but just > haven't gotten round to it yet. > > All the bits and pieces of the code was copied from existing projects and > libraries it being just a matter of finding the appropriate bits and > pieces, putting them together and making changes in a few places to improve > it's time keeping. It was a fun project to put together and has proven so > useful in my lab that I will probably put together a couple more. > > Cheers, Graham ve3gtc > > > =================================== > > Max, > > I see similar things here. I've always put it down to relatively poor > circuitry in the radio clock, which is why I built my NTP-controlled wall > clock! > > http://www.satsignal.eu/raspberry-pi/DigitalClock.html > > One radio clock is below. That particular MSF clock is actually not too > bad - visibly it's in sync with the NTP clock (which itself is within a few > microseconds of GPS time). > > 73, > David GM8ARV > -- > SatSignal Software - Quality software written to your requirements > Web: http://www.satsignal.eu > Email: david-taylor@blueyonder.co.uk > . > _______________________________________________ > 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. >

SW

Sarah White

Thu, Oct 3, 2013 10:45 PM

http://www.satsignal.eu/raspberry-pi/DigitalClock.html

third paragraph:

I've provided the source and binary files in >>>this<<< Zip archive, so
you can either run the program as-is, or modify it to suit your own
preferences.

On 10/3/2013 6:43 PM, Phil Genera wrote:

Is your code posted anywhere? I've been meaning to do roughly the same.

-- Phil
On Oct 3, 2013 12:07 PM, "Collins, Graham" CollinG@navcanada.ca wrote:

David,

Your raspberry-pi NTP clock is very cool.

I have put together something along the same line but is in reality just a
network connected NTP disciplined clock display using an Arduino and a
typical 16x2 LCD housed in a small project box.

The Arduino has a network shield and get's it power from a USB port
although it could be powered by a battery or wall wart type of supply.

When it starts, the device attempts to get an IP address using DHCP. Once
that is sorted it attempts to sync to my local GPS disciplined NTP server,
then sets and displays it's time. It resyncs every some value between 15
and 30 minutes with the NTP server. If ever my local NTP server can't be
found, it will attempt to sync to an outside NTP server on the internet. It
keeps pretty good time, not "time nuts" level but is always within a few
tenths of a second which is suitable for it's intended purpose.

Basic time keeping of the Arduino uses it's 16MHz crystal clock and there
is some provision for adjusting in code which I have done to improve it's
time keeping. I am toying with the idea of adding a 1 PPS input but just
haven't gotten round to it yet.

All the bits and pieces of the code was copied from existing projects and
libraries it being just a matter of finding the appropriate bits and
pieces, putting them together and making changes in a few places to improve
it's time keeping. It was a fun project to put together and has proven so
useful in my lab that I will probably put together a couple more.

Cheers, Graham ve3gtc

---==

Max,

I see similar things here. I've always put it down to relatively poor
circuitry in the radio clock, which is why I built my NTP-controlled wall
clock!

http://www.satsignal.eu/raspberry-pi/DigitalClock.html

One radio clock is below. That particular MSF clock is actually not too
bad - visibly it's in sync with the NTP clock (which itself is within a few
microseconds of GPS time).

73,
David GM8ARV

SatSignal Software - Quality software written to your requirements
Web: http://www.satsignal.eu
Email: david-taylor@blueyonder.co.uk
.

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.

http://www.satsignal.eu/raspberry-pi/DigitalClock.html third paragraph: I've provided the source and binary files in >>>this<<< Zip archive, so you can either run the program as-is, or modify it to suit your own preferences. On 10/3/2013 6:43 PM, Phil Genera wrote: > Is your code posted anywhere? I've been meaning to do roughly the same. > > -- Phil > On Oct 3, 2013 12:07 PM, "Collins, Graham" <CollinG@navcanada.ca> wrote: > >> David, >> >> Your raspberry-pi NTP clock is very cool. >> >> I have put together something along the same line but is in reality just a >> network connected NTP disciplined clock display using an Arduino and a >> typical 16x2 LCD housed in a small project box. >> >> The Arduino has a network shield and get's it power from a USB port >> although it could be powered by a battery or wall wart type of supply. >> >> When it starts, the device attempts to get an IP address using DHCP. Once >> that is sorted it attempts to sync to my local GPS disciplined NTP server, >> then sets and displays it's time. It resyncs every some value between 15 >> and 30 minutes with the NTP server. If ever my local NTP server can't be >> found, it will attempt to sync to an outside NTP server on the internet. It >> keeps pretty good time, not "time nuts" level but is always within a few >> tenths of a second which is suitable for it's intended purpose. >> >> Basic time keeping of the Arduino uses it's 16MHz crystal clock and there >> is some provision for adjusting in code which I have done to improve it's >> time keeping. I am toying with the idea of adding a 1 PPS input but just >> haven't gotten round to it yet. >> >> All the bits and pieces of the code was copied from existing projects and >> libraries it being just a matter of finding the appropriate bits and >> pieces, putting them together and making changes in a few places to improve >> it's time keeping. It was a fun project to put together and has proven so >> useful in my lab that I will probably put together a couple more. >> >> Cheers, Graham ve3gtc >> >> >> =================================== >> >> Max, >> >> I see similar things here. I've always put it down to relatively poor >> circuitry in the radio clock, which is why I built my NTP-controlled wall >> clock! >> >> http://www.satsignal.eu/raspberry-pi/DigitalClock.html >> >> One radio clock is below. That particular MSF clock is actually not too >> bad - visibly it's in sync with the NTP clock (which itself is within a few >> microseconds of GPS time). >> >> 73, >> David GM8ARV >> -- >> SatSignal Software - Quality software written to your requirements >> Web: http://www.satsignal.eu >> Email: david-taylor@blueyonder.co.uk >> . >> _______________________________________________ >> 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. >

PG

Phil Genera

Thu, Oct 3, 2013 11:05 PM

Sorry, I was looking for Graham's Arduino code; clearly my comprehension
and clarity limited on the phone.
On Oct 3, 2013 3:53 PM, "Sarah White" kuzetsa@gmail.com wrote:

http://www.satsignal.eu/raspberry-pi/DigitalClock.html

third paragraph:

I've provided the source and binary files in >>>this<<< Zip archive, so
you can either run the program as-is, or modify it to suit your own
preferences.

On 10/3/2013 6:43 PM, Phil Genera wrote:

Is your code posted anywhere? I've been meaning to do roughly the same.

-- Phil
On Oct 3, 2013 12:07 PM, "Collins, Graham" CollinG@navcanada.ca wrote:

David,

Your raspberry-pi NTP clock is very cool.

I have put together something along the same line but is in reality

just a

network connected NTP disciplined clock display using an Arduino and a
typical 16x2 LCD housed in a small project box.

The Arduino has a network shield and get's it power from a USB port
although it could be powered by a battery or wall wart type of supply.

When it starts, the device attempts to get an IP address using DHCP.

Once

that is sorted it attempts to sync to my local GPS disciplined NTP

server,

then sets and displays it's time. It resyncs every some value between 15
and 30 minutes with the NTP server. If ever my local NTP server can't be
found, it will attempt to sync to an outside NTP server on the

internet. It

keeps pretty good time, not "time nuts" level but is always within a few
tenths of a second which is suitable for it's intended purpose.

Basic time keeping of the Arduino uses it's 16MHz crystal clock and

there

is some provision for adjusting in code which I have done to improve

it's

time keeping. I am toying with the idea of adding a 1 PPS input but just
haven't gotten round to it yet.

All the bits and pieces of the code was copied from existing projects

and

libraries it being just a matter of finding the appropriate bits and
pieces, putting them together and making changes in a few places to

improve

it's time keeping. It was a fun project to put together and has proven

so

useful in my lab that I will probably put together a couple more.

Cheers, Graham ve3gtc

---==

Max,

I see similar things here. I've always put it down to relatively poor
circuitry in the radio clock, which is why I built my NTP-controlled

wall

clock!

http://www.satsignal.eu/raspberry-pi/DigitalClock.html

One radio clock is below. That particular MSF clock is actually not too
bad - visibly it's in sync with the NTP clock (which itself is within a

few

microseconds of GPS time).

73,
David GM8ARV

SatSignal Software - Quality software written to your requirements
Web: http://www.satsignal.eu
Email: david-taylor@blueyonder.co.uk
.

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.

Sorry, I was looking for Graham's Arduino code; clearly my comprehension and clarity limited on the phone. On Oct 3, 2013 3:53 PM, "Sarah White" <kuzetsa@gmail.com> wrote: > http://www.satsignal.eu/raspberry-pi/DigitalClock.html > > third paragraph: > > I've provided the source and binary files in >>>this<<< Zip archive, so > you can either run the program as-is, or modify it to suit your own > preferences. > > On 10/3/2013 6:43 PM, Phil Genera wrote: > > Is your code posted anywhere? I've been meaning to do roughly the same. > > > > -- Phil > > On Oct 3, 2013 12:07 PM, "Collins, Graham" <CollinG@navcanada.ca> wrote: > > > >> David, > >> > >> Your raspberry-pi NTP clock is very cool. > >> > >> I have put together something along the same line but is in reality > just a > >> network connected NTP disciplined clock display using an Arduino and a > >> typical 16x2 LCD housed in a small project box. > >> > >> The Arduino has a network shield and get's it power from a USB port > >> although it could be powered by a battery or wall wart type of supply. > >> > >> When it starts, the device attempts to get an IP address using DHCP. > Once > >> that is sorted it attempts to sync to my local GPS disciplined NTP > server, > >> then sets and displays it's time. It resyncs every some value between 15 > >> and 30 minutes with the NTP server. If ever my local NTP server can't be > >> found, it will attempt to sync to an outside NTP server on the > internet. It > >> keeps pretty good time, not "time nuts" level but is always within a few > >> tenths of a second which is suitable for it's intended purpose. > >> > >> Basic time keeping of the Arduino uses it's 16MHz crystal clock and > there > >> is some provision for adjusting in code which I have done to improve > it's > >> time keeping. I am toying with the idea of adding a 1 PPS input but just > >> haven't gotten round to it yet. > >> > >> All the bits and pieces of the code was copied from existing projects > and > >> libraries it being just a matter of finding the appropriate bits and > >> pieces, putting them together and making changes in a few places to > improve > >> it's time keeping. It was a fun project to put together and has proven > so > >> useful in my lab that I will probably put together a couple more. > >> > >> Cheers, Graham ve3gtc > >> > >> > >> =================================== > >> > >> Max, > >> > >> I see similar things here. I've always put it down to relatively poor > >> circuitry in the radio clock, which is why I built my NTP-controlled > wall > >> clock! > >> > >> http://www.satsignal.eu/raspberry-pi/DigitalClock.html > >> > >> One radio clock is below. That particular MSF clock is actually not too > >> bad - visibly it's in sync with the NTP clock (which itself is within a > few > >> microseconds of GPS time). > >> > >> 73, > >> David GM8ARV > >> -- > >> SatSignal Software - Quality software written to your requirements > >> Web: http://www.satsignal.eu > >> Email: david-taylor@blueyonder.co.uk > >> . > >> _______________________________________________ > >> 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. >

CG

Collins, Graham

Fri, Oct 4, 2013 11:03 AM

No, my code is not posted anywhere but I would be glad to email it to anyone interested.

Cheers, Graham

-----Original Message-----
From: time-nuts-bounces@febo.com [mailto:time-nuts-bounces@febo.com] On Behalf Of Phil Genera
Sent: October-03-13 6:44 PM
To: Discussion of precise time and frequency measurement
Subject: Re: [time-nuts] A man with two clocks...

Is your code posted anywhere? I've been meaning to do roughly the same.

-- Phil
On Oct 3, 2013 12:07 PM, "Collins, Graham" CollinG@navcanada.ca wrote:

David,

Your raspberry-pi NTP clock is very cool.

I have put together something along the same line but is in reality
just a network connected NTP disciplined clock display using an
Arduino and a typical 16x2 LCD housed in a small project box.

The Arduino has a network shield and get's it power from a USB port
although it could be powered by a battery or wall wart type of supply.

When it starts, the device attempts to get an IP address using DHCP.
Once that is sorted it attempts to sync to my local GPS disciplined
NTP server, then sets and displays it's time. It resyncs every some
value between 15 and 30 minutes with the NTP server. If ever my local
NTP server can't be found, it will attempt to sync to an outside NTP
server on the internet. It keeps pretty good time, not "time nuts"
level but is always within a few tenths of a second which is suitable for it's intended purpose.

Basic time keeping of the Arduino uses it's 16MHz crystal clock and
there is some provision for adjusting in code which I have done to
improve it's time keeping. I am toying with the idea of adding a 1 PPS
input but just haven't gotten round to it yet.

All the bits and pieces of the code was copied from existing projects
and libraries it being just a matter of finding the appropriate bits
and pieces, putting them together and making changes in a few places
to improve it's time keeping. It was a fun project to put together and
has proven so useful in my lab that I will probably put together a couple more.

Cheers, Graham ve3gtc

---==

Max,

I see similar things here. I've always put it down to relatively poor
circuitry in the radio clock, which is why I built my NTP-controlled
wall clock!

http://www.satsignal.eu/raspberry-pi/DigitalClock.html

One radio clock is below. That particular MSF clock is actually not
too bad - visibly it's in sync with the NTP clock (which itself is
within a few microseconds of GPS time).

73,
David GM8ARV

SatSignal Software - Quality software written to your requirements
Web: http://www.satsignal.eu
Email: david-taylor@blueyonder.co.uk
.

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.

No, my code is not posted anywhere but I would be glad to email it to anyone interested. Cheers, Graham -----Original Message----- From: time-nuts-bounces@febo.com [mailto:time-nuts-bounces@febo.com] On Behalf Of Phil Genera Sent: October-03-13 6:44 PM To: Discussion of precise time and frequency measurement Subject: Re: [time-nuts] A man with two clocks... Is your code posted anywhere? I've been meaning to do roughly the same. -- Phil On Oct 3, 2013 12:07 PM, "Collins, Graham" <CollinG@navcanada.ca> wrote: > David, > > Your raspberry-pi NTP clock is very cool. > > I have put together something along the same line but is in reality > just a network connected NTP disciplined clock display using an > Arduino and a typical 16x2 LCD housed in a small project box. > > The Arduino has a network shield and get's it power from a USB port > although it could be powered by a battery or wall wart type of supply. > > When it starts, the device attempts to get an IP address using DHCP. > Once that is sorted it attempts to sync to my local GPS disciplined > NTP server, then sets and displays it's time. It resyncs every some > value between 15 and 30 minutes with the NTP server. If ever my local > NTP server can't be found, it will attempt to sync to an outside NTP > server on the internet. It keeps pretty good time, not "time nuts" > level but is always within a few tenths of a second which is suitable for it's intended purpose. > > Basic time keeping of the Arduino uses it's 16MHz crystal clock and > there is some provision for adjusting in code which I have done to > improve it's time keeping. I am toying with the idea of adding a 1 PPS > input but just haven't gotten round to it yet. > > All the bits and pieces of the code was copied from existing projects > and libraries it being just a matter of finding the appropriate bits > and pieces, putting them together and making changes in a few places > to improve it's time keeping. It was a fun project to put together and > has proven so useful in my lab that I will probably put together a couple more. > > Cheers, Graham ve3gtc > > > =================================== > > Max, > > I see similar things here. I've always put it down to relatively poor > circuitry in the radio clock, which is why I built my NTP-controlled > wall clock! > > http://www.satsignal.eu/raspberry-pi/DigitalClock.html > > One radio clock is below. That particular MSF clock is actually not > too bad - visibly it's in sync with the NTP clock (which itself is > within a few microseconds of GPS time). > > 73, > David GM8ARV > -- > SatSignal Software - Quality software written to your requirements > Web: http://www.satsignal.eu > Email: david-taylor@blueyonder.co.uk > . > _______________________________________________ > 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.

DJ

Didier Juges

Fri, Oct 4, 2013 11:57 AM

Max,

This is a very interesting project and well documented, thank you!

Didier KO4BB

David J Taylor david-taylor@blueyonder.co.uk wrote:

Among my time nut toys is a Consumer grade GPS clock and a similar WWVB
clock. The WWVB clock consistently runs about 0.2 seconds ahead of the
GPS
one. I know no one can say why without knowing the particulars of the
two
clock's circuits. Just thought I'd post it for what it's worth.

Regards.

Max. K 4 O DS.

---==

Max,

I see similar things here. I've always put it down to relatively poor
circuitry in the radio clock, which is why I built my NTP-controlled
wall
clock!

http://www.satsignal.eu/raspberry-pi/DigitalClock.html

One radio clock is below. That particular MSF clock is actually not
too
bad - visibly it's in sync with the NTP clock (which itself is within a
few
microseconds of GPS time).

73,
David GM8ARV

SatSignal Software - Quality software written to your requirements
Web: http://www.satsignal.eu
Email: david-taylor@blueyonder.co.uk

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.

--
Sent from my Motorola Droid Razr 4G LTE wireless tracker while I do other things.

Max, This is a very interesting project and well documented, thank you! Didier KO4BB David J Taylor <david-taylor@blueyonder.co.uk> wrote: >Among my time nut toys is a Consumer grade GPS clock and a similar WWVB >clock. The WWVB clock consistently runs about 0.2 seconds ahead of the >GPS >one. I know no one can say why without knowing the particulars of the >two >clock's circuits. Just thought I'd post it for what it's worth. > >Regards. > >Max. K 4 O DS. >=================================== > >Max, > >I see similar things here. I've always put it down to relatively poor >circuitry in the radio clock, which is why I built my NTP-controlled >wall >clock! > > http://www.satsignal.eu/raspberry-pi/DigitalClock.html > >One radio clock is below. That particular MSF clock is actually not >too >bad - visibly it's in sync with the NTP clock (which itself is within a >few >microseconds of GPS time). > >73, >David GM8ARV >-- >SatSignal Software - Quality software written to your requirements >Web: http://www.satsignal.eu >Email: david-taylor@blueyonder.co.uk > >_______________________________________________ >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. -- Sent from my Motorola Droid Razr 4G LTE wireless tracker while I do other things.

MR

Max Robinson

Sat, Oct 5, 2013 12:57 AM

Still laughing. Actually I did it aurally. The GPS clock announces the
time on the hour with a series of beeps similar to the old BBC time and the
WWVB clock has an alarm which I can set to sound on the hour. The time
interval is an estimation. Someday I will use a microphone connected to a
storage oscilloscope to figure out what the difference is.

Regards.

Max. K 4 O DS.

Email: max@maxsmusicplace.com

Transistor site http://www.funwithtransistors.net
Vacuum tube site: http://www.funwithtubes.net
Woodworking site
http://www.angelfire.com/electronic/funwithtubes/Woodworking/wwindex.html
Music site: http://www.maxsmusicplace.com

To subscribe to the fun with transistors group send an email to.
funwithtransistors-subscribe@yahoogroups.com

To subscribe to the fun with tubes group send an email to,
funwithtubes-subscribe@yahoogroups.com

To subscribe to the fun with wood group send a blank email to
funwithwood-subscribe@yahoogroups.com

----- Original Message -----
From: "Tom Knox" actast@hotmail.com
To: "Time-Nuts" time-nuts@febo.com
Sent: Thursday, October 03, 2013 1:46 PM
Subject: Re: [time-nuts] A man with two clocks...

It is all a matter of proper placement, now I know you are expecting a
tirade on propagation delay and antenna placement and cable length. But
actually my thought is to place them far enough apart with the WWV clock
in front of your and your GPS at a 12-15 degree angle so it takes 0.2
second to look from one to the other.

Thomas Knox

From: david-taylor@blueyonder.co.uk
To: time-nuts@febo.com
Date: Thu, 3 Oct 2013 19:22:04 +0100
Subject: Re: [time-nuts] A man with two clocks...

Among my time nut toys is a Consumer grade GPS clock and a similar WWVB
clock. The WWVB clock consistently runs about 0.2 seconds ahead of the
GPS
one. I know no one can say why without knowing the particulars of the
two
clock's circuits. Just thought I'd post it for what it's worth.

Regards.

Max. K 4 O DS.

---==

Max,

I see similar things here. I've always put it down to relatively poor
circuitry in the radio clock, which is why I built my NTP-controlled wall
clock!

http://www.satsignal.eu/raspberry-pi/DigitalClock.html

One radio clock is below. That particular MSF clock is actually not too
bad - visibly it's in sync with the NTP clock (which itself is within a
few
microseconds of GPS time).

73,
David GM8ARV

SatSignal Software - Quality software written to your requirements
Web: http://www.satsignal.eu
Email: david-taylor@blueyonder.co.uk

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.

Still laughing. Actually I did it aurally. The GPS clock announces the time on the hour with a series of beeps similar to the old BBC time and the WWVB clock has an alarm which I can set to sound on the hour. The time interval is an estimation. Someday I will use a microphone connected to a storage oscilloscope to figure out what the difference is. Regards. Max. K 4 O DS. Email: max@maxsmusicplace.com Transistor site http://www.funwithtransistors.net Vacuum tube site: http://www.funwithtubes.net Woodworking site http://www.angelfire.com/electronic/funwithtubes/Woodworking/wwindex.html Music site: http://www.maxsmusicplace.com To subscribe to the fun with transistors group send an email to. funwithtransistors-subscribe@yahoogroups.com To subscribe to the fun with tubes group send an email to, funwithtubes-subscribe@yahoogroups.com To subscribe to the fun with wood group send a blank email to funwithwood-subscribe@yahoogroups.com ----- Original Message ----- From: "Tom Knox" <actast@hotmail.com> To: "Time-Nuts" <time-nuts@febo.com> Sent: Thursday, October 03, 2013 1:46 PM Subject: Re: [time-nuts] A man with two clocks... > It is all a matter of proper placement, now I know you are expecting a > tirade on propagation delay and antenna placement and cable length. But > actually my thought is to place them far enough apart with the WWV clock > in front of your and your GPS at a 12-15 degree angle so it takes 0.2 > second to look from one to the other. > > Thomas Knox > > > >> From: david-taylor@blueyonder.co.uk >> To: time-nuts@febo.com >> Date: Thu, 3 Oct 2013 19:22:04 +0100 >> Subject: Re: [time-nuts] A man with two clocks... >> >> Among my time nut toys is a Consumer grade GPS clock and a similar WWVB >> clock. The WWVB clock consistently runs about 0.2 seconds ahead of the >> GPS >> one. I know no one can say why without knowing the particulars of the >> two >> clock's circuits. Just thought I'd post it for what it's worth. >> >> Regards. >> >> Max. K 4 O DS. >> =================================== >> >> Max, >> >> I see similar things here. I've always put it down to relatively poor >> circuitry in the radio clock, which is why I built my NTP-controlled wall >> clock! >> >> http://www.satsignal.eu/raspberry-pi/DigitalClock.html >> >> One radio clock is below. That particular MSF clock is actually not too >> bad - visibly it's in sync with the NTP clock (which itself is within a >> few >> microseconds of GPS time). >> >> 73, >> David GM8ARV >> -- >> SatSignal Software - Quality software written to your requirements >> Web: http://www.satsignal.eu >> Email: david-taylor@blueyonder.co.uk >> >> _______________________________________________ >> 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@lists.febo.com

A man with two clocks...

73, David GM8ARV

73, David GM8ARV

73, David GM8ARV

73, David GM8ARV

73, David GM8ARV

73, David GM8ARV

73, David GM8ARV

73, David GM8ARV

73, David GM8ARV

73,
David GM8ARV

73,
David GM8ARV

73,
David GM8ARV

73,
David GM8ARV

73,
David GM8ARV

73,
David GM8ARV

73,
David GM8ARV

73,
David GM8ARV

73,
David GM8ARV