Why did my I2C sensor stop responding after I added a leaf?

Use this page with AI

Explore with your favorite AI

Gemini & other AI

Copy this page’s context into your AI to explore how it works and what you can build.

Open Gemini

Copy the prompt, then paste it into Gemini’s message box.

View prompt

On this page

Check for duplicate addresses on the same I2C bus. Devices may work individually but become impossible to address separately when another leaf uses the same address.

CombinationDuplicate address
AI05 LIS2DW12 accelerometer and AX06 I/O expander0x18
AC08 and AC09 control I/O expanders0x21

These are 7-bit addresses. Check other combinations in the I2C address map. Whether an address can be changed depends on the component and board implementation, so check each leaf’s specifications before changing only the software address.

If addresses do not overlap, also check power, signal levels, pin conflicts, and pull-up resistors. For example, AI05 R18 and R19 are not populated; with AP03, it uses the pull-ups on AP03.

Start from the configuration that worked

Disconnect all power before changing the stack, then work through these checks.

  1. Remove the added leaf and test with the original program. If the original configuration also fails, the added leaf may not be the only cause. Check power, contacts, wiring, and the program.
  2. Add leaves one at a time. When readings stop, compare the pins and I2C addresses used by that combination.
  3. If addresses overlap, first use just one of those devices. If you need both, check whether each device and board supports an address change. Changing only the software address setting does not change the actual device address.

See Combining leaves for a connection checklist.

Leaf photo
Search documentation, sample apps, and Q&A