Hi Oh, ok.
Any time you have a power “burp” the clock will start back at what ever it thinks was the time was last. That sounds simple. It’s not. If you want to save your eeprom or flash from burnout, you don’t write “it’s now ..” once a second. If you do, things die fairly quickly. I have empirical data (and a pile of 53131’s) to prove this. You write your magic bytes much less often. What likely happened is you are inside the granularity of that write process. Bob > On Dec 7, 2014, at 10:03 AM, Paul <[email protected]> wrote: > > On Sun, Dec 7, 2014 at 9:25 AM, Bob Camp <[email protected]> wrote: > >> They may have some odd setting deep in the scpi to get the log over to >> this or that time frame. I'd have thought that UTC would be the obvious >> choice. It also could just be a bug. > > > > Initially they were in sync. I hope this power "accident" didn't break > anything beyond causing time to briefly jump backwards. > > Log 037:20141201.00:25:47: GPS reference valid at 20141202.01:47:41 > Log 038:20141202.01:48:45: Locked mode entered > Log 038:20141201.00:00:00: Power on > Log 039:20141201.00:00:00: Power on > Log 040:20141201.00:00:17: Power settings ok, Int: 17 dBm, Ext: 17 dBm > Log 041:20141201.00:02:13: EXT reference valid > Log 042:20141201.00:03:14: EXT lock started > Log 043:20141201.00:25:42: GPS reference valid at 20141202.01:47:36 > Log 044:20141202.01:48:41: Locked mode entered > _______________________________________________ > 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.
