This is fantastic! I have questions, though. Forgive me if they seem elementary.
1:
If I wanted the same colors in the prototype (yellow, ice blue, and pink??), with matched brightness, and LVP, would I choose 1.7?
2:
Then, I can choose to either have the MCU control them or battery voltage. Since LVP doesn’t support high/low, is the difference:
- MCU: aux board turns off when main LEDs are on?
battery voltage: aux is always on?
3:
To use battery voltage control, it says to bridge MCPCB+ to the aux+. Do I just connect a very small wire from the MCPCB to the aux board? In that case, it seems nothing gets soldered to the driver and the driver doesn’t really need to be removed. Is that correct?
Edit: I just realized this would result in the aux board ONLY being on when the main emitters were on, so I guess the bridge needs to be from driver+ to aux+? Where on the driver should this bridge wire attach?
4:
If I wanted the aux LED brightness to be the same as a D4S with cyan aux on the low setting, how would I specify that?
MCU has always ON/OFF/Beacon
the simple solution is connected to battery voltage and always ON
Gen1.0 also supports LOW similar to Emisar aux board with one 0603 resistor to adjust brightness,
but in addition each LED has a balance resistor to mix colors
LVP or LDO are not compatible with LOW setting
I am not sure if the input cap of the LDO lets you flash the MCU when there is no LVP or if the LVP chip is there
but to flash the driver you have to disassemble it anyway so the question does not make practical sense
1. Prototype uses warm white not yellow, as its way more efficient
you can use v1.7 for LVP and constant brightness independent of battery voltage,
but also without the LDO the colors get matched pretty good by the balance resistors,
but a slight shift can be seen over the battery voltage,
most important is without LDO the LEDs get dimmer with drained cell voltage
2. Yes Aux board has to be flashed OFF when main LEDs are on, as it doesn’t support the aux ramping (only v1.0 works with low and ramp, but it makes no sense)
On battery aux LEDs are always on, not a big problem with low brightness, if you run them with 1mA or so it will be relative bright compared to moonlight
3. you always need to get ground to the board to run it, you can use + from the MCPCB,
but ground needs to be pulled from driver or the flashlight body
You can solder + to red MCPCB wire and ground to the plane I scraped off the paint next to the AMC, or solder directly on the AMC fin
Thanks for the reply, Lexel. I think I want high/low capability, which means Gen 1. I keep my batteries charged so not having LDO and LVP is ok.
With Gen 1, can I get low and high brightness similar to low and high on a cyan D4S?
I am able to flash Anduril, but I’m not set up for compiling. Would someone be able to post both the regular and 219B hex files with the changes already made for the aux board?
Got one of my dark blue 0.3mA aux boards installed today. Compiled a hex file with aux support and the latest Anduril features like manual memory, two level lockout brightness, soft reset, etc. The version with MCU support isn’t the most simple option but I did want the ability to turn it off.