Core Networking · Study deck

Wired Communication Fundamentals

A controller reads a slow temperature probe while refreshing a display and printing debug records.

Packet Pete is your guide for this deck.

wiredcomm
iotclass.org

After studying this chapter

Learning objectives

You will be able to:

  • Explain: A point-to-point, modest-rate pair may make UART the simplest choice; an addressed short bus points toward I2C, while high-rate full-duplex peripherals may justify SPI and extra selects.
  • Explain: The second is a shared pair that several peripherals sit on at once, which is what makes addressing and electrical loading a design problem rather than a wiring detail.
  • Explain: The record should state who controls the turn, how long the bus must settle, what happens on simultaneous transmission, and whether the measured workload includes those gaps.
  • record field evidence for wired-link reliability
The selection route should reject buses that do not meet physical or traffic constraints.
The selection route should reject buses that do not meet physical or traffic constraints.
iotclass.org

Major section

Start With Why a Wire Is Still Useful

A microcontroller is a small computer that reads devices and controls local work.

  • A protocol is an agreed set of exchange rules.
  • Universal asynchronous receiver-transmitter (UART), inter-integrated circuit (I2C), and serial peripheral interface (SPI) are three common ways to connect nearby parts.
  • The debug link needs simple point-to-point access.

Key terms

Wireless links
Wireless links are convenient, but wires still solve hard IoT problems: predictable timing, power delivery, noise control, security boundaries, and simple commissioning.
iotclass.org

Major section

Start With Why a Wire Is Still Useful (continued)

The deeper sections explain framing, addressing, pull-ups, timing, discovery, and stronger links for long or noisy cable runs.

  • The sensors can share a short addressed bus.
  • The display needs fast transfers and a separate select line.
  • One wire choice does not fit all three jobs.
Board-level serial buses and longer-distance wired standards solve different problems.
Board-level serial buses and longer-distance wired standards solve different problems.
iotclass.org

Major section

Start With Why a Wire Is Still Useful (continued)

These checks do not prove that data is true after it leaves the board.

  • Wireless links are convenient, but wires still solve hard IoT problems: predictable timing, power delivery, noise control, security boundaries, and simple commissioning.
  • The choice is not old versus new; it is which physical path gives the system enough trust.
  • UART, I2C, SPI, Ethernet, and industrial wiring each make different promises about distance, speed, topology, timing, and evidence.
Board-level serial buses and longer-distance wired standards solve different problems.
Board-level serial buses and longer-distance wired standards solve different problems.
iotclass.org

Major section

Overview: Wired Links Are Local Design Contracts

The second is a shared pair that several peripherals sit on at once, which is what makes addressing and electrical loading a design problem rather than a wiring detail.

  • The third spends more wires to buy speed and adds a select line for every device, so the wire count grows with the peripheral list.

Key terms

UART
UART is shown point to point, so its wiring is direct and a fault usually affects that pair.

Why it matters

Without it the other three prove nothing, because the signal levels have nothing agreed to be measured against.

Local wired protocols connect board-level peripherals before traffic ever reaches an IP network.
Local wired protocols connect board-level peripherals before traffic ever reaches an IP network.
iotclass.org

Major section

Overview: Wired Links Are Local Design Contracts (continued)

UART is shown point to point, so its wiring is direct and a fault usually affects that pair.

  • More wires can support full-duplex transfer, simpler timing, or higher throughput, but each pin consumes package, connector, and board-routing space.
  • The useful comparison is therefore not speed alone.
  • Both methods still face wire limits.
Duplex mode determines whether both sides can talk at once or must take turns.
Duplex mode determines whether both sides can talk at once or must take turns.
iotclass.org

Major section

Overview: Wired Links Are Local Design Contracts (continued)

Device count changes the cost again: I2C shares two signals, while basic SPI usually adds a select per peripheral.

  • Distance, traffic direction, pin budget, electrical loading, debugging access, and fault isolation decide whether the extra signals buy anything the product needs.
  • The cable side adds driver chips, set signal levels, line ends, or plugs.
  • A familiar plug can still join two parts that will harm each other.
  • The other side has no clock line.
Duplex mode determines whether both sides can talk at once or must take turns.
Duplex mode determines whether both sides can talk at once or must take turns.
iotclass.org

Major section

Overview: Wired Links Are Local Design Contracts (continued)

A point-to-point, modest-rate pair may make UART the simplest choice; an addressed short bus points toward I2C, while high-rate full-duplex peripherals may justify SPI and extra selects.

  • The last check is available pins and recovery behaviour.
  • SPI shares clock and data while giving peripherals separate select lines; that raises routing cost but helps isolate selection.
  • The controller's clock edge sets both the rate and sample time.
Duplex mode determines whether both sides can talk at once or must take turns.
Duplex mode determines whether both sides can talk at once or must take turns.
iotclass.org

Major section

Overview: Wired Links Are Local Design Contracts (continued)

Device count, connector boundaries, pull-ups, inactive-driver behaviour, and the required recovery method should travel with the chosen topology.

  • A start bit lines up the local clock for one frame, and stop bits check whether the two clocks stayed close.
  • Delay and poor edges hurt a clocked bus, while a baud mismatch grows across a frame.
  • That difference changes more than peak rate.
Duplex mode determines whether both sides can talk at once or must take turns.
Duplex mode determines whether both sides can talk at once or must take turns.
iotclass.org

Major section

Overview: Wired Links Are Local Design Contracts (continued)

The full-duplex panel gives each direction an independent path, so both endpoints can send at the same time without sharing a transmit turn.

  • Half-duplex reuses a path and requires alternation, which adds direction control, turnaround time, and a collision or arbitration rule.
  • A request-and-response sensor may fit half-duplex well, while continuous bidirectional streaming may not.
  • The record should state who controls the turn, how long the bus must settle, what happens on simultaneous transmission, and whether the measured workload includes those gaps.
Duplex mode determines whether both sides can talk at once or must take turns.
Duplex mode determines whether both sides can talk at once or must take turns.
iotclass.org

Major section

Budget the Debug Port and the Display Separately

For an illustrative asynchronous debug connection at 9,600 bits per second, use one start bit, eight data bits and one stop bit per byte.

  • Each useful byte therefore needs ten wire bits.
  • A 40-byte line takes 400 divided by 9,600 = about 0.0417 s, or 41.7 ms, before gaps.
  • Printing many such lines can block a simple program even though the sensor itself is slow.
  • The raw shift time is 8,192 divided by 1,000,000 = 0.008192 s, or 8.192 ms.
Topology drives both wiring effort and fault behavior.
Topology drives both wiring effort and fault behavior.
iotclass.org

Major section

Budget the Debug Port and the Display Separately (continued)

The comparison explains why a clocked peripheral link can suit the display while the debug port remains simple and separate.

  • A shared sensor bus saves pins but gives a stuck device a way to affect neighbours.
  • The synchronous-versus-asynchronous figure then explains which timing comes from a shared clock and which comes from framing.
  • Extra capacitance, noise and ground differences can violate the interface's electrical limits even when the bit-rate calculation still fits.
  • The calculations are useful upper-level budgets; a logic trace and the component timing requirements establish what the connected hardware actually tolerates.
iotclass.org

Major section

Summary

Wired communication is the local contract between an IoT controller and nearby peripherals.

  • UART, I2C, SPI, and longer-distance serial standards differ in clocking, topology, pin count, throughput, bus ownership, and electrical limits.
  • The right choice depends on the peripheral's supported interfaces, required data movement, available pins, distance, grounding, noise, and validation evidence.
iotclass.org

Deck summary

Key takeaways

A microcontroller is a small computer that reads devices and controls local work.

  • The deeper sections explain framing, addressing, pull-ups, timing, discovery, and stronger links for long or noisy cable runs.
  • These checks do not prove that data is true after it leaves the board.
  • The second is a shared pair that several peripherals sit on at once, which is what makes addressing and electrical loading a design problem rather than a wiring detail.
  • UART is shown point to point, so its wiring is direct and a fault usually affects that pair.
iotclass.org

Retrieval practice

Recall check 1 of 4

Packet Pete says: answer from memory, then check your reasoning.

Q1A wearable board has three low-rate sensors on the same PCB and very few spare microcontroller pins. Which wired bus is the best first candidate?

ASPI, because short transactions leave the processor more time to sleep between sensor reads.
BI2C, because multiple addressed sensors can share the same data and clock wires.
CUART on a shared data line, because it avoids needing a separate clock signal.
DRS-485, because differential signaling improves noise rejection when several devices share a link.
Show answer

Answer: B A same-board, low-rate, pin-limited sensor group is the classic reason to start with I2C.

iotclass.org

Retrieval practice

Recall check 2 of 4

Packet Pete says: answer from memory, then check your reasoning.

Q2A board has three low-rate I2C-capable sensors, a TFT display that needs frequent screen updates, and a microSD card. Which selection record is strongest?

APut the peripherals on I2C and slow TFT updates because the shared bus can carry each device's traffic.
BPut I2C-only sensors on SPI and add chip selects they cannot use.
CUse I2C sensors and SPI display and microSD, checking pins and bus loading.
DUse UART for all peripherals through one shared board debug link.
Show answer

Answer: C A defensible wired selection can mix buses when different peripherals have different traffic, pin, and electrical needs.

iotclass.org

Retrieval practice

Recall check 3 of 4

Packet Pete says: answer from memory, then check your reasoning.

Q3A wired sensor bus passes on a bench but fails after installation. Which record is most useful for finding the cause?

ARecord advertised bus speed alone instead of installed edges and fault timing.
BRecord dashboard's last value alone without electrical or timing evidence.
CScope installed cable edges, voltage and errors beside nearby site events.
DRecord an unpowered bench photo alone without installed signal traces.
Show answer

Answer: C These measurements connect the failure to electrical and timing conditions at the site.

iotclass.org

Retrieval practice

Recall check 4 of 4

Packet Pete says: answer from memory, then check your reasoning.

Q4A prototype works on short jumper wires, but the installed device sometimes corrupts I2C sensor readings when a nearby SPI display refreshes. What evidence should the team collect first?

AAdd a cloud dashboard first, because corrupted readings can be repaired after upload.
BScope I2C routing, pull-ups, capacitance, ground reference, and nearby SPI edges.
CSeparate display and sensor controllers, then compare whether the read errors disappear.
DMeasure errors after raising the I2C clock to shorten exposure to display activity.
Show answer

Answer: B Wired-bus failures often require electrical evidence: routing, pull-ups, capacitance, grounding, clock edges, and real installation conditions.

iotclass.org

Print reference

Answers

Answer key.

  1. B · A same-board, low-rate, pin-limited sensor group is the classic reason to start with I2C.
  2. C · A defensible wired selection can mix buses when different peripherals have different traffic, pin, and electrical needs.
  3. C · These measurements connect the failure to electrical and timing conditions at the site.
  4. B · Wired-bus failures often require electrical evidence: routing, pull-ups, capacitance, grounding, clock edges, and real installation conditions.
iotclass.org