Decoding Capacitor Code 103: ESP32 Hardware Debouncing & Interrupt Debugging

If you are holding a small ceramic disc or multilayer capacitor stamped with the numbers 103, you are holding a 10nF (0.01µF, 10,000pF) capacitor. The first two digits (10) represent the significant figures, and the third digit (3) is the multiplier (10³). In embedded electronics, the 10nF capacitor is the undisputed workhorse for hardware switch debouncing, low-pass ADC filtering, and high-frequency bypass.

But what happens when you omit this tiny component, or use the wrong value? Your microcontroller crashes. Below, we break down the theory of the 103 capacitor, build a hardware-debounced interrupt circuit on the ESP32, and debug the exact kernel panics that occur when your RC time constant fails.

The Physics of Code 103: Why 10nF?

Capacitor coding follows a standardized three-digit system outlined in IEC 60062. For a 103 capacitor:

• Digit 1 & 2: 10 (Significant digits)
• Digit 3: 3 (Multiplier: 10³ or 1,000)
• Base Unit: Picofarads (pF)

Calculation: 10 × 1,000 pF = 10,000 pF. Since 1,000 pF = 1 nF, the final value is 10 nF (or 0.01 µF).

Why is 10nF the magic number for debouncing? A typical mechanical tactile switch bounces for 1 to 5 milliseconds upon actuation. By pairing a 10nF (103) capacitor with a 10kΩ pull-up resistor, you create an RC low-pass filter. The time constant (τ = R × C) is 10,000Ω × 0.00000001F = 100µs (0.1ms). It takes roughly 3τ to 5τ (0.3ms to 0.5ms) for the capacitor to discharge through the switch to a logic LOW. This smoothly pulls the voltage down, completely absorbing the 2ms mechanical bounce without delaying the user-perceptible response time.

Project Build: ESP32 Hardware Debounce & ADC Filter

We will wire a 103 capacitor to filter a mechanical switch connected to an ESP32 input, triggering an interrupt. We are specifically using GPIO 34, which is an input-only ADC pin on the ESP32-WROOM-32. Because GPIO 34 lacks an internal pull-up resistor, this build forces you to wire an external 10kΩ pull-up, making the 103 capacitor's filtering role critical.

Parts List & Specifications

Pin Mapping Table

Complete ESP32 Code with ISR Error Handling

The following code targets the ESP32 DevKit v1 board in the Arduino IDE (ESP32 Core v3.x). It uses a hardware-filtered interrupt. Notice the use of portENTER_CRITICAL_ISR to prevent race conditions, a necessary precaution when handling high-frequency GPIO interrupts on the ESP32's dual-core FreeRTOS architecture.

#include <Arduino.h>

// Pin Definitions
#define BTN_PIN 34      // Input-only ADC pin, requires external pull-up
#define LED_PIN 2       // Onboard LED for visual feedback

// Volatile variables for ISR communication
volatile bool buttonPressed = false;
volatile uint32_t lastIsrTime = 0;
portMUX_TYPE mux = portMUX_INITIALIZER_UNLOCKED;

// Interrupt Service Routine
void IRAM_ATTR handleButtonPress() {
  // Hardware debounce via 103 cap handles the physical bounce.
  // This software check prevents double-triggers from EMI spikes.
  uint32_t currentTime = xTaskGetTickCountFromISR();
  if ((currentTime - lastIsrTime) > pdMS_TO_TICKS(50)) {
    portENTER_CRITICAL_ISR(&mux);
    buttonPressed = true;
    lastIsrTime = currentTime;
    portEXIT_CRITICAL_ISR(&mux);
  }
}

void setup() {
  Serial.begin(115200);
  delay(1000); // Allow USB-CDC to enumerate
  Serial.println("ESP32 Hardware Debounce (103 Cap) Initialized.");

  // GPIO 34 has NO internal pull-up. We rely on the external 10k resistor.
  pinMode(BTN_PIN, INPUT); 
  pinMode(LED_PIN, OUTPUT);
  digitalWrite(LED_PIN, LOW);

  // Attach interrupt on FALLING edge (switch pulls GPIO 34 to GND)
  if (!attachInterrupt(digitalPinToInterrupt(BTN_PIN), handleButtonPress, FALLING)) {
    Serial.println("ERROR: Failed to attach interrupt to GPIO 34.");
    while(1) { delay(1000); } // Halt execution
  }
}

void loop() {
  if (buttonPressed) {
    portENTER_CRITICAL(&mux);
    buttonPressed = false;
    portEXIT_CRITICAL(&mux);
    
    digitalWrite(LED_PIN, !digitalRead(LED_PIN));
    Serial.printf("[OK] Button Press Registered. Free Heap: %u bytes\n", ESP.getFreeHeap());
  }
  
  // Simulate other RTOS tasks
  vTaskDelay(pdMS_TO_TICKS(10));
}

Debugging: Interrupt WDT Timeout & The Missing 103

What happens if you forget to solder the 103 capacitor across the switch, or if the capacitor fails open? The mechanical contacts will bounce for 3 to 10 milliseconds. On a 240MHz ESP32, this single button press will generate dozens of rapid FALLING edges, triggering the ISR repeatedly.

If your ISR is complex, or if the sheer volume of interrupts starves the FreeRTOS Idle Task (which is responsible for feeding the hardware watchdog), the system will crash. You will see this exact error string in your serial monitor:

Guru Meditation Error: Core 1 panic'ed (Interrupt wdt timeout on CPU1)

According to the Espressif ESP-IDF GPIO & Interrupt API, an interrupt watchdog timeout occurs when an ISR takes too long or fires so frequently that the CPU cannot service the RTOS tick. The 103 capacitor prevents this by physically holding the voltage above the logic LOW threshold until the mechanical bounce has completely settled.

The First Three Things to Check When It Fails

1. Verify the 103 Capacitance with an LCR Meter: Cheap, unbranded ceramic capacitors stamped "103" can drift wildly. Measure the component at 1kHz. If it reads below 6nF, the RC time constant is too short to absorb a 5ms switch bounce. Replace it with a name-brand X7R part.
2. Check the Pull-Up Resistor Value: If you accidentally used a 1MΩ resistor instead of 10kΩ, your time constant (τ) jumps from 0.1ms to 10ms. The capacitor will take 30ms to discharge, making the button feel "sluggish" and potentially causing missed rapid presses. Verify the resistor bands or measure with a multimeter.
3. Inspect Breadboard Parasitics: If you are using long, daisy-chained jumper wires between the switch and GPIO 34, you are introducing parasitic inductance and antenna-like EMI pickup. Keep the 103 capacitor and 10kΩ resistor physically within 5mm of the ESP32 GPIO pin to filter noise right at the silicon gate.

Extending and Simplifying the Circuit

To Simplify: If you are running low on board space and cannot fit an external 10kΩ pull-up resistor and a 103 capacitor, move your switch to GPIO 33 (or any GPIO below 32). These pins feature internal weak pull-ups (~45kΩ). You can enable it in code via pinMode(BTN_PIN, INPUT_PULLUP);. However, because the internal pull-up is 45kΩ, pairing it with a 103 (10nF) cap yields a τ of 0.45ms. This is still sufficient for debouncing, but the rising edge (release) will be slightly slower.

To Extend: If you are reading an analog sensor (like a potentiometer or LDR) on GPIO 34 instead of a digital switch, the 103 capacitor transitions from a debounce role to an anti-aliasing filter. By placing the 103 cap between the ADC pin and GND, you create a low-pass filter that cuts off high-frequency EMI (from nearby WiFi antennas or switching regulators) before it hits the ESP32's SAR ADC, drastically reducing jitter in your analogRead() values.

Frequently Asked Questions

Can I use a 104 capacitor instead of a 103 for debouncing?

A 104 capacitor is 100nF (0.1µF), which is ten times larger than a 103 (10nF). If you pair a 104 cap with a 10kΩ resistor, your time constant becomes 1ms. It will debounce the switch perfectly, but the voltage will take roughly 5ms to recover to a logic HIGH after you release the button. If your application requires rapid, repeated button presses (like a gaming controller or rotary encoder), the 104 will "swallow" fast inputs. Stick to the 103 for general tactile switches.

Why does my 103 capacitor have a third character like 'Z' or 'K' printed on it?

That letter indicates the capacitance tolerance and sometimes the temperature coefficient. A "K" means ±10% tolerance, while an "M" means ±20%. A "Z" often indicates a -20% / +80% tolerance typical of older Y5V dielectrics. For critical timing circuits, always look for a 103 capacitor with a "K" tolerance and an X7R dielectric code to ensure the value remains stable across your operating temperature range.

Does the polarity of the 103 capacitor matter?

No. Standard ceramic disc and multilayer ceramic capacitors (MLCC) stamped with 103 are non-polarized. You can insert them into the breadboard or solder them in either direction. However, if you are using a 10nF electrolytic or tantalum capacitor (rare for this specific value, but possible), it will have a polarity stripe or marking and must be wired with the anode to the higher voltage. Always default to non-polarized ceramics for high-frequency filtering and debouncing.

How do I read capacitor codes that only have two digits, like '47'?

If a ceramic capacitor only has two digits printed on it (e.g., 47), there is no multiplier. The value is simply the number shown in picofarads. Therefore, a capacitor stamped "47" is exactly 47pF. This is common for small-value capacitors used in RF oscillators or high-speed I2C bus filtering, whereas the three-digit 103 code is reserved for values 100pF and above.