Why attachInterrupt() function in Arduino? - Purpose & Use Cases

The Big Idea

What if your Arduino could instantly react to events without wasting time checking again and again?

The Scenario

Imagine you want your Arduino to notice when a button is pressed, but you also want it to keep doing other tasks at the same time. If you check the button by constantly asking its state in your main program, you might miss quick presses or slow down other important work.

The Problem

Manually checking the button state over and over wastes time and can miss fast events. It makes your program slow and unreliable because it's busy watching the button instead of doing other things.

The Solution

The attachInterrupt() function lets your Arduino instantly react to changes like button presses without stopping other tasks. It listens quietly in the background and triggers a small special function only when needed, making your program faster and smarter.

Before vs After

✗ Before

void loop() {
  if (digitalRead(buttonPin) == HIGH) {
    // handle button press
  }
}

✓ After

attachInterrupt(digitalPinToInterrupt(buttonPin), handlePress, RISING);

void handlePress() {
  // handle button press
}

What It Enables

This lets your Arduino respond immediately to events while still running other code smoothly, like multitasking in real life.

Real Life Example

Think of a doorbell that rings instantly no matter what you're doing. Using attachInterrupt(), your Arduino can react to the doorbell press right away, even if it's busy with other tasks.

Key Takeaways

Manually checking inputs wastes time and can miss quick events.

attachInterrupt() listens for events in the background and triggers code instantly.

This makes your Arduino programs faster, more reliable, and able to multitask.

Practice

1. What is the main purpose of the attachInterrupt() function in Arduino?

easy

A. To start the main program loop

B. To set the baud rate for serial communication

C. To run a function automatically when a specific pin changes state

D. To declare a variable as volatile

Solution

1. Step 1: Understand the role of attachInterrupt()

   The function attachInterrupt() is used to make Arduino respond immediately when a pin changes, without waiting for the main loop.

2. Step 2: Identify the correct purpose

   It triggers a specific function automatically on pin state changes, unlike other options which are unrelated to interrupts.

3. Final Answer:

   To run a function automatically when a specific pin changes state -> Option C

4. Quick Check:

   attachInterrupt() triggers functions on pin changes [OK]

Hint: attachInterrupt() runs code on pin change instantly [OK]

Common Mistakes:

• Confusing attachInterrupt() with serial communication setup
• Thinking it starts the main loop
• Mixing it with variable declarations

2. Which of the following is the correct syntax to attach an interrupt on pin 2 that triggers on a rising edge and calls the function handleInterrupt?

easy

A. attachInterrupt(2, handleInterrupt, RISING);

B. attachInterrupt(digitalPinToInterrupt(2), handleInterrupt, RISING);

C. attachInterrupt(handleInterrupt, 2, RISING);

D. attachInterrupt(2, RISING, handleInterrupt);

Solution

1. Step 1: Recall correct attachInterrupt() syntax

   The correct syntax uses digitalPinToInterrupt(pin) to convert the pin number to an interrupt number.

2. Step 2: Match parameters order

   The order is: interrupt number, function name, mode (like RISING). Only attachInterrupt(digitalPinToInterrupt(2), handleInterrupt, RISING); follows this correctly.

3. Final Answer:

   attachInterrupt(digitalPinToInterrupt(2), handleInterrupt, RISING); -> Option B

4. Quick Check:

   Use digitalPinToInterrupt(pin) for correct interrupt number [OK]

Hint: Use digitalPinToInterrupt(pin) for correct interrupt number [OK]

Common Mistakes:

• Passing pin number directly without digitalPinToInterrupt()
• Mixing parameter order
• Using pin number instead of interrupt number

3. What will be the output on the serial monitor after pressing the button connected to pin 2 once, given this code?

volatile int count = 0;

void setup() {
  Serial.begin(9600);
  pinMode(2, INPUT_PULLUP);
  attachInterrupt(digitalPinToInterrupt(2), incrementCount, FALLING);
}

void loop() {
  Serial.println(count);
  delay(500);
}

void incrementCount() {
  count++;
}

medium

A. The count will increase continuously without button presses

B. The count will stay 0 because interrupts are not enabled

C. The program will crash due to volatile misuse

D. The count will increase by 1 each time the button is pressed

Solution

1. Step 1: Analyze interrupt setup and button wiring

   The button is connected to pin 2 with INPUT_PULLUP, so pressing it pulls pin 2 LOW, triggering FALLING edge interrupt.

2. Step 2: Understand interrupt effect on count

   Each button press triggers incrementCount(), increasing count by 1, which is printed repeatedly in loop.

3. Final Answer:

   The count will increase by 1 each time the button is pressed -> Option D

4. Quick Check:

   Interrupt increments count on button press [OK]

Hint: FALLING triggers on button press with INPUT_PULLUP [OK]

Common Mistakes:

• Ignoring INPUT_PULLUP logic and edge type
• Assuming count won't change without delay
• Thinking volatile causes crashes

4. Identify the error in this code snippet using attachInterrupt():

volatile int flag = 0;

void setup() {
  pinMode(3, INPUT);
  attachInterrupt(3, interruptHandler, CHANGE);
}

void loop() {
  if (flag == 1) {
    Serial.println("Interrupt triggered");
    flag = 0;
  }
}

void interruptHandler() {
  flag = 1;
}

medium

A. Pin number 3 is used directly instead of digitalPinToInterrupt(3)

B. Interrupt mode CHANGE is invalid

C. Flag variable should not be volatile

D. Interrupt handler function must return int

Solution

1. Step 1: Check attachInterrupt() parameter usage

   The first parameter must be the interrupt number, obtained by digitalPinToInterrupt(pin), not the pin number directly.

2. Step 2: Verify other parts

   CHANGE is a valid mode, flag should be volatile, and interrupt handlers return void, so no other errors.

3. Final Answer:

   Pin number 3 is used directly instead of digitalPinToInterrupt(3) -> Option A

4. Quick Check:

   Use digitalPinToInterrupt(pin) for correct interrupt number [OK]

Hint: Always convert pin to interrupt number with digitalPinToInterrupt() [OK]

Common Mistakes:

• Passing pin number directly to attachInterrupt()
• Misunderstanding valid interrupt modes
• Incorrect return type for interrupt handler

5. You want to count how many times a sensor connected to pin 4 triggers a LOW signal, but only if the sensor stays LOW for at least 50 milliseconds to avoid false triggers. Which approach using attachInterrupt() is best?

hard

A. Use attachInterrupt() on CHANGE, record the time in ISR, and check duration in loop()

B. Use attachInterrupt() on FALLING edge and increment count immediately without delay

C. Use attachInterrupt() on RISING edge and increment count immediately

D. Use attachInterrupt() on FALLING edge and in the ISR check if LOW lasts 50ms using delay()

Solution

1. Step 1: Understand the need for debouncing or filtering

   To avoid false triggers, you must check if the LOW state lasts at least 50ms, which requires timing logic outside the interrupt.

2. Step 2: Evaluate options for timing and counting

   Using CHANGE interrupt and recording time in ISR, then checking duration in loop() allows safe timing without delay() inside ISR, which is not allowed.

3. Step 3: Reject unsafe or incorrect options

   Using delay() inside the ISR is bad practice; incrementing the count immediately on an edge without checking duration ignores the 50ms requirement.

4. Final Answer:

   Use attachInterrupt() on CHANGE, record the time in ISR, and check duration in loop() -> Option A

5. Quick Check:

   Record time in ISR, check duration in loop for debounce [OK]

Hint: Never use delay() in ISR; check timing in main loop [OK]

Common Mistakes:

• Using delay() inside interrupt routine
• Ignoring debounce timing
• Incrementing count immediately on edge