Using sensor libraries in Arduino - Time & Space Complexity
When using sensor libraries in Arduino, it's important to know how the program's running time changes as it reads data repeatedly.
We want to see how the time to get sensor readings grows when we take more measurements.
Analyze the time complexity of the following code snippet.
#include <SensorLib.h>
Sensor sensor;
void setup() {
sensor.begin();
}
void loop() {
for (int i = 0; i < 100; i++) {
int value = sensor.read();
}
delay(1000);
}
This code initializes a sensor and reads its value 100 times in a loop every second.
Identify the loops, recursion, array traversals that repeat.
- Primary operation: Calling
sensor.read()inside the for-loop. - How many times: 100 times each time
loop()runs.
Explain the growth pattern intuitively.
| Input Size (n) | Approx. Operations |
|---|---|
| 10 | 10 sensor reads |
| 100 | 100 sensor reads |
| 1000 | 1000 sensor reads |
Pattern observation: The number of sensor reads grows directly with the number of loop iterations.
Time Complexity: O(n)
This means the time to read sensor data grows in a straight line as you increase the number of readings.
[X] Wrong: "Calling sensor.read() inside a loop is instant and does not affect time."
[OK] Correct: Each sensor read takes some time, so more reads mean more total time spent.
Understanding how sensor reading loops affect time helps you write efficient Arduino programs and shows you can think about how code scales.
"What if we changed the for-loop to read sensor data only once per loop cycle? How would the time complexity change?"
Practice
Solution
Step 1: Understand the library usage
Before using a sensor, you must include its library so Arduino knows how to communicate with it.Step 2: Identify correct placement
Including the library is done at the top of the sketch, before setup() and loop().Final Answer:
Include the sensor library at the top of the sketch -> Option AQuick Check:
Include library first = A [OK]
- Trying to create sensor object before including library
- Starting sensor in loop() instead of setup()
- Reading sensor before initializing it
Solution
Step 1: Recall object creation syntax in Arduino C++
Objects are created by calling the constructor directly, like ClassName objectName(parameters); without '=' or 'new' keyword.Step 2: Match correct syntax for DHT library
The DHT library uses: DHT sensor(pin, type); so DHT sensor(2, DHT11); matches this exactly.Final Answer:
DHT sensor(2, DHT11); -> Option CQuick Check:
Object creation = ClassName object(params); [OK]
- Using '=' sign when creating objects
- Using 'new' keyword which is not typical in Arduino sketches
- Confusing sensor type and pin order
#include <DHT.h>
#define DHTPIN 2
#define DHTTYPE DHT11
DHT dht(DHTPIN, DHTTYPE);
void setup() {
Serial.begin(9600);
dht.begin();
}
void loop() {
float h = dht.readHumidity();
if (isnan(h)) {
Serial.println("Failed to read humidity!");
} else {
Serial.print("Humidity: ");
Serial.println(h);
}
delay(2000);
}
Solution
Step 1: Understand the isnan() check
The code checks if the humidity reading is 'NaN' (not a number), which means the sensor failed to read.Step 2: Determine output when reading fails
If isnan(h) is true, the code prints "Failed to read humidity!" to Serial.Final Answer:
Failed to read humidity! -> Option AQuick Check:
isnan true prints error message [OK]
- Assuming sensor returns 0 on failure
- Printing raw value without checking for NaN
- Not calling dht.begin() in setup()
#include <DHT.h>
DHT dht(2, DHT11);
void setup() {
Serial.begin(9600);
}
void loop() {
dht.begin();
float t = dht.readTemperature();
Serial.println(t);
delay(1000);
}
Solution
Step 1: Locate sensor initialization
dht.begin() initializes the sensor and should be called once in setup() to avoid repeated initialization.Step 2: Identify why calling dht.begin() in loop() is wrong
Calling dht.begin() repeatedly in loop() can cause sensor communication issues and slow down the program.Final Answer:
dht.begin() should be called in setup(), not loop() -> Option BQuick Check:
Initialize sensor once in setup() [OK]
- Calling sensor start functions repeatedly in loop()
- Confusing Serial.begin() placement
- Assuming readTemperature() returns int
Solution
Step 1: Check sensor initialization and pin setup
#include <DHT.h> #define DHTPIN 2 #define DHTTYPE DHT11 #define LEDPIN 13 DHT dht(DHTPIN, DHTTYPE); void setup() { Serial.begin(9600); dht.begin(); pinMode(LEDPIN, OUTPUT); } void loop() { float h = dht.readHumidity(); if (!isnan(h) && h > 70) { digitalWrite(LEDPIN, HIGH); } else { digitalWrite(LEDPIN, LOW); } delay(2000); }correctly calls dht.begin() in setup() and sets LED pin as output.Step 2: Verify humidity check and LED control logic
#include <DHT.h> #define DHTPIN 2 #define DHTTYPE DHT11 #define LEDPIN 13 DHT dht(DHTPIN, DHTTYPE); void setup() { Serial.begin(9600); dht.begin(); pinMode(LEDPIN, OUTPUT); } void loop() { float h = dht.readHumidity(); if (!isnan(h) && h > 70) { digitalWrite(LEDPIN, HIGH); } else { digitalWrite(LEDPIN, LOW); } delay(2000); }checks if humidity is not NaN and greater than 70 before turning LED on, which prevents errors from failed reads.Final Answer:
The code snippet with !isnan(h) check and && h > 70 -> Option DQuick Check:
Initialize sensor + check isnan + control LED = A [OK]
- Not calling dht.begin() in setup()
- Missing isnan() check causing wrong LED behavior
- Using || instead of && in humidity condition
Ready to prove it?
Pass the test and this pattern moves unknown
