When building analog sensor interfaces, verifying your potentiometer wiring Arduino connections before uploading code saves hours of debugging. A potentiometer is fundamentally a three-terminal voltage divider. If wired correctly to a 5V microcontroller, the outer lugs provide the reference voltage and ground, while the middle wiper outputs a variable voltage from 0V to 5V. To verify this, you must measure 10kΩ across the outer lugs on the bench, then measure a smooth 0.00V to 5.00V sweep at the wiper under live power.

This guide walks through the exact multimeter setups, probe placements, and expected numeric readings to validate your circuit, whether you are using a classic Arduino Uno R3 or an ESP32.

Multimeter Setup and Safety Categories for 5V Logic

Before probing your breadboard, configure your meter correctly. While an Arduino operates at Safety Extra Low Voltage (SELV) — typically 5V DC or 3.3V DC — your multimeter's safety rating still matters if it is a general-purpose bench tool that might accidentally contact mains voltage later.

Meter Setup Block: Resistance & Voltage Testing
  • Dial Position: Ω (Ohms/Resistance) for de-energized bench testing; V⎓ (DC Voltage) for live circuit verification.
  • Lead Jacks: Black lead in COM; Red lead in V/Ω (never the 10A current jack, which will short your 5V rail to ground).
  • Range: Auto-ranging preferred. If manual, set to the 20kΩ range for resistance, and 20V DC range for live voltage.
Safety Category (CAT) Note: For purely low-voltage DC breadboard work, a CAT I or CAT II rated meter is technically sufficient. However, industry best practice dictates using a minimum CAT II 600V or CAT III 300V rated multimeter (like a Fluke 117 or Brymen BM235) for all bench work. This ensures the meter has adequate internal fusing and creepage distances to protect you if you inadvertently use the same meter on a 120V/240V AC mains circuit later without changing your mental safety model.

Bench-Testing the Potentiometer (De-energized)

Never assume a new component is flawless, and never assume your breadboard contacts are clean. Before applying power to your microcontroller, test the potentiometer in isolation. The table below outlines the exact probe placements and expected readings for a standard 10kΩ linear taper potentiometer (e.g., Bourns 3386P-1-103LF cermet trimmer or an Alpha RD901F panel-mount pot).

Table 1: De-energized Resistance Verification (10kΩ Linear Pot)
Test Point & Probe Placement Knob Position Expected Good Reading Bad Reading & Failure Mode
Lug 1 to Lug 3
(Red on 1, Black on 3)		 Any position 9.50kΩ - 10.50kΩ OL / Infinite (Open track) or < 1Ω (Shorted)
Lug 1 to Wiper (Lug 2)
(Red on 1, Black on 2)		 Fully CCW to Fully CW 0.00Ω smoothly sweeping to 10.00kΩ Jumpy/erratic values (Dirty carbon track or worn wiper)
Lug 3 to Wiper (Lug 2)
(Red on 3, Black on 2)		 Fully CW to Fully CCW 0.00Ω smoothly sweeping to 10.00kΩ Stuck at 10kΩ (Wiper not making contact)
Wiper to Metal Case
(Red on 2, Black on chassis)		 Any position OL (Infinite Resistance) Any value < 1MΩ (Internal short to chassis ground)

If your Lug 1-to-Wiper reading stutters or jumps by hundreds of ohms while turning the knob slowly, the resistive element is degraded. In audio or precision analog applications, this translates to severe scratchiness or ADC jitter. Replace the component.

Verifying Potentiometer Wiring Arduino Connections Under Power

Once the bench test passes, wire the potentiometer to your microcontroller. The standard configuration for an Arduino Uno R3 is:

  • Lug 1: GND (Ground)
  • Lug 3: 5V (or 3.3V depending on your board's logic level)
  • Wiper (Lug 2): Analog Input Pin (e.g., A0)

Switch your multimeter to V⎓ (DC Voltage). Place the black probe on a known good Arduino GND pin, and the red probe directly on the wiper lug (or the breadboard row connected to A0). Power the Arduino via USB or the barrel jack.

What a Good Reading Looks Like Numerically

A properly wired 10kΩ potentiometer on a 5V Arduino Uno should yield the following voltage readings at the wiper as you rotate the shaft. A "good" reading is stable, with a maximum delta of ±0.02V when holding the knob still.

Table 2: Live DC Voltage Sweep (5V Reference)
Knob Position Expected DC Voltage Expected Arduino ADC Value (10-bit)
0% (Fully CCW / GND side) 0.00V - 0.02V 0 - 4
25% Rotation 1.23V - 1.27V 250 - 260
50% Rotation (Mechanical Center) 2.48V - 2.52V 505 - 515
100% (Fully CW / 5V side) 4.98V - 5.02V 1018 - 1023

Mistakes That Give Misleading Readings

If your multimeter readings deviate from the table above, you have a wiring or power fault. Here are the most common culprits:

  • Floating Ground: If Lug 1 is not securely connected to the Arduino GND, the wiper voltage will float randomly (often reading between 1.5V and 3.5V) due to capacitive coupling and electromagnetic interference from your body. Fix: Verify continuity from Lug 1 to the USB shield ground.
  • Swapped Wiper and Outer Lug: If you accidentally wire the wiper to 5V and an outer lug to A0, turning the knob will not change the voltage at A0. Instead, it will act as a variable resistor pulling down the 5V rail, potentially causing microcontroller brownouts. Fix: Always identify the wiper using the bench resistance test in Table 1 before wiring.
  • USB Power Sag: If your 100% reading is only 4.60V, your Arduino's USB power source is sagging under load. The analogRead() function uses the supply voltage as its default reference. A sagging 5V rail means your ADC values will still max out at 1023, but your actual voltage resolution is degraded.

Troubleshooting Misleading Readings and ESP32 ADC Non-Linearity

A frequent point of confusion occurs when the multimeter reads a perfectly stable 2.50V at the wiper, but the Arduino Serial Monitor shows analogRead() values bouncing erratically between 505 and 518.

This is not necessarily a wiring fault. It is a combination of ADC quantization noise, USB power ripple, and the high output impedance of a 10kΩ voltage divider. The Arduino analogRead documentation recommends an input impedance of 10kΩ or less for accurate sampling. If you are using a 100kΩ potentiometer to save power, the internal sample-and-hold capacitor of the ATmega328P cannot charge fully during the conversion clock cycles, resulting in jitter.

Hardware Fix for ADC Jitter: Solder or breadboard a 0.1µF (100nF) ceramic capacitor directly between the wiper pin and GND. This creates a low-pass RC filter that stabilizes the voltage and provides a local charge reservoir for the ADC sampling capacitor, eliminating software-level noise without needing complex moving-average algorithms.

The ESP32 ADC Trap: Non-Linearity at the Top End

If you are transitioning your potentiometer wiring from an Arduino Uno to an ESP32 DevKit v1 (or similar ESP32-WROOM-32 board), your multimeter will reveal a harsh reality about the ESP32's internal ADC.

The ESP32 operates at 3.3V logic. You must wire Lug 3 to the 3.3V pin, never the 5V (VIN) pin, or you will permanently destroy the ESP32's GPIO pin. However, even with correct 3.3V wiring, the ESP32's ADC1 is notoriously non-linear.

As you sweep the potentiometer to 100%, your multimeter will read 3.30V at the wiper. But the ESP32's analogRead() (which is 12-bit, 0-4095) will typically saturate and max out around an ADC value of 3800 to 3900 (equivalent to ~3.1V). The Espressif ESP-IDF ADC documentation explicitly notes this hardware limitation. If your project requires the full 0-4095 range across the physical rotation of the knob, you must either:

  1. Use an external I2C ADC like the ADS1115.
  2. Implement a software calibration curve using analogReadMilliVolts() and ESP-IDF eFuse calibration data.
  3. Physically restrict the potentiometer's mechanical rotation to 90% to stay within the linear region of the ESP32's ADC.

By combining de-energized resistance checks with live DC voltage sweeps, you eliminate 90% of hardware bugs before writing a single line of C++ code. Always trust the multimeter's numeric readout over the serial monitor when diagnosing analog sensor wiring.