Hi Maxim,
When you complete any calibration routine (eg. CALXX), the scope
will have stored the calibration constants, and when you leave the
calibration menu, it will recalculate the checksum for the block
of all calibration data. It will *not* recalculate the parity for
the individual calibration constants... only those that it
affected by calibration.
Do not waste your time with calibration until you have fixed the
cause of the Fail04. That means replacing the NVRAM or battery.
If you decide that you really want it calibrated, contact me off
group.
-Chuck Harris
Max Vlasov via Groups.Io wrote:
toggle quoted message
Show quoted text
Hello Chuck,
Thank you for answering.
My 2445a repair/calibration project is the life long (almost 10 years, almost no time). I should of given up on it long before, but it's just not an approach of an engineer to give up on something which almost already works (put lots of hours already, but 2445a in my setup will be more of an artifact). I just wanted to understand how serious is the data integrity failure (FAIL04) and whether I can do the calibration in steps powering up the o-scope every time for the new CALxx routine?
I simply assumed that if the data integrity is OK then I can do the CAL routines selectively (therefore the idea was to get the calibration data w/o errors and then do one calibration routine by another). Otherwise I have to go from the beginning though the end non-stop otherwise nothing will be stored... So far whatever I have calibrated wasn't taken into account by o-scope since I didn't have the right set of equipment to perform the CAL ALL. For example I did perform CAL01 and CAL02 separately, then powered off the scope then I'm back to the same problems. Like it was not simply stored.
Have you managed to calibrate the 24xx scope in separate CAL sessions by having initially FAIL04?
Also do you know which CAL routing will contribute to the AUTO LVL trigger function. In my case channel 1 with the replaced hybrid has the offset too high on AUTO LVL, so trigger level isn't found automatically.
Thank you again and all the Best,
Maxim