Hi all,
Watching various YouTube videos where Multimeter reviewers reach the stage where they test the continuity beep mode of the meter by 'clicking' the probes together as fast as they can to see if they can beat the 'beep' into submission.....I thought "
there must be a better way than that".
Not to mention I was moving from Altium CircuitStudio to KiCad V6 and so needed a quick first KiCad project to test the workflow........the DMM Continuity Tester was born.
It's operation is kinda self-explanatory, but there are a couple folks out there I have pushed units out to given I had built up 3 or 4 so I guess YT videos will appear if indeed it's found to be useful.
I've made it open source, it's based around an Arduino Pro Mini (5V) a small Zoltech LCD........all the files are here:
https://www.ianjohnston.com/images/stories/IanJ/DMMContinuityTester/DMM_Continuity_Tester_PCB_and_CODE.zip(zip scanned with BitDefender)
Update 24/06/23:
I have attached the HEX file for the Arduino......some folks have been having problems compiling the source.
https://www.ianjohnston.com/images/stories/IanJ/DMMContinuityTester/DMMcont.ino.with_bootloader.zip(zip scanned with BitDefender)
The performance of some DMM's are quite surprising, here's a few:
Example MARK Examples (minimum) at 250mS SPACE:
- Brymen BM257 = 38mS
- Fluke 85 III = 0.9mS
- Fluke 87 = 0.9mS
- Agilent 34405A = 25mS
- Keysight 34461A - 1mS (needs Space = 300mS)
- Agilent 34401A = 20mS, but will work lower but gives continious tone
- Brymen BM786 = Better than 0.01mS
- V&A VA38 = 0.1mS (beep varies in volume to point it's hardly audible though, obviously not using a fixed beep length)
Only one meter (BM786) beat the minimum that can be set with the tester, I guess I should re-write the code using interrupts to try and squeeze a few more uS from it.
Ian.