Products > Test Equipment
HP 3478A behavior on low ranges
radar_macgyver:
I have an HP 3478A that shows a slowly increasing count on lower DC volts ranges (anything less than 30V). Eventually, it goes overrange, and starts faintly beeping and zeroes itself, then repeats the cycle. Any resistance applied between the probes (I tried several 1M resistors in series) will bring the voltage back to zero, as will putting it into the 30 or 300V range. I suspect the latter is due to a voltage divider. Is this normal behavior?
The instrument has not been used in many years (possibly decades), I cleaned it out with compressed air but am afraid to use any solvents after seeing the weird hybrid inside. I also need to replace its cal battery... it measures about 1.2V, and it somehow is still calibrated!
Fun fact: it was actually a prototype unit (the son of a former colleague used to work at HP and was apparently on the design team). Some folks from Keysight visited our lab and I showed it to them, they remarked that the missing front badge and no serial number was a good sign it was indeed a prototype.
bdunham7:
Completely normal due to the small pias current (tens of picoamperes) charging up the input capacitance. The resistance across the input is effectively nearly infinite. Once you add 10M in parallel, the tens of picoamperes of bias current only result in hundreds of microvolts.
alm:
Yes, this is normal. Happens to pretty much every meter that is high impedance (GOhms) on the lower DCV ranges. This won't happen if it's actually measuring a signal with a finite impedance. Fix is to set it to a higher range where the input impedance is only 10 MOhm.
adam4521:
Before changing the battery, you can read out your calibration constants if you have got a GPIB/USB cable. The feature is documented on the forum here:
https://www.eevblog.com/forum/repair/hp-3478a-how-to-readwrite-cal-sram
I've attached a python script I made a few years ago to extract the calibration. I haven't made the reverse one, but it would be easy enough to create that. Unfortunately the pyvisa module needs one of those gigantic VISA runtimes to be installed on your computer, in order to work. I think I used the Keysight one.
adam4521:
I just saw in the pyvisa docs that there is a pure python implementation as well (pyvisa-py), maybe that would be enough. It might depend on what type of interface cable you have got.
Navigation
[0] Message Index
[#] Next page
Go to full version