5

I was using my i2c OLED perfectly well when seemingly for no reason I started getting the Remote I/O Error when I ran my Python program. For some reason this was fixed by installing i2c tools again. This seemed to work several times (maybe it was just a strange coincidence). Now this doesn't work and I get the same errors. Another strange thing is that the i2c detect -y 1 is still reporting my OLED on 0x3C.

Here is the error code:Traceback (most recent call last): File "door_lock_code.py", line 13, in <module> disp.display() File "/usr/local/lib/python3.5/dist-packages/Adafruit_SSD1306-1.6.2-py3.5.egg/Adafruit_SSD1306/SSD1306.py", line 182, in display File "/usr/local/lib/python3.5/dist-packages/Adafruit_GPIO-1.0.3-py3.5.egg/Adafruit_GPIO/I2C.py", line 129, in writeList File "/usr/local/lib/python3.5/dist-packages/Adafruit_PureIO-0.2.3-py3.5.egg/Adafruit_PureIO/smbus.py", line 294, in write_i2c_block_data OSError: [Errno 121] Remote I/O error

Can anyone help me out?

Thanks, LouisP

P.S - I know this is similar to other threads but I think my errors are slightly different.

It was hard to capture pictures that were really clear but I have attached the ones I took. On the OLED, black is connected to the pin labelled GND, Red for VDD, Brown for SCK and Purple for SDA.Wiring picture

King Balloonion
  • 173
  • 1
  • 2
  • 14

1 Answers1

4

Since this used to work, I suspect that something is wrong with the wiring.

My suggestion is that one or more of the wires has an intermittent fault. I would get a new set of wires, and replace the wires one-by-one until things start working again. Please do not reuse any of the old wires for this test.

You will have to replace the wires while the Pi is turned off and unpowered. To do this more quickly, replace all the wires at the same time.

Another possibility is that the OLED might be faulty, but without more information, I have no ability to deal with this.

NomadMaker
  • 1,580
  • 10
  • 10