# Explorer Hat Pro believes it an Explorer Hat basic **URL:** \ **Category:** Support\ **Created:** [June 26, 2017, 6:52pm UTC](https://forums.pimoroni.com/t/explorer-hat-pro-believes-it-an-explorer-hat-basic/5136 "2017-06-26T18:52:08Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![GaryJFbr](https://avatars.discourse-cdn.com/v4/letter/g/c89c15/32.png) [@GaryJFbr](https://forums.pimoroni.com/u/GaryJFbr)\ **Post date:** [June 26, 2017, 6:52pm UTC](https://forums.pimoroni.com/t/explorer-hat-pro-believes-it-an-explorer-hat-basic/5136/1 "2017-06-26T18:52:08Z")
I’ve being using an Explorer Hat Pro with Scratch on a Pi Zero to read the analog output of an Adafruit UV Light Sensor S12SD. The out put is connected to analog 1 with the power from the 5v pin. I’m using Scratch 1.4 on a Pi Zero, although the same issue appears on a Pi 3. When the program is loaded the Pi displays a message stating the I2C needs to be enabled. On checking it is enabled. I’ve swapped the Explorer Hat Pro with another and the program works without a problem. The sensor is working correctly as I’ve checked on another identical setup. When I run the [test.py](http://test.py) program the first line says that an ‘Explorer Hat Basic’ has been detected. However, when run with my other Explorer Hat Pro this line states ‘Explorer Hat Pro’ detected. I’m guessing the board is faulty, unless anyone has any better suggestions. ---
**Author:** ![RogueM](https://sea2.discourse-cdn.com/flex016/user_avatar/forums.pimoroni.com/roguem/32/311_2.png) [@RogueM](https://forums.pimoroni.com/u/RogueM)\ **Post date:** [June 29, 2017, 3:17pm UTC](https://forums.pimoroni.com/t/explorer-hat-pro-believes-it-an-explorer-hat-basic/5136/2 "2017-06-29T15:17:18Z")
what do you get is you run: `i2cdetect -y 1` ---
**Author:** ![GaryJFbr](https://avatars.discourse-cdn.com/v4/letter/g/c89c15/32.png) [@GaryJFbr](https://forums.pimoroni.com/u/GaryJFbr)\ **Post date:** [June 29, 2017, 7:29pm UTC](https://forums.pimoroni.com/t/explorer-hat-pro-believes-it-an-explorer-hat-basic/5136/3 "2017-06-29T19:29:28Z")
i2cdetect -y 1 returns two addresses 0x28 which I think is the cap touch and 0xUU I think UU means drivers have been loaded and are waiting. The other boards return 0x48 so my guess is the ADC chip is fried