Two fundamental approaches to exchanging data: wired (physical signals over copper traces and cables) and wireless (electromagnetic signals through air). Both exist in embedded systems - for different reasons.
Wired Communication
In wired communication, two devices are connected by a physical conductor - a trace on a PCB, a wire in a cable, or a pin on a connector. Electrical signals carry data directly between the two points.
How Wired Signals Work
The transmitting device drives a pin HIGH (logic 1, typically 3.3 V or 5 V) or LOW (logic 0, 0 V). The receiving device reads that voltage level. The signal travels at near the speed of light along the conductor but is constrained to the physical path of that wire.
Wireless Communication
In wireless communication, devices encode data as modulated electromagnetic waves and radiate them through the air (or vacuum). A receiver demodulates the incoming wave to recover the original data. No physical conductor is needed between sender and receiver.
Wired vs Wireless — Direct Comparison
| Property | Wired | Wireless |
|---|---|---|
| Reliability | High - no external interference | Variable - affected by environment |
| Speed | Very high - SPI 50 MHz, USB 5 Gbps | Lower in practice - protocol overhead, retries |
| Latency | Deterministic - fixed and predictable | Non-deterministic - packet loss, retransmissions |
| Range | Short - PCB traces, cm to meters | Long - meters to kilometers |
| Mobility | None - physical connection required | Full - devices can move freely |
| Power | Lower - no RF transmitter | Higher - radio consumes significant power |
| Real-Time Use | Yes - automotive, industrial, safety systems | Difficult - latency jitter breaks timing guarantees |
Why Embedded Systems Mostly Use Wired
The majority of chips on an embedded board communicate over wired interfaces like SPI, I2C, or UART because it is the most reliable engineering choice for internal system architecture. Wired connections offer deterministic timing, guaranteeing data delivery within microsecond windows - a critical requirement for safety-critical hardware like an automotive CAN bus where wireless packet drops or retransmissions could cause catastrophic delays.
Furthermore, wired circuits consume mere microamps of power, allowing battery-operated systems to run for years, and their firmware drivers are exceptionally lightweight, requiring only basic register configurations rather than massive, complex network and security stacks.
Choosing a wired design also drastically simplifies product commercialization by avoiding costly regulatory RF certifications (such as FCC or CE) required for any device emitting over-the-air radio frequencies. Wireless modules like Wi-Fi or Bluetooth drastically increase power consumption up to 400 mA, introduce variable latency, and add significant hardware and development costs.
Consequently, engineers adhere to a foundational design rule: build with wired interfaces by default to maximize speed, power efficiency, and simplicity, reserving wireless connectivity strictly for applications that demand mobility or remote access, such as wearables or isolated IoT nodes.
When Both Are Used Together
Many real embedded systems use both. The internal components communicate over wired interfaces, while the system as a whole communicates externally over wireless.
Quick Summary
- Wired: Physical conductor carries electrical signals - reliable, fast, deterministic
- Wireless: Electromagnetic waves carry modulated data - mobile, long-range, but variable
- Embedded systems prefer wired (UART, SPI, I2C, CAN) because timing must be deterministic
- Wireless adds RF stack complexity, regulatory certification, and power cost
- Most IoT nodes use wired internally and wireless only for the external uplink
- Use wireless only when the device genuinely needs mobility or remote range