Ok, after some additional experimenting...
I made a wrong assumption that the ON/OFF count and/or the power on
cycles was included in the checksum that I was watching at EXER 02
location 0000. They do not seem to be included since the checksum
never changed.
Here's a better test. I placed a bad checksum value at 0000 and
verified the scope now had a TEST 04 FAIL 10 (bad checksum) on boot.
Then, going into CAL 05 and getting out without changing anything, the
scope rewrote the checksum back to the correct value. Subsequent
boots had no error.
Don: Can you give CAL 05 a try?
-mark
On Fri, 19 Apr 2024 11:35:05 -0400
"Mark Litwack" <mark@...> wrote:
Hi Victor,
That was the first thing I tried. The checksum is at EXER 02 address
0000. Changing the ON/OFF count or hours does not change the checksum
location.
I don't know all the details of the implementation and I suppose it's
possible that 0000 is only a checksum for the cal data and not other
operating data.
It certainly won't hurt if Don can try it.
(Actually, nothing will hurt since he can put it all back anyway.)
-mark
On Fri, 19 Apr 2024 05:33:08 -0700
"victor.silva via groups.io" <daejon1@...> wrote:
Mark,
I believe if you make a small change to the ON TIME or ON/OFF counter in CAL 05 it will refresh the checksum.
--Victor
