PiSupply / PaPiRus

Resources for PaPiRus ePaper eInk displays
https://www.pi-supply.com/product/papirus-epaper-eink-screen-hat-for-raspberry-pi/
Other
346 stars 88 forks source link

IOError: [Errno 121] Remote I/O error #124

Closed eat-sleep-code closed 7 years ago

eat-sleep-code commented 7 years ago

I have a new Pi Zero W with the PaPiRus Zero. When I run any of the command line items, I get an error similar to:

File "/usr/local/bin/papirus-clear", line 29 in main() File "/usr/local/bin/papirus-clear", line 23 in main papirus = Papirus() File "/usr/local/lib/python2.7/dist-packages/papirus/epd.py", line 58, in init self._lm75b = LM75B() File "/usr/local/lib/python2.7/dist-packages/papirus/lm75b.py", line 22, in init self._bus.write_byte_data(self._address, LM75B_CONF_REGISTER, LM75B_CONF_NORMAL) IOError: [Errno 121] Remote I/O error

The Pi Zero is running the latest version of Jessie Lite.

tvoverbeek commented 7 years ago

Smells like the Zero W cannot communicate with the lm75b temperature sensor via I2C. Check I2C is enabled with raspi-config. If enabled then use i2cdetect (from the i2c-tools package, install if not there) . 'i2cdetect -y 1' should report a device on address 0x48 (the lm75b). If not check the connections between the Zero W and Papirus Zero.

shawaj commented 7 years ago

@eat-sleep-code did you get this sorted?

eat-sleep-code commented 7 years ago

Yeah, apparently a bad solder job. Switched to solderless hammer headers and it is working.

shawaj commented 7 years ago

@eat-sleep-code you mean that you're now using the hammer header or were before?

Because we've had issues with the hammer headers not getting a good connection previously. We recommend everyone to solder or buy one of our pre soldered Pi Zeros.

In any case, glad you've got it working

CentralHarlemAnonymous commented 5 years ago

I was getting the same error message so, per the advice above, I revisited my solder joints and cleaned up anything that looked suspicious. I also took he opportunity to remove a small splatter of solder on the underside of the board. Victory! Test code is now running without error. The hardware does as it should; when I power the machine down, my test remains on the screen.

shawaj commented 5 years ago

@MichaelSternNYC thanks for the input. What was the solder spatter and what were the dodgy looking connections. Would be interesting to know for our reference and to improve manufacture quality

CentralHarlemAnonymous commented 5 years ago

Not your lousy soldering — mine. I hadn’t done a great job putting headers on my Pi.

Von meinem iPhone gesendet.

On May 11, 2019, at 4:34 PM, Aaron Shaw notifications@github.com wrote:

@MichaelSternNYC thanks for the input. What was the solder spatter and what were the dodgy looking connections. Would be interesting to know for our reference and to improve manufacture quality

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

shawaj commented 5 years ago

Aha! Even better news 😁