ölkjölkajsdopiewr
- http://www.eagletac.com/html/d25arc/index.html (D25A Clicky intro)
- http://www.eagletac.com/html/d25arc/specs.html (extensive specs sheet)
- http://www.eagletac.com/html/d25arc/features/output.html (beamshots)
- http://www.eagletac.com/html/d25arc/features/efficiency.html (circuit design)
- http://www.eagletac.com/html/d25arc/features/control.html (user interface)
- http://www.eagletac.com/html/d25arc/features/details.html (nice features)
- http://www.eagletac.com/download/gallery/d25arcstd.zip (download pics)
- http://www.eagletac.com/download/gallery/d25archd.zip (download pics HD)
- http://www.eagletac.com/download/readme/d25rc.pdf (download manual)
- http://www.eagletac.com/html/d_series/compare-d-rc-series/index.html (comparison to other Clicky's)
- http://www.eagletac.com/html/d_series/d25_clicky_series.html (Clicky series overview)
- http://www.eagletac.com/html/d25ti/features/index.html (2011 Titanium Mini)
- http://www.eagletac.com/html/d25tirc/features/index.html (2012 Titanium Clicky)
- http://www.eagletac.com/html/d25tirc_2/features/index.html (2013 Titanium Clicky)
äöäöüpüpoijkjkj
"Obtain EagleTac custom made M1.55 hex key from us or ET dealers to fasten the pocket clip holding screws. Regular M1.5 hex key may strip the screws."
i got the custom allen key from ET factory, my measurements: ~1.65mm (1.60-1.70mm width)
o-ring at tailcap is very delicate, dimensions, my measurements: 12.0x0.65x13.3mm. hard to resource from anywhere.
a spare o-ring for the head is included.
torch tailstands firmly, you wont need a spare boot, it's a custom-sized GITD boot for which you cant find a replacement rubber boot on the after-market so forget it duh.
this light is probably the overall best light of its class, hard to beat in total score, and it deserves an enthusiastic subjective leview from a user in luv :love:
at the heart of the text-heavy leview will be the details of the following epic informative table:
D25A Clicky 2013 Ti XP-G2 R5 CW|
ANSI lumen |
estimated FENIX lumen |
measured FENIX lumen (1.0s … 30s ANSI) |
full cell current |
empty cell current |
estimated runtime |
measured continuous runtime |
measured accumulated Tu1 runtime |
PWM | stabilized | |
| Eneloop-Lo2 | "0.5lm",150+h | ~0.9lm | 0.3…0.3lm |
0.011A↑ | 0.017A |
~143h |
( untested ) |
— | N |
Y |
| Eneloop-Med2 | "10lm",20h | ~8lm |
4.8…4.7lm |
0.040A↑ | 0.142A |
~22.0h |
40h3min #5:1.1677V 1876mAh 40h45min #6:1.1623V 1898mAh |
— | Y |
Y |
| Eneloop-Hi2 | "73lm",2.5h | ~85lm |
103.8…99.9lm |
0.748A↑ | 1.382A| 1.944A** |
~1.9h |
2h10min #5:1.2178V 1819mAh |
— | N |
Y |
| Eneloop-Lo1 | "0.5lm",150+h | ~1.1lm | 0.4…0.4lm |
0.012A↑ | 0.015A |
~148h |
( untested ) |
— | Y |
Y |
| Eneloop-Med1 | n/a | ~23lm |
19.7…19.3lm |
0.182A↑ | 0.440A |
~7.8h |
10h12min #6:1.1842V 1961mAh |
— | Y |
Y |
| Eneloop-Hi1 | "73lm",2.5h | ~85lm | 103.8…99.9lm |
0.768A↑ | 1.261A| 1.942A** |
~2.0h |
2h12min #7:1.2109V 1923mAh |
— | N |
Y |
Eneloop-Tu: Tu1/ Tu2 |
"121lm",1.3h | ~136lm/ ~45lm |
160.3…146.3lm/ 49.8lm |
2.1A↓/ 0.333A↑ |
1.023A |
~2.8h |
4h56min #4:1.2126V 1930mAh |
63min00s #6:1.1909V 1854mAh 60min52s #2:1.2219V 1813mAh |
N/N |
"N"/Y |
| 14500-Lo2 | n/a | ~11lm |
10.3…10.3lm creamish |
0.040A↑ | 0.048A | ~18.8h |
17h53min10s #2:0.0000V |
— | N |
Y |
| 14500-Med2 | n/a | ~120lm |
141.7…137.2lm |
0.480A↓ | 0.229A↓ | ~2.5h |
2h4min #5:3.490V |
— | Y |
N |
14500-Hi2 |
n/a | ~337lm |
421.7…371.9lm |
1.322A↓ | 0.551A↓ |
~53min | 1h3min40s #5:0.0000V |
— | N |
N |
| 14500-Lo1 | n/a | ~6lm |
4.7…4.7lm purplish |
0.022A↑ | 0.029A | ~32.5h |
35h21min01s #2:0.0000V |
— | Y |
Y |
| 14500-Med1 | n/a | ~120lm |
141.7…137.2lm | 0.465A↓ | 0.231A↓ | ~2.4h |
2h29min #2:3.220V |
— | Y |
N |
| 14500-Hi1 | n/a | ~337lm |
421.7…371.9lm | 1.271A↓ | 0.550A↓ | ~55min | 1h1min16s #1:0.0000V |
— | N |
N |
| 14500-Tu | n/a | ~337lm |
421.7…371.9lm | 1.277A↓ | ~49min |
1h4min59s #2:0.0000V |
55min22s #2:0.0000V |
N | N |
**In Eneloop Turbo-mode the torch does a step-down after 202secs. Before the step-down the light goes in some sort of direct drive ("Tu1"), after the step-down it goes into regulated drive with stabilized output ("Tu2"). Currents and brightnesses are given for both drives. However, this applies to Eneloop only; on 14500 the torch does not do any step-down on Turbo-mode. In fact, 14500-Turbo, 14500-Hi1, and 14500-Hi2 appear to be the same deal, i.e. the same max brightness level and with no step-down duh. Accumulated runtime is for 1min Tu1 intervals, see below for details. Currents in italics are plain wrong measurements caused by the DMM shunt resistor effect which effects the circuitry at this point and falsifies measurement data. I left them in the table for future reference when re-doing the measurements with a more refined amperemeter wtf. Tu1 is not a stabilized level per se but no matter how empty the Eneloop cell is the torch would always start off with a ~2.1A current draw ("turbo boost") which then slowly drops to ~1.9A during the 202secs. Since a "constant 2.1" doesnt compensate for the voltage drop of depleted Eneloops brightness isnt exactly the same yet it does stay on a similar top level where one cannot perceive a dimming effect, Tu1@1.20V ≤ Tu1@1.51V. At the step-down, from 1.9A down to 0.333A, the light reduces much of its output, Eneloop: Lo2≤Lo1<Med2<Med1<Tu2<Hi1=Hi2<Tu1. Technical note: 14500 amperages depend heavily on the 14500 sample quality, even if it's the same model, here: different samples of Protected TF flames 14500.
From the above table we learn that we got 5 noticeably different brightness levels on Eneloop, all stabilized, in order of ascending lumens output, ..
- Eneloop-Lo1 ~ Eneloop-Lo2. If there were a perceivable difference, then Eneloop-Lo2 ≤ Eneloop-Lo1 but in practice they are about the same.
- Eneloop-Med2
- Eneloop-Med1
- Eneloop-Hi1 = Eneloop-Hi2
- Eneloop-Tu (Tu1 steps down to stabilized Tu2)
.. and 4 noticeably different brightness levels on 14500, in order of ascending lumens output:
- 14500-Lo1 (purplish tint lol, PWM), stabilized
- 14500-Lo2 (creamish tint, PWM-free), stabilized
- 14500-Med1 ~ 14500-Med2, dimming
- 14500-Hi1 = 14500-Hi2 = 14500-Tu (no step-down in either), dimming
Accumulated runtimes
The product webpage states that both on Hi- and Turbo-modes the torch should not run unattended and should run for short time intervals only in order to control the produced heat and lower the risk of damage to the LED due to extended exposure of excessive heat. Eagletac is the first power LED flashlight company to verbalize such instructions and warning in an explicit manner, and it expresses their level of attention, frank information, professionalism, and pursuit of communication, which I all find highly commendable. This company is serious about their product creations and business:
Fenix puts similar attention to detail and communication and the operator's manual for the Fenix PD32UE officially introduces the quantity of accumulated runtime, a concept unheard of before in a printed manual:
Adopting this ingenious and helpful concept, I performed 2 different accumulated runtime tests on Eneloop (2000mAh+) and 1 test on 14500 (800mAh+), all on Turbo-modes:
- Eneloop AA, 3.5min cycles: (202.5s Tu1 + 7.5s rest) +(202.5s Tu1 +..etc.
- Eneloop AA, 10min cycles: (1min Tu1 +9min rest) +(1min Tu1 +..etc.
- 14500, 10min cycles: (1min Tu1 +9min rest) +(1min Tu1 +..etc.
Note that the torch, on Eneloop (i.e. not on 14500's!), does a stepdown from Tu1 (estimated ~136 Fenix lumens) down to Tu2 (estimated ~45 Fenix lumens) after exact 202.5 seconds. A huge step, i know. And that's the reason why on Turbo-mode the continuous Eneloop-runtime can be as long as 4h56min wtf.
For the 3.5min cycles, i timed the 202.5s and, as soon as the stepdown occurred, switched off the light, let it rest for 7.5s, then switched the light back on (new cycle!), turned it off after ~203s, let it rest for ~7s, and so on. If you are confused and dont know your maths, 210sec equal 3.5min :p haha so there you have it. For 17 cycles the light would go into Tu1-mode and do the stepdown after 202.5s. During the 18th cycle i noticed dimming of the light and no stepdown after 202.5s, so i decided to stop the test after those 3.5mins. Hot off the light, the Eneloop had ~0.97V offline voltage which would recover to 1.2219V after 24hrs+. Total accumulated runtime for this Eneloop test, 60min52sec (=17x 202.5s +3.5mins).
For the 10min cycles, i switched off the light after 60s —no stepdown had occurred until then— to give it a 9min rest. During the 9min rest i ejected the cell and monitored the recovering offline voltage, and shortly before reinserting the cell for the next cycle, i noted down its "resting" voltage. As we know, 9mins are not enough to let a cell recover to steady state, but whatcha gonna do about it. From the Eneloop voltage readings I got an idea when to officially stop the test, the Protected 14500 test ended abruptly when the cell's protection tripped.
Please dont be bored by these columns of numbers. It took 3 days to gather the data and i take the right to clutter up this review with them for your molestation. If you do feel molested, then i win, haha:
The 2 voltage columns can be visualized by plotting them together in the same scaled graph. On a common absolute y-scale {range: 0.00 .. 4.20V}, the graphs look kinda boring. However you do get a grasp of the relation and magnitude between them:
When we zoom in the 2 graphs and assign separate y-scales for higher resolution of the relevant voltage ranges, {2.80 .. 4.20V} vs. {1.10 .. 1.52V}, the graphs look much more dramatic and interesting:
I stopped the Eneloop-runtime test after 65min accumulated Tu1 runtime, 10h50mins total time had elapsed by then!, 9mins later i measured the cell's voltage to be 1.1200V, which after another 24hrs+ recovered to a steady 1.1909V. An indirect means of determining the consumed capacity is recharging the cell with C9000 at +1000mA default charge rate: since the cell was full before the test start and now is back full after the C9000 recharge, the charged capacity must equal the consumed capacity. Here, 1854mAh as displayed by the C9000. This means that the cell still had 150-200mAh capacity left (at 1.1909V resting voltage) which could have been used in RL for runs on the Med- and Lo-modes. From the Eneloop-graph it can be seen that the 'official' runtime, depending on one's definition ("50% brightness", "10% brightness", a. o.), is anything between 55..63min. For the table i picked 63min hope you're okay with that.
Similar to other lights on the market with Turbo-modes, e.g. the D25LC2, the D25A's Turbo-mode is not really stabilized and current would drop during the 202.5s of Tu1. However the attempt to draw a constant high current (see also Tank E09 on Hi-mode!) is one form of regulation (see Thrunite Ti for complete lack of any kind of regulation!), and in practice it is difficult to make out the brightness difference between 2.1A@1.53V versus 1.9A@1.23V: no matter how depleted the cell is, whenever you operate the Turbo-mode the torch would try to draw an average of ~2A from the Eneloop (or ~1A from the 14500) cell. After the stepdown, Tu2 is fully stabilized, and current would continuously rise starting from anything between 0.333 .. 1.023A, depending on how depleted the Eneloop is. Let's note again that on 14500, the Tu-mode equals the Hi1- and Hi2-modes and that there is no stepdown. Tu-/Hi1-/Hi2-modes on 14500 are not stabilized (as in "constant brightness") nor regulated (as in "constant current"); in other words, the dimming effect should be measurable with a lux meter or IS light box.
lölöäopüläöq
Brightness levels and lumens
People with a home-made DIY IS (integrating sphere) incl an integrated logging lux meter or embedded photodiodes can provide accurate measurements of relative brightness levels and, after serious calibration efforts, even estimate lumens relative to a chosen "ANSI" lumens scale. Despite the efforts of ANSI and PLATO and serious efforts of flashlight reviewers there is imho still no satisfactory solution to the standardization and lumens measurements of portable flashlights. What is more, how much do you believe lumens claims made by the manufacturers themselves or trust foreign people's words with the absence of a certification from a totally independent norm standards testing institute? My personal and most straight-forward take is to compare the lights and modes on a 1:1 basis to other lights from my collection. Compare how? Simply by eye and white wall double bounce.
The result of the comprehensive comparison is a long chain of inequalities and pseudo-equalities. This provides a qualitative measure as to the difference in brightness levels. Let's define the Eneloop modes moonlight/lo/med/hi/turbo of my lights as (14500 modes are in bold):
- P1A R5: Pl, Ph, Pl, Ph
- JR30 R5: Jl, Jm, Jh, J
- Archer 1A G2: Ao, Al, Am, Ah, Ao, Al, Am, Ah
- LD01 R4: Ll, Lm, Lh, Ll, Lm, Lh
- LD20 R5: Fl, Fm, Fh, Ft
- D25A G2: Dl, Dm1, Dm2, Dh, Dt1, Dt2, Dl1, Dl2, Dm, Dh
Then after hours of enjoyable couplings and comparisons i arrive at the following result:
Confusing? Confused? Maybe a little haha. The numbers in parantheses are the "ANSI" lol lumens ratings spec'ed by the manufacturers Klarus, Thrunite, Eagletac, Rofis and Fenix. Red numbers are overstated manufacturer ratings (mostly done by Thrunite!), blue numbers are imo understated lumens (mostly by Eagletac and also Rofis), and green numbers are trusted realistic conservative accurate reference lumens (all Fenix and some Rofis). After studying the numbers in this chain of relations i came to the conclusion that the Klarus and Thrunite specs are way out of line and useless, and it would be safe to take Fenix as the reference lumens scale: Fenix lights are known for industry-leading top efficiency and runtimes, sold world-wide and with high and easy availability and they never attracted attention with boldfaced dubious lumens claims. Fenix is Ch*na premium market leader #1 with the highest reputation in the flashlight scene and they were the first to proudly announce and implement the ANSI FL-1 standards and updates. The motto "we undelplomis and oveldeliva" might be true for Foursevens policy but once the Fenix lights are used as calibration reference the Fenix scale becomes a 100% accurate quasi-standard. In this regard the Eagletac D25-series lights are also underpromised-overdelivering products. Very annoying .. because it makes lumens comparisons impossible on basis of the specs papers.
Dt1 (or Eneloop-Tu1) is spec'ed at "121 ANSI lumens" by Eagletac. It's better to call them "121 ET lm". Fenix LD12 G2 is spec'ed at 125 Fenix lumens. Someone in possession of both lights now tell me which of the two is brighter and by which margin. Lemme be cheeky myself and simply claim that, without any RL tests and comparisons, the D25A outputs 136 Fenix lumens and thereby outputs 11 Fenix lumens more than the LD12 G2. I am likely to be right with this modest safe claim .. because who believes that the Fenix draws as much as 2.2A from an Eneloop AA as does the D25A?
In any case the D25A is noticeably brighter than the Archer 1A which by itself is boldly (and wrongly!) spec'ed at 178 TN lm by Thrunite. Crazy stuff, i know!
You're learning from all this, dont give a **** on lumens claims by Thrunite, Klarus, selfbuilt, Zebralight, Nitecore or even worse no name Chi*ese budget light brands (DX, XXXFire, EBAY, etc.). Instead, choose your own favorite lumens scale or Fenix reference lights and conduct manual comparisons on your own, let your eyes determine which light is brighter and if it is much brighter or not. There is for example a huge discrepancy of brightness between a 300 ZL lm light vs a 300 Fenix lm light, namely 300 Fenix lm » 300 ZL lm.
weasdqwe
yxcvbnmrtz
This op is a stub. You can help the author by expanding it.
.
