You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello guys, I'm a noob with upsplus, but quite experienced with 18650 cells and projects.
I just got my Upsplus running with a Raspberry Pi, but somehow the battery reading is completely wrong,
I've fully charged my batteries with a external 18650 charger (Opus BT-C3100) but once inserted in the Upsplus, the reading is about 3.6v.
Have anyone experienced such issue?
The cells are brand new panasonic NCR18650B, I've also tried to discharge them on the Opus, and the reading was way bellow reality as well. (2.9v)
Of course I double check that with the multimeter, and the readings on the Upsplus are always way bellow.
The text was updated successfully, but these errors were encountered:
pedroo84
changed the title
UPS Reading battery voltage wrong
UPS Reading battery voltage wrong - Way bellow reality - NCR18650B Cells
Oct 18, 2021
What I do for what functions is: turn off the ups (bus.write_byte_data(DEVICE_ADDR, 24,120)), remove the power, remove the batteries, put the batteries back and finally, put the usb power. It doesn't always work the first time. And other times, it shows the correct voltage and as the days go by, it shows 3.6 volts again.
Hello guys, I'm a noob with upsplus, but quite experienced with 18650 cells and projects.
I just got my Upsplus running with a Raspberry Pi, but somehow the battery reading is completely wrong,
I've fully charged my batteries with a external 18650 charger (Opus BT-C3100) but once inserted in the Upsplus, the reading is about 3.6v.
Have anyone experienced such issue?
The cells are brand new panasonic NCR18650B, I've also tried to discharge them on the Opus, and the reading was way bellow reality as well. (2.9v)
Of course I double check that with the multimeter, and the readings on the Upsplus are always way bellow.
The text was updated successfully, but these errors were encountered: