<p>When we use the I2C communication protocol, the first thing we must do is identify the different slaves that we connect to the bus. The same happens when we connect an input or an output, they have to have a name to identify themselves on the bus; is usually 0x... To do this I use <b>Neil's program</b> to see what number the I2C interface of the LCD uses.</p>
<p>When we use the I2C communication protocol, the first thing we must do is identify the different slaves that we connect to the bus. The same happens when we connect an input or an output, they have to have a name to identify themselves on the bus; is usually 0x... To do this I use <b>Neil's program</b> to see what number the I2C interface of the LCD uses. On this <ahref="https://diyprojects.io/i2c-addresses-of-the-most-common-sensors-and-actuators/#.X4HA82gzZPb"><b>link</b></a> you can find the addresses of the different input and output modules that use the I2C communication protocol.</p>
<p>When we use the I2C communication protocol, the first thing we must do is identify the different slaves that we connect to the bus. The same happens when we connect an input or an output, they have to have a name to identify themselves on the bus; is usually 0x... To do this I use <b>Neil's program</b> to see what number the I2C interface of the OLED uses.</p>
<p>When we use the I2C communication protocol, the first thing we must do is identify the different slaves that we connect to the bus. The same happens when we connect an input or an output, they have to have a name to identify themselves on the bus; is usually 0x... To do this I use <b>Neil's program</b> to see what number the I2C interface of the OLED uses. On this <ahref="https://diyprojects.io/i2c-addresses-of-the-most-common-sensors-and-actuators/#.X4HA82gzZPb"><b>link</b></a> you can find the addresses of the different input and output modules that use the I2C communication protocol.</p></p>
