>
> Your original email with the link did not make it into the digest, which is
> what I receive.
>
> Chirs, Did you also send it directly to Bill. Perhaps that is what he got.
>
> Bob
Yes, sorry. I sent the follow-up hastily on an iPad, and the URL I thought I
was pasting was an image
: Robert Feldman
Subject: [cctalk] Re: WWVB
>Message: 17
>Date: Mon, 15 Jan 2024 12:52:15 -0500
>From: Bill Gunshannon
>Subject: [cctalk] Re: WWVB
>To: cctalk@classiccmp.org
>Message-ID:
>Content-Type: text/plain; charset=UTF-8; format=flowed
>
>On 1/15/2024 10:47 AM
>Message: 17
>Date: Mon, 15 Jan 2024 12:52:15 -0500
>From: Bill Gunshannon
>Subject: [cctalk] Re: WWVB
>To: cctalk@classiccmp.org
>Message-ID:
>Content-Type: text/plain; charset=UTF-8; format=flowed
>
>On 1/15/2024 10:47 AM, Chris Elmquist via cctalk wrote:
>>
On 1/15/2024 10:47 AM, Chris Elmquist via cctalk wrote:
On Sunday (01/14/2024 at 09:55PM -0600), Chris Elmquist via cctalk wrote:
There are a number of WWVB simulator projects out there that will transmit a
weak but usable signal to your clock after getting sync’d from ntp or GPS NMEA
time
On Sunday (01/14/2024 at 09:55PM -0600), Chris Elmquist via cctalk wrote:
> There are a number of WWVB simulator projects out there that will transmit a
> weak but usable signal to your clock after getting sync’d from ntp or GPS
> NMEA time messages. They were developed to help people develop
January 2024 01:47
To: Jonathan Chapman via cctalk
Cc: Nigel Johnson Ham
Subject: [cctalk] Re: WWVB
That would be good old MSF!
https://www.npl.co.uk/msf-signal
I wasn't aware of it being heard in NA though - maybe being in the great lakes
is a bit too far.
Bit it should still sync correctly
There are a number of WWVB simulator projects out there that will transmit a
weak but usable signal to your clock after getting sync’d from ntp or GPS NMEA
time messages. They were developed to help people develop receivers :-) One
in particular uses an AVR and it should be pretty simple to
Will Cooke and Jonathon Chapman explained it.
A change to the protocol that old clocks don't know about.
bill
That would be good old MSF!
https://www.npl.co.uk/msf-signal
I wasn't aware of it being heard in NA though - maybe being in the great
lakes is a bit too far.
Bit it should still sync correctly!
cheers,
Nigel
On 2024-01-14 20:41, Jonathan Chapman via cctalk wrote:
I agree with Don on the
> I agree with Don on the interference. We have a very high noise floor
> here in Toronto as well as being on the fringe
IIRC there's something on-frequency in England that often swamps WWVB on the
northeastern part of North America, too!
Thanks,
Jonathan
I agree with Don on the interference. We have a very high noise floor
here in Toronto as well as being on the fringe, and an older watch in
the same window as my two Citizens frequently comes up with a fantastic
date and time - possibly due to lack of data redundancy are error-checking.
73 de
I have two watches that sync to WWVB and they always agree with CHU on
HF and a ham rig that syncs to GNSS. So I think it is bang on or there
is a government conspiracy to make us late for work 樂
73 de ve3id
On January 14, 2024 2:49:19 p.m. EST, Bill Gunshannon via cctalk
wrote:
This
I also have a decades old SkyScan WWVB LCD wall clock which has survived a few
sets of leaking AA batteries :).
It still keeps accurate, occasionally it doesn’t sync, though I think that can
be chalked up to signal propagation.
It’s possible the problem is interference EMF, RF etc. Try
> On 01/14/2024 1:54 PM CST Jonathan Chapman via cctalk
> wrote:
>
>
> Bill,
>
> If it's an older clock it's probably tripping over a timecode transmission
> format/modulation change. I forget the exact details but changes were
> required to my old 8085-based Spectracom receiver.
>
>
I have two watches that sync to WWVB and they always agree with CHU on HF and a
ham rig that syncs to GNSS. So I think it is bang on or there is a government
conspiracy to make us late for work 樂
On January 14, 2024 2:49:19 p.m. EST, Bill Gunshannon via cctalk
wrote:
>
>This is kind
On 1/14/2024 2:54 PM, Jonathan Chapman via cctalk wrote:
Bill,
If it's an older clock it's probably tripping over a timecode transmission
format/modulation change. I forget the exact details but changes were required
to my old 8085-based Spectracom receiver.
Thanks, that's probably it.
Bill,
If it's an older clock it's probably tripping over a timecode transmission
format/modulation change. I forget the exact details but changes were required
to my old 8085-based Spectracom receiver.
Thanks,
Jonathan
On Sunday, January 14th, 2024 at 14:49, Bill Gunshannon via cctalk
17 matches
Mail list logo
