Wired and Wireless Connectivity

Connectivity links an embedded product to other boards, instruments, networks, gateways, and users. Good hardware design covers not only the protocol, but also connectors, voltage domains, ESD, isolation, cable length, antenna placement, certification, and field diagnostics.

Learning Objectives

By the end of this lesson, you should be able to choose wired or wireless connectivity hardware, identify required protection and isolation, plan RF module integration, and review production-test and compliance risks.

Connectivity Architecture

The physical layer often determines whether the product is reliable in the field.

Wired Interfaces

Common wired choices:

• UART: simple board-to-board or debug link.
• RS-232: legacy point-to-point serial, higher voltages.
• RS-485: differential, long cable, multidrop industrial networks.
• CAN: robust automotive and industrial control.
• USB: high-speed host/device connectivity, strict layout and ESD needs.
• Ethernet: networked products, magnetics, PHY, and controlled impedance.
• 4 mA to 20 mA: industrial sensor signaling.

Select the electrical layer from distance, noise, grounding, speed, node count, and connector environment.

Cable and Grounding Risks

Long cables bring:

• ESD and surge;
• ground potential difference;
• common-mode noise;
• reflections and termination needs;
• miswiring and hot-plug transients;
• shield termination decisions.

Use differential signaling, isolation, common-mode chokes, surge protection, and proper termination where required.

For a terminated differential bus:

$$
R_{term} \approx Z_0
$$

For typical RS-485 twisted pair, use about 120 Ohm at the bus ends only.

Isolation

Isolation is required when:

• equipment grounds may differ by unsafe voltage;
• regulatory safety isolation is required;
• industrial noise would corrupt communication;
• the interface leaves the product enclosure into harsh wiring.

Isolation planning includes:

• isolation voltage rating;
• creepage and clearance;
• isolated power supply;
• data rate and propagation delay;
• surge rating and standards.

Do not add a digital isolator while leaving grounds shorted elsewhere.

Wireless Options

Common wireless choices:

• Bluetooth LE: phones, short range, low power.
• Wi-Fi: high throughput, higher power, internet connection.
• LoRa/Sub-GHz: long range, low data rate.
• Cellular: wide-area connectivity, high peak current, certification burden.
• GNSS: receive-only positioning, antenna placement critical.
• NFC/RFID: very short range identification or commissioning.

Wireless selection depends on range, data rate, power budget, antenna size, regulatory region, and cloud or gateway architecture.

RF Module Integration

A pre-certified module reduces RF design risk, but only if used according to its integration guide.

Check:

• antenna type and keepout;
• ground plane requirements;
• RF trace impedance if using an external antenna connector;
• module peak current and bulk capacitance;
• coexistence with noisy DC-DC converters;
• regulatory labeling and allowed antennas;
• programming and test access.

For free-space path loss:

$$
FSPL_{dB} = 20\log_{10}(d) + 20\log_{10}(f) + 32.44
$$

where d is kilometers and f is megahertz. This is an ideal estimate; walls, orientation, antenna loss, and interference reduce real range.

Power Budget

Connectivity devices often dominate power:

• Wi-Fi transmit peaks may be hundreds of milliamps.
• Cellular transmit peaks can exceed 1 A or 2 A.
• BLE sleep current can be microamps if the board supports it.
• Ethernet PHYs add continuous power.

Size regulators and bulk capacitors for peak current, not only average current.

Production and Field Test

Plan how the factory will verify connectivity:

• loopback connector for wired ports;
• known-good gateway or test fixture;
• RF conducted test pads or approved radiated test;
• MAC address, serial number, and key provisioning;
• antenna visual inspection;
• firmware log of link quality and fault counters.

Connectivity failures are easier to diagnose when the hardware exposes link status, termination options, and test points.

Practical Checks

• Add ESD protection close to external connectors.
• Verify connector pinout against cable drawings.
• Place termination only where the bus topology requires it.
• Keep USB and Ethernet pairs length-matched and impedance-aware.
• Keep RF antenna areas clear of copper, batteries, metal enclosures, and tall parts.
• Check radio peak current with oscilloscope during transmit.
• Confirm regulatory requirements before enclosure tooling.

Common Mistakes

• Treating UART as suitable for long noisy cables.
• Terminating every RS-485 node instead of only bus ends.
• Placing ESD parts far from the connector.
• Routing RF under an antenna keepout.
• Ignoring cellular peak-current pulses.
• Changing antenna type after module certification.
• Forgetting production provisioning for IDs and keys.

Summary

Connectivity hardware must satisfy the physical environment as well as the protocol. Reliable designs specify cable length, grounding, protection, isolation, termination, RF layout, antenna rules, power peaks, compliance constraints, and production tests before schematic release.

Further Reading

• TI and Analog Devices RS-485 and CAN transceiver application notes.
• USB-IF layout and compliance guidance.
• Ethernet PHY and magnetics layout guides from PHY vendors.
• Module integration manuals from the selected Wi-Fi, BLE, LoRa, or cellular vendor.

Mind Map