|
|
Wiki > Main > IriverBattery (compare)
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Difference: IriverBattery (r15 vs. r14)iRiver battery informationH100The following results were gathered by running mpa2wav in a loop and collecting battery level (For the technically inclined, I did this by adding int adc_read(int) to the plugin api struct, and calling adc_read(2) from my plugin) each time the decoding starts over. Current consumptionThe following values were gathered by connecting the battery connector inside the player directly to an Agilent power supply. After that the voltage level was set to 3.70V and current limit to 2.000A.
The decoding current was same no matter what codec/bitrate we used or if the playback was paused or not. Also the battery indicator in debug menu is accurate, only with +- 0.05V error. If a fully charged battery level (4.2V) was put to the system, CPU takes only 51 mA at 48 MHz. With empty battery (3.0V) the system current was 73 mA. GraphsThe following results were gathered by running mpa2wav in a loop and collecting battery level (For the technically inclined, I did this by adding int adc_read(int) to the plugin api struct, and calling adc_read(2) from my plugin) each time the decoding starts over. Logs attached - see bottom. 11MHz:
48MHz:
120MHz:
Same as the above, except only read the mp3 once, and never write anything (meaning less HDD access, but still access when writing the battery log).
r15 - 19 Sep 2005 - 14:58:13 - JonasHaeggqvist
Revision r15 - 19 Sep 2005 - 14:58 - JonasHaeggqvistRevision r14 - 27 Mar 2005 - 11:54 - JonasHaeggqvist Copyright © by the contributing authors.
|