✌ FREEME - ASTROLUX FT03 Mini XHP50.2 (4200lm) / SST40 Anduril AUX LEDs USB-C 18650 Flashlight - ALIVE

Is it possible for someone to alter NarsilM to give the ability to change AUX lights? I’d like to flash the FT03 Mini as Anduril is too overwhelming for the average user. I could gift a light with NarsilM to my Dad but with Anduril, forget it.

I’ve messaged Ben at Mateminco suggesting they need to release two versions as they’re limiting their audience. Anduril is only attractive to flashaholics. If they had something basic it could be much more popular.

Would you dad care if the aux lights didnt work?

Haha, I gave that as an example.

I’d be selling these if I there’s an interest as a gun light with usb charging, most hunters don’t like too many functions.

I think I need to make my own firmware that suits my customers

I would be curious to know how the driver controls the aux lights. With older designs, a single output from the MCU would be connected to the aux through a resistor and the MCU would send a PWM signal to it. You had on or off. Then I think Anduril added bright or dim. Now we have color control and I don’t know how it’s doing it. Anyone know? I try not to bother TK.

How exactly is Anduril too overwhelming? Basic functions the same as NarsilM…

Narsil has simple ramping and has the ability to disable all strobes, no accidental 4 clicks to ramp config, if a customer enters it they could mess it up and complain. I’m not the only one that thinks it’s overwhelming, I see it mentioned on multiple reviews and Sofirn has said they’d never personally use Anduril as it’s too much. They only offer it because this forum demands it.

I’d see it so beneficial to have a mode like muggle that disables all strobes, config menus, but offers the full brightness.

I would not gift Anduril, either. It’s way too easy to accidentally go into a menu. Also, 2, 3 or 4 clicks can do different things depending whether it’s on or off.

I like it for myself though. I just think manufacturers are limiting their audience by just releasing one version with Anduril.

It’s not profitable to release different UI options. I have never seen it done. I would not expect them to ever do that. Especially after they already ordered all their drivers.

I only thought of it since the Meote FM1 released two versions.

I wrote this to make it more simple

What happened to the temp rating of the XHP-50?

When I ordered my 2 units it offered 5000k or 6500k now the website says just 6500k

I ordered 5000k for both of my units originally.

They probably sold all their 5000K. Happens all the time.

PS, Banggood shows both choices in stock so I’m not sure why yours says only 6500K is available.

What do you mean exactly by change the AUX lights?

At this point if it's somewhat an involved change for NarsilM, I'd rather change Anduril to remove options. I've been modding Anduril to my own prefs for a while now.

Right now, for a simple single AUX (usually switch) LED, Anduril can control 2 output levels while NarsilM only does one level. For the more complex TIR optic multi-color AUX LED's, Anduril must be running on a more advance MCU that has more I/O pins and code space like the Atttiny 1634 which NarsilM does not support.

So for this FT03 mini, I don't see any info anywhere posted about the AUX LED design.

To add 1634 NarsilM support is a relatively big project - not at all planned or in the works. Even adding the simpler-to-do option of supporting 2 levels may not be that easy because I might not have the available code space with the limit of 8 KB the Atmel ATtiny85 has.

Sent.

Color control is done by having many extra I/O pins available and having more code space by using a more advanced MCU, the 1634, see the Atmel family of MCU's here: https://en.wikipedia.org/wiki/ATtiny_microcontroller_comparison_chart

NarsilM and Anduril previously required the ATtiny85, first came out in 2005, then TK added supported for the 1634 (and possibly other variants). The 1634 first came out in 2011.

Our goal should be, maybe is right now, to support the ATtiny1616 or ATtiny3216 (out in 2018) because mainly of the feature listed in the far right column: UPDI, plus they have 16 KB and 32 KB of code space (ATtiny85 has 8 KB). UPDI allows 1 pin flashing. The advantages of UPDI have been discussed here in the tech threads, but maybe not a 1 pin, but I think 3 pins can be used for a pogo pin flash kit.

Our ideal MCU right now would be a 20 pin flat pack (called QFN-20 in the chart), and having UPDI. The 4 mm x 4 mm size is nice and compact for our drivers, and relatviely easy to design in. The "1-series" MCU's on the chart are preferred. See gchart's thread: https://budgetlightforum.com/t/-/55911

Mmm, so no AT85 means no easy reflash to NarsilM.

yep!

I don’t know either. Wasn’t aware the FT03 Mini existed until a few minutes ago.

I haven’t really worked with Mateminco for a while, because they’ve got a few products being distributed without source code, in violation of the license. Have tried to resolve it with Ben (Survivor), and sent all the info necessary for that six months ago, but nothing has happened yet. Sent another message just now, so maybe it can get fixed.

Anduril definitely isn’t for everyone.

However, getting Anduril to work on a light mostly means getting FSM to work on that hardware. And if FSM works, it means a variety of other interfaces should work too.

Ideally, vendors should be able to offer any FSM-based UI. It could even be an option at time of purchase. It could use Anduril, or a ZebraLight UI, or an Olight UI, or a simplified ramping UI, or even a ported version of NarsilM (though neither Tom nor I has ported it to FSM yet). As long as the driver has flashing pads in a standard layout, it’s easy to change the UI — before or after purchase.

The idea is: people write UI apps on top of FSM, and then FSM handles all the differences in hardware. It’s like how people can run their favorite programs on almost any computer, mixing and matching hardware and software as they please.

The idea isn’t fully realized yet, but it’s at least sort of close… it makes portability a lot easier.

Yup, it seems like a good step forward, and gchart has already done most of the work. I need to get the code merged in… have just been a bit distracted with all the other stuff happening lately.

Interested!