Hi I think there are a lot of ways to come up with a “local” WWVB signal that has all the DST stuff in it (or not if you prefer …). There’s not a lot of code or development involved. Even with the current shortage of parts, there are an ocean of dirt cheap MCU’s and boards to pick between. Assuming you already have an accurate “frequency” source, running that into a board is also pretty simple.
Doing this with a closed source “black box” sort of device …. not for me. There simply is no reason in this day and age to do it that way. There’s nothing crazy hard to do inside the device. I see no compelling reason any of it should be “closed”. Nobody is going to turn off WWVB next week. The budget will go around in loops for months and months (at the very least). We seem to have a way to get boards built and sold, so even that part isn’t crazy. This sort of thing should be a lot more popular than the buffer board that now is into it’s second batch. Firing something like this up *before* WWVB goes away might get you into interesting issues with the FCC. I’d wait until things are a bit more clear before building a bunch of boards ….. Bob > On Aug 24, 2018, at 12:21 PM, Graham / KE9H <ke9h.gra...@gmail.com> wrote: > > That is the problem I am trying to avoid. > The politicians insist on messing-with/changing Daylight Savings time. > (I'll stop there before Tom comes after me.) > > Today I have a convenient bit I can look at on a WWV or WWVB signal and > know whether to offset for DST. > Little intelligence and no OS required. > No software/firmware update required when someone decides to change the > changeover weekend in the US. > GPS doesn't tell me. > NTP doesn't tell me. > > NIST seems to be suggesting the clock makers move off of radio, and onto > the net for accurate time. > Is there something as simple on the net that I could query with a single > packet and get a single packet answer? > > --- Graham > > == > > On Fri, Aug 24, 2018 at 9:23 AM Hal Murray <hmur...@megapathdsl.net> wrote: > >> >> ke9h.gra...@gmail.com said: >>> If both the HF and LF signals go away due to the proposed budget cuts, >> what >>> is the next simplest way (for something like a microprocessor based >> clock) to >>> get DST information? >> >> "microprocessor" isn't a well defined term. >> >> If you have an OS, use the time conversion package. They all use the same >> collection of zone info files. >> >> If you don't have an OS, use a system with an OS to pre-compute the >> switch-dates for the next N years and store them in a table. You will >> have to >> update that table whenever Congress screws with things. >> >> -- >> These are my opinions. I hate spam. >> >> >> >> >> _______________________________________________ >> time-nuts mailing list -- time-nuts@lists.febo.com >> To unsubscribe, go to >> http://lists.febo.com/mailman/listinfo/time-nuts_lists.febo.com >> and follow the instructions there. >> > _______________________________________________ > time-nuts mailing list -- time-nuts@lists.febo.com > To unsubscribe, go to > http://lists.febo.com/mailman/listinfo/time-nuts_lists.febo.com > and follow the instructions there. _______________________________________________ time-nuts mailing list -- time-nuts@lists.febo.com To unsubscribe, go to http://lists.febo.com/mailman/listinfo/time-nuts_lists.febo.com and follow the instructions there.
