Multiple I2C devices on same bus in Raspberry Pi

Introduction

Using multiple I2C devices on the same bus lets you connect many sensors or modules to one Raspberry Pi without extra wires.

You want to read temperature from one sensor and humidity from another using I2C.

You have several small devices like displays and sensors that use I2C and want to connect them all.

You want to save GPIO pins by sharing the same two I2C wires for multiple devices.

You are building a project with many I2C modules and want to keep wiring simple.

Syntax

Raspberry Pi

import smbus

bus = smbus.SMBus(1)  # Use I2C bus 1

# To talk to a device, use its unique address
DEVICE_ADDRESS_1 = 0x40
DEVICE_ADDRESS_2 = 0x41

# Read or write data by specifying the device address
bus.write_byte(DEVICE_ADDRESS_1, 0x00)
data = bus.read_byte(DEVICE_ADDRESS_2)

Each I2C device must have a unique address on the bus.

Use the same bus object to communicate with all devices on that bus.

Examples

Control two LED devices with different addresses on the same I2C bus.

Raspberry Pi

DEVICE_ADDRESS_1 = 0x20
DEVICE_ADDRESS_2 = 0x21

bus.write_byte(DEVICE_ADDRESS_1, 0xFF)  # Turn on all LEDs on device 1
bus.write_byte(DEVICE_ADDRESS_2, 0x00)  # Turn off all LEDs on device 2

Read temperature and humidity from two sensors on the same bus.

Raspberry Pi

temperature_address = 0x48
humidity_address = 0x40

temp = bus.read_byte_data(temperature_address, 0x00)
hum = bus.read_byte_data(humidity_address, 0x01)

Sample Program

This program reads raw data from two I2C sensors with different addresses on the same bus every 2 seconds.

Raspberry Pi

import smbus
import time

bus = smbus.SMBus(1)  # Use I2C bus 1

# Example device addresses (replace with your devices')
TEMP_SENSOR_ADDR = 0x48
HUM_SENSOR_ADDR = 0x40

while True:
    # Read temperature data
    temp_raw = bus.read_byte_data(TEMP_SENSOR_ADDR, 0x00)
    # Read humidity data
    hum_raw = bus.read_byte_data(HUM_SENSOR_ADDR, 0x01)

    print(f"Temperature raw data: {temp_raw}")
    print(f"Humidity raw data: {hum_raw}")

    time.sleep(2)

Important Notes

Make sure each device has a unique I2C address to avoid conflicts.

Use the i2cdetect command on Raspberry Pi terminal to find device addresses.

Pull-up resistors are usually needed on the SDA and SCL lines for proper I2C communication.

Summary

You can connect many I2C devices on the same two wires if each has a unique address.

Use the same bus object to talk to all devices by specifying their addresses.

Check addresses with i2cdetect and ensure proper wiring with pull-up resistors.

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