FWIW, I added a STAR_1mode firmware to my repository since the changes needed to do this turned out to be non-trivial.
I’m not sure it should really be called STAR though (even though it’s 95% the same code), since it doesn’t use the stars any more. With only one mode there’s no point checking the stars.
And I’m rather using Linux but Avrdude seems to be working fine there. Compiling binaries should work in Linux too with some manual work, needing the avr-gcc toolchain. I’m mostly looking for a three mode driver, Lo-Hi-Strobe, so it’s probably already available in one of JonnyC’ or DrJones’ firmwares. I’d rather get rid of PWM completely, just run on 8x7135 for Hi and 1x7135 for Lo, but dunno if that’s possible without hardware tweaks?
I haven’t tried any of the flashing tools from DX; not totally sure if it works or not. Could you let us know your results?
All the tools work fine in Linux, and pre-built packages are available at least in Debian and Ubuntu.
For 1x7135 and 8x7135, you’ll need a driver with dual PWM, such as one of wight’s designs or the “moonlight special” from RMM. The only free firmwares which support both dual PWM and strobe are “starry-offtime” and “blf-a6”, found in my code repo linked below. However, almost nobody can see the difference between fast PWM and actual current control, so the dual PWM requirement is probably not really necessary.
Do you think those three items above will work? If so I’ll order them. And yes I promise that I’ll let you know if they work, or not
That sounds great. Will just have to look up a good tutorial then.
That was my hope too. Just a stock 105c/105d with custom firmware with fast pwm will be good enough for most people. Also I think the mtn dd+7135 should be able to run without pwm with custom firmware, running Lo on the 7135.
Yes, the DD+7135 drivers will work too, but I thought you wanted to stick with 7135s.
However, a single 7135 running at 100% is not what I would call a “low” mode. It should do about 100 to 150 lumens in that mode.
In any case, a regular nanjg works fine as long as you don’t mind being limited to 2.8A. It also has no offtime capacitor, but that’s not really an issue if you use memory decay to distinguish short vs long taps, add a capacitor yourself, or use an ontime-based firmware.
I was just wandering if anyone happens to have a version of this or some other OS firmware that is a just a traditional L, M, H, Strobe, SOS, with memory?
I think you could probably configure the’s TheStar firmware to do L/M/H/Strobe/SOS with memory, in such a way that the blinkies are hidden. It’s more complicated than that by default though.
Thanks _the_ I appreciate it. Would you possibly be willing to do me one more favor? I have tried and tried to get these files to work and so far had no luck generating any working code, and have not even succeeded at converting a working file to a hex.
Could you possible send me a hex with the second option where its low, med, high, strobe, SOS, with memory in one sequence? No hidden stuff.
If its is something that take much time I would compensate you.
No problem. Please PM me your email address and I'll compile the hex and send it to you.
What kind of mode percentages do you want for L->M->H? Do you want a full 100% high without turbo timer? Any other "annoying" features you would like me to strip away before compiling it?
On- or off-time memory?
..and please try also the one with hidden goodies.. Who knows, you might even like it. :)
Yeah, I kind of assumed the blinkies would need to be hidden. I don’t think I’ve ever heard anyone request non-hidden blinkies before. TheStar has a nice way of keeping those out of the main sequence without disabling memory.
That is fantastic, thank you so much!!! I will PM my info. This driver is not for me it was a request I had from someone else. I will message him and ask if he would like the blinkies to be hidden.
If the strobe and SOS were hidden how would they be accessed?
If so, you might find ToyKeeper/Baton.c useful as a starting point, since it already implements a lock mode toggled by a long long press from off. However, it uses long press while on to advance modes, and short press turns the light on or off in whatever mode was last used. But it might at least be useful as a base for making what you want.
The code is in the firmware repo link in my signature.
Thanks ToyKeeper, I’m using Garrybunk.c from here Index of /torches/garrybunk and made some mods and get all what i want less locking mode and duplicate imputs and outputs.
The extended turbo timer and gradual ramp down you guys helped write for me have served me very well especially when used with the off time memory version.
I’m looking to take it one step further and implement STAR in some higher capacity lights I’ve been using. These lights are typically used at lower outputs for several hours at a time.
What I’m after is a global timer that would turn the light off after 5 hours.
Global in the sense that it would apply to all of the settings on the light. If low, medium, or high was left on for five hours, it would automatically turn itself off.
Is something like this feasible within STAR off time memory?
You should be able to count the WDT ticks in a 16-bit unsigned int. I think the default is 500ms per tick, so 36000 ticks would be about 5 hours. If the code sees the timer has gotten that high, it can turn off the light using the same method the low-voltage protection uses.