| Products > Test Equipment |
| Do you often use peak/hold feature on your benchtop DMM? |
| (1/3) > >> |
| LinuxHata:
Hello. I'm developing an "upgrade" kit for Keithley 179 display module, which will have modern OLED indicator, with higher brightness and customizable colors. It will be "plug-n-play" module, no modification to DMM needed, you just unplug old display module and install the new one. Since there will be separate MCU on that board, which will eliminate these flashing zeros on over range, and replace them with non-flashing "-----", I can implement some additional features: 1. Peak value display - the screen will split into two parts, and larger digits will show the current measured value, and smaller digits will show the peak value measured. 2. Freeze/Hold display - Again, screen will split into two parts, and larger digits will show the current measured value, but smaller digits will hold the value, which was actual, when that button was pressed. 3. Continuity beeper - Activated by separate button, and when measured value is below or over certain value (user adjustable), there will be loud buzz. How do you think, are these features interesting to anyone? (Personally, I don't need first two, but need the 3rd one) |
| AVGresponding:
Peak, only rarely, hold fairly frequently, continuity, all the time. But when you need them, you need them. |
| tautech:
Yep, if you're not using Hold then it's probably a low energy, low density or low voltage DUT. For most everything else you need both eyes on what you're doing rather than short something out, blow the ends from probes etc where instead Hold in invaluable, just invaluable. |
| tooki:
I use peak occasionally and continuity all the time. However, the reason for using those features is that they’re far, far faster than the display update speed. A continuity tester that only responds in 400ms (the 179’s conversion time) is completely useless, and I don’t mean that as hyperbole: I’d never use it because even a $10 meter with horrible continuity will be better. Similarly, when I use my Fluke 87V’s peak detect, it’s because of its ability to detect 1ms pulses, which is far, far far, faster than the meter’s display update rate. Both of these are features implemented deep in the meter’s hardware and software, so you can’t emulate them by screen scraping a meter with a very slow display. So while I applaud your inventiveness at wanting to expand the feature set, I don’t think it’d actually add much in the way of actual utility because the performance would just be too poor. |
| LinuxHata:
Well these are a good points to consider (peak & hold), and I never thought about them, since I'm used to use digital scope, when I need to detect pulses 1ms and shorter. Regarding the continuity, yes, this won't be terribly fast, but as said, it will have customizable trigger ranges, have no idea if this feature is implemented in any of current DMMs - this means, you can set that say, beep will only sound, when resistance is in between, say 1k and 1.2k. This feature is quite usable when you need to test and sort and debug many similarly wired components or wires - sound will be only heard when the measured value is in range, so you can save time by not looking on the display. So, saying shortly, I will not implement peak and hold features, but will do adjustable continuity beeper. |
| Navigation |
| Message Index |
| Next page |