Crescendo clicky firmware by TK

Crescendo could be modified to start in turbo. You could just reverse the ramp table so it starts with 100% FET, and turn off memory. I think this would start in turbo then automatically ramp down? I’ve always used memory so I’m not certain how it behaves with no memory. Is there an additional simple modification to make it just turn on in turbo and stay there?

For that, I’d recommend Anduril with the START_AT_MEMORIZED_LEVEL option turned on, maybe also with the boot code modified a little to do turbo by default instead of memory. This way, the tail clicky switch would work as a tactical momentary button, while a side e-switch provides access to ramping and all the other general-purpose stuff.

Or Crescendo could be modified to start at the top instead of the bottom, but it’ll still be prone to doing odd things when bumped. Even with modifications, I don’t think I’d recommend it for tactical purposes.

ahh yes tactical… but strobes gunna be a dead give away, can you imagine it, out side the cartell, everyone’s in position, shh….shhhhh? whats that noise? i mirrion candle power strobe mode…WITH RAMPING!!..

hmm… inddeadly…

Thanks! I didn’t even see all these options on Mountain Electronics site before this thread.

What kind of fuse I have to use with the Crescendo25?. Moreover, it would be possible to use these same fuses with the Attiny25 and 85?

Thanks.

Some firmware projects have recommended fuse values inside the source file. However, for all of mine, check the bin/flash-tiny*-fuses.sh scripts in the code repository to see the most up-to-date recommended fuse values for each MCU.

Okay, I just updated a bunch of source files to remove any outdated fuse info from the .c file and replace it with a pointer to the flashing scripts. Those scripts are much more actively maintained, and more likely to be correct.

No, it uses some sort of 10-leg chip as the controller. I don’t know what it is, except that it’s not any of the chips Crescendo supports.

In the bin/flash-*-fuses.sh scripts in my firmware repository, it has recommended fuse values for each type of controller chip and usually a link to a calculator which shows what those values mean.

In most cases though, the fuses don’t need to be flashed. Sending a .hex file by itself is typically fine, and less risky.

Almost there. But it’s not under ToyKeeper/ , it’s under bin/ . :slight_smile:

BTW, to compile the code for an arbitrary driver, you’ll probably need to edit the source a little bit to choose relevant settings. And the crescendo.c file also points to those same flashing scripts for info about the fuse values.

I hope people aren’t defined by their national stereotypes… because if they are, I must be a horrible person. :cry:

It’s far better to be a hopeless romantic than to be an arrogant jerk. :blush:

It’s just my national stereotype. But fortunately, people are not defined by the country they live in. :slight_smile:

ToyKeeper, I just wanted to say a big THANK YOU! for all of your hard work creating these awesome flashlight interfaces for all of us flashlight fanatics to use—your work is very much appreciated!

It looks like you signed up at BLF just to say thanks? That’s awesome! I hope you’ll stick around, since there’s a lot more to do here. :slight_smile:

congrats
does Crescendo work on Eneloop?
does it have NoVisiblePWM on sublumen level?

pic is a link to sw45k mod of AA Copper Tool

The MTN 15mm driver is not a boost driver, so it doesn’t work with an AA cell.

Crescendo generally uses ~16 kHz PWM, but it depends on what hardware it’s running on and how it was built.

is there a way to make an AA Tool run a Ramping UI on Eneloop?
Similar to Nitecore D10.

else, the basic modes on the AA Tool will suffice to gift to a muggle.

Hum, I am note sure it that already exists Jon!
I believe it is a little bit like the Anduril for the Sofirn SP10S project (to be run on AAs and 14500s): it is still being “searched” the ideal formula to make those more “advanced” UIs on alkalines! :weary:

BTW, the light in which I have Crescendo currently is the On The Road i3 zoomie flashlight.

thanks for your thoughts

well… I just wont tell the AA alkleak using muggles, about the D10 ramping UI…

The CuTool AA is intended as a gift to an electrician friend. Now that it has a good beam with sw45k, they can just learn the clicky UI, with memory…

close enough for Government work, as we say on this side of the great water

enjoy your LiIon UIs :slight_smile:

Thank you for making this chart, now I understand Crescendo.

Thank you very much.

Keep in mind that Crescendo running on an attiny13a does not have memory; not enough space on the chip for all the code. The code written for an attiny25 has memory available.