Flashlight Firmware Repository

You have 2 lines that configure the debounce timing:

maybe try changing DB_REL_DUR to 200ms?

you can use Decimal to Binary converter to find the binary number for your ms.

sorry for misleading you (this definition is a bit mask, no a number), each bit is 16ms, so the max time is 128ms
try:

BTW, are you building a diving flashlight with that piezo switch :slight_smile: ?

Thank you very much
why do you think I can’t use a piezo button? I’m using them made of stainless steel that are very good, and also underwater, that you would have other ideas

I didn’t say that you can’t use it :slight_smile:
I just asked whether you’re using it to build a diving flashlight.
I used a piezo switch for a diving flashlight years ago, it was great.

[quote=HiTiT]
You have 2 lines that configure the debounce timing:

maybe try changing DB_REL_DUR to 200ms?

you can use Decimal to Binary converter to find the binary number for your ms.

sorry for misleading you (this definition is a bit mask, no a number), each bit is 16ms, so the max time is 128ms
try:

Hi I tried to do as you said but nothing is still too sensitive, sometimes pressing the button changes twice, you have some ideas

I notice that there are quite a few people who know nothing about coding yet are able to flash firmware. The recent introduction of flashing pads greatly expands this number.
Yet the latest Andruil is not available to them in a binary form. They have to compile the sources which is problematic to quite a few a needless nuisance to a number of others.

I think it would be worthwhile to have some continuous building process….

Uhhh, someone recently posted a link to a hex file of the latest Anduril build, least I thought, forgot where...

These are the latest builds from the development (not always fully tested) branch. I haven’t had any issues with the newest build on my D4V2 Ti.

Sorry I ask a question, do not kill me, it’s only recently that I discovered this forum thanks to all, I found this part where you have gathered all the firmware, but there is the possibility of finding some driver projects that you can create, thanks

Thanks, that’s exactly what I was looking for. :+1:

You mean ones where you buy PCB and a bag of parts, then solder everything together?
There are a few…but scattered over many topics.
It would be interesting to make a reference at some point…but as of now it doesn’t exist, so please tell us what kind of driver are you looking for and we may be able to help.

I am looking for the design of a driver for an xhp70.2 led, I have to be able to power it indifferently with 2s 3s 4s battery packs, I need the design because the pcb must have a specific shape for the flashlight that I am building, I am a hobbyist with the passion to build things, I’m not electronic, but I can assemble a pcb, I’m building an underwater torch, if you can help me thank you

2s is something I may be able to help with. Zener modded Texas Avenger should do the trick. Please note that recently Texas Ace started to use resistors instead of 7135 because with powerful 2s lights they are much more reliable.

For more than 2s you need some other driver, most likely buck. I’m not sure if there’s anything open source available…

:smiley:

In this beautiful software there are one awful thing.
Every time, when i am going to check voltage, if i shutdown flashlight on high level, i get huge preflash during 3 short click. And because moonlight not remembered - even if i firstly switch on by hold on moonlight and off then - huge preflash would appear.

It would be essential, if software d’t turn immediatly on memory level after first click. Just moonlight for first 0.1-0.2 sec and only after - turn back to memorized level. So, if we do many clicks - as for voltage check, software would catch next click before turning power up to memorized level.

I use gentoo on my dev machine. I just got a notice that bzr will be removed from the package repo in 30 days because it requires Python 2. They recommend that I switch to breezy.

Seems to be a worthy change if possible. I usually don’t turn off from High, so maybe I don’t encounter it often, but I’ve encountered this (bright pre-flash) when doing the triple-click battery check.

I use breezy for months already, works great. The multi backend support (bazaar and git) is nice. Much better than fast-export. But for me it’s still just a bridge between bazaar and git. :wink:

Not sure of the solution would be more painful than the problem. I do agree it's annoying - happens to me all the time, but adding the delay to the basic click ON - I dunno...

Just a quick question: I assume all flashlights have slightly different coding? So I can't just adjust 1 code and upload it to several Anduril lights I own, for example: Noctigon D18, Lumintop FW3A etc.

Actually I have a second question, when I go to this overview: https://bazaar.launchpad.net/~toykeeper/flashlight-firmware/trunk/files/head:/ToyKeeper

I'm trying to download but get errors each time.

Anduril has separate files for several more popular flashlights. They usually differ in the number of pwm outputs, auxes, button illumination, “maximum power” and temperature, or smaller “BLINK_AT_RAMP_MIDDLE” settings.
But if you are sure that the driver has the same structure and flashlights have the same functionality then one file should be enough.

TK seems to be trying to refresh the entire library. Check this thread.
At this link you will download (probably) the latest version (482). (Whole repository).