Well, you would need very long cables between driver and the LED - plus a thicker tube with place for those cables - or if you make it flatflex, you still need that.
It makes it just more complex - for example, how do you change the battery? You will have some cables in the way, no matter where you open the case
Not needing any wires going up the tube is the main reason, it simplifies manufacturing a ton.
Drivers typically produce very little heat, a few watts or tenths of a watt, so it’s not an issue to have it near the LED.
Even flashlights with charging in the tail cap choose to use a double ended battery (with both + and - on each end) to avoid any wires or other complications in the tube.
The Imalent DM 21 has driver and USB charger in the tailcap without wires running through the body. It is possible. Driver, battery and switch are all in series, so it shouldn’t matt where these component are in the string.
The Imalent DM21T does not have a wire going to the head. The driver (with brightness control knob) and usb charging are in the tail. It can be done without a wire running from driver to battery +.
The one thing the DM21T is missing is LVP. The driver does not have direct access to the battery voltage. LVP in their design would require a more complicated driver that approximates battery voltage by measuring current and knowing the Vf of the LED at that current.
So you see it can be done, but all that do charge a hefty price for their lights
For Narsil and Bistro based drivers that allow temp stepdown using the MCU it still is best to have led and driver close together or a temp sensor needs to be installed, adding complexity in parts and assembly AND sacrificing a MCU pin for the read out.
I am talking about BLF developed firmware that has the option to use the temp sensor build into the MCU for user calibrated thermal stepdown vs using extra parts to measure temperature.
It is quite useful to have the MCU located in the area where it can actually sense temp
You are talking about pretty names that some useless parts of firmware used to call here. Simple thermal resistor on pcb can do this job (thermal stepdown) better (much better) than mcu-integrated sensor (regardless what firmware do you use). There is no sense in applying so much efforts in firmaware which should manage so simple hardware.
FET is not driver. You can not garantee any value. Each of them will be always different. Simple things that are usual printed on brand light boxes - smth like runtime@100 lumens - cant be calculated, because fixed mods do not exist.
Hm. Sounds a bit negative.
I am not talking about FETs just stating hoe Narsil and Bistro achieve thermal stepdown without the need for a thermistor.
Yes as I wrote a dedicated part for measuring can be done.
Yes as you write, there is a big difference in how each individual driver without it measures temp.
(I have read it is the MCU doing the measuring not the FET)
Hence the clever workaround, one selects thermal stepdown instead of the default timed stepdown and the light starts on turbo, one selects the desired stepdown temp and it doesn’t really matter that other same hardware drivers measure temp different for it is setup based on that individual unit.
So i don’t disagree with what you say, I merely explain why IMHO things are done how they are done in the lights I know a little bit more about
This Costco Duracell 700 lumens flashlight has driver circuit in a tail:
Batteries, LED and driver circuit are in serial, but it needs a 24 Ohm resistor parallels with LED to pre-feeds power for driver circuit. Circuit likes that will “eat” some more energy (~ 200mA) from batteries when turns ON (because of current goes through LED and resistor at same time).
Yes it can be done (at least with a linear driver). It is a DC circuit, current is flowing in one direction so Pos+ Voltage is available anywhere in the circuit without any extra wires. It is this principle that allows the illuminated tailcap to work.
So why isn’t it popular here?
It makes a bigger tailcap necessary, which can be really ugly and is not accommodated by many hosts.
Driver modding started with Qlite drivers (which have a Pos+ battery connector), and evolved from there.