I thought about exploiting the lock timing to be infinite or removed
If the firmware does not lock the mode in after 1.2s it would all the time ready to change modes
ramping does not use the 1.2s mode lock timer its only used in modes set
I cant program so I do not know what ecxactly to change to get this timer set to infinite or disable it
so in ramping side switch has normal operation including putting the light in standby
Mostly, I was wondering how you’d want a ramping interface to work when the tail clicky is the only way to turn the light on/off. Like, what would happen when the user clicked the e-switch. But “no ramping” is also an answer to that question.
For a Forum member I am trying to get NarsilM first time individually set up on Modes
never used modes before myself
But I am stuck due to a bug
He wanted that the light has Mode memory when the light was powered down with tail switch
There is a switch in Setup file named #define OFFTIME_ENABLE 1
// 1: Do OFF time mode memory for Mode Sets on power switching (tailswitch), 0: disabled
Problem it its bugged when I turn on the light it has Next Mode Memory, so it gets to next mode after a power disconnection
If its meant to do next mode memory good feature if not bug, both would be great
maybe the code is OK but MCU does not like low voltages before shut down and notices a click before its off
I’m only guessing, but it sounds like maybe it’s doing what it’s supposed to do. Maybe the driver needs a way to bleed off power faster while power is disconnected, so it can measure shorter durations of offtime.
Or if the tail button is supposed to act as a momentary switch, maybe it’d be better to leave offtime disabled?
To do a UI where the tail is momentary and the side switch changes modes, it probably wouldn’t take much time. Click to go one level brighter, hold to go dimmer?
Since it’s a thing people might want, and since I think Lexel may have been requesting it, I took a moment to make a Werner-style momentary UI, side e-switch plus tail clicky-switch.
Thanks WTF. Saw that too, but the 7135 channel isn't working. I'm think I have eliminated potential hardware issues (faulty 7135, connections, etc). So I wondering if the hex file may be using different channels than what the documentation indicates. I'll reexamine hardware again tonight. I may have to build my own hex file if I still can't find a hardware problem.
I just had that happen to me today when stacking three of them, some uncooked solder paste got under the bottom 7135 and shorted it out, next I got a tiny solder bridge to a nearby capacitor. It’s always the simple stuff that causes the most grief.
I wonder if the Attiny has enough power to drive a small led and resistor, it would make a simple test lead to check pwm output. Remove the 7135, turn the light on and probe the Attiny.
I believe when I researched this before, one pin could output 40ma. I was looking to make a moonlight mode without using a 7135, just the output on that pin for moon mode.