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

forsh · 2020-04-27T05:16:53.000Z

outbackganked:

Can anyone please help me. My mate and I have a lot of previous experience with this kind of thing from custom building drones and we want to build some flashlights.

What we want to know is with regard to these Lexel AUX boards, do you have to use the stock FW3A driver? Can you use another driver like the DrJones driver for example? Or is it that you have to use the modified Anduril firmware?

Doesn’t the up-to-date Anduril firmware now support AUX out of the box?

See, here is what I am wanting from a UI:

- easy access to Moonlight from off (I also note that some drivers like DrJones appear to have dedicated hardware to make Moonlight awesome? Or am I a noob and Anduril does ML as well with the stock fw3a driver?

ability to turn off/on Aux LEDs. Ideally also control if they are on really low/normal low.

Can someone please explain what options I have here and also what hardware we would need to achieve this?

Thanks so much in advance.

lexel has made a how to on this forum somewhere

if you can program the firmware, if you can solder nicely then alls good

outbackganked · 2020-04-27T07:31:28.000Z

I’m thinking that the Anduril aux support does not support this Lexel board, which is maybe why he has this custom modified Anduril hex file.

loneoceans board is not yet really supporting aux LED’s as he’s not yet published any guide or doc on how to achieve it.

OK, so basically FW3A should keep the existing drivers.

Can anyone tell me if I can the UI I specified above?

forsh · 2020-04-27T07:34:06.000Z

outbackganked:

I’m thinking that the Anduril aux support does not support this Lexel board, which is maybe why he has this custom modified Anduril hex file.

loneoceans board is not yet really supporting aux LED’s as he’s not yet published any guide or doc on how to achieve it.

OK, so basically FW3A should keep the existing drivers.

Can anyone tell me if I can the UI I specified above?

The fw3 will support lexels bird but you have to update the firmware
Also there is a how to about this

Or you could do like lost people have done and just solder the aux board to the plus and mins of the triple mcpcb ,

outbackganked · 2020-04-27T12:07:36.000Z

@lexel will the board fit this: (3) Nichia NVSL219C D280 3000K 80+ CRI LEDs on 20mm 3XP MTN DTP Copper MCPCB ??

treellama · 2020-04-27T12:12:26.000Z

I have installed one over a MTN board, it fits

mfrey · 2020-04-27T22:42:17.000Z

contactcr:

Edit; posting my final changes now that Lexel has replied:

cfg-fw3a.h ADD TO END

// the button lights up
#define USE_INDICATOR_LED
// the aux LEDs are behind the main LEDs
#ifdef USE_INDICATOR_LED_WHILE_RAMPING
#undef USE_INDICATOR_LED_WHILE_RAMPING
#endif
// enable blinking indicator LED while off
#define TICK_DURING_STANDBY
#define STANDBY_TICK_SPEED 3 // every 0.128 s
#define USE_FANCIER_BLINKING_INDICATOR
#define INDICATOR_LED_DEFAULT_MODE ((3<<2) + 2)

hwdef-FW3A.h ADD/CHANGE

~~//#ifndef VISION_PIN~~
~~//#define VISION_PIN PB2 // pin 7, optic nerve~~
~~//#define ADC_CHANNEL 0x01 // MUX 01 corresponds with PB2~~
~~//#define ADC_DIDR ADC1D // Digital input disable bit corresponding with PB2~~
~~//#endif~~
#define ADC_PRSCL 0x06 // clk/64

#ifndef AUXLED_PIN
#define AUXLED_PIN PB2 // pin 7
#endif

If you are compiling your own hex file based upon the most recent Andúril update, are there any other changes that need to be made to the code? Any changes to the .c file, for instance, to make the auxiliary board function?

Is there a way to slow down the frequency of the blink in aux beacon mode?

I assume the crossed out code denotes that it is deleted or disabled. Correct?

trakcon · 2020-05-06T15:42:40.000Z

LoPan12:

Another color combo to help people choose!
Turns out, the Vf is different enough that the blue don’t illuminate on Low… Kinda neat actually…

Is that blue+orange or blue+red?

LoPan12 · 2020-05-06T20:30:49.000Z

Blue and orange sir!

LoPan12 · 2020-05-07T01:40:33.000Z

I’ll be ordering a few more boards from you in a couple days Lexel…thanks!

Krisinpudding · 2020-05-19T02:37:32.000Z

If I want the aux to be always on, can I just jumper the + & -?

LoPan12 · 2020-05-19T03:01:45.000Z

Krisinpudding:

If I want the aux to be always on, can I just jumper the + & -?

I think You connect -(aux) to grnd on driver. Bridge mcu and (the bridge pads on L) and then or L to +(on mcpcb)

Krisinpudding · 2020-05-19T03:21:38.000Z

Am I correct to assume that pictures are available at the beginning of this thread?

johnpoyhonen · 2020-05-25T15:16:48.000Z

I would like some suggestions. I want to order a lexel board for my FW3A but I’m not sure which version to order. I might be able to handle some soldering but I want to try to stick to the simplest procedure possible because my hands (and eyes) aren’t good with tedious things anymore. I’m not totally against flashing the board myself but don’t really have the stuff to do it with or the time. High/low option would be cool but not necessary. I have another light that was modded by jku2017 before he stepped away. I like how that one turns on/off opposite the main leds but I kind of wish it still had the bike strobe. I don’t know if there are any other modes that can be replaced to add aux. About the only modes I never use are tactical strobe and muggle. Any suggestions on board or firmware versions would be greatly appreciated. Either that or recommendations for modders who would be willing to do the job would be great. ~I contacted Vinh but he declined.

LoPan12 · 2020-05-25T15:21:54.000Z

If you compile using Linux and TK’S optimized settings you don’t have to “sacrifice” anything from the code. Thats why d4v2 or anything else with an aux light or switch light is still fully functional…
Vihn declined and Jku stopped because the 1-2 hours it takes for the mod isn’t economically viable, unless you charge at least $60 to do the mod…and I’m not sure anyone would pay more than the light itself to get aux lights modded in…

contactcr · 2020-05-25T18:41:12.000Z

D4v2 uses a different mcu with more space for code. Not comparable.

I removed muggle mode when I did mine. Ymmv

LoPan12 · 2020-05-25T19:04:08.000Z

contactcr:

D4v2 uses a different mcu with more space for code. Not comparable.

I removed muggle mode when I did mine. Ymmv

They all use the same code. They use you use a different hardware profile when compiling, but the base code is the same. The Anduril.c file is the same. I compiled mine just fine using a full build of the most recent Anduril revision, and didn’t remove anything.

Like I said, Toykeeper has specific compiling instructions within the library, that contain several instruction modifiers that make it compile more efficiently.

I’m not by my computer right now, so I don’t remember what the command is, but its just as states in the Readme file

Lexel · 2020-05-25T21:51:39.000Z

Any version will work without using the MCU, its just what you want
1.0 is not using LVP and is high/low capable but you cant use low
1.2 voltage stabilized
1.7 voltage stab and LVP
2.0 LVP and high/low which is not used

LoPan12:

If you compile using Linux and TK’S optimized settings you don’t have to “sacrifice” anything from the code. Thats why d4v2 or anything else with an aux light or switch light is still fully functional…
Vihn declined and Jku stopped because the 1-2 hours it takes for the mod isn’t economically viable, unless you charge at least $60 to do the mod…and I’m not sure anyone would pay more than the light itself to get aux lights modded in…

Doing this Mod on the driver takes like 35-40 minutes if you do it slowly and are experienced with it
I have no problem modding a FW3A for others if they order just a new light to me

I sent out today quite some drivers and Aux boards

uselessuser · 2020-08-11T11:44:20.000Z

mfrey:

contactcr:

Edit; posting my final changes now that Lexel has replied:

cfg-fw3a.h ADD TO END

// the button lights up
#define USE_INDICATOR_LED
// the aux LEDs are behind the main LEDs
#ifdef USE_INDICATOR_LED_WHILE_RAMPING
#undef USE_INDICATOR_LED_WHILE_RAMPING
#endif
// enable blinking indicator LED while off
#define TICK_DURING_STANDBY
#define STANDBY_TICK_SPEED 3 // every 0.128 s
#define USE_FANCIER_BLINKING_INDICATOR
#define INDICATOR_LED_DEFAULT_MODE ((3<<2) + 2)

hwdef-FW3A.h ADD/CHANGE

~~//#ifndef VISION_PIN~~
~~//#define VISION_PIN PB2 // pin 7, optic nerve~~
~~//#define ADC_CHANNEL 0x01 // MUX 01 corresponds with PB2~~
~~//#define ADC_DIDR ADC1D // Digital input disable bit corresponding with PB2~~
~~//#endif~~
#define ADC_PRSCL 0x06 // clk/64

#ifndef AUXLED_PIN
#define AUXLED_PIN PB2 // pin 7
#endif

If you are compiling your own hex file based upon the most recent Andúril update, are there any other changes that need to be made to the code? Any changes to the .c file, for instance, to make the auxiliary board function?

Is there a way to slow down the frequency of the blink in aux beacon mode?

I assume the crossed out code denotes that it is deleted or disabled. Correct?

I’m a bit late here, but I only recently started playing with Lexel’s aux boards. Here are a few remarks that others might find helpful:

Yes, the ~~strikethrough~~ indicates that you should delete the lines. Normal text means that you should add it at the end of the respective file.
Note that hwdef-FW3A.h at the time of writing already has a line that starts with `#define ADC_PRSCL`. You may want to delete that one or else you get an inconsequential warning when you compile the code.
Be careful when copy/pasting from the above code. The forum botches the `#define INDICATOR_LED_DEFAULT_MODE` statement for cfg-fw3a.h, there are two symbols missing at the end. (Click “Quote” to see the original text.) You can safely just leave the entire line out, there’s a default set elsewhere at the time of writing.
When the forum displays a fancy “times” symbol instead of a regular letter x, that’s a trap. Use the letter. (Click “Quote” to see the original text.)
No changes in any other files are necessary, unless…
If you get a cryptic error that says this-and-that is too large, it means the resulting hex file is too large to flash to your driver. The easiest way around it is to remove a feature you don’t need. For example, to remove Mugle Mode, open the file anduril.c and put two slashes (//) before `#define USE_MUGGLE_MODE` in line 89. That’ll solve the space issue by removing Muggle Mode from the resulting firmware.

trakcon · 2020-08-11T12:26:37.000Z

uselessuser:

If you get a cryptic error that says this-and-that is too large, it means the resulting hex file is too large to flash to your driver. The easiest way around it is to remove a feature you don’t need. For example, to remove Mugle Mode, open the file anduril.c and put two slashes (//) before `#define USE_MUGGLE_MODE` in line 89. That’ll solve the space issue by removing Muggle Mode from the resulting firmware.

At least in Atmel, there’s a compiling option to “optimize for size” that I believe should take care of this.

ToyKeeper · 2020-08-11T12:51:41.000Z

trakcon:

uselessuser:

If you get a cryptic error that says this-and-that is too large, it means the resulting hex file is too large to flash to your driver. The easiest way around it is to remove a feature you don’t need. For example, to remove Mugle Mode, open the file anduril.c and put two slashes (//) before `#define USE_MUGGLE_MODE` in line 89. That’ll solve the space issue by removing Muggle Mode from the resulting firmware.

At least in Atmel, there’s a compiling option to “optimize for size” that I believe should take care of this.

The bin/build.sh script has a few options which are necessary to make the build fit. I’d strongly recommend using the build script if at all possible.