> For the complete documentation index, see [llms.txt](https://pekaway.gitbook.io/van-pi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://pekaway.gitbook.io/van-pi/debug/i2c.md).

# I2C

#### Overview of I2C Integration in VAN PI OS

I2C (Inter-Integrated Circuit) is a standard protocol for chip-to-chip communication, widely used for connecting various components in a system. VAN PI OS leverages I2C to connect and communicate with different chips efficiently.

**I2C Device Check**

In the web interface, there is a button to scan and check all devices connected to the I2C bus. This feature serves as the first troubleshooting step in identifying any hardware faults.

**I2C Device Addresses**

The following addresses are used for specific components in the system:

* **0x20**: MCP Relay Controller
* **0x55 and 0x70**: PCA PWM Controller (DIMMY)
* **0x48**: ADS Water Level Sensor
* **0x67**: MPU (Motion Processing Unit)

By using this integrated I2C communication, VAN PI OS ensures seamless interaction between various hardware components, enhancing the overall functionality and reliability of the system.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://pekaway.gitbook.io/van-pi/debug/i2c.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.