Skip to main content

Professional / Industrial Connector Field Guide

Practical connector selection for rugged, industrial, military-style, and electromechanical systems.

v0.9 Beta — Hobby Guide Expansion + Two-Track Polish

Technical corrections welcome with sources. This guide is an educational engineering reference. Always verify ratings, qualifications, tooling, and environmental limits against current datasheets, governing standards, qualified-products listings, and program/customer requirements.

Picking connectors is harder than it should be. The information is scattered across datasheets, standards, catalogs, vendor naming systems, and tribal knowledge. This guide exists to help engineers who are not connector specialists figure out what connector family to start with, what specifications actually matter, what mistakes to avoid, and how to turn "I need a plug here" into a buildable, documented interface.

The goal is not to make you a connector expert. The goal is to help you classify the interface, choose a sane connector family to investigate first, understand what specs matter, avoid common traps, and document the interface properly.

Core mental model

A connector is a controlled interface between subsystems. It carries power, signals, and data; survives the environment; defines the service boundary; and becomes a configuration-controlled item in your released design baseline.

Disclaimer

This guide is educational and intended to teach engineering judgment. It is not a substitute for applicable standards, manufacturer datasheets, safety requirements, customer specifications, qualification requirements, or program-specific design rules. Exact connector ratings, part numbers, tooling, assembly instructions, and qualification status must be verified before use in released hardware. When this guide conflicts with a datasheet, applicable standard, customer requirement, or qualified program requirement, the datasheet / standard / customer requirement wins.

Start Here: Pick a Connector

Use these cards to get to a reasonable starting family before you disappear into catalogs and datasheets. If you are still trying to figure out how to search, start with How to Search for Connectors.

A sealed industrial sensor cable
Start with M8 or M12 A-coded
Then check pinout, current, IP rating, torque, cable OD, vibration
Rugged Ethernet outside an enclosure
Start with M12 D-coded, M12 X-coded, or sealed/rugged RJ45
Then check data rate, shielding, cable category, sealing, latch protection
Internal PCB power harness
Start with Micro-Fit, Mini-Fit, Nano-Fit, TE/Harwin/JST family as appropriate
Then check current, wire gauge, latch, TPA, tooling, vibration
Better-than-hobby field wiring on a budget
Start with Sealed automotive — Deutsch DT/DTM/DTP, Superseal, MX150, Metri-Pack
Then check wire seal range, correct contact/crimp, cavity plugs, wedgelock/secondary lock
High-current DC power
Start with Anderson SB, industrial rectangular power insert, high-current circular, 38999 power contacts where appropriate
Then check derating, wire gauge, loaded contacts, heat rise, touch safety, sealing (Anderson SB is unsealed/genderless — add a boot outdoors)
Defense/rugged external payload interface
Start with MIL-DTL-38999, MIL-DTL-26482, or similar rugged circular
Then check shell size, insert arrangement, contacts, backshell, keying, caps
Compact high-reliability internal interface
Start with Micro-D or other high-reliability compact connector
Then check current, tooling, assembly process, service model
Debug or service access
Start with Protected USB-C, keyed shrouded header, Tag-Connect, Micro-D, D-sub, sealed service connector
Then check access level, ESD, mating cycles, pin protection, documentation
Removable machine module
Start with Industrial rectangular / Han-style connector or 38999 hybrid
Then check mixed power/signal/data, serviceability, keying, ground-first sequencing
RF/GPS/radio path
Start with SMA, TNC, N-Type, BNC, MCX, SMP/SMPM, or coax contacts in a hybrid connector
Then check impedance, frequency, cable, torque, shielding

Want a step-by-step walkthrough? Most of these scenarios have a full Decision Path — including the rugged-on-a-budget, removable machine module, and RF/GPS/radio paths. (The compact high-reliability internal card is the one scenario without a dedicated path — start from the Micro-D coverage in Standards and Families.)

Working on a maker or dev-board project instead?

Breadboards, Arduino/Raspberry Pi/ESP32 wiring, 3D printers, LEDs, RC power, connector kits from online marketplaces — that ecosystem has its own naming chaos and its own guide. See the Hobby Connector Field Guide, or Hobby or Professional? if you're torn.

Who this is for

  • Mechanical engineering interns
  • Junior electromechanical / mechatronics engineers
  • Robotics and controls engineers
  • Small hardware teams
  • Makers transitioning into professional hardware design

What this guide helps you do

  • Classify the interface you are trying to build
  • Pick a sane connector family to investigate first
  • Know which specifications actually matter
  • Avoid common beginner traps
  • Turn a loose connector choice into a buildable, documented interface

What this guide is not

  • Not a connector catalog
  • Not a replacement for standards
  • Not a manufacturer datasheet
  • Not a qualification document

Use the guide

Source discipline

Source/connector-engineering-field-guide.md in the repository is the canonical guide source — the single source of truth for the 14 numbered guide sections and appendix on this site, kept in sync with the corresponding pages here (0014, appendix/). The source-verification backlog is Source/source-notes.md. This website adds site-only material with no Source/ equivalent — the guide landing pages, Decision Paths, Tools & Templates, Examples, What People Forget, and the diagrams — but the guide's factual claims and citations are governed by Source/. If a numbered guide page here and Source/ ever disagree on a fact, Source/ wins and the page is due for a refresh. Datasheets, applicable standards, customer requirements, and qualified program requirements always win over both.