Electronics & Communication Basics

By the end of this guide, you will:

• Reason about a circuit in terms of voltage, current, and resistance, and use Ohm's Law to size a resistor instead of guessing.
• Recognise which parts are polarized, and know that fitting one backwards is the most common beginner mistake.
• Explain what ground is, why every part of a circuit must share it, and what a short circuit actually is.
• Work in 3.3 V logic and know why 5 V on a GPIO pin can destroy the board.
• Respect the ESP32's current limits, so an LED gets a series resistor every time.
• Tell apart the three buses this kit uses: UART, I²C, and SPI.

There is nothing to wire here. This is the vocabulary every later project assumes.

A helpful model is water in pipes:

• Voltage is a difference between two points. "3.3 V" means 3.3 V relative to a reference: usually ground (GND, 0 V).
• Current is charge flow; here it's small: milliamps (mA) (1000 mA = 1 A).
• Resistance opposes current. Resistors are built to a specific value.

For a fixed voltage, more resistance → less current.

Why every LED gets a 220 Ω resistor

An LED barely resists current itself: straight across 3.3 V it draws too much and burns out. A series resistor limits the current. An LED drops ~2 V, leaving 1.3 V across the resistor:

I = V / R = (3.3 V − 2 V) / 220 Ω ≈ 0.006 A = 6 mA

6 mA is safe and bright: well under the ESP32's limits (§6). Power is P = V × I (watts); our circuits use tiny fractions of a watt, so parts stay cool.

Polarity means a connection has a + (higher voltage) side and a − (lower / ground) side. Some parts only work one way around.

Not polarized (either way): resistors, ceramic capacitors, pushbuttons.

• DC (Direct Current) flows one steady direction: batteries, USB, the ESP32. AC (wall outlets) reverses; we avoid it (except carefully via the relay in Project 7).
• The board takes 5 V from USB and regulates it to the 3.3 V the chip uses. Headers: VIN ≈ 5 V, 3V3 = 3.3 V, GND = 0 V.
• Ground is the shared 0 V reference. Every part connects to the same ground; two boards talking need a common ground.

Chips represent data as two voltage levels:

• HIGH ≈ 3.3 V = logic 1
• LOW ≈ 0 V = logic 0

Analog is different: a continuous range 0–3.3 V that the ESP32's ADC reads as 0–4095 (Project 2).

• ≤ 40 mA per GPIO absolute; keep ≤ ~12 mA in practice → always use series resistors for LEDs.
• Double‑check polarity before applying power.
• Build with the board unplugged, then power up.
• Keep a common ground across everything.
• When unsure, measure with a multimeter (voltage between two points; continuity to check a connection).

Reading a diagram: schematic vs. breadboard style

You'll see two kinds of wiring picture in this kit, and both describe the same circuit:

• A schematic uses symbols (a zigzag or box for a resistor, a triangle with a bar for an LED, a circle for a battery) joined by lines that mean electrically connected, not routed this way. Datasheets and most online tutorials use schematics. Project 7's relay diagram, showing the module's COM/NO/NC terminals, is this kit's clearest example.
• A breadboard diagram draws the real board, the real component shapes, and the real jumper‑wire paths, so you can copy it hole‑for‑hole. Every project's main wiring image in this kit (like Project 1's button‑and‑LED layout) is breadboard style, because there's no translation step between the picture and the parts in your hand.

Once you can read both, a schematic from a random datasheet is no harder than this kit's own breadboard diagrams: the symbols are the only new vocabulary.

Worked example: measure the 3.3 V rail and test continuity

1. Set the multimeter's dial to DC volts (a straight line next to the V, not a wavy one), red lead in the socket marked VΩmA, black lead in COM.
2. Power the ESP32 over USB. Touch the black probe to any GND pin and the red probe to the 3V3 pin: you should read close to 3.30 V. Move the red probe to VIN instead and you should read close to 5 V. Reading 0 V on either means the board isn't powered, or you're on the wrong pin.
3. To test continuity (whether two points are actually connected, e.g. a jumper wire or a solder joint), switch the dial to the continuity setting (a sound‑wave or diode symbol) and touch a probe to each end with the circuit unpowered. A beep means the connection is good; silence means it's broken somewhere in between.

This is the fastest way to answer "is my wiring actually doing what I think it's doing?" before you even open the Arduino IDE.

Sensors, displays, and the ESP32 exchange bits over shared wires. Three standards cover almost everything in this kit: libraries handle the details, but knowing them helps you wire correctly.

UART: simplest (asynchronous serial)

2 wires, TX and RX, cross‑connected. No clock: both sides agree on a baud rate (why the Serial Monitor is always 115200). Point‑to‑point; the USB Serial Monitor uses UART via the CP2102 chip.

I²C: few wires, many devices

2 shared wires: SDA (data) + SCL (clock): on the ESP32, GPIO 21 & 22. Each device has a unique address (the OLED is 0x3C), so many share the same pair. Needs pull‑ups (usually on‑module). The OLED (Project 10) uses I²C.

SPI: fast, more wires

4 wires: MOSI, MISO, SCK, plus a CS per device. Full‑duplex and fast: displays, SD cards, high‑rate sensors. ESP32 VSPI: MOSI 23, MISO 19, SCK 18, CS 5.

Want a deeper explanation of any idea above? These free, well‑illustrated guides are excellent starting points.

Fundamentals

• What is a circuit?
• Voltage, current, resistance & Ohm's Law
• Electric power
• Resistors
• LEDs
• Polarity
• AC vs. DC
• Analog vs. digital
• Logic levels (3.3 V vs 5 V)

Tools

• How to use a breadboard
• How to use a multimeter

Communication buses

• UART / serial communication
• I²C
• SPI

ESP32‑specific

• ESP32 pinout reference (Random Nerd Tutorials)
• Our own GPIO Reference and Components Glossary.

External links open on third‑party sites and were chosen for being clear and beginner‑friendly.

None of this is trivia. Every rule here exists because breaking it breaks hardware, and each one comes back in a later project:

• V = I × R is the whole toolkit for the passive parts. It is how you get 220 Ω for an LED rather than a number someone told you (Project 1).
• Voltage is always relative. "3.3 V" means 3.3 V above ground, which is why every device must share a common ground. A sensor reading nonsense usually has a missing GND wire.
• Polarity matters for LEDs, electrolytic capacitors, and modules. A backwards LED does not light and gives no other clue.
• The ESP32 is a 3.3 V device. Its GPIO pins are not 5 V tolerant. VIN supplies 5 V for parts that need it (the PIR in Project 4), but nothing at 5 V may drive a GPIO directly.
• Current has limits: roughly 12 mA per pin as a safe working figure. A series resistor on every LED is a habit, not a calculation you redo each time.
• Digital is two values, analog is a range. That single distinction separates Project 1 (digitalRead) from Project 2 (analogRead) and Project 3 (PWM faking an analog output).
• Chips talk over buses. UART is the serial monitor, I²C is two shared wires with addresses (the OLED in Project 10), SPI is faster and uses more pins.

If a later project misbehaves, the cause is far more often one of these six ideas than a bug in the code.

With these fundamentals you can reason about every circuit in the kit. Next:

1. Foundation 2: Introduction & Board Tour
2. Foundation 3: Arduino IDE Setup
3. Project 1: Inputs & Outputs