[SALE] FW3A lighted TIR board multicolored with LVP, stabilized or High/low

18 posts / 0 new
Last post
Lexel
Lexel's picture
Offline
Last seen: 23 min 25 sec ago
Joined: 11/01/2016 - 08:00
Posts: 5145
Location: Germany
[SALE] FW3A lighted TIR board multicolored with LVP, stabilized or High/low

how it began can be read here
http://budgetlightforum.com/node/59061#comment-1355514

Boards can be build as Gen 1 to 1.7 now

Generation 1 High/low capability but then LEDs dim to about 50% between full and empty battery
Generation 1.2 LEDs are voltage stabilized High/low does not work, no LVP
Generation 1.5 unregulated LED voltage + LVP
Generation 1.7 stabilized with LDO + LVP

- version with LDO → High/low not possible
- version with LVP → High/low not possible
→ flash #define INDICATOR_LED_SKIP_LOW setting as well

LDO → constant brightness and color mix over full battery voltage
LVP → shuts down when battery low (2.93V without MCU, 3.3V with MCU used)

.

LVP chip shuts down at 2.93V voltage,
if the MCU is used for Aux control also the reverse polarity protection diode counts in with about 0.35V
- above 3.3V all LEDs on and below 3.3V all LEDs off

.

fits FW3A and Noctigon Triple

Sample with warm white, ice blue and pink

.

Production board and stencil ready

any color combinations are possible each LED could have a different color

.

LEDs as you wish colors and patterns
450nm blue, pink, red, orange, yellow, green, ice blue, WW, CW (the yellowish green is too inefficient)
new LED batch cooperator boards for 3 brightness levels made

[LED colors] (top are most efficient, bottom inefficient)

LED color and each single LED current based on my “medium 0.5mA” brightness level

green 19.1uA
blue 21.2uA
ice blue 25.2uA
pink 30.7uA
CW 38.7uA
WW 40.2uA
red 50.9uA
orange 124uA
yellow 206uA

my LED brightness scale is based on my Rainbow+WW boards total current while LEDs seem same brightness

basically I have 5 levels “1mA”, “0.75mA”, “0.5mA”, “0.3mA” and “0.15mA”
this does only reflect on rainbow boards with WW the total current drawn

on the boards the total current depends on used colors and brightness level (“0.15-1mA”)

.

I can also build a board with a current consumption you want
for example, you can order a “0.3mA” pink/green all 12 LEDs equipped

Edited by: Lexel on 07/07/2019 - 09:43
Lexel
Lexel's picture
Offline
Last seen: 23 min 25 sec ago
Joined: 11/01/2016 - 08:00
Posts: 5145
Location: Germany

Prices:

4.5€ Single color board
+0.25€ voltage stabilization
+0.5€ LVP chip
custom color combination
2-3 colors +0.75€
>4 colors +1.5€

Orders with more than 3 identical or single color boards get 10% discount

.

Shipping:

I will add some plastic card and structured paper to protect the boards

1.5€ standard bubble envelope 0.5cm <20g
2€ thick bubble envelope 1cm <50g
tracking adds 4€

Tracking Info
https://www.deutschepost.de/sendung/simpleQuery.html?locale=en_GB

Lexel
Lexel's picture
Offline
Last seen: 23 min 25 sec ago
Joined: 11/01/2016 - 08:00
Posts: 5145
Location: Germany

How to order

send me a PM if you want to order boards

tell me
- which color(s) you want,
- the color pattern you can make a simple picture from the preview picture like this example

- I need to know which version
- brightness or current consumption you want

Lexel
Lexel's picture
Offline
Last seen: 23 min 25 sec ago
Joined: 11/01/2016 - 08:00
Posts: 5145
Location: Germany

Modding guide

First remove the retaining ring, lens and optics

Unsolder the MCPCB wires and pull the driver

.

Now we got 2 options
- use the MCU with Aux support firmware flashed
- use battery voltage to drive the board without MCU control
in first case simply ignore the optical nerve connection and do a bridge from MCPCB+ to aux board +

.

Remove the optical nerve resistor and tin the right pad

Prepare a thin wire for the aux board + connection and solder it to the tinned pad

(AWG28 silicone wire used, it’s cut a bit too long)

Scrape off some solder stop mask and tin the area for ground and solder the 2. wire to it

Modify Anduril for Aux support and flash MCU with programming adapter

Align the driver with the flat side to the head so it rests flat on the whole surface and screw down retaining ring, solder MCPCB

Aux board is build and tested, put it on the MCPCB

solder the Aux pads + and -, add optic to the light then screw down bezel with lens

(The picture shows v1.5 with green/pink build for 1mA max current and a 0 Ohm resistor, higher value like 1-5k can make the board significant dimmer)

bmengineer
bmengineer's picture
Offline
Last seen: 2 hours 23 min ago
Joined: 01/26/2018 - 11:38
Posts: 634
Location: Ontario, Canada

How are these wired up?

Find all my reviews of flashlights and more gear at www.bmengineer.com

TrueRMS
Offline
Last seen: 5 hours 59 min ago
Joined: 08/09/2013 - 13:24
Posts: 215
Location: Marysville OH

Is LVP one stage or two?

What i mean by “one or two stages” is this: are these like your other aux boards where they have regular colors above x volts, red between X and Y voltage and then all off below Z volts? Or are they simple on if above X volts and off below that point?

Lexel
Lexel's picture
Offline
Last seen: 23 min 25 sec ago
Joined: 11/01/2016 - 08:00
Posts: 5145
Location: Germany
bmengineer wrote:
How are these wired up?

see post 4

TrueRMS wrote:
Is LVP one stage or two?

What I mean by “one or two stages” is this: are these like your other aux boards where they have regular colors above x volts, red between X and Y voltage and then all off below Z volts? Or are they simple on if above X volts and off below that point?

LVP means
with aux board directly connected to the battery voltage
- above 2.93V all LEDs on
- below 2.93V all LEDs off

If the MCU is used add 0.35V from the reverse polarity protection diode

KawiBoy1428
KawiBoy1428's picture
Offline
Last seen: 4 hours 5 min ago
Joined: 04/11/2014 - 18:05
Posts: 3615
Location: The Motor City

Incoming PM….for 2 please…thanks!

KB1428 “Live Life WOT

Lexel
Lexel's picture
Offline
Last seen: 23 min 25 sec ago
Joined: 11/01/2016 - 08:00
Posts: 5145
Location: Germany

contactcr wrote:
I feel like this board needs a flow chart to even understand the options, lol. Is this accurate?


I have shown the full modding guide with flashing that should be easily be done if the right equipment is available

not quite right
if with or without LDO color mixing is always possible
each LED has an individual resistor, the LDO can be replaced with a 0603 resistor, the LVP chip bridged with pads below it

- version with LDO → High/low not possible
- version with LVP → High/low not possible
→ flash #define INDICATOR_LED_SKIP_LOW setting as well

LDO → constant brightness and color mix over full battery voltage
LVP → shuts down when battery low (2.93V without MCU, 3.3V with MCU used)

I plan a version that allows LVP and high/low, but this means a 3. wire for the aux board
this will be then v2.0

contactcr
Offline
Last seen: 33 min 5 sec ago
Joined: 05/19/2017 - 18:52
Posts: 2054
Location: US

If it’s controlled by MCU does it also have OFF? Also, with it wired this way can I also re-flash the firmware while aux board is connected?

If I want 1 or 2 color + MCU (low/high/off) it’s only 1 possible option right?

trakcon
trakcon's picture
Online
Last seen: 43 sec ago
Joined: 01/23/2019 - 15:50
Posts: 126

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?

Thanks so much!
Mike

Lexel
Lexel's picture
Offline
Last seen: 23 min 25 sec ago
Joined: 11/01/2016 - 08:00
Posts: 5145
Location: Germany

contactcr wrote:
If it’s controlled by MCU does it also have OFF? Also, with it wired this way can I also re-flash the firmware while aux board is connected?

If I want 1 or 2 color + MCU (low/high/off) it’s only 1 possible option right?

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

trakcon wrote:
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?

Thanks so much!
Mike

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

trakcon
trakcon's picture
Online
Last seen: 43 sec ago
Joined: 01/23/2019 - 15:50
Posts: 126

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?

Lexel
Lexel's picture
Offline
Last seen: 23 min 25 sec ago
Joined: 11/01/2016 - 08:00
Posts: 5145
Location: Germany

trakcon wrote:
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?

D4S uses a fairly high brightness, I would reach about the same with “2mA” setting

trakcon
trakcon's picture
Online
Last seen: 43 sec ago
Joined: 01/23/2019 - 15:50
Posts: 126

Actually, I’d be ok with the high being a little dimmer than the D4S high.

I’d like the low to be about the same as the D4S low, though. I use it on my nightstand facing the bed. Is that possible?

I realize I’ve been occupying your sales thread. We can move to PM if you like.

Lexel
Lexel's picture
Offline
Last seen: 23 min 25 sec ago
Joined: 11/01/2016 - 08:00
Posts: 5145
Location: Germany

trakcon wrote:
Actually, I’d be ok with the high being a little dimmer than the D4S high.

I’d like the low to be about the same as the D4S low, though. I use it on my nightstand facing the bed. Is that possible?

I realize I’ve been occupying your sales thread. We can move to PM if you like.

low is always based mainly on the internal pull up resistor in the MCU, nothing you can change there

selection guide added

I also compiled hex files for the FW3A, but they are untested yet
It’s not stock Anduril there are some changes
http://www.metronixlaser.de/bilder/flashlight/FW3A/FAnduril_aux.zip

TrueRMS
Offline
Last seen: 5 hours 59 min ago
Joined: 08/09/2013 - 13:24
Posts: 215
Location: Marysville OH

Payment sent for two v1.7 boards. Thank you Lexel!

MikeMacD
Offline
Last seen: 9 hours 44 min ago
Joined: 05/15/2018 - 01:53
Posts: 50
Location: Texas, USA

Lexel, the link to the zipped hex file you mentioned previously says “File Not Found”.