Why Multiple I2C devices on same bus in Raspberry Pi? - Purpose & Use Cases

The Big Idea

What if you could connect dozens of devices with just two wires and never get tangled in cables again?

The Scenario

Imagine you have several sensors and small devices that need to talk to your Raspberry Pi. You try to connect each one with its own wires and pins, making a big messy web of cables everywhere.

The Problem

Connecting each device separately means using many pins, which quickly runs out. It also becomes confusing to manage and easy to make mistakes, like mixing up wires or addresses. Troubleshooting this mess is slow and frustrating.

The Solution

Using multiple I2C devices on the same bus lets you connect many devices using just two wires. Each device has a unique address, so the Raspberry Pi can talk to them one by one without confusion. This keeps wiring simple and organized.

Before vs After

✗ Before

device1 = connect_to_pin(1)
device2 = connect_to_pin(2)

✓ After

bus = I2CBus()
device1 = bus.connect(address=0x20)
device2 = bus.connect(address=0x21)

What It Enables

You can easily add many sensors and devices to your Raspberry Pi without extra wires or complexity, making your projects cleaner and more scalable.

Real Life Example

Imagine building a weather station with temperature, humidity, and pressure sensors all connected on the same I2C bus, sharing just two wires to send data to your Raspberry Pi.

Key Takeaways

Manual wiring for each device is messy and limited.

I2C bus allows many devices on just two wires.

Each device has a unique address to avoid confusion.

Practice

1.

What is the main requirement to connect multiple I2C devices on the same bus?

Choose the best answer.

easy

A. Each device must have a unique I2C address.

B. Each device must use a different bus.

C. Devices must be connected with separate wires.

D. Devices must have the same address to communicate.

Solution

1. Step 1: Understand I2C bus addressing

   I2C devices share the same two wires but must have unique addresses to avoid conflicts.

2. Step 2: Identify the correct requirement

   Since devices share the bus, unique addresses allow the master to select each device individually.

3. Final Answer:

   Each device must have a unique I2C address. -> Option A

4. Quick Check:

   Unique addresses = multiple devices on one bus [OK]

Hint: Remember: unique addresses prevent device conflicts on I2C [OK]

Common Mistakes:

• Thinking devices need separate wires
• Assuming devices can share the same address
• Believing each device needs its own bus

2.

Which Python code snippet correctly initializes communication with two I2C devices at addresses 0x20 and 0x21 on the same bus?

import smbus2
bus = smbus2.SMBus(1)

# What comes next?

easy

A. device1 = smbus2.SMBus(0x20)
device2 = smbus2.SMBus(0x21)

B. device1 = bus.read_byte(0x20)
device2 = bus.read_byte(0x21)

C. device1 = 0x20
device2 = 0x21

D. device1 = bus
device2 = bus

Solution

1. Step 1: Understand bus and device addressing

   The bus object is created once; devices are identified by their addresses.

2. Step 2: Assign device addresses as variables

   Assigning device addresses to variables allows easy communication calls later.

3. Final Answer:

   device1 = 0x20\ndevice2 = 0x21 -> Option C

4. Quick Check:

   Bus once, devices by address [OK]

Hint: Create one bus object; use addresses to identify devices [OK]

Common Mistakes:

• Trying to create multiple bus objects for each device
• Calling read_byte immediately without setup
• Assigning bus object directly to devices

3.

Given this Python code snippet on a Raspberry Pi with two I2C devices at addresses 0x20 and 0x21:

import smbus2
bus = smbus2.SMBus(1)

value1 = bus.read_byte(0x20)
value2 = bus.read_byte(0x21)
print(value1, value2)

What will be the output if device 0x20 returns 10 and device 0x21 returns 20?

medium

A. 10 20

B. 20 10

C. 0 0

D. Error: Address not found

Solution

1. Step 1: Read bytes from each device address

   The code reads one byte from address 0x20 and one from 0x21.

2. Step 2: Print the values in order

   Since value1 reads from 0x20 (returns 10) and value2 from 0x21 (returns 20), print outputs "10 20".

3. Final Answer:

   10 20 -> Option A

4. Quick Check:

   Read from 0x20 then 0x21 = 10 20 [OK]

Hint: Read bytes by address order matches output order [OK]

Common Mistakes:

• Mixing up device addresses and values
• Assuming output is reversed
• Expecting error without checking device presence

4.

Consider this Python code snippet intended to read from two I2C devices on the same bus:

import smbus2
bus = smbus2.SMBus(1)

value1 = bus.read_byte(0x20)
value2 = bus.read_byte(0x20)
print(value1, value2)

Why might this code cause a problem when trying to read two different devices?

medium

A. The code is missing pull-up resistors on the bus.

B. Both reads use the same address, so the second device is never accessed.

C. The addresses 0x20 and 0x20 are invalid on the bus.

D. The bus object is created twice, causing conflict.

Solution

1. Step 1: Check device addresses used in reads

   Both read_byte calls use address 0x20, so only one device is accessed twice.

2. Step 2: Understand impact on multiple devices

   To read two different devices, their unique addresses must be used; otherwise, the second device is ignored.

3. Final Answer:

   Both reads use the same address, so the second device is never accessed. -> Option B

4. Quick Check:

   Same address twice = one device only [OK]

Hint: Use different addresses to access multiple devices [OK]

Common Mistakes:

• Assuming bus object creation causes error
• Thinking addresses 0x20 are invalid
• Confusing hardware wiring issues with code errors

5.

You have three I2C sensors connected to the same Raspberry Pi bus with addresses 0x20, 0x21, and 0x20. You want to read data from all three devices. What is the best way to fix this setup?

hard

A. Use separate I2C buses for devices with the same address.

B. Use software to ignore address conflicts and read anyway.

C. Connect devices with the same address to different GPIO pins.

D. Change the address of one device so all three have unique addresses.

Solution

1. Step 1: Identify address conflict

   Two devices share address 0x20, causing bus conflicts and communication errors.

2. Step 2: Resolve conflict by changing address

   Most I2C devices allow changing their address via hardware pins or software configuration to ensure uniqueness.

3. Step 3: Alternative solutions

   Using separate buses or GPIO pins is complex; ignoring conflicts causes errors.

4. Final Answer:

   Change the address of one device so all three have unique addresses. -> Option D

5. Quick Check:

   Unique addresses fix conflicts [OK]

Hint: Ensure all devices have unique addresses to avoid conflicts [OK]

Common Mistakes:

• Trying to read devices with duplicate addresses
• Assuming software can fix hardware address conflicts
• Using separate GPIO pins without separate buses