Error handling in embedded projects in Arduino - Time & Space Complexity

Time Complexity: Error handling in embedded projects

O(n)

Understanding Time Complexity

When we add error handling in embedded projects, it can affect how long the program takes to run.

We want to know how the time to handle errors grows as the program checks more conditions or inputs.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

void checkSensors(int sensorValues[], int size) {
  for (int i = 0; i < size; i++) {
    if (sensorValues[i] < 0) {
      Serial.println("Error: Negative sensor value");
    }
  }
}
    

This code checks each sensor value and prints an error message if the value is negative.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Loop through the sensorValues array to check each value.
• How many times: The loop runs once for each sensor value, so 'size' times.

How Execution Grows With Input

As the number of sensor values increases, the program checks more values one by one.

Input Size (n)	Approx. Operations
10	10 checks
100	100 checks
1000	1000 checks

Pattern observation: The number of checks grows directly with the number of sensor values.

Final Time Complexity

Time Complexity: O(n)

This means the time to handle errors grows in a straight line with the number of sensor values.

Common Mistake

[X] Wrong: "Error handling will only take constant time no matter how many sensors there are."

[OK] Correct: Because the code checks each sensor one by one, more sensors mean more checks and more time.

Interview Connect

Understanding how error checks affect program speed helps you write reliable embedded code that runs efficiently.

Self-Check

"What if we added nested loops to check pairs of sensor values? How would the time complexity change?"

Practice

1. What is the main purpose of error handling in embedded projects like Arduino?

easy

A. To increase the power consumption of the device

B. To make the code run faster without checks

C. To add more sensors to the project

D. To detect and manage problems to keep the project safe and reliable

Solution

1. Step 1: Understand the role of error handling

   Error handling is used to find and manage problems that may happen during the project operation.

2. Step 2: Identify the goal of error handling in embedded systems

   It helps keep the system safe and reliable by preventing crashes or unexpected behavior.

3. Final Answer:

   To detect and manage problems to keep the project safe and reliable -> Option D

4. Quick Check:

   Error handling = detect and manage problems [OK]

Hint: Error handling means catching problems early [OK]

Common Mistakes:

• Thinking error handling speeds up code
• Confusing error handling with adding features
• Ignoring safety and reliability

2. Which of the following is the correct way to check for an error after reading a sensor value in Arduino?

easy

A. if (sensorValue == -1) { handleError(); }

B. if sensorValue = -1 then handleError();

C. if (sensorValue = -1) { handleError(); }

D. if sensorValue == -1 { handleError(); }

Solution

1. Step 1: Identify correct syntax for if statement in Arduino (C++)

   The condition must be inside parentheses and use double equals (==) to compare.

2. Step 2: Check each option for syntax correctness

   if (sensorValue == -1) { handleError(); } uses correct syntax: if (sensorValue == -1) { handleError(); }

3. Final Answer:

   if (sensorValue == -1) { handleError(); } -> Option A

4. Quick Check:

   Correct if syntax uses parentheses and '==' [OK]

Hint: Use '==' inside parentheses for comparisons [OK]

Common Mistakes:

• Using single '=' instead of '==' for comparison
• Missing parentheses around condition
• Using wrong keywords like 'then'

3. What will be the output on Serial Monitor if the following Arduino code runs and sensorValue is -1?

int sensorValue = -1;
void setup() {
  Serial.begin(9600);
  if (sensorValue == -1) {
    Serial.println("Error: Sensor not found");
  } else {
    Serial.println("Sensor OK");
  }
}
void loop() {}

medium

A. Sensor OK

B. Error: Sensor not found

C. No output

D. Compilation error

Solution

1. Step 1: Check the value of sensorValue

   sensorValue is set to -1 before setup runs.

2. Step 2: Evaluate the if condition in setup()

   Since sensorValue == -1 is true, the code prints "Error: Sensor not found" to Serial.

3. Final Answer:

   Error: Sensor not found -> Option B

4. Quick Check:

   sensorValue == -1 triggers error message [OK]

Hint: Trace variable values to predict output [OK]

Common Mistakes:

• Assuming else branch runs when condition is true
• Forgetting Serial.begin() before printing
• Confusing output with compilation errors

4. Identify the error in this Arduino code snippet for error handling:

int readSensor() {
  int val = analogRead(A0);
  if (val = -1) {
    return -1;
  }
  return val;
}

medium

A. Function should return void, not int

B. Missing semicolon after return statements

C. Using '=' instead of '==' in the if condition

D. analogRead() cannot return -1

Solution

1. Step 1: Check the if condition syntax

   The code uses single '=' which assigns -1 to val instead of comparing.

2. Step 2: Understand the impact of assignment in condition

   Assignment returns the assigned value, so condition is always true (-1 is true in C++), causing wrong behavior.

3. Final Answer:

   Using '=' instead of '==' in the if condition -> Option C

4. Quick Check:

   Use '==' to compare, not '=' [OK]

Hint: Use '==' for comparison, '=' for assignment [OK]

Common Mistakes:

• Confusing '=' and '==' in conditions
• Assuming analogRead returns -1 normally
• Ignoring return type correctness

5. You want to indicate an error in your Arduino project using an LED connected to pin 13. Which code snippet correctly turns the LED on when an error occurs (errorCode != 0) and off otherwise?

hard

A. if (errorCode != 0) { digitalWrite(13, HIGH); } else { digitalWrite(13, LOW); }

B. if (errorCode = 0) { digitalWrite(13, HIGH); } else { digitalWrite(13, LOW); }

C. if (errorCode != 0) { digitalWrite(13, LOW); } else { digitalWrite(13, HIGH); }

D. digitalWrite(13, errorCode);

Solution

1. Step 1: Understand the logic for error indication

   LED should be ON (HIGH) when errorCode is not zero, OFF (LOW) otherwise.

2. Step 2: Check each option for correct logic and syntax

   if (errorCode != 0) { digitalWrite(13, HIGH); } else { digitalWrite(13, LOW); } correctly uses '!=' to check error and sets pin 13 HIGH or LOW accordingly.

3. Final Answer:

   if (errorCode != 0) { digitalWrite(13, HIGH); } else { digitalWrite(13, LOW); } -> Option A

4. Quick Check:

   Use '!=' and digitalWrite HIGH/LOW correctly [OK]

Hint: Turn LED HIGH on error, LOW otherwise [OK]

Common Mistakes:

• Using '=' instead of '!=' in condition
• Reversing HIGH and LOW states
• Passing errorCode directly to digitalWrite