I thought latched continuity beeper only existed as a compensation for not being able to implement a fast-acting detector.
That makes no sense. Slow detection is the
result of a poor latching circuit, not the
reason for adding latching. Fast detection is not a challenge (non-latching continuity is cheaper and easier to implement after all!). Latching
while maintaining fast detection is a bit of an art, and one that many meter makers haven’t mastered.
The point of latching is to extend a brief, possibly inaudible beep into one that is long enough and loud enough to be heard reliably. (Not all meters get used in quiet lab environments; they’re also used widely in industry where there needs to be NO ambiguity about whether there is or isn’t continuity.)
I just did a quick test using an MCU to pulse a relay for a few ms (2.25ms is the shortest where its normally-closed contacts open long enough for my multimeters to detect it at all). With a meter with unlatched continuity, the interruption is so brief it really doesn’t sound like a pause; it just adds a click over the continuous beep. On the Fluke 87V, it extends the interruption in the beeping to something plainly audible.
For intermittent contact, I had to set the code to 5ms to get any detectable beep. On the Fluke, it’s a plain, clear beep. On the non-latching meter, a barely audible chirp so short it sounds more like a click. Fine in my quiet bedroom, but if there were any sources of noise in here, you’d be totally unable to hear it.
The scratchiness of unlatched continuity is good for detecting scratchy things (where it’s making and breaking contact many times in a split second), but not good at finding sparse intermittent open circuits.