Chuck Guzis wrote:
It's not an autoranger like the Fluke, but
I'm not sure that I care
for the autoranging feature.
Always been curious about that; I don't like autoranging meters either - but
I've never really worked out why.
Nor do I. I find it takes considerably longer for me to read the thing if
the range has changed between readings.
The worst I ever used was a Fluke 73 (the original one, this was over 25
years ago). It was autoranging _only_ and had the analogue bargraph
along the bottom of the display. You can guess the rest. You'd be trying
to peak or null something, the darn thing would change ranges, and the
bar would suddnetly shrink or grow. Rather defeated the prupose of that
bargraph... I would _never_ consider an autoranging-only meter.
Maybe I just like knowing what a tool's going to do, without feeling like it's
second-guessing me - but that logic probably doesn't really make much sense in
a multimeter context :-)
I think it does. The best tools are ones that you know how they are going
to behave, so you don't ahve to think about them. This is one reason I'll
not use anything but an RPN calcualtor, I don't want to have to remember
all the precedence rules (i.e. what does '-2^2' evaluate to?).
And probalby why I hate autoconfiguration programs. Any program that
thinks it knows more aobut my computer's hardware than I do is wrong. Period.
Some of the DEC autoconfuration programs drove me mad. You could end up
having to change the addresses and vecotrs of almost all the devices in
the machine ebcause you'd removed one controller. Ouch. I would much
prefer to be able to say 'I have an RL11 at address <foo>, vector <bar>.
Yes, I know htat's non-standard, but just take my word for it':-).
My holy grail would be a meter where the test leads
didn't auto-tangle on the
bench as soon as my back was turned for more than five minutes ;-)
Alas all test gear suffers from that. No manufactuer has solved that one.
-tony