Hello everyone!
My grandpa gave me his old multimeter two weeks ago.
It is a Voltcraft M-3650D, which seems to be a re-branded Metex M-3650D. I think in the US it was sold as the RadioShack 22-168.
There is a problem when trying to measure voltage and I thought I could try to repair it, as I think it is a pretty nice meter otherwise.
I am pretty new to electronics (and new in the forum ^^) and after many hours of staring at the schematics I thought that I should probably document what I have and ask for some help. (Because if I can't solve it, I am not learning much either.) So, here I am!
Already I am very grateful for everyone who takes the time to read this.
===The Problem (initially)===Probes connected to COM and V/OHM.
Range: 20VDC
Result:
The display shows a reading of -14V shortly after turning the meter on. It quickly rises to -12V and further, gradually slowing down.
I connected a 9V rechargeable battery and left the meter switched on over night. After tens of hours the offset was at approx. -0.1V.
I disconnected the battery to recharge it and tried it again a few days later with the same result of a slowly decreasing offset from 0V.
===My Initial Thoughts===A temperature sensitive component?
A bad/missing reference?
A bad connection or defective component leaving some pin floating and collecting parasitic charges?
===Some Documentation===The sigrok website has a little bit of documentation on the voltcraft-version
https://sigrok.org/wiki/Voltcraft_M-3650Dand a little bit more on the Radioshack-version (including very nice pictures!)
https://sigrok.org/wiki/RadioShack_22-168There is a link to a service manual for the M-3610D and M-3650D, containing schematics and parts-lists.
https://www.eserviceinfo.com/preview.php?fileid=33728&file=Metex M3610D-3650D.gifThe schematics are cut in half which I found hard to read, so I exported the images (using XpdfReader) and stitched them back together.
It took me waaaay to long to understand how to read the range-selector matrix, so here is a small explanation:
Every ring on the range selector pcb is one column in the schematics. (Two PCBs with each 6 rings for a total of 12 rings and corresponding 12 columns in the schematics.) The contacts on the range selector wheel always connect two rings (and columns) that are next to each other. (1&2, 3&4, ...)
On the left of the schematic there is a numbered legend of the range options. I thought the numbers correspond to the numbers on the right side of the selector-matrix. This is not true. (I have no idea what those are actually for.) Instead the legend is aligned with the matrix in a way to directly lable each row. I added some colored bars to make it easier to read.
schematics

(How do I make the images appear actually inline at this position?

... images are at the bottom)
I then tried to identify the main parts and functional blocks with ... mixed results. I can not find any documentation about IC6 and IC11. Could those be an amplifier and a frequency counter?
I added some lables and tried to highlight the signal paths for the 20V and 200µA ranges in green and red:
highlighted schematics
===The Problem (further investigation)===Measuring voltages still works when accounting for the voltage offset. For example when the offset is at -8V, connecting a 9V battery returns a measurement of approximately 1V.
In the voltage ranges, the offset is the same, regardless of the selected range. For example, it measures -3V for the ranges 1000V, 200V and 20V, but out of limit for the ranges 2V and 200mV. As the offset drifts closer to 0V over time the lower voltage ranges can be used as well.
I thought this must mean that the offset-voltage exists across the entire resistor-chain (R1-R6) (used as voltage divider for the different voltage ranges) and that I should be able to force it to zero by shorting the probes (COM & V/OHM). But that did not work.
I was confused and thought that I should try looking somewhere else to get a wider picture of the problem.
I switched to the amp-range of the meter. It uses a different resistor-chain (R9-R12) but other than that the signal seems to take a very similar path throughout the meter.
For the different amp-ranges it displays the following readings (if V-range would show an offset of -10V):
200µA --> -1.0µA
2mA --> -0.010mA
20mA --> -0.10mA
200mA --> -1.0mA
That is always 0.5% of the selected range (contrasted to the v-range where the offset has a consistent absolute value across all ranges).
When in the 200µA-range (and only there) the offset can be reduced to zero by shorting the test probes (connected to COM and mA).
Something I noticed while looking at the schematic was that the "ground" connected to the COM terminal is not the same as the negative pole of the battery "V-" (foolish thought of a beginner, I guess ^^). I believe this is because some chips need symmetric supply voltages? As far as I can see "V-" is only connected to IC6, IC4 and Q9. As the offset is negative I thought I should check the related components and started by de-soldering C3 (close to IC6) as it looked to me like it would be connected to some negative potential and it is fairly close to the signal path.
I have one of those very cheap component testers. I put C3 into the socket and measured 337nF, 20Ohm ESR and 0.7% Vloss. I think that is normal for these small electrolytic caps?
(Afterwards I noticed that if C3 would leak current into COM that I would probably measure a positive voltage offset, not a negative one.)
===What I will do next===As everything is so tightly packed (testing C3 wasn't easy/quick) I would like to avoid de-soldering and testing all the components in the signal-path. Instead I will go back to trying to wrap my head around what I would need to change in the schematic in order to cause the observed effects. I am still confused as to how everything connects together. Maybe I should make a simplified schematic with less zig-zag paths to help my monkey brain.
I will also try measuring the voltage across R69 and R70 (once I have put everything back together again) in order to see how much current goes through them.
In the meantime I thought I should post what I have so far. Not because I want someone to solve this for me entirely ... but I am very slow and sometimes feel a bit lost. So, if someone notices something really obvious or could point me to some useful troubleshooting techniques I would be very very grateful!
Greetings from Germany (and sorry if my english is a little bit funny

)