Why motor control is needed in Arduino - Performance Analysis

Time Complexity: Why motor control is needed

O(n)

Understanding Time Complexity

When controlling a motor with Arduino, it is important to understand how the time it takes to run the control code changes as the motor commands or inputs increase.

We want to know how the program's work grows when controlling the motor more or less.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

int motorSpeed = 0;
void setup() {
  pinMode(9, OUTPUT);
}
void loop() {
  for (int speed = 0; speed < 256; speed++) {
    analogWrite(9, speed);
    delay(10);
  }
}
    

This code gradually increases the motor speed from 0 to 255 by sending PWM signals to the motor control pin.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: The for-loop that runs from speed 0 to 255.
• How many times: It runs 256 times each time the loop() function runs.

How Execution Grows With Input

As the motor speed range increases, the number of steps to set the speed grows linearly.

Input Size (n)	Approx. Operations
10	10 speed steps
100	100 speed steps
255	255 speed steps

Pattern observation: The number of operations grows directly with the number of speed steps.

Final Time Complexity

Time Complexity: O(n)

This means the time to control the motor grows in a straight line as you increase the number of speed steps.

Common Mistake

[X] Wrong: "Increasing motor speed steps will not affect how long the program runs."

[OK] Correct: More speed steps mean more times the program sends signals, so it takes longer.

Interview Connect

Understanding how motor control code grows with input size helps you write efficient programs for real devices, showing you can think about performance in practical ways.

Self-Check

"What if we changed the for-loop to increase speed in steps of 5 instead of 1? How would the time complexity change?"