Debouncing a button in software in Arduino - Mini Project: Build & Apply

Debouncing a button in software

📖 Scenario: You have a button connected to an Arduino. When you press the button, the Arduino should detect the press correctly without mistakes caused by the button's mechanical noise.

🎯 Goal: Build a simple Arduino program that reads a button press and uses software debouncing to avoid false multiple detections.

📋 What You'll Learn

Create a variable to store the button pin number.

Create a variable to store the button state.

Create a variable to store the last button reading.

Create a variable to store the last debounce time.

Create a constant for debounce delay.

Read the button input and apply software debouncing logic.

Print "Button pressed" only once per press.

💡 Why This Matters

🌍 Real World

Buttons often produce noisy signals when pressed. Debouncing in software helps microcontrollers read button presses correctly, avoiding errors in devices like remote controls, keyboards, and user interfaces.

💼 Career

Understanding debouncing is important for embedded systems developers, hardware engineers, and anyone working with physical buttons and microcontrollers.

1

Set up button pin and initial variables

Create an int variable called buttonPin and set it to 2. Create an int variable called buttonState and set it to LOW. Create an int variable called lastButtonState and set it to LOW.

Arduino

int buttonPin = 2;
int buttonState = LOW;
int lastButtonState = LOW;
// Your code here

Hint

Use int to create variables and assign the exact values given.

2

Add debounce timing variables

Create an unsigned long variable called lastDebounceTime and set it to 0. Create a const unsigned long variable called debounceDelay and set it to 50.

Arduino

int buttonPin = 2;
int buttonState = LOW;
int lastButtonState = LOW;
unsigned long lastDebounceTime = 0;
const unsigned long debounceDelay = 50;
// Your code here

Hint

Use unsigned long for timing variables and set the debounce delay to 50 milliseconds.

3

Write the debouncing logic inside loop()

Inside the loop() function, read the button input using digitalRead(buttonPin) and store it in a variable called reading. If reading is different from lastButtonState, update lastDebounceTime to millis(). If the time since lastDebounceTime is greater than debounceDelay, and reading is different from buttonState, update buttonState to reading. If buttonState is HIGH, print "Button pressed". Finally, update lastButtonState to reading.

Arduino

int buttonPin = 2;
int buttonState = LOW;
int lastButtonState = LOW;
unsigned long lastDebounceTime = 0;
const unsigned long debounceDelay = 50;

void setup() {
  pinMode(buttonPin, INPUT);
  Serial.begin(9600);
}

void loop() {
  // Read the button input and apply debounce logic
  // Your code here
}

Hint

Follow the debounce steps carefully: detect change, wait for delay, then confirm button press.

4

Print the debounced button press

Make sure the program prints "Button pressed" only once each time the button is pressed.

Arduino

int buttonPin = 2;
int buttonState = LOW;
int lastButtonState = LOW;
unsigned long lastDebounceTime = 0;
const unsigned long debounceDelay = 50;

void setup() {
  pinMode(buttonPin, INPUT);
  Serial.begin(9600);
}

void loop() {
  int reading = digitalRead(buttonPin);

  if (reading != lastButtonState) {
    lastDebounceTime = millis();
  }

  if ((millis() - lastDebounceTime) > debounceDelay) {
    if (reading != buttonState) {
      buttonState = reading;

      if (buttonState == HIGH) {
        Serial.println("Button pressed");
      }
    }
  }

  lastButtonState = reading;

  // Your code here
}

Hint

Press the button once and check the serial monitor to see the message printed only once.

Practice

1. What is the main purpose of debouncing a button in software on an Arduino?

easy

A. To ignore rapid, repeated signals caused by mechanical noise

B. To increase the button press speed

C. To make the button LED blink faster

D. To reduce power consumption of the Arduino

Solution

1. Step 1: Understand button noise

   Mechanical buttons create multiple quick signals when pressed due to bouncing contacts.

2. Step 2: Purpose of debouncing

   Debouncing filters these quick repeated signals to register only one clean press.

3. Final Answer:

   To ignore rapid, repeated signals caused by mechanical noise -> Option A

4. Quick Check:

   Debouncing = Ignore noise [OK]

Hint: Debouncing stops false multiple presses from one button push [OK]

Common Mistakes:

• Thinking debouncing speeds up button presses
• Confusing debouncing with power saving
• Assuming debouncing controls LED blinking

2. Which Arduino function is commonly used to measure time for software debouncing?

easy

A. delay()

B. analogWrite()

C. digitalRead()

D. millis()

Solution

1. Step 1: Identify timing functions

   delay() pauses the program but is not ideal for debouncing timing checks.

2. Step 2: Use millis() for non-blocking timing

   millis() returns the time since the program started, allowing to check elapsed time without stopping code.

3. Final Answer:

   millis() -> Option D

4. Quick Check:

   Debounce timing uses millis() [OK]

Hint: Use millis() to track time without stopping code [OK]

Common Mistakes:

• Using delay() which blocks code execution
• Confusing digitalRead() with timing
• Using analogWrite() which controls PWM output

3. What will be the output on the serial monitor if the following code is run and the button is pressed once?

const int buttonPin = 2;
int buttonState = 0;
unsigned long lastDebounceTime = 0;
unsigned long debounceDelay = 50;

void setup() {
  pinMode(buttonPin, INPUT);
  Serial.begin(9600);
}

void loop() {
  int reading = digitalRead(buttonPin);
  if (reading != buttonState) {
    lastDebounceTime = millis();
  }
  if ((millis() - lastDebounceTime) > debounceDelay) {
    if (reading != buttonState) {
      buttonState = reading;
      if (buttonState == HIGH) {
        Serial.println("Button pressed");
      }
    }
  }
}

medium

A. Button pressed printed multiple times rapidly

B. Button pressed printed once

C. Syntax error, code won't compile

D. No output printed

Solution

1. Step 1: Analyze initial buttonState and reading

   buttonState starts at 0 (LOW). If button is pressed, reading becomes HIGH (1).

2. Step 2: Check debounce logic

   The code updates lastDebounceTime when reading differs from buttonState, and after debounce delay, if reading still differs, buttonState updates and prints.

3. Step 3: Confirm output

   After debounce delay, buttonState updates and "Button pressed" is printed once.

4. Final Answer:

   Button pressed printed once -> Option B

5. Quick Check:

   Debounce logic allows one print after stable press [OK]

Hint: Debounce logic prints once after stable press [OK]

Common Mistakes:

• Assuming print happens immediately on press
• Ignoring debounce delay effect
• Thinking code has syntax errors

4. Identify the error in this debounce code snippet and select the fix:

const int buttonPin = 3;
int buttonState = LOW;
unsigned long lastDebounceTime = 0;
unsigned long debounceDelay = 50;

void loop() {
  int reading = digitalRead(buttonPin);
  if (reading != buttonState) {
    lastDebounceTime = millis();
  }
  if ((millis() - lastDebounceTime) > debounceDelay) {
    buttonState = reading;
    if (buttonState == HIGH) {
      Serial.println("Pressed");
    }
  }
}

medium

A. Initialize buttonState as HIGH instead of LOW

B. Move buttonState = reading inside the first if block

C. Add pinMode(buttonPin, INPUT_PULLUP) in setup()

D. Change debounceDelay to 5000 for longer delay

Solution

1. Step 1: Check hardware setup assumptions

   Without enabling INPUT_PULLUP, the button pin may float causing unreliable readings.

2. Step 2: Importance of INPUT_PULLUP

   Using INPUT_PULLUP activates internal pull-up resistor, stabilizing input and making debounce logic reliable.

3. Final Answer:

   Add pinMode(buttonPin, INPUT_PULLUP) in setup() -> Option C

4. Quick Check:

   Use INPUT_PULLUP for stable button input [OK]

Hint: Use INPUT_PULLUP to avoid floating pin errors [OK]

Common Mistakes:

• Changing initial buttonState without hardware reason
• Moving state update incorrectly breaking debounce logic
• Setting too long debounce delay unnecessarily

5. You want to detect a single button press and toggle an LED state only once per press using software debounce. Which approach below correctly implements this behavior?

const int buttonPin = 4;
const int ledPin = 13;
int ledState = LOW;
int lastButtonState = LOW;
unsigned long lastDebounceTime = 0;
unsigned long debounceDelay = 50;

void setup() {
  pinMode(buttonPin, INPUT_PULLUP);
  pinMode(ledPin, OUTPUT);
  digitalWrite(ledPin, ledState);
  Serial.begin(9600);
}

void loop() {
  int reading = digitalRead(buttonPin);
  if (reading != lastButtonState) {
    lastDebounceTime = millis();
  }
  if ((millis() - lastDebounceTime) > debounceDelay) {
    if (reading != lastButtonState) {
      lastButtonState = reading;
      if (lastButtonState == LOW) {
        ledState = !ledState;
        digitalWrite(ledPin, ledState);
        Serial.println(ledState ? "LED ON" : "LED OFF");
      }
    }
  }
}

hard

A. This code toggles LED once per press correctly

B. LED toggles multiple times due to missing debounce

C. LED never toggles because lastButtonState is not updated

D. Code causes syntax error due to missing semicolons

Solution

1. Step 1: Check debounce timing logic

   The code updates lastDebounceTime when reading changes, then waits debounceDelay before accepting new state.

2. Step 2: Confirm state update and toggle

   Inside debounce check, lastButtonState updates to reading, and LED toggles only when button is pressed (LOW due to INPUT_PULLUP).

3. Step 3: Verify output and toggle behavior

   LED state flips once per valid press, and serial prints correct status.

4. Final Answer:

   This code toggles LED once per press correctly -> Option A

5. Quick Check:

   Debounce + toggle once per press = Correct [OK]

Hint: Toggle LED only when stable press detected after debounce [OK]

Common Mistakes:

• Not updating lastButtonState causing repeated toggles
• Ignoring debounce delay causing multiple toggles
• Confusing HIGH/LOW logic with INPUT_PULLUP