# I2C issues on Pico W

**URL:** <https://forum.core-electronics.com.au/t/i2c-issues-on-pico-w/17570>\
**Category:** Raspberry Pi\
**Created:** [13 July 2023 11:47 UTC](https://forum.core-electronics.com.au/t/i2c-issues-on-pico-w/17570 "2023-07-13T11:47:02Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![James](https://yyz2.discourse-cdn.com/flex028/user_avatar/forum.core-electronics.com.au/james/32/4400_2.png) [@James](https://forum.core-electronics.com.au/u/James)\
**Post date:** [13 July 2023 23:17 UTC](https://forum.core-electronics.com.au/t/i2c-issues-on-pico-w/17570/3 "2023-07-13T23:17:48Z")

</div>

Hi Alan, welcome back. Keen to dig a little deeper into this with you.

> [@Alan37799](#):
>
> I found the post earlier today recommending that an updated version of PiicoDev\_Unified.py be installed, which I did.

This would’ve upgraded you to our more recent, “graceful” error handling, that instead of something cryptic:

> [@Alan37799](#):
>
> OSError: [Errno 5] EIO

Tells you what’s wrong and what to check first:

> [@Alan37799](#):
>
> ` PiicoDev could not communicate with module at address 0x3C, check wiring`

Just as a precaution, could you shoot us a photo of how you’ve got everything hooked up, and confirm that your address jumpers are set right?

 ![image](https://canada1.discourse-cdn.com/flex028/uploads/core_electronics/original/2X/b/bb97eefe81f0feb733ac7af3174c1cb2782a4b91.jpeg)

P.S. Once we’ve ruled out the basics, we can do stuff like replicate your setup over here.

---

_[View the full topic](https://forum.core-electronics.com.au/t/i2c-issues-on-pico-w/17570)._
