Reading sensor data over I2C in Raspberry Pi - Time & Space Complexity
When reading sensor data over I2C on a Raspberry Pi, it's important to know how the time taken grows as we read more data.
We want to understand how the number of sensor reads affects the total time the program takes.
Analyze the time complexity of the following code snippet.
import smbus
bus = smbus.SMBus(1)
address = 0x48
for i in range(n):
data = bus.read_byte_data(address, 0x00)
print(f"Reading {i}: {data}")
This code reads one byte of data from a sensor at a fixed address repeatedly n times.
Identify the loops, recursion, array traversals that repeat.
- Primary operation: Reading one byte from the sensor using I2C bus.
- How many times: This read operation happens inside a loop that runs n times.
Each additional read adds a fixed amount of time because the sensor is read once per loop.
| Input Size (n) | Approx. Operations |
|---|---|
| 10 | 10 sensor reads |
| 100 | 100 sensor reads |
| 1000 | 1000 sensor reads |
Pattern observation: The total time grows directly in proportion to the number of reads.
Time Complexity: O(n)
This means if you double the number of reads, the total time roughly doubles too.
[X] Wrong: "Reading sensor data multiple times is almost instant and does not add up."
[OK] Correct: Each sensor read takes time because it communicates over I2C. Doing many reads adds up linearly.
Understanding how repeated hardware communication affects time helps you write efficient code and explain performance clearly.
What if we read multiple bytes in one I2C call instead of one byte per call? How would the time complexity change?
Practice
Solution
Step 1: Understand I2C communication basics
I2C allows multiple devices to connect using unique addresses on the same bus.Step 2: Identify the role of I2C with sensors
The Raspberry Pi uses I2C to talk to sensors by addressing each one uniquely.Final Answer:
To communicate with multiple sensors using unique addresses -> Option AQuick Check:
I2C = Multiple devices, unique addresses [OK]
- Thinking I2C increases processing speed
- Confusing communication with power supply
- Assuming I2C stores data permanently
Solution
Step 1: Recall common Python libraries for hardware
For I2C communication on Raspberry Pi, the smbus library is standard.Step 2: Eliminate unrelated libraries
pygame is for games, matplotlib for plotting, requests for web requests, so they don't fit.Final Answer:
smbus -> Option BQuick Check:
Python I2C library = smbus [OK]
- Choosing pygame or matplotlib for sensor reading
- Confusing web libraries with hardware libraries
import smbus bus = smbus.SMBus(1) address = 0x48 value = bus.read_byte_data(address, 0x00) print(value)
Solution
Step 1: Understand the code's function
The code reads one byte from register 0x00 of the device at I2C address 0x48.Step 2: Identify the output of print(value)
It prints the numeric byte value read from that register, not the address or a string.Final Answer:
The byte value stored at register 0x00 of device 0x48 -> Option DQuick Check:
read_byte_data returns register byte value [OK]
- Thinking SMBus(1) is invalid (it's correct for Raspberry Pi)
- Confusing address with data value
- Expecting string output instead of number
import smbus bus = smbus.SMBus(0) address = 0x40 data = bus.read_byte_data(address, 0x01) print(data)
Solution
Step 1: Check SMBus bus number
On Raspberry Pi, I2C bus 1 is standard; bus 0 is usually invalid or unused.Step 2: Verify other code parts
Address 0x40 is valid, read_byte_data takes two arguments, and print(data) is correct.Final Answer:
SMBus(0) is incorrect; Raspberry Pi usually uses bus 1 -> Option CQuick Check:
Use SMBus(1) on Raspberry Pi [OK]
- Using SMBus(0) instead of SMBus(1)
- Thinking I2C addresses like 0x40 are invalid
- Misunderstanding read_byte_data arguments
Solution
Step 1: Understand byte order for temperature
MSB is the high byte, so shift it left by 8 bits to make space for LSB.Step 2: Combine MSB and LSB correctly
Use bitwise OR to combine shifted MSB with LSB for full 16-bit value.Final Answer:
temp = (bus.read_byte_data(0x5A, 0x07) << 8) | bus.read_byte_data(0x5A, 0x08) -> Option AQuick Check:
Combine MSB << 8 with LSB using OR [OK]
- Adding bytes instead of bitwise OR
- Swapping MSB and LSB order
- Multiplying bytes instead of combining bits
Ready to prove it?
Pass the test and this pattern moves unknown
