Did the 60 khz Ft. Collins time signal transmitter send out the
correct time signals this morning?
I've got 3 different radio-controlled clocks (atomix I think) and none
of them had the right time this morning.
Did the 60 khz Ft. Collins time signal transmitter send out the
correct time signals this morning?
I've got 3 different radio-controlled clocks (atomix I think) and none
of them had the right time this morning.
Did the 60 khz Ft. Collins time signal transmitter send out the
correct time signals this morning?
I've got 3 different radio-controlled clocks (atomix I think) and none
of them had the right time this morning.
Did the 60 khz Ft. Collins time signal transmitter send out the
correct time signals this morning?
I've got 3 different radio-controlled clocks (atomix I think) and none
of them had the right time this morning.
This year my clocks set ok but did not do so until about 10am. Last year it >took a week before my clocks got a strong enough signal to reset.
Did the 60 khz Ft. Collins time signal transmitter send out the
correct time signals this morning?
I've got 3 different radio-controlled clocks (atomix I think) and none
of them had the right time this morning.
had 2 that reset....wristwatch did not until i forced it to
reset....other clock still hasn't reset.
tonight, at approximately 8:30 PM EDT, two of my analog models went a
bit "haywire" and reset themselves to Standard Time. We shall see if
they correct themselves later tonight. This has happened on several
occasions previously and I do not understand why.
Did the 60 khz Ft. Collins time signal transmitter send out the
correct time signals this morning?
I've got 3 different radio-controlled clocks (atomix I think) and none
of them had the right time this morning.
La Crosse clocks have a firmware bug. When the daylight bit comesoverloads
on at UTC 00:00, the clocks are not allowed to reset until local 02:00,
some 7 or more hours later. So they remember it in a bit.
They do this fine (if you have several of the same model, watch them
do it in absolute lockstep).
There's a slight problem at 00:00 UTC the next night (8 PM EDST!)
when they find the daylight bit set but ``it's not 2am yet and there
hasn't been a full day of daylight time yet'' and it says, oops, it ought
to be standard time still, and they all reset back to standard time.
I've never been up to see what time they reset back to correct time
(midnight or 2am, UTC or standard or daylight time, 6 possibilities).
La Crosse, when consulted about this, claimed that the WWVB signal
the clocks when they change times, translation we'd rather not replace
a million clocks on warrantee. But I find it endearing, happening to like hardware screwups that you can figure out.
It will do the same thing in the fall, by the way. You get 6 time changes
a year with this chipset.
Did the 60 khz Ft. Collins time signal transmitter send out the
correct time signals this morning?
I've got 3 different radio-controlled clocks (atomix I think) and none
of them had the right time this morning.
On Mar 11, 3:58 pm, Radio Guy <R...@Guy.com> wrote:
Did the 60 khz Ft. Collins time signal transmitter send out the
correct time signals this morning?
I've got 3 different radio-controlled clocks (atomix I think) and none
of them had the right time this morning.
Five out of Six did OK.
Numb3r Six is on a Desk between a Computer and Printer
below a LCD Monitor and did not reset to DST only has
One Bar. Just put it next to a Window and got Three Bars.
Hit the "TS Seak" Button and will check it in the Morning.
dst waits for no one - and that is why . . .
many of us will be late this monday ~ RHF
.
.
. .
On Mar 12, 2:39 am, "RHF" <rhf-newsgro...@pacbell.net> wrote:
On Mar 11, 3:58 pm, Radio Guy <R...@Guy.com> wrote:
Did the 60 khz Ft. Collins time signal transmitter send out the
correct time signals this morning?
I've got 3 different radio-controlled clocks (atomix I think) and none
of them had the right time this morning.
Five out of Six did OK.
Numb3r Six is on a Desk between a Computer and Printer
below a LCD Monitor and did not reset to DST only has
One Bar. Just put it next to a Window and got Three Bars.
Hit the "TS Seak" Button and will check it in the Morning.
dst waits for no one - and that is why . . .
many of us will be late this monday ~ RHF
.
.
. .
OK - So now # 6 has sync'ed itself. ~ RHF
FWIW this Computer is a Dell Dimension 4700 with
the Windows XP [OS] and it did the new DST switch
over 'on-time' Sunday 11 March 2007.
On Mar 11, 6:58 pm, Radio Guy <R...@Guy.com> wrote:
Did the 60 khz Ft. Collins time signal transmitter send out the
correct time signals this morning?
I've got 3 different radio-controlled clocks (atomix I think) and none
of them had the right time this morning.
Hello All.
I have fifteen of these clocks. Two of them (both LaCrosse digital
models) are set to GMT and do not change when DST is incorporated. Of
the other thirteen (three analog models), all but two showed the
correct time this morning. One which did not catch the signal was one
of my analog clocks. I "forced" it to hunt for the signal around 10:30
AM EDT and, after finding it, did set itself correctly. However,
tonight, at approximately 8:30 PM EDT, two of my analog models went a
bit "haywire" and reset themselves to Standard Time. We shall see if
they correct themselves later tonight. This has happened on several
occasions previously and I do not understand why. All of the batteries
in my clocks are fresh. The last digital clock which did not show the
correct time this morning still, as of 11:30 PM EDT, had not corrected
the time, so I finally did so manually. (This particular clock had
never had this problem previously.) I live in New Jersey. I wish that
a second transmitter were incorporated somewhat closer to the eastern
part of the country as the signal from Ft. Collins is not completely
reliable here. Especially now, with the low sunspot count, one would
think that the signal on 60 kHz would travel farther and adjust the
clocks properly. Sadly, as evidenced by all writing here, this is not
the case.
Best,
Joe
I'm in Chicago area and only 3 of my 7 clocks set. They need more power or
a better antenna system. My friends at work also had problems with lack of signal.
"Joe Analssandrini" <analssandrinij@yahoo.com> wrote in message news:1173671318.769342.136350@p10g2000cwp.googlegroups.com...
On Mar 11, 6:58 pm, Radio Guy <R...@Guy.com> wrote:
Did the 60 khz Ft. Collins time signal transmitter send out the
correct time signals this morning?
I've got 3 different radio-controlled clocks (atomix I think) and none
of them had the right time this morning.
Hello All.
I have fifteen of these clocks. Two of them (both LaCrosse digital
models) are set to GMT and do not change when DST is incorporated. Of
the other thirteen (three analog models), all but two showed the
correct time this morning. One which did not catch the signal was one
of my analog clocks. I "forced" it to hunt for the signal around 10:30
AM EDT and, after finding it, did set itself correctly. However,
tonight, at approximately 8:30 PM EDT, two of my analog models went a
bit "haywire" and reset themselves to Standard Time. We shall see if
they correct themselves later tonight. This has happened on several
occasions previously and I do not understand why. All of the batteries
in my clocks are fresh. The last digital clock which did not show the
correct time this morning still, as of 11:30 PM EDT, had not corrected
the time, so I finally did so manually. (This particular clock had
never had this problem previously.) I live in New Jersey. I wish that
a second transmitter were incorporated somewhat closer to the eastern
part of the country as the signal from Ft. Collins is not completely
reliable here. Especially now, with the low sunspot count, one would
think that the signal on 60 kHz would travel farther and adjust the
clocks properly. Sadly, as evidenced by all writing here, this is not
the case.
Best,
Joe
| Sysop: | KJ5EKH |
|---|---|
| Location: | Siloam Springs, Ar. |
| Users: | 10 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 77:10:58 |
| Calls: | 32 |
| Files: | 76,049 |
| Messages: | 59,683 |