Skip to main content

Worked Example: Connector Selection Packet

This is a packet structure for an interface design review. It demonstrates the reasoning and required artifacts, but its placeholder parts, electrical limits, and qualification evidence remain open. It is not a buildable or released design. It ties together the selection workflow, the rugged-on-a-budget and removable machine module decision paths, and every template under Tools & Templates.

Read this as reasoning, not a shopping list

This example teaches how to decide and document, not what to buy. Part numbers like J1, P1, and CONTACT-SIZE16-SKT-EXAMPLE are placeholders. In a real project, replace every one with an exact, datasheet-verified P/N and size every current against the manufacturer's derating curve. None of the example ratings below is yours to reuse.

Scenario​

A small outdoor field robot has a removable sensor/control module. When the module is pulled for service, its harness must disconnect cleanly at the module boundary. The interface must handle:

  • 24 VDC power input to the module
  • Several low-current discrete I/O lines
  • One CAN differential pair
  • A chassis / shield strategy
  • Sealed external connection, outdoor splash/dust exposure, moderate vibration
  • A technician-serviceable harness
  • No formal MIL-DTL / QPL requirement
  • A budget-sensitive prototype-to-small-production path

1. Requirements summary​

ItemValue / decisionNotes
Subsystem boundaryRobot chassis harness ↔ removable moduleOne clean disconnect at the module face
EnvironmentOutdoor, dust + splash, moderate vibrationTarget sealed when mated; capped when unmated
Power24 VDC nominal inputSize current against the contact derating curve — not assumed here
Discrete I/OTwo 24 V-class discrete inputs and one sinking discrete output; thresholds/current limits TBDDirection defined relative to the module; interface circuits require verification
DataOne CAN pairTwisted pair; bus termination is a system property, not a connector feature
Shield / chassisCable shield + chassis-ground strategyDefined in the pinout and cable notes
Service modelTechnician-serviceable, fieldDT/DTM/DTP: mating-face release after wedge removal, rear withdrawal; approved hand tooling
Production posturePrototype → small productionLow tooling cost, easy sourcing, second source available
ConstraintsNo MIL/QPL requirement; budget-sensitiveDrives toward sealed automotive, away from mil circulars

2. Connector family candidates​

At least three families are worth a look before committing:

  • Sealed automotive (Deutsch DT / DTM / DTP) — sealed, hand-crimpable, cheap, ubiquitous. See rugged-on-a-budget and the DEUTSCH Deep Dive.
  • M12 (A-coded + a separate coded connector for CAN) — clean COTS ecosystem, molded cordsets. See industrial sensor.
  • MIL-DTL-38999 — rugged and configuration-controlled, but overkill here. See the 38999 deep dive.
  • Industrial rectangular / Han-style — great for serviceable modules, but large for a small robot. See removable machine module.

3. Decision matrix​

Qualitative scoring — no fake precision. + favorable, ~ acceptable/depends, − unfavorable for this job.

CandidateWhy it fitsWhy it may not fitTooling / assemblySealing / serviceabilityCost / availabilityDecision
Deutsch DT/DTM/DTPSealed, hand-crimpable, service access at both ends; power + signal covered by one familyNot a mil ecosystem; no EMI backshell ecosystem+ low-cost hand tools+ sealing per exact assembly; front-actuated release, rear withdrawal+ cheap, widely stocked, second-sourcedSelected
M12 (A-coded + CAN-coded)Clean COTS, molded cordsets, sealedTwo+ connectors for this mix; per-connector pin/current limits; more connectors on the panel~ cordsets easy; field-wireable fiddly+ IP67 sealed when mated~ low-cost but more connectorsBackup
MIL-DTL-38999Rugged, keyed, config-controlledCost, tooling, lead time all unjustified with no requirement driving them− positioner/insert tooling+ sealed, but far beyond need− expensive, long leadRejected
Industrial rectangular / HanServiceable, mixed media in one housingToo large/heavy for a small robot module~ insert tooling+ serviceable~ mid cost, bulkyRejected

4. Selected architecture​

Split into two sealed connectors from the same family: one power, one signal + data. Both DEUTSCH-class; confirm the tool, contact line, and positioner for each exact contact rather than assuming common tooling.

  • J1 / P1 — Power (small pin count, larger contacts sized for the 24 VDC feed and its return).
  • J2 / P2 — Signal + CAN (discrete I/O plus the CAN pair on a smaller-contact housing).

Why split rather than one mixed connector?

  • Segregation — keeps the 24 VDC power path away from low-level discrete and the CAN pair, reducing coupling and simplifying the shield story.
  • Serviceability — power and signal harnesses can be built, tested, and replaced independently.
  • Smaller, cheaper housings — two small sealed connectors are easier to route, seal, and hand-crimp than one dense mixed one.
  • Failure isolation — separate harnesses can simplify fault isolation and routing, but add interfaces and service actions. Compare those failure opportunities with the single-connector option.

The cost is two disconnects instead of one and two caps — acceptable here. If panel space were extremely tight, a single mixed connector with documented power/signal segregation would be the trade the other way.

5. Pinout​

Generic signal names; contact sizes are illustrative and must be sized against the datasheet and derating curve.

J1 / P1 — Power

PinSignalDirectionWire (class)Shield / twistService notes
1+24 VDCInto modulePower gauge, sized to load + derating—Larger contact size
224 V RTN (0 V)From modulePower gauge, sized to load + derating—Larger contact size

J2 / P2 — Signal + CAN

PinSignalDirectionWire (class)Shield / twistService notes
1DISCRETE_IN_1Into moduleSignal gauge—
2DISCRETE_IN_2Into moduleSignal gauge—
3DISCRETE_OUT_1From moduleSignal gauge—
4CAN_HBidirectionalTwisted pair w/ pin 5Twisted pair; shieldedKeep pair together end-to-end
5CAN_LBidirectionalTwisted pair w/ pin 4Twisted pair; shielded
6SIGNAL_RTNSignal referenceInsulated signal conductorNot the shield drainDedicated reference for the field-side CAN and discrete circuits

Return and shield architecture​

For this illustration, choose CAN, with a module-side isolated field-I/O domain. CAN and the discrete interface circuits share SIGNAL_RTN in that domain; isolation separates it from the module's 24 V RTN and chassis. This is an architectural requirement, not a claim that a transceiver or isolator has already been selected.

PathChassis-harness endModule endDesign intent
J1 pin 2: 24 V RTNPower-source returnModule power returnNormal module power current stays in J1
J2 pin 6: SIGNAL_RTNDefined field-bus/discrete commonIsolated field-I/O commonInsulated reference conductor; no module-side tie to J1 return or chassis
CAN_H / CAN_LCAN bus pairIsolated CAN transceiver field sidePreserve pair; define termination and common-mode limits
Discrete pins 1–3Field I/O referenced to SIGNAL_RTNIsolated input/output circuitsTwo inputs and a sinking output; define thresholds, source/load currents, and off-state behavior
Cable shieldChassis-entry shield clampModule-entry shield clampProposed chassis bonds at both ends; no shield-drain contact in J2
Enclosure bondMachine/chassis bond networkDedicated enclosure bondDo not use SIGNAL_RTN or the shield as a protective bonding conductor

Independent functional sketches distinguish a load-current power return, a driver/receiver signal reference, and a local cable-shield bond to an enclosure.

Role map only: these are independent sketches, not this packet’s wiring schematic. The table above defines the proposed isolated topology and external shield clamps; no additional bonds are implied. Chassis bonding and signal reference serve different functions, as illustrated in TI’s separate chassis/signal-ground discussion.1

The plastic signal connector does not provide a metal backshell shielding path. The proposed external shield clamps and enclosure bonds need their own drawing and service procedure. Verify equipotential bonding, possible shield currents, and EMC performance; a CAN bit rate alone is not a shielding rationale. Define isolation working voltage, transient/fault withstand, and the field-side power arrangement before selecting components.

Release remains blocked until the schematic identifies every intentional common-to-chassis connection and demonstrates normal and fault return paths, including external-I/O backfeed. Pin 6 must not become a second module power return when J1 is disconnected.

6. BOM checklist​

Every required line must become a real orderable item. The placeholders below are not part numbers.

ItemJ1/P1 (power)J2/P2 (signal + CAN)
Connector body (receptacle)J1-RCPT-EXAMPLEJ2-RCPT-EXAMPLE
Mating connector (plug)P1-PLUG-EXAMPLEP2-PLUG-EXAMPLE
Contacts (pins/sockets)CONTACT-SIZE16-*-EXAMPLECONTACT-SIZE20-*-EXAMPLE
Wedgelock / secondary lock (TPA)as applicableas applicable
Cavity / sealing plugsfor every unused cavityfor every unused cavity
Rear seal / grommet / strain reliefper familyper family
Dust cap (unmated protection)CAP-J1-EXAMPLECAP-J2-EXAMPLE
Crimp tool + die/positionerfor contact sizefor contact size
Extraction toolfor the retention systemfor the retention system
Cablepower cableshielded cable w/ a twisted pair
Labels / heat-shrink markersboth endsboth ends
Boot / heat-shrink (if used)as neededas needed

7. Cable drawing notes​

  • Wire gauge — power conductors sized to the load and the contact derating curve; signal conductors per the contact and signal.
  • Pair twisting — CAN_H/CAN_L a maintained twisted pair end-to-end; do not split the pair through the connector transition.
  • Shield termination — external chassis-entry clamps at both ends are the proposed topology in §5; no drain wire shares J2 pin 6. Detail clamp hardware, bonds, insulation, and service disconnection. Verify the choice against the system's interference spectrum and bonding network; see §5.7.
  • Seal dimensions — DT/DTM/DTP rear grommets seal each wire's insulation OD. Verify every populated cavity and sealing plug. Separately check overall cable OD against any boot, gland, clamp, or strain-relief accessory.
  • Bend radius — respect the cable's minimum bend radius at the connector exit; pick a straight vs. right-angle backshell/boot accordingly.
  • Label scheme — both ends of every wire and both connector shells (J1/P1, J2/P2).
  • Electrical test — verify point-to-point continuity and absence of unintended shorts between all isolated nets and between nets, shield, and shell/chassis; use defined limits and protect connected electronics.
  • Retention and workmanship — inspect crimps, contact seating, and installed wedgelocks. Distinguish the manufacturer's gentle seating check from controlled retention tests and destructive crimp pull tests on specified samples.

The template for this is the cable drawing template.

8. ICD entry​

  • Interface name: Module boundary — Power (J1/P1) and Signal+CAN (J2/P2)
  • Connector role: Receptacles J1/J2 on the module; plugs P1/P2 on the chassis harness
  • Mating pair: J1↔P1, J2↔P2 — physical non-intermateability to be established with exact housing/key/contact selections
  • Pinout: per §5 above (source-controlled)
  • Voltage / current class: 24 VDC nominal; per-contact current sized against the derating curve (verify)
  • Signal definitions: isolated 24 V-class discrete I/O and CAN per §5; thresholds, common-mode limits, termination, and isolation specifications remain open
  • Shield / chassis treatment: external shield clamps to chassis at both ends; separate insulated SIGNAL_RTN in the isolated field-I/O domain. Bond hardware, EMC evidence, and fault analysis remain open (§5)
  • Environmental assumptions: sealed (target IP67-class) when mated and locked; unmated only when capped (verify the exact family/assembly rating)
  • Service / cap note: environment-rated caps as required on unmated ports; DT/DTM/DTP repair needs mating-face wedgelock/release access and rear contact withdrawal (procedure)
  • Revision control: this ICD and the pinout are rev-controlled; changes go through the interface owner
  • Source / evidence tracking: every rating in the released version cites its datasheet + revision, the derating basis, and — because this packet is a teaching example — every placeholder is marked example-only (verification status: example). Family-level figures trace to the sourced §3.2 table; nothing here is a verified part rating

Use the ICD template for the full form.

9. Design review checklist​

  • Current derating checked against the contact's derating curve at temperature (not the headline number)
  • Wire seal range matches every wire OD; cable OD inside the gland/seal range
  • Unused cavities plugged on both connectors
  • Torque / assembly procedure defined (coupling, backshell, and crimp)
  • Correct crimp tooling and extraction tool identified for each contact size
  • Cable exit / bend radius checked; straight vs. right-angle boot chosen
  • Keying / polarization prevents cross-mating P1↔J2
  • Mating connectors and dust caps on the BOM
  • Source-controlled pinout exists and matches the harness
  • Power/signal segregation, isolation, and shield termination reviewed; schematic traces all normal/fault returns and external-I/O backfeed
  • Electrical levels and limits defined for each discrete and CAN signal; mating-face pin drawings attached
  • Load-break / mate-under-power status recorded from the datasheet — for this module: de-energize the 24 V feed and external I/O sources before disconnect; check for backfeed; sealed automotive families are not load-break rated unless the exact datasheet says so
  • Workmanship/acceptance standard named (IPC/WHMA-A-620 or the program/customer equivalent) along with the crimp tool and inspection criteria

Run the full design review checklist before sign-off.

10. What would change if…​

  • A formal defense / QPL requirement appears → reconsider MIL-DTL-38999 (or 26482 where a bayonet fits); the sealed-automotive choice no longer satisfies the requirement.
  • Ethernet is added → add a rugged Ethernet path (M12 D/X-coded or sealed RJ45); do not try to run gigabit on the discrete signal connector.
  • RF / GPS is added → use the RF/GPS/radio path — a coax contact or a separate coax bulkhead, not a spare signal pin.
  • Current increases significantly → revisit contact size, the derating curve, and possibly a dedicated/split power connector.
  • Production volume increases → revisit tooling (applicator vs. hand crimp), second sources, keyed variants, and assembly inspection sampling.

Templates for each artifact above live under Tools & Templates. For the family-selection reasoning behind the choice, start at rugged-on-a-budget.

Footnotes​

  1. Texas Instruments, System Design Guidelines for the TM4C129x Family of Tiva C Series Microcontrollers, SPMA056 (October 2013), §3.3.6 and Figure 13 (printed p. 15), with connector-shield examples in §§4.1.3 and 4.3.4. These illustrate chassis-bonding functions; they do not establish this packet’s grounding, isolation, or fault-protection design. https://www.ti.com/lit/an/spma056/spma056.pdf ↩