|
If you have an A or B series, you can get the calibration values back in the NVRAM with this utility (or with GPIB, if you have the equipment):
toggle quoted message
Show quoted text
/g/TekScopes/files/24xxAB-writecal-1.1.zip The only way to get them back into a 2445/2465 (plain) that I know of at the moment is via the optional GPIB interface (OPT 10). A similar utility to the above for A/B versions could be developed for 2445/2465 scopes, but ER1400 failures are far and few between (unlike dead batteries), and virtually no one has backed up their 2445/2465 cal data so it can be used with such a utility. If you have a backup of your cal data and are trying to get it back in the ER1400, please speak up! The above zip archive has demonstration code in ./related/earom.c on how the Tek "spiral add" checksum algorithm works on the 2445/2465, plus how parity is calculated for the range of locations that include parity. So, you might be able to determine the offending entry by putting your EXER 02 data in the code. If you want to post your 2465 EXER 02 data, we could also look at it together in this thread. Theoretically, you could force the scope to recalculate the checksum by performing a calibration step, such as CAL 04, where you don't actually modify anything and then exit the cal procedure. I haven't tried this, but keep in mind if you do you're ignoring bad cal data that could affect the scope's operation. From a reliable source, I am told there is an undocumented screen utility similar to EXER 02 for *entering* the data, but the person I spoke to can't recall how it was done. More work with a better logic analyzer (which I have now), and/or analysis with Siggi's 2465 Ghidra image and 2465 MAME simulator may find the answer. It's on my to-do list. -mark On Thu, Apr 10, 2025 at 02:52 AM, Mr Lurpak's Electronics Rescue wrote:
|
