Hmm i don’t think the FET+7135 driver & firmware works like that, if i am understand things right, it uses various PWM levels for controlling the AMC7135 also.
But i hope i am wrong, or it can be made to work like how you are suggesting because, pwm for a low moon mode/as much light as the 350mAh or 380mAh AMC7135 can provide non PWM/full non PWM FET blast as much amp as the circuit can provide, sound like a good idea.
From what I understand...
When in any mode below 350ma....it is running on only the 7135. When running all out it is a combination of both 7135 and FET. To get the two modes that is being asked I am assuming (because I do not write code) that one would just delete or comment out the modes in between.
With the current STAR off-time, it wouldn’t be possible to control the channels separately (without tweaking a few things). You set a PWM level for each mode, then tell the FW at what PWM level to stop using just the 7135 and start using both FET+7135. For instance your modes could be 5, 60, 255. Then you tell it for anything above PWM 6, use FET+7135.
With TK’s firmware, it is possible. You set a separate PWM value for each channel on each mode. So your modes would be would as follows:
7135: 5, 255, 0
FET: 0, 0, 255
I do a similar thing on all of my large thrower lights, but with a higher medium. I use
7135: 50, 255, 0
FET: 0, 0, 255
But I have an extra 7135 stacked on top of the first one, so my low is at about 150ma, and my medium is CC at 760ma, then FET high.
that sounds like a translation of my favourite UI :-)
Yep!
TK’s blf-a6 firmware also allows 2 mode groups, so you could do one group with L,M,H and the second group with just L,H (or whatever else you want). You change groups by tapping the button approx 15 times in quick succession. (but you don’t have to use the second group if you dont want to)
I know that it is hard to not use available options, but disabling moonlight is not a needed option for me, just moon-7135:100%-FET:100% is fine 
. But if this firmware can be made more attractive to other users by adding a (any) second mode group I'm all for it.
I believe that TK may have set a new standard for versatile UI's.
Nitecore has something similar by twisting the head on the P10. Two mode groups with one being what Djozz is asking for and the other being standard. I think TK's method of changing mode groups is much better.
The two mode groups are already there. The first has 7 modes and the second has 4 modes. Unless someone gets into the code to change the number of modes on one of the groups, depending on their desires, I do not think that there is enough room for the Attiny13 to add any more mode groups like Dr.Jones did.
You’re right, but it’s designed to be easy to go to the code and change the modes (and it is). I don’t think any of my lights have the exact same FW as any other. All are tweaked to that particular light.
…………………………………………….
djozz: If you don’t want the second group, no problem. Just wanted to make sure you were aware of everything thats available. I can make your FW and send you the .hex file if you want, I just don’t have the extra Attiny’s to send. I assume you want no turbo timer as well?
...unless you change about one or two lines of code. Pretty simple to do. I wouldn't have said it was possible if I hadn't already done it.
Well my apologies then, I didn’t know that. I’ve always just started with TK’s code for better control of the PWM channels. I edited post #126 to clarify.
you're my hero, Richard! So I can just order a couple of programmed Attinies at your site with a note (and a few more nice parts while I'm at it :-) ) and I'm good to go? :-)
(don't hurry with it btw, I understand there's a brand new little flashoholic due soon..)
Better to send an e-mail to mountainelectronics at gmail dot com for this one, listing the requested items, quantities, and options. Amsterdam isn't available to order directly from the website yet.
will do that :-)
7135: 5, 255, 0
FET: 0, 0, 255
Does that mean that at moonlight 7135: 5 there is a 350mah thats PWM’ed to get it to moonlight, and 7135: 255 means it has no PWM even when it is called 255 PWM value? :~
And for the FET: 255 PWM value even when it is called that don’t actually do any PWM but only a continuous current level dropping only by the sagging battery?
Yes, a PWM value of 255 is “Full on” or “Wide open”
PWM value 5 divided by 255 is roughly 2% output, so 2% of 350ma is 7ma output on ‘moon.’ Many people even take it down to 3 PWM for an even lower moon.
Or even PWM 1.
Unfortunately PWM percentages don't track directly with 7135 output current. Remember, some of that PWM signal is being used just to power the 7135, and there is a certain amount of latency in switching on and off.
5 is the lowest value ? or you can go 1?
This
I really don’t understand the mechanics of it, but personally I’ve never had an LED light up under 3. I usually use 4 or 5 for my moon modes.
You can go down to 1 with a single 350mA binned 7135. Sometimes the 380mAs require 2.
Remember, I'm talking about a single 7135. As the number of 7135s increases, so does the minimum PWM level required to have them turn on and be stable. Again, this makes sense when you remember that the 7135s are wired in parallel and powered entirely by the PWM signal.