#9955 NORM Not Tri: Battery has some issues as below.
Zarro Boogs per Child
bugtracker at laptop.org
Thu Jan 7 14:10:07 EST 2010
#9955: Battery has some issues as below.
------------------------------------+---------------------------------------
Reporter: Andy Pei | Owner:
Type: defect | Status: new
Priority: normal | Milestone: Not Triaged
Component: not assigned | Version: not specified
Resolution: | Keywords:
Next_action: never set | Verified: 0
Deployment_affected: | Blockedby:
Blocking: |
------------------------------------+---------------------------------------
Comment(by rsmith):
Replying to [comment:1 Andy Pei]:
> > (2)Battery volume auto go to 97% while charging from 86%.
The full charge marker is not based on time. The criteria for full is
Vbatt >= 7.4V and Ibatt <= 120mA. When this condition is reached the
battery is marked full and the SOC is set to 97%.
I can think of 3 possibilities for yout jumping behavior.
1) If the SOC is out of sync with the battery state then you would see a
large jump in SOC when
full is reached. The fix is to simply try agin. This time the SOC will
be in sync with the battery.
2) Incorrect 1% ACR. Our 1% SOC ACR differance may not be correct anymore
for the increased charge current of CL1B.
I ran some tests and although the charge current of CL1B is in general
400mA higher than CL1A it does not appear to affect the SOC counter rate
enough to cause a 11% offset. I do not beleive this is a problem.
3) Your battery has lower capactity than expected. You sould run a full
discharge/charge cycle and verify the capacity of the battery. olpc-pwr-
log will let you verify your capacity.
> == (./battery_life03 after charging finish check >log.txt) ==
Rather than battery_life03 please use 'olpc-pwr-log'. They record the
same information but olpc-pwr-log does not do the graphics and OLPC has
other tools that can process the log generate by olpc-pwr-log.
See: http://wiki.laptop.org/go/XO_power_draw#olpc-pwr-log
Do you have the log that battery_life03 generated? If so then please
attach.
> (3)Battery voltage and temperature show failed message by executing
Cl1batt test tool. Add test tool and fail picture.
What are you using as your pass/fail criteria for Voltage and Temperature?
--
Ticket URL: <http://dev.laptop.org/ticket/9955#comment:5>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system
More information about the Bugs
mailing list