📖 Read the guides here → zcohen-nerd.github.io/connector-engineering-field-guide
Two connector field guides, one site:
- Professional / Industrial Connector Field Guide — practical connector selection for rugged, industrial, military-style, and electromechanical systems, written for engineers who are not connector specialists.
- Hobby Connector Field Guide — a practical map through hobby connector chaos for makers, students, and dev-board projects: identify, choose, buy, crimp, and avoid the traps.
Status: v0.9 Beta — Hobby Guide Expansion + Two-Track Polish · A zcohen-nerd technical guide
Picking a connector is harder than it should be. The information you need is scattered across vendor catalogs, datasheets, standards, and tribal knowledge — and the part that looks right on a shelf can still leak, fret loose, or stall your build because a wedgelock or crimp tool never made it onto the BOM.
This guide's core idea: a connector is a controlled interface between subsystems, not just "a plug with enough pins." It helps you classify the interface, pick a sane family to investigate first, check the specs that actually matter, dodge the classic traps, and document the result so someone can actually build it.
- Mechanical engineering interns and junior electromechanical/mechatronics engineers
- Robotics and controls engineers
- Small hardware teams
- Makers and student teams transitioning into professional hardware design
🧭 Decision Paths — ten scenario walkthroughs that take "I need a plug here" to a documented choice: industrial sensors, rugged Ethernet, internal PCB harnessing, rugged on a budget, high-current DC power, sealed feedthroughs, debug/service ports, defense/rugged external I/O, removable machine modules, and RF/GPS/radio paths.
🔍 Deep dives — MIL-DTL-38999, MIL-DTL-26482, and M12/M8, plus a 14-section core guide covering what connectors actually do, anatomy, datasheet reading, selection workflow, and red flags.
🛠️ Tools & Templates — a selection checklist, a sourced comparison matrix, cable drawing and ICD templates, and a design-review checklist, ready to copy into your own design package.
📦 Worked examples — including a complete Connector Selection Packet: requirements → decision matrix → architecture → pinout → BOM → cable notes → ICD → review checklist for a rugged field-robot module.
📚 Quick help — How to search for connectors, What People Forget, a shared glossary, and quick-reference tables.
🔌 Hobby track — identifying mystery connectors, JST Is Not One Connector, JST-SM and LED strings, crimping, marketplace kits, and when hobby connectors are not enough.
This guide is educational and judgment-focused. It is not a replacement for manufacturer datasheets, applicable standards, customer requirements, or qualification rules — and when it conflicts with any of those, the datasheet / standard / customer requirement wins. Ratings in the guide are cited, family-level orientation values, never a substitute for the exact part's datasheet.
Found an error or have a better source? Corrections are very welcome — open an issue. Ground rules:
- Technical corrections need sources (a public datasheet, standard summary, or equivalent).
- No paid-standards tables, no verbatim catalog tables, no unsourced exact ratings.
- Practical decision logic beats vendor marketing.
See CONTRIBUTING.md for the full source-discipline rules. For contributors: Source/connector-engineering-field-guide.md is the canonical source of truth for the professional guide's 14 numbered sections and appendix — factual corrections land there first, and the matching docs/ pages are refreshed from it. Decision paths, tools, examples, the entire hobby track (docs/hobby/), and the other site pages are site-only material under docs/.
- Content (the guide text,
docs/,Source/, templates, examples): CC BY 4.0 - Code (site configuration and build files): MIT
When reusing material, credit: A zcohen-nerd technical guide by Zac Cohen.
GitHub may display a single license for the repository based on the
LICENSEfile. The dual-license split above is authoritative — content is CC BY 4.0, code is MIT.