What We Specify for IoT Devices: Connector and Interconnect Notes

We review a lot of IoT BOMs — trackers, smart locks, environmental sensors, e-bike controllers. Run the numbers on a 50,000-unit lot with a 1% field failure rate: that is 500 units. The SoC and the firmware usually take the blame, but the real culprit is the $0.03 connector that got picked by default.

Here is what we actually specify for battery lines, board-to-board links, RF, and I/O — and what we refuse to sign off.

Battery and Power Lines: Match the Pitch to the Current

The JST pitch ladder is the fastest way to make a power decision: SH at 1.0 mm is a 1 A part, PH at 2.0 mm is 2 A, XH at 2.5 mm is 3 A. GH (1.25 mm) and Molex PicoBlade (1.25 mm) sit in between with better latch geometry.

Nothing smaller than PH gets a battery, and anything that gets dropped, bumped, or ships with the cell installed moves up to XH. A tracker project last year ran its Li-ion pack on a PH connector because the layout was tight; drop testing sheared the latch on the third cycle. The redesign moved to XH and the harness survived forty cycles. The fix cost 1.5 mm of board edge.

Board-to-Board and FPC: Plan the Rework Before You Pick the Pitch

Board-to-board pitch follows an inverted curve: 0.4 mm parts (Hirose DF40 class) are wonderful until one misaligned placement kills a board you cannot rework; 0.5 mm FPC ZIF connectors are reworkable, but the latch is the weak point, and on vibrating products the cable works it loose over time. For anything that ships with a flex cable inside, default to 1.25 mm latched connectors (DF13 class) over unlatched FPC, even when the extra millimeter costs board space. If you must use a ZIF, specify the double-lock version and route the flex so it cannot lever the latch open.

RF Links: U.FL-Class Cables Have a 6 GHz Ceiling

For sub-6 GHz radios, U.FL-class connectors are the workhorse — but check the cable, not just the plug. A U.FL assembly with 1.13 mm coax bent tighter than the datasheet radius picks up a permanent 1 dB of extra loss that nobody measures in production. We specify double-lock U.FL (MHF4 class) for anything that ships with the antenna attached, and we keep two cable SKUs on the BOM: a long one for the RF bench, a short one for the product. Using the test cable on the production line quietly changes the antenna's tuning.

USB-C Is the Default Port — With Caveats

USB-C covers power and data in one footprint: 5 A at 20 V, 100 W PD out of the box, 240 W with EPR. For a rechargeable product it beats the barrel jack on every axis except price, which at $0.20–0.50 in volume is still trivial. Three caveats. First, the receptacle alone does not make a legal PD port: you need the PD controller, and above 3 A an e-marked cable; cheap no-name cables negotiate at 1.5 A, and the customer blames you. Second, add physical retention. The standard USB-C receptacle's solder anchors are famously weak, so a strain-relieved case or a through-hole version is mandatory on anything portable. Third, if the product is sealed and rechargeable only, skip the port entirely and use a pogo-pin charging dock — one fewer hole in the enclosure to fail IP testing.

What We Refuse to Sign Off

Unlatched FPC in a product that will be dropped. Tin-plated contacts on a port customers plug weekly. A 1.0 mm wire-to-board connector without a lock on any wire longer than 30 mm. And multiple identical-looking connectors on one board without keying — "they swapped the motor cable and the sensor cable" is a support ticket, not a field failure, but it costs you the same.

Paste your connector list into the BOM upload on partscubeglobal.com and we will check availability and pricing across JST, Molex, TE, and Hirose before you commit the layout — because the connector you spec in week one is the one you ship in week thirty.