Hi
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.
Bob
On Dec 6, 2014, at 5:23 PM, Paul tic-...@bodosom.net wrote:
I was curious about the six second
On Sun, Dec 7, 2014 at 9:25 AM, Bob Camp kb...@n1k.org 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
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
On Sun, Dec 7, 2014 at 10:26 AM, Bob Camp kb...@n1k.org wrote:
Any time you have a power burp the clock will start back at what ever it
thinks was the time was last.
I understand this.
I was referring to:
Log 037:20141201.00:25:47: GPS reference valid at 20141202.01:47:41
Log
Hi
On Dec 7, 2014, at 1:31 PM, Paul tic-...@bodosom.net wrote:
On Sun, Dec 7, 2014 at 10:26 AM, Bob Camp kb...@n1k.org wrote:
Any time you have a power burp the clock will start back at what ever it
thinks was the time was last.
I understand this.
I was referring to:
Log
On Sun, Dec 7, 2014 at 2:05 PM, Bob Camp kb...@n1k.org wrote:
If the magic write the time to flash routine runs once every 2 hours,
then that would explain the log. Numbers like 4 or 8 times a day are not
uncommon for this sort of thing.
I'm being unclear. If you look at a Z3811 log you'll
Hi
Here’s what I’m suggesting:
The local time is updated *after* the GPS Valid hits the log. Put another way,
the time used for the log is *not* corrected to GPS time until after the valid
message is logged.
Bob
On Dec 7, 2014, at 2:59 PM, Paul tic-...@bodosom.net wrote:
On Sun, Dec 7,
On Sun, Dec 7, 2014 at 3:07 PM, Bob Camp kb...@n1k.org wrote:
The local time is updated *after* the GPS Valid hits the log. Put another
way, the time used for the log is *not* corrected to GPS time until after
the valid message is logged.
And I completely agree with you.
My point is the
Hi
On Dec 7, 2014, at 4:11 PM, Paul tic-...@bodosom.net wrote:
On Sun, Dec 7, 2014 at 3:07 PM, Bob Camp kb...@n1k.org wrote:
The local time is updated *after* the GPS Valid hits the log. Put another
way, the time used for the log is *not* corrected to GPS time until after
the valid
I was curious about the six second difference between GPS valid on the two
boxes. Is that likely just due to (message) processing overhead?
___
time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to
10 matches
Mail list logo
