07-21-2016, 11:15 AM
Hoping to get some insight from anyone who is successfully using the I2C expansion board.
I'm using the Pine temp/humidity sensor...tested with some python code (grabbed from the web and modified) and the sensor works great when using the Pi Bus I2C pins. It also works with the I2C expansion board plugged in and connected to the expansion board pins.
When I plug into one (any) of the I2C expansion board ports, nada...I get an I/O error. After some quick troubleshooting, I see that the device is no longer seen on the I2C bus when i do an i2cdetect command. The fact that the bus pins are confirmed functional, and its specifically with the board ports, it suggests to me there is something more needed that I'm missing.
I have a second I2C expansion board, same issue, so would not appear the board is defective.
Jumpers are on the 3.3v pins as I've confirmed they should be.
I'm running debian-mate, and since I2C works from the bus pins, I don't see it as an OS issue. KH Goh mentioned checking bus speed and confirming its at 10 khz, but would think bus speed would not be a factor as far as being able to see the device on the bus. That said, if anyone can tell me where within the OS configs I can check I2C bus speed, I'd love to eliminate that possibility and also know where it is for future reference.
There is not a lot of detail on the wiki page regarding the expansion board, but I interpret what is there to suggest that I should be able treat the expansion ports just like I would a connection direct to the bus pins.
Thoughts?
I'm using the Pine temp/humidity sensor...tested with some python code (grabbed from the web and modified) and the sensor works great when using the Pi Bus I2C pins. It also works with the I2C expansion board plugged in and connected to the expansion board pins.
When I plug into one (any) of the I2C expansion board ports, nada...I get an I/O error. After some quick troubleshooting, I see that the device is no longer seen on the I2C bus when i do an i2cdetect command. The fact that the bus pins are confirmed functional, and its specifically with the board ports, it suggests to me there is something more needed that I'm missing.
I have a second I2C expansion board, same issue, so would not appear the board is defective.
Jumpers are on the 3.3v pins as I've confirmed they should be.
I'm running debian-mate, and since I2C works from the bus pins, I don't see it as an OS issue. KH Goh mentioned checking bus speed and confirming its at 10 khz, but would think bus speed would not be a factor as far as being able to see the device on the bus. That said, if anyone can tell me where within the OS configs I can check I2C bus speed, I'd love to eliminate that possibility and also know where it is for future reference.
There is not a lot of detail on the wiki page regarding the expansion board, but I interpret what is there to suggest that I should be able treat the expansion ports just like I would a connection direct to the bus pins.
Thoughts?