Battery Test - Test Your Batteries Life


mc power 3000 mah bought from ebay...

STATISTICS:
Clock Speed: 200 Mhz
Running Time: 3:25:37
Average FPS: 81.73

Current charge: 9%
Initial internal charge: 976
Current internal charge: 674

STATISTICS:
Clock Speed: 245 Mhz
Running Time: 3:05:55
Average FPS: 99.91

Current charge: 10%
Initial internal charge: 897
Current internal charge: 675

imo pretty bad for a 3000 mah
 
NaCCuRiT posted on Dec 7 2006 at 10:47 PM said:
imo pretty bad for a 3000 mah

most batteries over 2700mAh never actually reach that level, and it's just marketing spin by unscrupulous companies. If you look here you'll see that even Uniross 2300mAh only reach 1795.15mAh under optimal conditions in real world tests (some brands like Ansmann give results much closer to the stated value though). I've also seen reports of some cheap batteries being completely mislabeled by up to 200mAh (ie. the "company" flat out lies about it).

So taking that into account, the batteries you've got could be mislabeled 2800mAh ones, giving real world values in the range 2500-2700mAh.

2700mAh seems to be the highest "real" value batteries can reach at the moment. I seem to remember reading somewhere that 3000mAh are on the horizon for 2007, but I'd wait until a respectable company such as Ansmann announces it before you take it to be the truth.
 
Last edited by a moderator:
thanks for the info, xythen

Weird part is the 3000 mah is about 2 hours long 90-100% of the accu status
After the 2 hours the accu is going down very fast ( tested 5 times...)
 
Maplin 2400 Nimah *note: unsused for months*

STATISTICS:
Clock Speed: 200 Mhz
Running Time: 1:15:00
Average FPS: 81.78

Current charge: 12%
Initial internal charge: 821
Current internal charge: 678

STATISTICS:
Clock Speed: 266 Mhz
Running Time: 0:56:16
Average FPS: 109.22

Current charge: 9%
Initial internal charge: 940
Current internal charge: 674



I did test some fujicells that got nearly 2 hours 30 but i wiped the stats <_<
 
Duracell 2500

Clock Speed: 200 Mhz
Running Time: 3:20:00
Average FPS: 81.56

Current charge: 17%
Initial internal charge: 811
Current internal charge: 684

Why did it stop at 17%??


Lenmar 2000

Clock Speed: 200 Mhz
Running Time: 2:15:00
Average FPS: 81.56

Current charge: 0%
Initial internal charge: 787
Current internal charge: 631
 
OK! Here they are! This is the battery I have gotten a few board and many PM requests about since I announced I had them...

015.jpg


I ran a pair of them down in a flashlight 5 times then ran this program twice(7 charges/discharges). They were almost the same actually...

GPX-GP2X-F100( B ) MKII
Firmware 2.0.0
Blank 512MB SD card (Not running GMenu or anything if it makes a difference)
Energizer 2500mAh charger
Clock Speed: 200MHz
File writes: 5 minutes

---------------------------------
RUN ONE(last night):

STATISTICS:
Clock Speed: 200 Mhz
Running Time: 3:55:00
Average FPS: 82.16

Current charge: 34%
Initial internal charge: 906
Current internal charge: 722
---------------------------------
RUN TWO(just finished now):

STATISTICS:
Clock Speed: 200 Mhz
Running Time: 3:50:00
Average FPS: 81.32

Current charge: 45%
Initial internal charge: 911
Current internal charge: 719
---------------------------------

I started watching it drop like a stone last night at about 3:46:19 from 92% to 13%(3:58:42) then got the white scanlines for a few seconds to a pure white screen with one black bar across it for another few seconds to ... dead. The battery level meter seems like it might not be calibrated? Anyway there's the results. :)

On a side note I sadly found my GP2X won't run at 245MHz(in this program at least) for longer than 2:00 or so. Best I could maintain was 233MHz. Bleh... :blink: :blink: :blink: :blink: :blink: :blink:

Edit: Added the charger.

Edit 2: Added a 3rd run below.

---------------------------------
RUN THREE(ran before I went to work):

STATISTICS:
Clock Speed: 200 Mhz
Running Time: 3:55:00
Average FPS: 81.15

Current charge: 5%
Initial internal charge: 979
Current internal charge: 669
---------------------------------
 
Ok... Here's the state of my current research in to the dark world of recharging batteries...
[Not recommeding products from any of these sites, but the info may be of use].

http://www.digibattery.com/ - For a quick charge time calculator for those of you with manual chargers.

http://www.digibattery.co.uk/nimh_charger_faqs.html - For a handy FAQ on charger issues. Note the line "as it is always preferable to undercharge NiMH batteries than overcharge them". I'm guessing that's a long term use issue.

And the final entry http://www.imaging-resource.com/ACCS/BATTS/BATTS.HTM - For a slightly out dated, but still very handy review. The Watt hours vs mAh section towards the end of the article is very handy, as is the comment that the right or wrong charger can double (or half) the result for the same battery.

Now I'm not about to rig up a breadboard battery tester, but I am going to go find a decent charger with V-Delta cut off to keep these heavy little 2700 rated batteries sweet...
 
Short Question for the People, who have experience with this program (I was too lazy yet to test it XD )
Can you see a difference in the Battery Life with/without the faster RAM-Timings?
 
Rivroner posted on Feb 12 2007 at 11:58 AM said:
Some weeks ago Puck2099 launch Battery Test 2.It´s like first one except now it have a Validation Key:
I'd feel more comfortable if Puck2099 (author) had put this new version 2 in his file repository (http://www.gp32wip.com/projects/), but v0.1 is the only one there. There is no readme either for v2. Did he really write v2 or is it an unofficial version?
 
Last edited by a moderator:
He didn´t say nothing about official or unofficial, simply put it on a thread :D
 
What does a 'validation key' do and how do you know I have posted so quickly?! :D
 
Hi,

I uploaded in that thread Battery Test v2 in order to test that the 5:27 hours weren't a fake (and it wasn't :huh: ).

It's a beta version that I uploaded also to test it with real results, the only difference with the "public one" is the validation key, a "crypted" code to found fakes. It has a bug: the validation key doesn't work with much hours (like the 10 hours obtained with the hacked battery pack), so I'll update it and public a new public version (v2) when it'll be finished.

Take it as a WIP version :p

Sorry if my English is worse than usual, but it's quite late here and I'm so tired coding University's practices (I hate Pascal :( )...

Regards
 
imhotep posted on Feb 14 2007 at 01:14 AM said:
What does a 'validation key' do and how do you know I have posted so quickly?! :D

Puck can verify that your test is real.You know, there is people who like to cheat....

I am always pressing F5 :D
 
Last edited by a moderator:
Puck2099 posted on Feb 14 2007 at 11:23 AM said:
so I'll update it and public a new public version (v2) when it'll be finished.
Thanks, Puck. I am really enjoying testing all my batteries. It's a very useful app and thanks for keeping all the English speakers in these forums informed.

The results below are pretty run of the mill for 2300mAh I would say.
PowerCell 2300mAh
@200 MHz = 3:10:00
@260 MHz = 2:40:00

However, I got some very interesting results with some Inca 2700mAh batteries I purchased a few weeks ago. I wasn't optimistic before purchase as I had never heard of them before.
@200 MHz = 4:46:38 <-- amazing :D
@260 MHz = 1:40:00 <-- what the??! :ph34r:

The Incas seem to be alot better than average at stock speed, but considerably worse than average when overclocked (compare to the PowerCell results above). It is interesting how most brands are more optmised for the super high drain caused by overclocking (check the 270 MHz results at http://wiki.gp32spain.com/index.php/Pilas), but these Incas seem more appropriate for standard clock speed. It will be interesting to see what a middle clock speed will produce.
 
Last edited by a moderator:
Nice program, been testing my batteries too only problem is lack of sound testing? How much would sound effect battery life? Anyway here's my results for 7dayshop.com 2800 Ni-MH batteries

Set 1:

STATISTICS:
Clock Speed: 200 Mhz
Running Time: 4:40:00
Average FPS: 81.85

Current charge: 29%
Initial internal charge: 911
Current internal charge: 699

Got white screen lines on 4:43:~

Set 2:

STATISTICS:
Clock Speed: 200 Mhz
Running Time: 4:40:00
Average FPS: 81.68

Current charge: 50%
Initial internal charge: 921
Current internal charge: 726

Again got white screen lines on 4:41:~

Set 2:

STATISTICS:
Clock Speed: 280 Mhz :D
Running Time: 3:58:34
Average FPS: 114.20

Current charge: 10%
Initial internal charge: 924
Current internal charge: 675

Wasn't there when they finally died assuming at around 4:00:~

Got to say that reading from the forums people say that overclocking kills your batteries but 40 mins doesn't sound that bad to me, maybe because of the higher capacity? :huh:
 
Zenny posted on Feb 15 2007 at 03:29 AM said:
Got to say that reading from the forums people say that overclocking kills your batteries but 40 mins doesn't sound that bad to me, maybe because of the higher capacity? :huh:
That's what's so great about this app. You found out that extreme overclocking only affects your batteries a little bit. You can overclock to your hearts content! B)

I on the other hand lose 3 hours if I overclock to 260 MHz with my Incas, but only 30 mins if I overclock to this level with my PowerCell brand (Overclocking to 233 is ok on my Incas though.).

P.S. I think that sound is probably unnecessary for this app. It would likely just lower your frame rate a little, but not affect actual length of battery life.
 
Last edited by a moderator:
Back
Top