![]() I'm not aware of an authoritative source for why this was the case, but most likely there must've been a technical reason like accounting, and then they just kept it around. But the problem was that even if you reconnected manually at a convenient time, every now and then you'd have a connection issue at a random time, and then it would keep happening at that exact time until you manually changed it again. ![]() It wasn't actually strictly at night, but just exactly 24h after the connection was established. > German providers disconnecting customers every night is a ridiculous feature in itself. ie the clock would compare the time to the set alarm exactly once a minute, but when the clock would receive a new time signal of 7:01:00 when its local time was 6:59:59 or earlier, I'd oversleep. ![]() So my theory at that point was that sometimes the clock just managed to fall behind enough in its old spot and then resync just when the alarm would've gone off, and there was no logic to account for this. Years later when I long didn't use that clock as an alarm anymore, I had it in a spot where it wouldn't properly receive the DCF signal and I noticed that it would quickly lag behind after just a few days. I didn't look at the clock so was not able to see what was going on, but at least knew it wasn't me. I eventually got a second alarm and set it a few minutes before the other one, and sure enough eventually there was a day where the second one (so my original one) didn't ring its alarm. Got one of these and totally overslept every couple months. On that note, about 20 years ago, there suddenly was an abundance of small cheap alarm clocks with DCF77 receivers available.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |