xans/3458A-RepairArticle
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Update readme.md

Browse Source
This commit is contained in:
xans 2024-10-02 22:39:17 +02:00
parent 0c8ffb143d
commit 0ff2876588
1 changed files with 14 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

28
readme.md
View File

@ -1,9 +1,9 @@
# 3458A worklog
## Inspecting the multimeter
This unit has clearly seen better days as the pushrods are gone and it looks pretty battered. But looks are not the reason I bought this meter, mainly the legendary performance of the 3458A. Before powering up a used unit that's known to be faulty. It's always important to open it up and have a look, for fear of making a bad situation worse.
[Fix]
On inspection, there are some initial problems that are quite obvious, namely burnt resistors on the main A1 DC measurement board. These have been burned to a crisp, probably due to overvoltage. Looking at the schematics, these are two 10K resistors along the DC input path. Looking at the components, they appear to be CRF65 resistors, very similar to the PTF65. Luckily I had some resistors on hand that could function as a suitable replacement with some artistic creativity. Selftest afterwards reveals seemingly no issue with the DCV section.
This unit has clearly seen better days as the pushrods are gone and it looks pretty battered. But looks are not the reason I bought this meter, mainly the legendary performance of the 3458A are what I was after. Before powering up a used unit that's known to be faulty. It's always important to open it up and have a look, for fear of making a bad situation worse.
On inspection, there are some initial problems that are quite obvious, namely burnt resistors on the main A1 DC measurement board. These have been burned to a crisp, probably due to overvoltage. Looking at the schematics, these are two 10K resistors along the DC input path. Looking at the components, they appear to be CRF65 resistors, very similar to the CRF65. Luckily I had some resistors on hand that could function as a suitable replacement with some artistic creativity. Selftest afterwards reveals seemingly no issue with the DCV section, excellent!
![fix](3458-WorkLog/imgA.jpg)
![post fix](3458-WorkLog/imgB.jpg)
@ -13,6 +13,16 @@ Next I checked the integrity of the signal chain by applying an input and probin
It seems that U008 was the culprit. I have a feeling that the failure mode had something to do with the 5V supply disappearing and the A3 ADC board forcing too high a digital voltage into the shift register output. Interestingly , the shift register in question still put out correct control signals on it's outputs.
![ac fix](3458-WorkLog/imgE.png)
## Calibration
For calibration, the multimeter was first calibrated at home and then taken to a recently calibrated 3458A in another lab. Here the multimeter was adjusted relative to the calibration of the reference 3458A. Due to the erased calibration memory, SCAL was also required. This was done using an oscilloscope set up to measure RMS and a function generator feeding a signal to both. Is this good enough to meet the 3458A specifications? Certainly not in terms of amplitude adjustment, but it was good enough to get the self-test and start-up errors out of the way.
Once the unit was back home, ACAL ALL was run at various points during the drift evaluation, and it was found that the 204 flatness dac error returned when the ambient temperature became too high. This indicates that the error has not yet been found correctly. Interestingly, in the firmware issues listed one finds an improvement that might be related to this.
## Final bugs
Now that the meter seems to be working, I tried ACAL with the meter after letting it run, and now it shows me an error I have never seen before. error 204 flatness dac convergence 199. The error occurs while the meter is warming up and the ACAL step is always 100V. This immediately made me suspect the HV attenuation part, mainly the DAC. Cooling the board slightly, and seeing which component cooling makes it work, made me suspect U302, the LT318 op-amp behind the DAC. However, after replacing it with a different one, the problem still seemed to persist deterring me from assuming the fault is U302.
![amprep](3458-WorkLog/imgC.png)
Now, the resistors for this amp seemed to be affecting the pass or fail, replacing them and retrying indeed made the error disappear. Interestingly, looking at the circuit in question I would not intuitively expect this to fix the fault.
![resrep](3458-WorkLog/imgD.png)
## Replacing the capacitors
To save the meter from an early demise, I replaced all the capacitors, and indeed some seemed to be leaking already, I was lucky to replace them before the corrosion got worse.
@ -26,18 +36,8 @@ Another healthy upgrade I did was to update the firmware to the latest version,
- Revision 5,X: DCV measurements on the 10 V range were shifted by 0.13 uV (within specifications but slightly biased)
- Revision 5,X: Sending “AZERO ONCE” does not always cause the 3458A to immediately make the autozero measurement.
## Final bugs
Now that the meter seems to be working, I tried ACAL with the meter after letting it run, and now it shows me an error I have never seen before. error 204 flatness dac convergence 199. The error occurs while the meter is warming up and the ACAL step is always 100V. This immediately made me suspect the HV attenuation part, mainly the DAC. Cooling the board slightly, and seeing which component cooling makes it work, made me suspect U302, the LT318 op-amp behind the DAC. However, after replacing it with a different one, the problem still seemed to persist deterring me from assuming the fault is U302.
![amprep](3458-WorkLog/imgC.png)
Now, the resistors for this amp seemed to be affecting the pass or fail, replacing them and retrying indeed made the error disappear. Interestingly, looking at the circuit in question I would not intuitively expect this to fix the fault. Interestingly, in the firmware issues listed above one finds an imporvement
![resrep](3458-WorkLog/imgD.png)
## Calibration
For calibration, the multimeter was first calibrated at home and then taken to a recently calibrated 3458A in another lab. Here the multimeter was adjusted relative to the calibration of the reference 3458A. Due to the erased calibration memory, SCAL was also required. This was done using an oscilloscope set up to measure RMS and a function generator feeding a signal to both. Is this good enough to meet the 3458A specifications? Certainly not in terms of amplitude adjustment, but it was good enough to get the self-test and start-up errors out of the way.
Once the unit was back home, ACAL ALL was run at various points during the drift evaluation, and it was found that the 204 flatness dac error returned when the ambient temperature became too high. This indicates that the error has not yet been found correctly.
## U180 drift evaluation
Now the big question with any 3458A project is whether the U180 ASIC at the heart of the meter is still in good condition. This requires an extensive check, powering the meter and monitoring the calibration constants from the ACAL DCV. I have written a toolkit for this (linked here). Although this is a rather short data capture, several captures were made. All with similar results in terms of the drift observed.
Now the big question with any 3458A project is whether the U180 ASIC at the heart of the meter is still in good condition. This requires an extensive check, powering the meter and monitoring the calibration constants from the ACAL DCV. I have written a toolkit for this. Although this is a rather short data capture, several captures were made. All with similar results in terms of the drift observed.
![u180-drift](3458-WorkLog/U180-drift.png)