You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A C project was found which uses the PiGPIO library. This C project should provide a good start.
Steps to reproduce with current code base (18 March 2016)
Currently if only one device is connected the code runs fine. In order to see this issue in action, connect at least two devices to the I2C bus.
Run commands such as i2cdetect -y 1 repeatedly. You will see inconsistent behavior with phantom devices appearing, devices disappearing, or no devices at all
The text was updated successfully, but these errors were encountered:
Used bit bang with pigpio library. With current hardware, it supports up to 3 devices over 9 feet/3 meters. This is limited due to the line's RC time constant. May look into shorter cables and test with more devices to see if it will work. Also need to look into possible redesign of hardware although I am happy with the result.
The bug is in the hardware of the Raspberry Pi. (See Raspberry Pi I2C clock-stretching bug for more information.)
A recomendation is to use the PiGPIO library to bit bang the I2C bus.
A C project was found which uses the PiGPIO library. This C project should provide a good start.
Steps to reproduce with current code base (18 March 2016)
i2cdetect -y 1
repeatedly. You will see inconsistent behavior with phantom devices appearing, devices disappearing, or no devices at allThe text was updated successfully, but these errors were encountered: