Update July 15th, 2019: I've added runtime graphs on the 4D version in post #21
Over the last couple of years, I've performed run-time tests on most of my other Maglites, and have always been able to validate their listed run-times using rechargeable NiMH batteries. The 6D ML300L was a notable exception.
A couple of months ago, I purchased the 6 D-cell version of the ML300L and noticed that Maglite's listed runtimes seem a bit unusual . . .
High - 71hrs
Low - 73hrs
Can that be correct? Perhaps a typo? High is only two hours less than low? This model has been in production for at least four years, but I couldn't find any runtime graphs for the 6 D-cell version.
Having done runtime tests on my other Maglites, I had to find out for myself what sorcery Maglite was using on the ML300L that allows "high" to be only two hours less than "low".
First, for high, I tried using six fully charged (and relatively new) Powerex NiMH D cells for a runtime test on high.
As you can see, I only got about 15hrs of runtime - nowhere near 71hrs. Is my light defective?
I'm aware that Maglite bases their runtimes on alkaline batteries. From their website:
OK fine, I will spend a little money in alkaline batteries to verify how much difference it might make. The next test is with six Duracell Quantum D batteries. As you can see, alkalines do in fact make a profound difference in runtime. The ML300L throttles down to about 12.5% brightness and stays there for over two days. It now becomes evident that Maglite is milking ANSI for all its worth - hovering just above the minimum ANSI 10% brightness level. Yes, technically Maglite's listed runtime are correct, assuming you use one of the better alkalines. My runtime was 17min longer than Maglite's.
The next runtime is for low - again using six Duracell Quantum D cells. Once again, my runtime was only minutes longer than Maglite (7 minutes).
In conclusion, we now see why high and low have similar runtimes. Low stays stable at approx 167 lumens, while high eventually throttles down much lower (to about 87 lumens). Note this was a learning experience for me, in understanding how some manufacturers achieve their listed runtimes. At one point, I considered requesting an RMA (return merchandise authorization) from Maglite, before I was able to confirm their runtimes.
Runtime tests were done using a Reed Instruments SD-1128 light meter data logger.
Those spex are only valid when the light’s sitting still. Once you start moving the light around, it goes into higher-current mode and runtime drops to 34.5hrs, but it’s lots brighter!
I think he means that moving the light around would allow for better cooling - the assumption would then be - that thermal regulation would affect the outcome.
Nobody remembers the Volkswagen “scandal”? The car runs in “clean” mode when on a treadmill and not moving (ie, it knows it’s being tested), but in Real Life™ it just runs nicer.
It was a joke. Like the funny kind, only different.
Oh, I’m sorry but english is not my first or second language . I do remember the Volkswagen incident, now I get it . I thought the flashlight had some kind of integrated motion sensor like there was or there is a maglite. I have always thought that motion sensors should be integrated into the flashlights for several purposes:
- If you have an accident in the mountain (or other distant place) and the flashlight know that is not moving then it would change to a beacon mode and very low consumption.
- If you forget to turn off a flashlight, she alone would go into saving mode.
- If an elderly person falls, the flashlight could switch to an alert mode or call for help.
You can turn on or turn off a flashlight by shaking it, baby!
There are many applications that I can think off, and with tiny accelerometers is even more easy for manufacturers or even hobbyist to integrated it in the drivers. But somehow motion sensors are not a “thing” in the flashlight world.
Per request, here is a dump of five other runtime graphs from five of my other Maglites. Note that these were done over the last two years, and the format is not always the same. Some of the graph's notes were meant for my own knowledge, and not necessarily for posting (keep that in mind). Some of the graph's lumens values are based on Maglite's spec, some are based on the Texas Ace Calibrated Lumens Tube. None-the-less, this is a great snapshot of how Maglite handles runtimes. One of Maglite's tricks that you'll see on some of their lights - is to have this initial spike at 40 sec (not 30 sec per ANSI) right after turn-on that only lasts a few seconds, which then becomes their basis for lumens output on high.
The first is my foliage green ML50LX, a 2C LED light (HIGH).
Yeah, I think there is a Mag that does that, an XL something? 500?
I could use that for mum. She leaves flashlights turned on overnight, etc., and claims she doesn’t. Crappy 3×AAA lights, but still. I burn down those “dead” cells in dumb lights that wring ’em dry, and I can’t even keep up, not even “wasting” them as nightlights.
Something that’d turn off the light after 5min of non-use would be ideal.
Thank you so much for this. So, they are cheating about the high mode, but no the low mode.
Still a lie, but at least they have the expected performance in low mode, sometimes is what you are looking for in a flashlight, low lumens but very long runtime.
. I do remember the Volkswagen incident, now I get it 
. I thought the flashlight had some kind of integrated motion sensor like there was or there is a maglite. I have always thought that motion sensors should be integrated into the flashlights for several purposes:
