What Is an ADC? Understanding Analog-to-Digital Converters for ESP32 and Arduino Sensors

An Analog-to-Digital Converter (ADC) is a hardware circuit that translates continuous real-world voltage signals into discrete binary numbers a microcontroller can process. When you wire a temperature sensor, a potentiometer, or a current monitor to your Arduino or ESP32, the ADC is the bridge that turns physical phenomena into math your code can act on. But introducing an ADC into a real circuit changes everything: it forces you to manage output impedance, scale voltages to match reference limits, and accept a baseline quantization error that dictates your maximum possible precision.

The Math: Resolution, Step Size, and Quantization

To understand what an ADC actually does, think of it like a staircase. The continuous voltage is a smooth ramp, but the ADC can only stand on specific stairs. The number of stairs is determined by the resolution (measured in bits).

Let's run a worked numeric example using the classic Arduino Uno (ATmega328P). This chip features a 10-bit ADC with a default reference voltage of 5V.

• Total Steps: 2^10 = 1024 discrete steps (numbered 0 to 1023).
• Step Size (LSB): 5.0V / 1024 = 4.88 millivolts per step.

If your analog sensor outputs exactly 2.15V, the ADC calculates the raw value by dividing the input voltage by the step size: 2.15V / 0.00488V = 440.5. Because the ADC can only output whole integers, it rounds to 440. When your code reads this value, it multiplies back: 440 * 0.00488V = 2.147V. That 0.003V difference is your quantization error. You can never eliminate it; you can only reduce it by using a higher-resolution ADC (like the 12-bit ADC on the ESP32, which offers 4096 steps) or a lower reference voltage.

Where You Meet ADCs in Practice

You will encounter ADCs anytime a microcontroller needs to monitor a physical environment. Common bench scenarios include:

1. NTC Thermistors: Used in voltage dividers to measure battery pack or 3D printer hot-end temperatures.
2. Potentiometers: Used for manual user inputs, like dimming an LED strip or setting a motor speed threshold.
3. Hall-Effect Current Sensors (e.g., ACS712-20A): Outputs a ratiometric voltage centered at VCC/2 to measure AC or DC current draw.
4. MQ-Series Gas Sensors: Changes resistance in the presence of volatile organic compounds, read via a load resistor.

Real-World Scenario Walkthrough: The ESP32 Thermistor Trap

The ESP32-WROOM-32 boasts a 12-bit ADC, which theoretically offers four times the resolution of an Arduino Uno. However, its internal architecture introduces non-linearities that catch many makers off guard. Here is a real-world failure scenario from the bench.

The Setup

You are building a battery temperature monitor using an ESP32 DevKit v1. You wire a 10kΩ NTC thermistor to GPIO 34 (an ADC1 input) with a 10kΩ pull-up resistor to the 3.3V pin. You write a simple Arduino IDE sketch using analogRead(34).

The Numbers

At exactly 25°C, the NTC thermistor's resistance is 10kΩ. Because it forms a perfect 1:1 voltage divider with the 10kΩ pull-up, the voltage at GPIO 34 should be exactly half of 3.3V: 1.65V.
With a 12-bit ADC (4096 steps) and a 3.3V reference, the expected raw reading is: (1.65 / 3.3) * 4095 = 2048.

The Outcome

You upload the code, open the Serial Monitor, and the raw reading bounces around 1750. Your code converts this to voltage (1750 / 4095 * 3.3 = 1.41V), calculates the thermistor resistance, and reports the battery temperature as 38°C—even though the room is 25°C and your multimeter confirms 1.65V at the pin.

What Went Wrong

The ESP32's ADC requires explicit attenuation settings to read voltages above ~1.1V accurately. By default, the ESP32 Arduino core often initializes ADC inputs with 0 dB attenuation, meaning the internal circuitry clips or severely distorts any voltage above 1.1V. Your 1.65V signal was being crushed by the front-end amplifier.

The Fix: In the Arduino IDE, you must explicitly set the attenuation before reading the pin:

void setup() {
  analogSetAttenuation(ADC_11db); // Allows safe reading up to ~3.3V
  Serial.begin(115200);
}

Even with 11 dB attenuation, the ESP32 ADC is notoriously non-linear near the 0V and 3.3V rails. For precision work (like a 3D printer PID controller), professional designs bypass the internal ESP32 ADC entirely and use an external I2C ADC like the ADS1115, which offers 16-bit resolution and a programmable gain amplifier.

ESP32 ADC Attenuation vs. Safe Voltage Ranges

If you are committed to using the ESP32's internal ADC, you must match your attenuation setting to your expected voltage range. According to the Espressif ESP-IDF Technical Reference, here are the safe operating windows:

Note: While 11 dB technically allows reading up to 3.3V, the ESP32's ADC curve flattens out above 2.5V. Design your voltage dividers to peak around 2.0V to 2.4V for the most accurate linear results.

Common Confusions: Resolution vs. Accuracy and ADC vs. DAC

When debugging sensor circuits, makers frequently mix up three distinct concepts:

• Resolution vs. Accuracy: A 16-bit ADC has a resolution of 65,536 steps. However, if the ADC has an Integral Non-Linearity (INL) error of ±4 LSBs, its accuracy is effectively only 14 bits. High resolution gives you smaller steps; high accuracy guarantees those steps are placed exactly where they should be on the voltage ruler.
• ADC vs. DAC: An ADC (Analog-to-Digital) reads the physical world into code. A DAC (Digital-to-Analog) does the reverse, outputting a smooth voltage from code to drive analog actuators or audio amplifiers. The Arduino Uno has an ADC but no true DAC (it fakes it with PWM). The ESP32 has both.
• Reference Voltage (VREF) vs. VCC: On many basic microcontrollers, the ADC compares the input pin against the main power rail (VCC). If your USB port sags from 5.0V to 4.7V under load, your ADC reference drops too, and your sensor readings will artificially spike. For stable readings, use a dedicated voltage reference IC (like the LM4040) connected to the microcontroller's AREF pin.

FAQ: Debugging Your ADC Readings