Battery Charging: Difference between revisions
m (→EEPROM init) |
|||
Line 58: | Line 58: | ||
EEPROM rewrite procedure: |
EEPROM rewrite procedure: |
||
# Download the 'batman.fth' forth code recovery program from [http://dev.laptop.org/~rsmith/batman.fth batman.fth] and save it onto a USB disk. |
# Download the 'batman.fth' forth code recovery program from [http://dev.laptop.org/~rsmith/batman.fth batman.fth] and save it onto a USB disk in the very top directory. |
||
# Put that USB disk into the XO and power up the XO. |
# Put that USB disk into the XO and power up the XO. |
||
# When OpenFirmware boots watch for the following text<br><code>Type any key to interrupt automatic startup</code><br>When you see this string do as instructed and press a key on the keyboard. This will place you at the 'ok' prompt. |
# When OpenFirmware boots watch for the following text<br><code>Type any key to interrupt automatic startup</code><br>When you see this string do as instructed and press a key on the keyboard. This will place you at the 'ok' prompt. |
||
# Load the batman.fth program by typing<br><code>fload disk:\batman.fth</code><br> |
|||
# Run the recover program<br><code>bat-check-and-recover</code><br>This will either |
|||
==Long Term Storage== |
==Long Term Storage== |
Revision as of 23:39, 30 March 2007
Battery Charging
Types of Batteries
OLPC is using two battery chemistries: NiMH, and LiFePo4 batteries. The LiFePo4 batteries allow charging at higher temperatures. The NiMH batteries cannot be charged above about 45 degrees C.
The LiFePO4 batteries have labels "Battery sample" on them, and are lighter than NiMH. The LiFePO4 batteries have more capacity because they can be charged to max capacity. In order to achieve 2000 cycles with a NiMH we have to reserve capacity to prevent overcharging. Overcharging significantly reduces the life of a NiMH battery.
Battery Charging Issues
Field reports from the BTest-1 and BTest-2 units have have provided us with information on several different types of battery charging issues. The 2 major symptoms are:
1. Units that will not power up when a battery is inserted even when plugged into AC.
2. Batteries that are not recognized/charged.
Symptom 1: This is a hardware problem with BTest-1 systems where a very low battery voltage will prevent the power system from starting up correctly. You can tell this is the case if:
- You cannot power up your BTest-1 system with a battery inserted even if its plugged up on AC power.
- You insert the battery on a running BTest-1 system and it instantly shuts off.
BTest-2 systems do not have this problem and will start up properly.
Symptom 2: This is the result of a firmware bug that would corrupt some info stored inside the battery. You can tell this is the case if:
- You insert a battery and nothing happens with the battery indicator light.
[Insert picture of battery light here]
In some cases both symptoms may be present at the same time.
Recovery of Dead Batteries
The first step in battery recovery is to upgrade the firmware to B83 or later. Please see Autoreinstallation image or Upgrading the firmware for details on how to update your firmware.
Additional tools that may be needed:
- USB keyboard.
Once you have upgraded then the exact methods depend on what system you have.
BTest-1 Systems
- Symptom 1
- BTest-1 systems are not capable of trickle charging batteries. If your battery has discharged to a very low capacity then they must be externally charged. To recover these batteries please see External Charging.
- Symptom 2
- Follow the EEPROM Init procedure.
BTest-2 Systems
- Symptom 1
- BTest-2 systems can trickle charge. Please insert the battery into a BTest-2 system and leave it plugged up to AC power for 6 hours. Your battery indicator light may or may not light up depending on the status of the EEPROM inside the battery. After you have charged for 6 hours then please follow EEPROM Init.
- Symptom 2
- Follow the EEPROM Init procedure.
EEPROM init
The following is a procedure for recovering batteries with corrupted EEPROM info. This procedure requires that the embedded controller (EC) in the laptop be placed into reset. As a result the keyboard and buttons will quit working. Once you follow the procedure you will have to unplug the XO from AC power and remove the battery.
If you have a USB keyboard then the power cycle is not necessary. USB keyboards are not affected by the EC and you can reboot with by typing 'reboot' at the 'ok' prompt.
EEPROM rewrite procedure:
- Download the 'batman.fth' forth code recovery program from batman.fth and save it onto a USB disk in the very top directory.
- Put that USB disk into the XO and power up the XO.
- When OpenFirmware boots watch for the following text
Type any key to interrupt automatic startup
When you see this string do as instructed and press a key on the keyboard. This will place you at the 'ok' prompt. - Load the batman.fth program by typing
fload disk:\batman.fth
- Run the recover program
bat-check-and-recover
This will either
Long Term Storage
If you plan to store a system for many weeks or months, your best strategy is to fully charge the battery and remove the battery from the laptop. Batteries naturally lose charge with time (how fast depends on the battery and its chemistry), and the embedded controller in the laptop, while sipping tiny amounts of power in its low power state, will drain the battery faster. Even though BTest-2 systems should now always be able to recover batteries that are fully discharged (except those noted above), it is a trickle charge process and time consuming.
As you can see above, letting a battery drain all the way will cause problems when recharging, how severe depends on the circumstances.
This strategy to remove batteries is true for all battery powered equipment, from flashlights up. Batteries sometimes leak. And some chemistries of Lithium batteries (not LiFePo) can get into a metastable state where they cannot be recharged.