-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Charging don't stop #87
Comments
Hi, some problem here. |
Problem is that device have full battery voltage 100mA higher than maximum of full voltage on batteries I don't know why.. |
@neresus , my batteries are 4.2V I'm feeding with info I got from the UPS Plus script: |
I think I may have the same issue as above. I have tried a couple of different batteries, have done the firmware update, reset to factory defaults, tried different chargers and tried setting the parameters manually. Still the UPS does not charge to 100%, https://api.52pi.com/ says "It seems that your battery is still not fully charged." The batteries I would like to be using are used LGDAME11865 (https://secondlifestorage.com/index.php?threads/lg-lgdame11865-cell-specifications.8332/) Output from upsPlus_iot.py Watching this thread with interest. |
With f/w v.10: |
I have 65W usb-c charger. Second day of charging 8,682V 0,2A... still not charged :( |
Unfortunately I, like many people here, have the exact same problem. I'm not sure what's up with the UPS, but it never stops charging, despite reaching 4.2V on the battery already. It won't go higher, of course.
You can even see I've set:
But unfortunately the UPS seems to ignore it? How do those settings work?
Could someone please explain how do those settings work? Firmware version is 10, as stated above. I would really wish to set the max voltage to some arbitrary number, to prolong the battery life (not to mention, I really want the UPS to stop constantly charging them when they are full already), probably at around 60-70% capacity, that's more than enough for my use case. I've also tried two different battery types, they are both 4.2V.
Makes me wonder what the "remaining capacity" is given that current bat voltage is above "max voltage" reported by Full-featured-demo-code.py as above... Is there a firmware version that actually honours the max voltage setting? Thank you. |
Hello. Is someone who haven't this issue and charging stops? Can you write here your batteries manufacturer and type? |
Currently on firmware version 14, seeing this issue as well. Charging never stops, I suspect because the batteries aren't isolated once full and continue to contribute something to powering the pi. As such the UPS is showing a charging current of like 40 mah. Is this going to damage the batteries? Or is this current low enough to be irrelevant for the battery lifespan? |
Hello. I'm using two different UPS Plus EP-1036 (rev. 5.4 2020-01-05 PCB03a) and (rev. 5.0 2020/12/23 PCB01b) both on Firmware v14. Because I can not revert to Firmware v10. OTA_firmware_upgrade.py failed to download any other Firmware version ("File not found"). |
Hello
I don't know what I am doing wrong.
I used litokala 18650 batteries and still have 3,7V on them after three days ups still charging.
Raspberry Pi power supply voltage: 5.084 V
Current current consumption of Raspberry Pi: 1791.590 mA
Current power consumption of Raspberry Pi: 8962.153 mW
Batteries Voltage: 3.736 V
Battery current (charging), rate: 360.000 mA
Current battery power supplement: 1253.659 mW
Current processor voltage: 3265 mV
Current Raspberry Pi report voltage: 5104 mV
Current battery port report voltage: 4211 mV
Current charging interface report voltage (Type C): 5010 mV
Current charging interface report voltage (Micro USB): 19 mV
Currently charging through Type C.
Current battery temperature (estimated): 48 degC
Full battery voltage: 4292 mV
Battery empty voltage: 3791 mV
Battery protection voltage: 3700 mV
Battery remaining capacity: 92 %
Sampling period: 2 Min
Current power state: normal
Shutdown countdown: 198 sec
Automatically turn on when there is external power supply!
Restart countdown: 198 sec
Accumulated running time: 3125 sec
Accumulated charged time: 3136 sec
This running time: 748 sec
Version number: 10
The text was updated successfully, but these errors were encountered: