Reducing power consumption tips in Arduino - Time & Space Complexity

Time Complexity: Reducing power consumption tips

O(n)

Understanding Time Complexity

When we write code to save power on an Arduino, we want to know how much work the code does as it runs.

We ask: how does the time the code takes change when we add more steps or checks?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

void loop() {
  delay(1000); // wait 1 second
  digitalWrite(LED_BUILTIN, HIGH); // turn LED on
  delay(100); // short on time
  digitalWrite(LED_BUILTIN, LOW); // turn LED off
  delay(1000); // wait 1 second
}
    

This code blinks an LED with delays to save power by turning the LED off most of the time.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: The loop function repeats forever.
• How many times: Each loop cycle runs once, but inside it, delay pauses the program.

How Execution Grows With Input

Explain the growth pattern intuitively.

Input Size (n)	Approx. Operations
10	10 cycles of loop, each with fixed delays
100	100 cycles, same fixed delays each time
1000	1000 cycles, delays do not change

Pattern observation: The time spent grows linearly with the number of cycles, but each cycle takes the same fixed time.

Final Time Complexity

Time Complexity: O(n)

This means the total time grows directly with how many times the loop runs, but each loop takes a fixed amount of time.

Common Mistake

[X] Wrong: "Adding more delay calls makes the program faster."

[OK] Correct: Delay pauses the program, so more delays actually make it slower, not faster.

Interview Connect

Understanding how your code's timing grows helps you write better programs that save power and run efficiently on small devices like Arduino.

Self-Check

"What if we replaced delay() with a non-blocking timer? How would the time complexity change?"

Practice

1. Which of the following is a common method to reduce power consumption on an Arduino?

easy

A. Keeping all hardware modules enabled at all times

B. Increasing the clock speed to maximum

C. Using sleep modes to pause the CPU when idle

D. Running the Arduino without any power source

Solution

1. Step 1: Understand power saving basics

   Sleep modes reduce power by pausing the CPU when it is not needed.

2. Step 2: Evaluate other options

   Increasing clock speed or keeping hardware enabled increases power use; running without power is impossible.

3. Final Answer:

   Using sleep modes to pause the CPU when idle -> Option C

4. Quick Check:

   Sleep modes = power saving [OK]

Hint: Sleep modes save power by pausing CPU [OK]

Common Mistakes:

• Thinking higher clock speed saves power
• Believing all hardware should stay enabled
• Ignoring the need for a power source

2. Which Arduino function is used to put the microcontroller into sleep mode?

easy

A. pinMode()

B. digitalWrite()

C. delay()

D. sleep_mode()

Solution

1. Step 1: Identify sleep mode function

   The function sleep_mode() is used to put the microcontroller into sleep mode.

2. Step 2: Check other functions

   digitalWrite() controls pins, delay() pauses code, pinMode() sets pin mode; none put it into sleep.

3. Final Answer:

   sleep_mode() -> Option D

4. Quick Check:

   sleep_mode() = enter sleep [OK]

Hint: sleep_mode() puts Arduino into sleep [OK]

Common Mistakes:

• Confusing delay() with sleep functions
• Using digitalWrite() to control power
• Not knowing pinMode() sets pin direction

3. What will be the effect of this code snippet on power consumption?

void setup() {
  pinMode(13, OUTPUT);
  digitalWrite(13, LOW);
  // No sleep mode used
}
void loop() {
  // Empty loop
}

medium

A. Power consumption remains high because no sleep mode is used

B. Power consumption is reduced by turning off pin 13

C. Power consumption is zero because loop is empty

D. Pin 13 will blink, increasing power use

Solution

1. Step 1: Analyze pin state

   Pin 13 is set to LOW, so it does not consume extra power from that pin.

2. Step 2: Check for sleep mode

   No sleep mode is used, so the CPU runs continuously, consuming normal power.

3. Final Answer:

   Power consumption remains high because no sleep mode is used -> Option A

4. Quick Check:

   No sleep mode = normal power use [OK]

Hint: No sleep mode means no power saving [OK]

Common Mistakes:

• Assuming LOW pin means zero power
• Thinking empty loop stops CPU
• Believing pin 13 blinks automatically

4. Identify the error in this code that tries to reduce power consumption:

void setup() {
  sleep_enable();
  sleep_mode();
  sleep_disable();
}
void loop() {
  // do nothing
}

medium

A. The code does not put the CPU to sleep properly because it lacks an interrupt to wake up

B. sleep_disable() should be called before sleep_mode()

C. sleep_mode() is called without enabling sleep first

D. pinMode() is missing for sleep functions

Solution

1. Step 1: Review sleep sequence

   sleep_enable() and sleep_mode() are correctly called to enter sleep.

2. Step 2: Check wake-up mechanism

   Without an interrupt or event to wake the CPU, it may stay asleep indefinitely or behave unexpectedly.

3. Final Answer:

   The code does not put the CPU to sleep properly because it lacks an interrupt to wake up -> Option A

4. Quick Check:

   Sleep needs wake interrupt [OK]

Hint: Sleep requires wake interrupt to resume [OK]

Common Mistakes:

• Thinking sleep_disable() must come before sleep_mode()
• Ignoring the need for wake interrupts
• Assuming pinMode() affects sleep functions

5. You want to reduce power consumption by disabling unused hardware modules on your Arduino. Which approach is best?

hard

A. Use digitalWrite() to disable hardware modules

B. Use power_adc_disable() to turn off the analog-to-digital converter when not needed

C. Keep all modules enabled to avoid errors

D. Increase the clock speed to finish tasks faster

Solution

1. Step 1: Identify hardware disabling functions

   Functions like power_adc_disable() turn off specific hardware modules to save power.

2. Step 2: Evaluate other options

   Increasing clock speed uses more power; keeping all modules enabled wastes energy; digitalWrite() controls pins, not modules.

3. Final Answer:

   Use power_adc_disable() to turn off the analog-to-digital converter when not needed -> Option B

4. Quick Check:

   Disable unused hardware = power_adc_disable() [OK]

Hint: Disable unused hardware with power_*_disable() [OK]

Common Mistakes:

• Thinking digitalWrite() disables hardware modules
• Believing higher clock speed saves power
• Not disabling unused modules wastes battery