Interesting.
What's meant by #2 is feed back from the string's current - A resistor is included in the string, at the bottom usually. A voltage is developed across the resistor that is directly related to the current running thru the string. This provides for accurate current control.
That is how the 3409 works. The resistor is actually directly upstream of the power transistor. The inductor and LED string are after the power transistor in the current flow.
Having an external FET is not bad! It allows the unit to control more current, otherwise the controller chip gets too hot.
It has pluses and minuses. The advantages are as you say, plus one can choose the parameters to suit one's desires. The disadvantage is simply additional components and complexity. However, that additional complexity is a bit of an illusion.
I almost chose the LM3406 for my design (1.5A internal power transistor) simply because it does not require an external transistor. However, when I started looking at the various "extras" one should probably add to protect the 3406 from various failure modes, the two or three extra diodes plus handful of resistors looked like more trouble than just having an extra transistor. As long as the 3409 is paired with a transistor that can handle the full Vin, it is protected from things like disconnecting the load.
So the basic design of the 3409 is more complex because it needs an external transistor. But it saves another handful of components in real world design because it is more naturally resistant to failure modes.
"Current limit" is some final say in what you can command the driver to reach. This is also important so that if a LED shorts the current doesn't increase across the string, or you send something dumb to the driver from your controller.
Are you referring to number 3 here, "sets max allowable current"? The sense resistor does this. I suppose that if the sense resistor failed shorted though then one would probably get the full Vin across the LED string. I don't see how any design could protect against that though in a general fashion.
Sometimes the resistor value chosen will automatically set the maximum current. That's a solid dependable method too.
For the LM3409 the maximum current is Vcst/Rsense, where Vcst =~.25V. The Vcst can be adjusted downward with the Iadj pin. The maximum value for Vcst (according to the datasheet) is .261V which is about a 4% variation off the nominal. So the maximum current set with the sense resistor shouldn't be able to wander more than about 4% without the sense resistor failing shorted.
Your ATs can certainly monitor the temps and throttle back the current if the cooling isn't hacking it for some reason.
The 3409 also has a built-in thermal shut down, but it may be at a higher temperature than one wishes. My thought is that one of the I2C commands will be to set the ATtiny25 to alert the master controller if a temperature threshold is exceeded, or perhaps simply to perform a shutdown. Or perhaps two commands, one to set each mode and limit. The ATtiny has a built-in temperature sensor tied to its ADC, which is very cool. There's a ton of functionality in that tiny 8 pin chip.
The only thing you haven't covered is that this controller is a BUCK controller.. so where are you going to get 75Vdc? That is not common to come by.
I will probably use it with 24V supplies. The *maximum* is 75V. One can still use it at lower voltages. I need to go through the equations and make sure that the components I have on my preliminary BOM yield sensible results in all the boundary operating modes. E.g. Vin = 6V, 1 LED; Vin = 75V, 1 LED; Vin = 75V, 18 - 19 LEDs. And perhaps some middle values as well such as, Vin = 24V, 3 LED or 6 LEDs. And Vin = 48V, 3, 6, 9 or 12 LEDs.
But this would give others (assuming anyone else is interested) the ability to use it with higher capacity supplies. If no one else is interested then I'll economize the parts by targeting them at my environment. But the savings from a moderate group buy, would exceed the savings of limiting the components' capacities.
Perhaps you should keep looking and go for a boost controller. That will make a higher voltage allowing you to amortize your controller costs over very many more LEDs.
I've looked at Boost. Partly because I have a dozen 12V 47A supplies on hand from old Compaq servers.
I do not like two things about boost. Most of the available components seem fairly limited in the output current they'll deliver, rarely getting up to 1.5A with any margin. Second, I do not like the inability to operate at voltages below Vin. I want one to be able to attach any number of LEDs (well, 2+) without concern that the driver will kill the LEDs. And have the ability to analog dim down very close to zero.
The Meanwells apparently have a minimum operating voltage of about 21V and more than one person has burnt out smaller strings of LEDs on the 48V version. I wonder if the 48V meanwells are actually a 24V supply with a boost circuit following the voltage regulator.
Now, in reality, 1A is probably plenty. But as I wrote, I'm aiming for versatile and heavy duty. It may be foolish. But this is where I'm starting.
It might be more reasonable to just aim at 24V and 1A as the maximum ratings. The history of my investigations has kind of led me to the maximum versatility version, though.
I like the 3409 topology. The non-HV version of the 3409 has a 42V limit. But 48V supplies are not unheard of. And the 3409HV is not that much more expensive than the non-HV. In larger quantities they're practically the same price. But once one has the 3409HV in the design, now the chip limit is 75V. If one chooses the other components for 24V or 48V operation, that's okay for personal use, but if others come along on a group buy they might get confused and think that 75V is the limit because of the 3409HV spec.
So why not go for a full out 75V (even though most folks will go 24V and a few will go 48V) 2A limit. Then with the switch settings to set the maximum current from 350mA to 2A it will be very easy for anyone to choose (roughly) their initial operating point and then adust that with a pot. on Iadj and/or the PWM through the ATtiny25.
I'm also considering connecting the potentiometer to an ADC pin on the ATtiny25 and a PWM with low pass filter to the Iadj pin of the 3409. Then the ATtiny25's EEPROM can be programmed with a flag which tells it to either use the value at the ADC pin to set Iadj, or to use a programmed value which was sent over the I2C. That way one could set the analog levels manually, or by controller depending on the setting of the flag.
But that's wandering over into a discussion of the command set for the ATtiny25 controller. Which is a discussion I'd like to have, but again, it's one I'm wondering if it belongs in this thread. I would love to see a group effort to create a sort of standard command set (via I2C) for the ATtiny25. Then I can whip up a program to implement the commands and we'll have a general control system for any PWM capable LED driver, not just the one I'm proposing here. It would be extremely versatile because up to 128 drivers could be controlled on a single I2C bus (yes, I know about capacitance limitation, *and* bus extenders).
So instead of a hodge podge of port expanders that are currently being used, we could have a standard client control system for LED drivers which any host control system (with an I2C interface) could easily access. The cost would be one ATtiny25 per driver, but the things are cheap, especially if one buys 100 at a time.