X1200 UPS not detected on Raspberry Pi 5 i2c | Geekworm's Forum
  1. Forum
  2. General Discussion
  3. X1200 UPS not detected on Raspberry Pi 5 i2c

X1200 UPS not detected on Raspberry Pi 5 i2c

  • k

    After installing fresh new X1200 UPS I can't get any status code from i2cdetect:

    i2cdetect -y 1
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:                         -- -- -- -- -- -- -- -- 
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
70: -- -- -- -- -- -- -- --

    I made sure that I enabled i2c interface in raspi-config, when running command to check if i2c is active it shows its working:

    ls /dev/i2c*
/dev/i2c-1  /dev/i2c-13  /dev/i2c-14

    In boot confix.txt, I also have active i2c:

    dtparam=i2c_arm=on

    I made sure the pins are well connected to the board, I even pressed boards harder together yet the command i2cdetect did not detect anything. Overall the UPS is working as it should, the batteries are charging and it works well, however I can't get i2c to detect it. Any way to fix this?

    0 likes
  • HH

    Hello

     

    1. Make sure you enable i2c interface, refer to How to enable I2C

    2. The UPS connects to the Pi GPIO via pogo pins, If the I2C address (0x36) is not detected, Please clear the leads of pin 3 and pin 5 on the GPIO header from the bottom of the Raspberry Pi PCB and install again, and also check if the pogo pin of ups shield is in close contact with the pad position of PI 5(you can adjust the [pogo pin] position).

    There won't be any other problems, it's this poor contact that's causing it.

    0 likes
  • k

    I already checked connections 4 times by disassembling it. I cleared the connections with rubber, even though they are very clean because my Pi is only one year old. I also sent logs confirming ic2 ports are enabled. I physically pressed both boards together at that connection you're showing, and i2c did not see anything.

    So I am not sure what to do now, but is that a big issue if i2c doesn't report anything? Atleast the UPS does its job.

    0 likes
  • D

    Did anyone find a fix for this, because I am also having the same issue; I have re-seated the pins multiple times but get that same set of dashes from i2cdetect?

    EDIT: I did find a solution; despite my RPI5 being an almost brand-new RPi5 board, which didn't look in any way dirty and despite having re-seated the pins multiple times, it appears that that still wasn't cleaning the pins enough.

    I eventually well-and-truly rubbed the pins down with 99.9% pure IPA. Now the connection seems to work and I can read the I2C battery fuel gauging chip.

  • T

    @Deloril I had the exact same experience!!  I struggled to figure out wth was going on.  Brand new Pi5, and no 36 - googled, found your post, took a q-tip and 99% iso and rubbed the crap out of all my header pins (for future need) - I also cleaned the pogo pins on the UPS Hat - reinstalled, booted up, and immediately have my 36 - and all the other commands work to see voltage, charging...and so on.  Thank you!!

    0 likes
Please login to reply to this topic!

Participants