Today, I wrote an email directly to product manager "Mr. Mega 1000" (see p. 5 in linked pdf), but I don't even know if this person still works for Junghans. We'll have to wait until after the Easter holidays for an answer.
Honestly, I wouldn't expect that. Even the official NIST "howto" hasn't been corrected yet (as of 2007-04-05), and it was last updated in December 2005, quite probably after the US Congress passed the change. If the NIST doesn't know, how can others outside the US be expected to know?collector wrote:Fourth, The US Congress passed the DST time change law back in 2005, ample time for watch manafactures to code / re-code IF NECESSARY. Any "Atomic" watches sold in late 2006 or 2007 clearly should have had the necessary changes done to them before sale!!!
Anyway, it's certainly not good engineer's practice to hardcode such things that could be made flexible with very little effort - just stupid.
DCF77 is not a problem, because the transmitted time changes from CET to CEST, so there's no necessity for an RC clock to decide whether to add 1h or not - it simply displays what it receives. Maybe one day the UK will decide to use a rule different from the rest of Europe - then they'll have a problem too (but deserved :wink:). The rules for DST end were changed some years ago (from end of September to October) without problems.collector wrote:Seventh, If and when, other countries besides the US change the date when DST changes the problem will become larger and believe me you will hear about it!!!
The point with WWVB is that it always transmits UTC and is received in many different time zones, so it is not possible to add DST in the time data. The watch has to decide.
AFAIK, Japan (JJY40 and JJY60) has only one time zone and not even DST (yet) - no problems to expect.
EDIT:
Just saw jblin's posting - so there are more RC watch manufacturers with problems...