How to get rid of errno 121 remote Io error?
The lazy hobbyist knew where was the problem, so removed one pullup, but the error did not go away. So the lazy guy removed one more, and then one more, until all pullups were removed, then everybody was happy, and the error 121 remote IO error disappeared. But the error kept coming back intermittently.
What to do when you get remote I / O error in Python?
What I usually do when first using any I2C device, is remove the device’s built in pullups. This is almost an immediately cure, when I got the Error 121, remote IO error. You may like to google around to see the pictures of how other happy guys removing their I2C chips built in pull ups and problem solved.
Why do I get remote I / O error with SMBus on?
Electrical connection is perfect so this is not the issues. Furthermore I also dont get any errors while using i2cget -y 1 0x04 Only the python scripts sucks sometime and I dont know why.
What causes RPI to get a remote I2C error?
If your connecting wires are longer than 15cm, then they are antennas picking up nearby 50/60Hz mains EMI waves, which might also cause trouble. There are perhaps a couple of more trouble making causes I forgot. Perhaps I would update later. I almost never use Rpi’s built in SCL/SDA signals.
What does remote I / O error message mean on Raspberry Pi?
Th problem is I suddently getting an error message when the script is running for the moment OSError: [Errno 121] Remote I/O error when use smbus library so I change it to pigpio but get an error message pigpio.error: ‘I2C read failed’
Why do I get errors while using i2cget-y?
Furthermore I also dont get any errors while using i2cget -y 1 0x04 Only the python scripts sucks sometime and I dont know why. I register an onReceive and an onRequestEvent. onReceive Callback will define what kind of data should be send back to the raspberry. onRequest Callback does the response.