Flashlight Firmware Repository

Flashlight Modding and DIY Parts
600

If you have enough room left, you can do anything you want. The only real limitation is ROM space.

Most of the logic you described seems pretty straightforward too. Just add some extra clauses to detect the mode and step down in different ways, and it should be fine. Or you could perhaps do it in less space by using a mode change table… like each entry would define what “stepping down” means from that mode. Here’s a rough idea of what I mean:

uint8_t modes = {0, 0, 0, 255};
uint8_t altmodes = {0, 255, 30, 255};
uint8_t stepdowns = {0, 2, 0, 1};

void stepdown() {
  mode_idx = stepdowns[mode_idx];
}

I suspect Tom’s suggestion would be simpler though. :slight_smile:

601

That works. How do I make it skip the next-to-last mode?

602

Something like this:

if (++mode_idx == (sizeof(modes) - 2))

++mode_idx;

if (mode_idx >= sizeof(modes))

...

...

Ok - you'd be adding the first 2 lines, and modding the 3rd line to remove the ++. This is all in the function: next_mode().

Hope I made this clear enough. Basically you detect if the mode is incrementing to the 2nd highest mode. If so, increment the mode index again.

603

I think I have everything working now. I haven’t actually tested LVP yet, but I don’t know why it wouldn’t work as the mode order is now back to “normal”.

Would one of you mind looking over it to make sure there isn’t some hidden screw-up that will cause me grief later? thanks

once again, mine is on the right, stock STAR is the left.
Diff check

edit: JK, now I’m back to having the problem that when power is cycled when in mode “0” it doesn’t come on in mode “3”. :frowning:
plot twist: So if I hold the button for 2.5 seconds it enters mode “0” (off). If I then remove power for <5 seconds, when power is reapplied it is still in mode “0” (no bueno). However, if I remove the power for >5 seconds before reapplying, it comes on in mode “3” as it should. Any ideas here?

604

There's something that's keeping power goin for 5 secs - no other explanation I can think of. Cap? Something?

605

Oops, forgot to update here.

That issue was on my “power supply.” I decided it wasn’t a big deal, so I installed it in the light anyways. Miracle of miracles, once in the light that weird behavior went away.

606

U mean a bench PS? Ohhh - if so, would explain the 5 secs shutdown... My bench PS is super slow on shutting down.

607

FWIW, I did some tests a while ago for the mem-decay method of detecting short presses. If I drain the OTC, it seems to take about 0.5s for the memory to decay. If I leave the OTC fully charged, it seems to take about 4s for memory to decay.

Just a thought. I don’t even know if you’re using that method.

608

It’s actually just a cheap buck converter I use to test drivers, but I have a omten switch in series anyways.

609

Hhhmmm. Something wasn't right bout that setup I guess? if it worked once in the light.

610

I’ve had other issues with it before, especially with turbo timers. Idk if it’s ripple or what.

For instance on this driver, I have the timer set to 2 minutes. Its 6*7135 (2.3amps). If I have my buck converter limited to a lower output, like 1.5amps, the turbo timer steps down wayyyy early, like 1 minute instead of 2. But if I don’t limit output on the “power supply”, the timer works just fine.

I don’t understand it, but I’m slowly learning that if something isn’t acting the way the firmware says it should, try it on a battery before freaking out.

611

I do my initial tests on a batt 90% of the time - an old TrustFire in a holder w/red&black wires ended with alligator clips. Sometimes if it's more risky, I'll go slowly up with the bench PS. I'm usually carefully continuity testing everything out first, so not much risk applying power.

612

Oh, on a variable current / voltage power supply, with current limited, the voltage can do some weird things. You can only limit one or the other, basically, and the other will adjust itself accordingly.

I’ve been finding that even voltage calibration seems to work better with a battery than with a power supply (and a DMM to confirm voltage in real time).

613

Do we have a Yezl Y3 Star firmware - el switch and a tail switch, several modes switched through the el switch and an offtime memory?

614

I do. On the 25/45/85 thread, have a dnld link but it requires a 45 or 85. Blew past 2KB code, so the 25 won't cut it. It's also fully programmable (64 possible mode combos) and I posted an instruction manual (2 pages) on it's operation. Didn't upgrade a Y3 yet, but I'll have to do 4 of them shortly. Have the dual switch (e-switch/power) version dnld'ed in a X6R and works well so far.

615

Great, but can it be applied on wight`s A17dd ver 0.44 and tinny13? The last Y3 i modded was with that driver, el and tail switch and TK Ramping UI table firmware, V6 1D dedomed and 210k cds, came out exellent but now i need the firmware i mentioned

616

No tiny13 support, only a 45 or 85 on a FET+1 driver. I've only used the FET+1 wight drivers, like the BLF A6 driver, in 17 and 22 mm sizes. All my e-switch build/mods are or will be 85 based. It can be changed to work with a conventional FET or 7135 (only) driver but I don't see it worth the effort for now. There are some newer OSHPark boards available now for the larger footprint of the 45/85, but mostly I'm doing the "bent in pin" technique to retrofit.

617

thanks, fet+1 will do fine too, have to start trying 85 out now :wink:

618

Hi,

I’m thinking about giving bistro a try. I have components for wight’s 17mm FET+7135 and I recently ordered an Attiny 25. Unfortunately I got the normal 25, not 25V. Would I have to make some important changes to the code for the use of the “standard” 25?

619

Nope, no changes. In fact Richard at MtnE sells the 25, not the 25V. Only difference is low operating voltage, but the LVP kciks in before you should get that low anyway.