Hi I suspect that it's one of those - I'll be gone before then sort of firmware issues. Some fix it others ignore it unless it's on the marketing tick list. The marketing guys may or may not have been born when the last roll over occurred ….
Bob On Jun 7, 2012, at 8:50 PM, Mike S wrote: > On 6/7/2012 8:02 PM, Bob Camp wrote: >> One could put in a routine that looks at the date the software was >> written and "fix" any date that shows up as being in the past. > > After all the issues seen after the last rollover, I'd think receivers would > have been made robust against this. > > One obvious method would be to keep a checkpoint date (or 1024 week cycle # + > week offset) in EEPROM. To avoid issues with using up EEPROM r/w cycles, only > update it anytime the currently received date is more than a year beyond the > currently stored date. > > _______________________________________________ > time-nuts mailing list -- [email protected] > To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts > and follow the instructions there. _______________________________________________ time-nuts mailing list -- [email protected] To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
