I am in the process of attempting to design two adapter PCBs for handheld LCR meters that provide:
- Four in-line BNC connectors, allowing attachment of cabled kelvin clips and component probe fixtures
- A ZIF socket and a series of SMD footprints for easy measuring without cables taking up space
Types of probes and fixtures that can be connected to 1. above:
I know that similar adapter designs exist, but none of them provide "standard" spacing, they are designed for specific LCR meter models and some of them require too much hand soldering to my taste.
I will attempt to make my design (riser-PCB, probe-PCB and 3D printed enclosure) universal, so it will fit as many handheld LCR meters as possible.
To achieve that, I will need to know the order and dimensions of the "kelvin PCBs" for the various handheld LCR meter models currently marketed, and this is where I could really use you guys' help in providing me with information about handheld LCR meters you have access to.
The order of the slots vary, with the DER DE-5000 being the "odd man out". In the following list "H"/"+" are synonymous as are "L"/"-" and "Guard"/"G":
- East Tester ET43x: H, L, G
- Hantek 183x: H, L, G
- Keysight U1733C: H, L, G
- UNI-T UT622: H, L, G
- BK PRECISION Model 8xx: H, L, G
- GW-INSTEK LCR-91x: H, L, G
- DER DE-5000: G, L, H
The information that I require to design a universal "riser" PCB are (see illustration):
- LCR Meter Brand and Model
- Order of slots (e.g. H, L, Guard)
- Height of PCB edge fingers beyond any enclosure (H)
- Width of PCB edge fingers (Aw, Bw, Cw)
- Position of PCB edge fingers (B0, C0)
- Thickness of PCB edge fingers
Example:
Meter: Hantek 1832C
Slot order: H, L, Guard
Height (mm): H=13.5
Widths (mm): Aw=14.2, Bw=14.2, Cw=12.2
Position (mm): B0=18.8, C0=39.6
Thickness (mm): 1.0
Thank you in advance for any assistance you can provide to make this project possible.
PS: I will be making the adapter PCBs available for sale (possibly on Tindie), as well as making PCB Design Files (KiCad) and Enclosure 3D Models available on GitHub once I have verified the functionality and fit.