Update: NIST wrote back to me. Apparently they did not update that particular channel on that particular server. This, however, has nothing to do with why my clock did not update.
I suffer from having an older, dumber (cheaper) clock that doesn't look at the DST code at all. DST is programmed in the clock to change on the 1st Sunday in April. That's it.
So, for the next 3 weeks, I have to set my clock to the "Atlantic" time zone (just east of "Eastern"). Might be time for a new clock...
-------------------------------------
My clock also did not set itself properly, even after cycling power to force it to reset.
This morning (3/12/07) I decided to check with NIST at http://www.bldrdoc.gov/doc-tour/atomic_clock.html to see if it was me or them. From this site, you can follow the link to get the current time code at http://132.163.4.101:14/.
The first page details what all of those funky codes are. The important code here is the DST code.
Here's what the time code was this morning:
54171 07-03-12 13:25:52 71 0 0 216.4 UTC(NIST)
Note that the "71" means that there are still 20 days until DST. They didn't correct their signal! I e-mailed them about this and did not get an answer.
Here's the code right now as I write this:
54171 07-03-12 18:19:33 50 0 0 619.6 UTC(NIST)
Note that the "71" has now changed to "50" meaning that we are now on DST.
What this all means is that NIST didn't correct their signal until sometime between 9:30am & 2:00pm EST.
What I can't understand is the folks here who claim their clocks did update.
2007-03-12 07:25:10
·
answer #1
·
answered by Bluto 1
·
0⤊
0⤋
Most "atomic" clocks aren't. They're normal clocks that get synchronized to a government maintained standard clock. The US National Institute of Standards and Technology (NIST) radio sync did the DST correction at about 1 am this morning; I just happened to be going to bed at that time.
2007-03-11 06:05:32
·
answer #2
·
answered by arbiter007 6
·
0⤊
0⤋
Mine didn't either.
Could be the the government didn't send the signal?
Most "Residential" atomic clocks actually pick up an AM signal that is sent out at a specific time from Colorado (and I think only there) and set themselves according to it. If the weather is freaky, it can take an extra day till it picks it up.
2007-03-11 04:42:59
·
answer #3
·
answered by reallyboredlurker 2
·
0⤊
0⤋
Look for a switch on the back. You may have to set it to DST. After that, it will take care of itself.
All atomic clocks are based off of one standard. If all else fails, it will get a signal to change soon. My clock did that once, but it has been fine with DST ever since.
2007-03-11 04:36:19
·
answer #4
·
answered by PHI 1.618 2
·
1⤊
0⤋
Today 8 March 2015 both my Citizen & Casio Atomic watch did not reset to the correct time (DST). Maybe it didn t receive the signal properly here in Toronto, Canada. Will wait another day.
2015-03-08 08:49:55
·
answer #5
·
answered by Bob 1
·
0⤊
0⤋
Atomic clocks are reference clocks and don't get reset. Day light saving time etc. is man made to save energy.
2007-03-11 04:38:08
·
answer #6
·
answered by Swamy 7
·
0⤊
1⤋
I have three throughout my house and all of mine did. Some only make updates once a day around midnight and that might be the case. Either set it manually (it will straighted out tonight) or remove the batteries and put them back in to force it to reset itself.
2007-03-11 04:41:06
·
answer #7
·
answered by Anonymous
·
0⤊
0⤋
March 27 2014 still waiting for idiot thing to be set to just even the correct time.
2016-03-29 00:05:32
·
answer #8
·
answered by Anonymous
·
0⤊
0⤋
Mine has a little switch underneath.
2007-03-11 04:41:30
·
answer #9
·
answered by Ade 6
·
0⤊
0⤋
there is a clock like that ,maybe you blow it up to re sett ha ha
2007-03-17 22:03:40
·
answer #10
·
answered by melanie12354@sbcglobal.net 1
·
0⤊
1⤋