TDS8000 / CSA8000 ACQ Calibration Failed - Page 1
Forum section: electronics / testgear

author: richardb
author_rank: Newbie
timestamp: July 26, 2020, 12:58:33 pm
content: Anyone had any success getting the calibration procedure to work on these? I purchased six of these units, they all had the normal things wrong (NVRam batteries, corrupt bios). Have got to the point where they all work but once they load the application they show ACQ recall failures, same on each one. Looking on the net other people have seen these but I am yet to find a remedy.https://www.eevblog.com/forum/testgear/tds8000-dc-calibrator-adjustment-procedure-does-not-produce-expected-results/msg502618/#msg502618Looking at the serial header on the PowerPC board I see after vxWorks loads:0x2abb500 (aCalDiagExecutor): CCMgr: Recall ACQ cal constants failed!0x2abb500 (aCalDiagExecutor): --> Initializing to defaults!0x2abb500 (aCalDiagExecutor): CCMgr: Recall user ACQ comp data failed!0x2abb500 (aCalDiagExecutor): --> Initializing to defaults!The GPIB interface works, commands I have sent to try and make the machine happy and not report errors include:syst:prot offcal:save:fact:maical:updateinfo:maisyst:prot onsyst:prot offcomp:sav:fact:allcal:save:fact:maical:update:allsyst:prot on:syst:prot off:cal:save:fact:mai:cal:updateinfo:mai:syst:prot on:syst:prot off:comp:sav:fact:all:cal:save:fact:mai:cal:update:all:syst:prot onTIN and some others have written excellent articles on the 7404 which is similar. I see also some other people posting about the same errors but no remedy as yet. None of the machines have a serial number currently programmed into them so I am unsure if this makes any difference. If it does could someone enlighten me as to the GPIB command to send to program the serial numbers.Richard

author: Jwalling
author_rank: Unknown
timestamp: July 27, 2020, 09:13:51 am
content: Here are my notes on this scope from when I last performed a successful calibration. Hopefully it helps, I don't think I could help any further as it was so long ago. You did replace the battery on the acquisition board as well, correct?REM CSA8000 and TDS8000 serial reprogramming after battery replacementREM the serial # can be seen under menu item  [system properties]REM Serial # programming:SYST:PROT OFFSYST:PROP:MAI:SER "B010243"SYST:PROT ONREM A reboot is not needed to see the new #REM Model # programming:SYST:PROT OFFSYST:PROT:MAI:MODE "TDS8000" orSYST:PROP:MAI:MODE "CSA8000"SYST:PROT ONREM CALIBRATION - an experiment.SYST:PROT OFFCAL:SAVE:FACT:MAICAL:UPDATEINFO:MAISYST:PROT ONIt did not solve the error 171 NVRAM data integrity, but no more cal errors are seen in the serial port logs, such as:0x2ee98a0 (aCalDiagExecutor): CCMgr: Recall ACQ cal constants failed!0x2ee98a0 (aCalDiagExecutor): --> Initializing to defaults!0x2ee98a0 (aCalDiagExecutor): CCMgr: Recall user ACQ comp data failed!0x2ee98a0 (aCalDiagExecutor): --> Initializing to defaults!0x2ee98a0 (aCalDiagExecutor):  M: 1,0:00:29,23.50,## FIRST TEST ##0x2ee98a0 (aCalDiagExecutor):  P: 1,0:00:44,23.50,171,AcqCalInfo(2), AcqCalConst(2), AcqCompFactory(2), AcqCompUser(2)donedonedoneconnectionTask: handshaking with peer...connectionTask: handshaking with peer - done.connectionTask: handshaking with peer...0x2ee98a0 (aCalDiagExecutor): CCMgr: Recall ACQ cal constants failed!0x2ee98a0 (aCalDiagExecutor): --> Initializing to defaults!0x2ee98a0 (aCalDiagExecutor): CCMgr: Recall user ACQ comp data failed!0x2ee98a0 (aCalDiagExecutor): --> Initializing to defaults!So I followed this procedure and it worked - it got rid of error 171It did not require setting the write protect switch off either.Try, :calcomp:double instead of CALCOMP:DOUBLE.The following may help. Notes and memory joggers for me to remember how to calibrate these. I do recall there was a step(s?) where the capitalization of the gpib commands had to be just right, and not as documented, looks like I changed all of the gpib commands to lower case...Unprotect the cal memory by toggling the memory write protect switch in the rear of the unit (to the outside hole).:syst:prot off:calcomp:double "DcCalOffsetAdj",4.0e-4 ; this is equivalent to a positive 4mA shift.(querry form, :calcomp:double? "DcCalOffsetAdj"):calcomp:double "DcCalLsbAdj",0.9967 ; where 0.9966 and -0.9967 dmm values, see notes:calcomp:double "Internal10MHzRefFreq",9.99008e6:comp:sav:fact:all:cal:save:fact:mai:cal:update:all:syst:prot onNotes:Use capitalization exactly as above.I am not certain how many digits of precision are allowed. A 6.5 dmm per instructions implies, based on above, 4.00e-4 (or equiv) and 0.996700 as permissible values. Simple experimentation with the latter did not result in obvious influence on calibration. The values used in the top example were adequate to meet cal specs.DcCalLsbAdj = this is a compromise adjustment and is dependent on offset being correct. You take a dmm measurements of the 1 volt calibrator signal, plus and minus, look at them as absolute values and pick the best value in between. So, 0.9966 and -0.9967 becomes: 0.9966 and 0.9967, now pick an in between value, 0.9966 or 0.9967. So, on this system you are telling it that a 1V signal is actually 0.9967, and it needs to adjust for that... This value is never negative! You could choose to use 0.9966 instead. If you see a greater spread than 2 digits your offset voltage is probably wrong.The Internal10MHzRefFreq result that I got may have been wrong. This one is probably best left alone, or the 10e6 value. My math skill are not that great.I replaced my batteries, so all of the above values were zeroed out already.Menu Soft Key to get to calibrator.-> lkup "DcC"calCompSetDcCalibratorAdjConst 0x01000a8c text (rtlLibTarget.o)calCompGetDcCalibratorAdjConst 0x01000a38 text (rtlLibTarget.o)calLibGetDcCalibratorCalDefaults 0x01032ef8 text (rtlLibTarget.o)