Why interrupts improve responsiveness in Arduino - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to attach an interrupt to pin 2 that calls the function handleInterrupt.

Arduino

attachInterrupt(digitalPinToInterrupt([1]), handleInterrupt, RISING);

Drag options to blanks, or click blank then click option'

A2

B3

C4

D5

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing a pin that does not support interrupts.

Pin 2 is the correct pin to attach the interrupt on many Arduino boards.

2fill in blank

medium

Complete the code to declare the interrupt service routine function named handleInterrupt.

Arduino

void [1]() {
  // code to run when interrupt occurs
}

Drag options to blanks, or click blank then click option'

AinterruptHandler

BhandleInterrupt

ConInterrupt

DinterruptRoutine

Attempts:

3 left

💡 Hint

Common Mistakes

Using a different function name than in attachInterrupt.

The function name must match the one used in attachInterrupt.

3fill in blank

hard

Fix the error in the code to correctly enable interrupts.

Arduino

noInterrupts();
// critical code here
[1]();

Drag options to blanks, or click blank then click option'

AdisableInterrupts

BstartInterrupts

CenableInterrupts

Dinterrupts

Attempts:

3 left

💡 Hint

Common Mistakes

Using a non-existent function name to enable interrupts.

The function interrupts() re-enables interrupts after noInterrupts().

4fill in blank

hard

Fill both blanks to create a dictionary that maps pin numbers to their interrupt numbers.

Arduino

const int interruptMap[] = { [1]: 0, [2]: 1 };

Drag options to blanks, or click blank then click option'

A2

B3

C4

D5

Attempts:

3 left

💡 Hint

Common Mistakes

Using pins that do not correspond to interrupt numbers.

Pin 2 maps to interrupt 0 and pin 3 maps to interrupt 1 on many Arduino boards.

5fill in blank

hard

Fill all three blanks to complete the code that sets up an interrupt and handles it.

Arduino

volatile bool flag = false;

void [1]() {
  flag = true;
}

void setup() {
  attachInterrupt(digitalPinToInterrupt([2]), [3], FALLING);
}

void loop() {
  if (flag) {
    flag = false;
    // handle event
  }
}

Drag options to blanks, or click blank then click option'

AhandleInterrupt

B2

D3

Attempts:

3 left

💡 Hint

Common Mistakes

Mismatching function names or wrong pin number.

The interrupt service routine is named handleInterrupt, attached to pin 2, and the function name is handleInterrupt.

Practice

1. Why do interrupts improve the responsiveness of an Arduino program?

easy

A. They allow the Arduino to stop its current task and immediately handle important events.

B. They make the Arduino run faster by increasing its clock speed.

C. They reduce the power consumption of the Arduino.

D. They automatically fix errors in the code.

Solution

1. Step 1: Understand what interrupts do

   Interrupts pause the current program to quickly respond to urgent events like button presses.

2. Step 2: Compare with other options

   Increasing clock speed or reducing power are unrelated to interrupts. Fixing code errors is not automatic.

3. Final Answer:

   They allow the Arduino to stop its current task and immediately handle important events. -> Option A

4. Quick Check:

   Interrupts improve responsiveness by immediate handling [OK]

Hint: Interrupts pause code to handle urgent events fast [OK]

Common Mistakes:

• Thinking interrupts speed up the whole program
• Confusing interrupts with power saving
• Believing interrupts fix code errors automatically

2. Which of the following is the correct syntax to attach an interrupt in Arduino?

easy

A. interruptAttach(pin, ISR, mode);

B. attachInterrupt(digitalPinToInterrupt(pin), ISR, mode);

C. attachInterrupt(pin, ISR);

D. interrupt(pin, ISR, mode);

Solution

1. Step 1: Recall Arduino interrupt syntax

   The correct function is attachInterrupt with parameters digitalPinToInterrupt(pin), ISR function, and mode.

2. Step 2: Check other options

   Other options use wrong function names or missing parameters.

3. Final Answer:

   attachInterrupt(digitalPinToInterrupt(pin), ISR, mode); -> Option B

4. Quick Check:

   Correct Arduino interrupt syntax = attachInterrupt(digitalPinToInterrupt(pin), ISR, mode); [OK]

Hint: Use attachInterrupt with digitalPinToInterrupt for correct syntax [OK]

Common Mistakes:

• Using wrong function names like interruptAttach
• Omitting digitalPinToInterrupt wrapper
• Missing mode parameter in attachInterrupt

3. What will be the output on the serial monitor when this Arduino code runs?

volatile int count = 0;

void setup() {
  Serial.begin(9600);
  attachInterrupt(digitalPinToInterrupt(2), increment, RISING);
  pinMode(2, INPUT);
}

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

void increment() {
  count++;
}

medium

A. The count will decrease every second.

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

C. The code will cause a compile error due to missing interrupt setup.

D. The count will increase each time pin 2 detects a rising signal.

Solution

1. Step 1: Analyze interrupt setup

   Interrupt is attached to pin 2 with RISING mode, calling increment() to increase count.

2. Step 2: Understand loop output

   Loop prints count every second. Each rising edge on pin 2 increases count by 1.

3. Final Answer:

   The count will increase each time pin 2 detects a rising signal. -> Option D

4. Quick Check:

   Interrupt increments count on rising edge = The count will increase each time pin 2 detects a rising signal. [OK]

Hint: Interrupt increments count on pin signal, loop prints it [OK]

Common Mistakes:

• Assuming interrupts are disabled by default
• Thinking code will not compile
• Believing count decreases without code for that

4. This Arduino code is supposed to count button presses using an interrupt, but the count never increases. What is the error?

volatile int count = 0;

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

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

void increment() {
  count++;
}

medium

A. Serial.begin() must be called inside loop() instead of setup().

B. pinMode should be set to OUTPUT instead of INPUT_PULLUP.

C. attachInterrupt should use digitalPinToInterrupt(2) instead of 2.

D. The ISR function increment() must return a value.

Solution

1. Step 1: Check attachInterrupt parameter

   attachInterrupt requires digitalPinToInterrupt(pin) for portability and correctness, not just pin number.

2. Step 2: Review other options

   pinMode INPUT_PULLUP is correct for button with pull-up. ISR functions return void. Serial.begin() belongs in setup.

3. Final Answer:

   attachInterrupt should use digitalPinToInterrupt(2) instead of 2. -> Option C

4. Quick Check:

   Use digitalPinToInterrupt for attachInterrupt pin [OK]

Hint: Always wrap pin number with digitalPinToInterrupt() [OK]

Common Mistakes:

• Passing raw pin number to attachInterrupt
• Changing pinMode to OUTPUT for input button
• Expecting ISR to return a value
• Calling Serial.begin() repeatedly inside loop

5. You want your Arduino to quickly detect a sensor signal and also run a long calculation in loop(). How can interrupts improve responsiveness in this case?

hard

A. Use an interrupt to detect the sensor signal and set a flag, then handle the flag in loop().

B. Run the long calculation inside the interrupt service routine (ISR) for faster response.

C. Disable interrupts during the long calculation to avoid conflicts.

D. Avoid using interrupts and check the sensor signal only inside loop().

Solution

1. Step 1: Understand ISR best practices

   ISRs should be short and fast; long calculations inside ISR cause delays and missed interrupts.

2. Step 2: Use interrupts to set flags

   Use ISR to set a flag when sensor triggers, then handle the flag in the main loop after calculation.

3. Final Answer:

   Use an interrupt to detect the sensor signal and set a flag, then handle the flag in loop(). -> Option A

4. Quick Check:

   ISR sets flag; loop handles work = Use an interrupt to detect the sensor signal and set a flag, then handle the flag in loop(). [OK]

Hint: Keep ISR short; set flag, process later in loop [OK]

Common Mistakes:

• Doing long tasks inside ISR
• Disabling interrupts unnecessarily
• Ignoring interrupts and polling only