Hi
> On Aug 24, 2018, at 1:18 PM, Mark Sims wrote:
>
> Lady Heather has DST support code in it (in file heathmsc.cpp). It supports
> the current standard settings for several areas (US, Europe, Australia, New
> Zealand) or you can specify a custom DST rule. The code is around 200 lines
>
Good Idea, John.
I'll do that.
Just to see what they say.
--- Graham
==
On Fri, Aug 24, 2018 at 1:25 PM John Marvin wrote:
>
> Someone suggested scraping the NIST time service website for this
> information. The NIST website specifically says "Also, it is
> inappropriate to generate your own
There's support in "over the air" ATSC digital TV signals for DST info,
but most TV stations aren't known for keeping their time information up
to date. There's a system time packet that has the GPS time, the number
of seconds difference between GPS time and UTC (and a lot of stations
don't
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.
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
Currently, getting Daylight Savings Time status is easy using WWV or WWVB
since they have bits in the protocol marking status for the US, and in the
case of WWVB, impending change.
If both the HF and LF signals go away due to the proposed budget cuts, what
is the next simplest way (for something
