Hi The issue with the fudge option is that you need to engage it at exactly the right point. Put another way, there's a period between it failing and your entering a fudge that the NTP server is down. With a couple lines of auto correct code in there, it would (essentially) never fail. If you are running a GPS, you enable the auto-correction and forget about it. My guess is that many GPS devices will eventually suffer from the wrap around. The only way they could avoid it would be some sort of external correction (like continuous firmware updates) or a "no reverse" on the year. Both approaches have their drawbacks…..
Bob On Aug 11, 2013, at 1:51 PM, Hal Murray <hmur...@megapathdsl.net> wrote: > > mag...@rubidium.dyndns.org said: >> I'm sure that the NTP drivers can be hacked to make necessary adjustments >> without too much code. > > The code is already in there. It's got a fudge option in the config file. > That was intended to fixup small offsets. I think it will work with big > offsets too. > > 1024 weeks is 1024*7*86400 seconds. That's 0x24EA0000, 30 bits. It won't > fit in a float if you also need to correct for a few ms, but it should work > if you changed enough stuff from floats to doubles. They are likely to be > doubles already. > > It would be fun to try. > > > -- > These are my opinions. I hate spam. > > > > _______________________________________________ > time-nuts mailing list -- time-nuts@febo.com > To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts > and follow the instructions there. _______________________________________________ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
