It doesn’t compile, Loneoceans modified the code in a couple of files and these changes aren’t merged into Toykeeper’s branch.
My apologies Limsup I see that you are aware of the github and I missed it. It is true that Fireflies has not be the best at communication and I understand your troubles. I downloaded the package on github and it compiles on Microchip studio for me, but maybe that is an older code. At the moment I can’t help you other than suggest you email loneoceans. Anyway, it does makes me think twice about buying a flashlight from them in the future based on what you have said.
No worries. And thank you for trying to help me out.
However, I have no knowledge of compiling firmware from codes or merging into the main branch and so on. So I might have no idea what the developer loneoceans replies even if he kindly takes time to reply. I might have to get basic knowledge first.
Regardless, thank you for the tip! I will share it here if I get any meaningful answers either from the manufacturer or the developer.
I recently bought an E07X Pro with the old driver (RevB) and I was wondering if you got any response from Loneoceans or FF about any updates to the hex or merging to the official anduril 2 branch? I would like to see features from the new anduril like 3C from lockout to unlock or the ability to change turbo behavior with 10H.
Long story short, I don’t have any Lume1 lights so I can’t test whether they work. This, plus some personal issues, have kept me from merging and maintaining the code for those lights.
Of course, it’s not my job to maintain Fireflies’ code. But if I had the hardware, I’d probably at least update it once in a while and notice if anything major broke.
Similar story for the FW3X. I don’t have one, or anything which even uses the same architecture. I merged it blind and don’t really know if it works.
In contrast, there’s Hank (Emisar / Noctigon), who often doesn’t need new firmware because he tends to make new lights compatible with older driver architectures… but he often sends me lights anyway, “as a gift”. Maybe that’s a cheeky way to get free work done, or maybe he’s just being nice… I dunno. But either way, I end up using his lights during development, which means they end up with pretty good support. Because he makes sure they’re available and convenient to reflash – over and over and over.
Meanwhile, I almost never touch my ROT66, because it generally takes 100+ tries to get it to reflash successfully. It has some sort of analog issue which interferes with that. So I’m always afraid it’ll just end up bricked if I try. And I don’t want it bricked. It’s a 219B light with a fantastic beam. So I leave old firmware on it instead of using it to test new builds.
3 Thanks
Has loneoceans contacted you about merging his addition to the main branch ?
He says this in his github Lume (new version) repo GitHub - loneoceans/lume1-ff-6af: Anduril Firmware for the Lume1-FF-6AF Flashlight Driver :
I am aware of the current awkward repository management - there is ongoing work to merge this firmware branch with the main flashlight repository on Launchpad. Thank you for your patience.
There are a couple of useful additions that would be great to have merged in the main branch, notably the TURBO_TEMP_EXTRA and the ”UDR” (USE_MULTIPLE_POWER_PATH …)
Apparently Fireflies didn’t even send one to him either, which is weird to say the least, I mean he must have prototype drivers since he developed them but without hosts he couldn’t even test them in situ…
I was thinking of buying one shipped to you, but wow, 118$ for the E07x, I don’t remember paying that much for my E12R… maybe several members could participate? A discount from fireflies would be nice as well.
I appreciate the thought, but getting community folks to buy hardware for this doesn’t seem like the right answer… basically paying FF for the privilege of doing work for them.
I think so? I forget. I’ve been sick so much, I missed a lot of things. I have a huge list of stuff to catch up on, and I’m pretty sure that’s on it somewhere.
I haven’t even kept up with what lights FF sells now. It looks like the unsupported lights are the models ending in “Mu” and “X”? I wonder if Fireflies could send some of those to LoneOceans (who did the OEM firmware for those) and me (the upstream maintainer). (which you already know, but random people reading this thread might not)
I have an original E07, but it uses a different driver… and I have the first batch (where the MCPCB is floating on air), so it overheats easily… and mine doesn’t turn on the main LEDs any more. I haven’t opened it to check what broke; it acts like a wire may have detached itself while it was sitting on a shelf. One more in a big pile of repairs to do when I have time.
Anyway, if FF sent any dev hosts, I’m not super picky about what they are, since I don’t really plan on using it beyond testing… but in general I like small lights in the 4000K to 5000K CCT range… especially when it has negative duv (pink tint). So, like, 219B is good, SST-20 is bad. Not that it really matters for testing. The important part is having a diverse range of circuit types to test on.
Unrelated to Fireflies though, I’ll probably be busy with firmware pretty soon because I have a 3-channel light showing up aaaaaany day now. Allegedly. Gotta revamp the multi-channel code for that, and I’ll probably try to catch up on other stuff while I’m at it.
You’re right, maybe they’d be willing to send one for free if asked ?
I very sorry to hear that, I wish you the best.
Not exactly, their naming scheme isn’t exactly consistent, prior to end of 2022 there was only the E12R and Nov-MU with lume1 drivers, 6A buck + FET, with standard dynamic range, T1634, orange PCB. GitHub - loneoceans/lume1-fireflies: Anduril Firmware for the Lume1-Fireflies Flashlight Driver
Since the end of 2022 the lume1 lights use the newer revision with ”UDR”, T1616, black PCB : E12R, Nov-MU, E07x Pro, T1R. GitHub - loneoceans/lume1-ff-6af: Anduril Firmware for the Lume1-FF-6AF Flashlight Driver
The new revision uses 3 sense resistors for achieving a ”ultra” dynamic range, and DAC control.
It’s similar to my drivers except I use only two sense resistors and I abused the 2 led channel code to turn on the high power sense resistor at some ramp level : ~toykeeper/flashlight-firmware/anduril2 : contents of ToyKeeper/spaghetti-monster/anduril/cfg-thefreeman-lin16dac.h at revision 659
~toykeeper/flashlight-firmware/anduril2 : contents of ToyKeeper/hwdef-thefreeman-lin16dac.h at revision 659
So Loneoceans added proper code for that (the ”MULTIPLE_POWER_PATH" code).
The T1616 DAC support and VREF switching to increase the DAC resolution is already in the main branch.
The other models are classic FET+7135 : E07, ROT66, PL47/G2, PL09 quad, PL09 MU, E12C
1 Thank
This seems like exactly the sort of thing the new site’s bookmark feature is good at. Something I need to remember to do … but can’t do right now.
On the old site, I’d often leave threads unread to remind me that I needed to do something with them, or leave tabs open, or collect unloaded tabs in Tabs Outliner (which is unfortunately quite buggy)… but I think perhaps Discourse bookmarks might be more reliable.
Thank you for addressing this! I really appreciate all of the work that you do. I wish you the best in health.
I just got into the flashlight hobby and all of this is somewhat confusing coming from a non-coding background. All I know is that Anduril is an amazing UI and it gives the user so much control and power over their tools that are seldom seen elsewhere.
1 Thank
Hey! I reached out on Reddit to see if anyone had any answers and a modder replied with their hex code with some updates to Anduril for the FF E07X. I’m not sure if this is the answer you are looking for, but I hope it will provide some insight.
1 Thank
For everybody looking for firmware updates - here is the way for lume1 orange driver:
2 Thanks
Any chance you could post the hex you used on your E12R?
Yes, you are welcome
Builded with this config, so adjust accordingly:
Config
#define MODEL_NUMBER «0443"
#include "hwdef-fireflies-lume1.h»
#define DEFAULT_THERM_CEIL 55
#define USE_AUX_RGB_LEDS
#define RGB_LED_OFF_DEFAULT 0x29
#define RGB_LED_LOCKOUT_DEFAULT 0x10
#define DEFAULT_AUTOLOCK_TIME 10
#define DEFAULT_LEVEL 27
#define DEFAULT_MANUAL_MEMORY DEFAULT_LEVEL
#define DEFAULT_MANUAL_MEMORY_TIMER DEFAULT_AUTOLOCK_TIME
#define MAX_1x7135 149
#define TURBO_TEMP_EXTRA 7
#define THERM_FASTER_LEVEL 116
#define MIN_THERM_STEPDOWN 69
#define THERM_NEXT_WARNING_THRESHOLD 16
#define THERM_RESPONSE_MAGNITUDE 96
#define RAMP_LENGTH 150
#define PWM1_LEVELS 1,2,3,3,3,3,3,4,4,4,5,5,6,6,7,7,8,8,9,9,10,10,11,12,13,14,15,16,17,18,20,21,23,24,26,27,29,31,33,35,37,39,41,43,45,48,50,53,56,58,61,64,67,70,74,77,80,84,88,91,95,99,103,108,112,116,121,125,130,135,140,145,150,156,161,167,173,178,184,191,197,203,210,217,223,230,238,245,252,260,268,275,283,292,300,308,317,326,335,344,353,363,372,382,392,402,413,423,434,445,456,467,478,490,502,514,526,538,551,563,576,589,603,616,630,644,658,672,687,702,717,732,747,763,778,794,811,827,844,861,878,895,913,931,949,967,985,1004,1023,0
#define PWM2_LEVELS 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1023
#ifdef BLINK_AT_RAMP_MIDDLE
#undef BLINK_AT_RAMP_MIDDLE
#endif
#ifdef USE_DYNAMIC_UNDERCLOCKING
#undef USE_DYNAMIC_UNDERCLOCKING
#endif
#define RAMP_SMOOTH_FLOOR 3
#define RAMP_SMOOTH_CEIL 149
#define RAMP_DISCRETE_FLOOR RAMP_SMOOTH_FLOOR
#define RAMP_DISCRETE_CEIL RAMP_SMOOTH_CEIL
#define RAMP_DISCRETE_STEPS 7
#define SIMPLE_UI_FLOOR 3
#define SIMPLE_UI_CEIL 139 // 139 for 5A max
#define SIMPLE_UI_STEPS 5
#define LED_ENABLE_PIN_LEVEL_MIN 1
#define LED_ENABLE_PIN_LEVEL_MAX 149
#ifdef USE_INDICATOR_LED_WHILE_RAMPING
#undef USE_INDICATOR_LED_WHILE_RAMPING
#endif
#define PARTY_STROBE_ONTIME 4
#define USE_VOLTAGE_LOWPASS
#define USE_SOFT_FACTORY_RESET
2 Thanks
Thank you so much!