Crescendo clicky firmware by TK

Thanks MascaratumB & chops728 I was actually thinking of those 2 light along with a Maratac and ITP.

.
Basic operation:

(tap = half press)

.
From OFF:
(memory off) 1 full click = on at moon level and begins ramping
(memory on) 1 full click = on at memorized level and remains steady
1 full click then Single tap = Moon
1 full click then double tap = Turbo
1 full click then triple tap = Strobe / Batt check / Special modes

.
From ON (while ramping):
Single tap = pause ramping (steady on at the level when tapped)
1 full click = OFF

.
From ON (after pause ramping):
Single tap = resume ramping UP
Double tap = resume ramping DOWN
Triple tap = Turbo
Quad tap = Strobe / Batt check / Special modes
1 full click = OFF

.
From Moon:
Single tap = begin ramping
Triple tap = Turbo
1 full click = OFF

.
From Turbo:
Single tap = back to steady on at previous level
1 full click = OFF

If no one can check this meanwhile, I can do it later today! But, from what I recall it is pretty much what you descibed :+1:
BTW, strobes are before battery check!

Thanks MB, no hurry to check… whenever you get time.

I wanted to understand it better than just to look at the diagram, it only shows “taps” which is slightly confusing since the first tap (from OFF) will actually be a full click.

I’m trying to decide if I’ll like this UI so I wanted to have it “written” since these more complicated diagrams can also be slightly confusing with all the different dotted lines and arrows running in different directions.
:nerd_face:

.
The diagram does show Batt check first before “Special 1, Special 2, etc.” so I will note that strobes are first, thanks.

I wanted to understand it better than just to look at the diagram, it only shows “taps” which is slightly confusing since the first tap (from OFF) will actually be a full click. —— Yes the first tap from off should be a full press and or click of the button.——

I’m trying to decide if I’ll like this UI so I wanted to have it “written” since these more complicated diagrams can also be slightly confusing with all the different dotted lines and arrows running in different directions. ——It definitely looks confusing,doesn’t it.——

The diagram does show Batt check first before “Special 1, Special 2, etc.” so I will note that strobes are first, thanks.
—— Yes the strobes are first(at least on my driver).——

Thanks. So “written” operation I made (post #20 above) is completely correct? (except for strobes first)

(memory on) 1 full click = on at memorized level and begins ramping

Mine (with memory on) goes where I last stopped mine. So say I stopped it at a medium level, turn it off, it will go back to that brightness level when I turn it back on again and stay there.
From the looks of everything else on your chart, awesome BTW, looks great to me. :beer:
I’m going through you chart and tried it all on my light and everything but the memory thing above is good on mine.

I hope this helps you out bud. :slight_smile:

Yes that’s a big help, thanks for taking the time of doing this!

About the memory…
“Mine (with memory on) goes where I last stopped mine. So say I stopped it at a medium level, turn it off, it will go back to that brightness level when I turn it back on again and stay there.

So the difference between what I wrote and what really happens are the words “and stay there” ?

So…

(memory on) 1 full click = on at memorized level and begins ramping EDIT with: “remains steady”

Sound right?

(memory on) 1 full click = on at memorized level and begins ramping EDIT with: “remains steady”

Sound right?

Yes, to me it’s good.

Thanks primal, I’ll finalize it now.

Final rendition of worded operation (confirmed):

.
Basic operation:

(tap = half press)

.
From OFF:
(memory off) 1 full click = on at moon level and begins ramping
(memory on) 1 full click = on at memorized level and remains steady
1 full click then Single tap = Moon
1 full click then double tap = Turbo
1 full click then triple tap = Strobe / Batt check / Special modes

.
From ON (while ramping):
Single tap = pause ramping (steady on at the level when tapped)
1 full click = OFF

.
From ON (after pause ramping):
Single tap = resume ramping UP
Double tap = resume ramping DOWN
Triple tap = Turbo
Quad tap = Strobe / Batt check / Special modes
1 full click = OFF

.
From Moon:
Single tap = begin ramping
Triple tap = Turbo
1 full click = OFF

.
From Turbo:
Single tap = back to steady on at previous level
1 full click = OFF

Sorry I couldn’t confirm yesterday :person_facepalming:
I’m glad that others did and that the diagram is explained now :+1:

No worries MB, I appreciate you were going to check it too, the OP was on it!

Hopefully this will be helpful to others as (IMO) the “map” is especially confounding for this because of the “Full click vs Single Tap” conflict.

Hi.

I‘ve flashed a Nanjg105D (Crescendo firmware), but I cant access to the memory activation I have push the indicated times in the instructions and also more times. I cant access.
Does anyone know what problem is? (Fuses are correct).

Thank you very much.

From what I gather; Crescendos Firmware with ramping will work with a tailcap clicky switch, correct?

Did your flash of Crescendo involve a port/edit of the standard Crescendo code? It is possible that mode memory is one of those additional features that was removed in order to fit the standard Crescendo code into the smaller memory space of the ATTiny13a MCU used on the Nanjg105D driver.

Yes, and personally I’ve had better luck using it on reverse clicky rather than forward clicky tailswitches.

Thanks SeniorXJ and PC_Light.

Do you have knowledge of where I can download the firmware crescendo for the ATTiny, being able to choose which additional features has been removed?.

I can do without strobo and other things, but memory is important for me.

Thank you.

@Maiden666. the small amount of memory in the ATtiny13 MCU limits the code that can fit. I had a similar experience when I first tried Crescendo13 on a BLF A6 driver which like the Nanjg105D uses the ATtiny13a.

In order to get Crescendo to fit the ATtiny13, Toykeeper had to pare the original file down to fit, which necessitated elimination of Config and some other special modes.

I am NOT a coder and have never used C but FWIW, working slowly through TK’s excellent commented source Crescendo.C file. I was able to (hack) my way through the code to retain Memory by sacrificing the smoothness of the Ramping. It was the only place I could squeeze out enough space to restore the Config and other features. So now I have Crescendo with Memory working on the ATtiny13 but ramping is a little choppy compared to the original smooth version.

I am reluctant to share my .hex for two reasons (1) our two driver boards are different, and (2) I’m unsure of how properly share altered versions of TK’s code. But hopefully this will give you an idea that might work for you.

You may also want to consider gChart’s ramping_ui which was actually written for the Nanjg driver.

is this the crescendo?

crescendo?