I think this is impossible. Long/short press functionality while on has been implemented by a member here in STAR off-time, but I believe it is impossible from an off state.
I meant, of course “Star momentary driver” program.
I apologize for the error
No worries! Unless I am misunderstanding what you want to do, the momentary program already does have that functionality.
Function may be already in the program, but I do not find it there. So, I just may have to study more about the program.
It is already there by default. You can change the amount of time that constitutes a long press by changing the LONG_PRESS_DUR value. 32 ticks (0.016 seconds each tick) is the default, but I prefer 22 to 24 ticks.
That should be do-able with only small changes.
First, you’d want to put a 0 in the middle of the mode sequence. Second, you’d need to add a line in the main loop which sets the mode index to zero when the PWM level is zero. This way, it would reset to the default “off” state whenever you reach that level.
Using the stock STAR_momentary, you may also need to redefine the number and value of output levels, disable alt PWM, and possibly disable the hidden momentary mode.
Does this make sense?
Yes, it does make sense!
Now I just need to focus on programming.
Thank you for your help.
A couple of members have recently sought a “1 mode” driver/firmware for various reasons.
Using STAR as a base, it’s easy enough for people with limited code skills such as myself to comment out all modes bar 255, but I found that this method doesn’t play nice with the low voltage warning/step down, as there is no lower mode to step down to.
If I keep a 2nd lower mode in there, the code works as it should, but there will be instances where the lower mode can be inadvertently changed to, even when set to come on in High mode every time.
I want to keep the low voltage step down routine, so “Mr. Muggles” sees the light has dimmed noticeably, & figures that it’s time to change the battery.
I’m thinking that the best solution would be to disable the part of the code that looks for the ‘quick-click’ for the mode change, or just shorten that time so as it’s not possible to click into the lower mode.
Could one of the code Guru’s help me out with what needs to be changed - I’ve tried to follow it through, but can’t put my finger on it.
Cheers 
I guess easiest would be to simply comment out the “next_mode()” call from the mode_idx&0x10 check (or comment out the entire mode_idx&0x10 check routine), disable mode memory and have mode direction high to low.
I assume we are talking about the clicky firmwares.
For the clicky firmwares I think the most straightforward way to handle it is to set the minimum stepdown brightness manually. This line determines the lowest PWM level the driver will stepdown to:
if ((PWM_LVL >> 1) < modes[0]) {
Note that it’s based on modes [0], the first mode, but in a single mode driver that’s the only mode we have! Instead we just set it like this:
if ((PWM_LVL >> 1) < 30) {
where “30” is the lowest level we want it to step down to in this case. Assuming the single-mode was set to 255, stepdown pattern would look like this:
255, 128, 64, 32, 30, 30, 30, etc, …, critical shutdown
If you’re building a lot of single mode drivers and plan to change the minimum stepdown level a lot you may use a define for that value, just add one at the top like:
#define STEPDOWN_MINIMUM 30
if ((PWM_LVL >> 1) < STEPDOWN_MINIMUM) {
EDIT: My kingdom for a [code] tag. The forum software is messing up the first code quote, the mistake is fairly visible though (modes with a superscript zero).
That's what I usually do: define a lower mode, but don't put it in the normal mode orders, then tell the program to step down to that level as the minimum. I also do the same thing when I want the turbo timer to step down to a "hidden" level.
Hi all,
I have a somewhat related question. Is there any way to use a pot to control a 7135 based driver?
See my posts a few pages ago where I started working on the code to do that with LVP integrated.
Alternatively you can use a VaraPower driver and hook up the PWM input on the 7135’s to the gate pin on the FET of the VaraPower (but do not route LED power through the VaraPower of course!).
Thanks for the help everyone, I’ll try defining the step-down level & adding it in there.
I’ll be flashing a couple this weekend if all goes well.
It should work to simply make the step-down reduce the PWM level without changing the mode index. Like, if the PWM_LVL is less than some minimum (10, maybe?) blink and shut off. Otherwise, tell it to cut the PWM level in half — “PWM_LVL = PWM_LVL >> 1;”.
If there’s only one level defined, any quick tap should return the light to its maximum level… and then it’ll step down when the voltage has been low for a while.
I’m assuming this is a clicky switch.
I think the clicky firmwares already behave in exactly this way (only the momentary firmware actually steps down through the modes IIRC). The issue is that with normal operation the “some minimum” is the lowest defined mode rather than an arbitrary value. After swapping in an arbitrary minimum (10, whatever) the behavior is almost exactly as you described, except that after we reach the (10) or whatever the firmware will maintain a constant output level until it hits the ADC_CRIT value, then it shuts down.
OK, I've defined the stepdown value in this section of the code;
=========================================================================
* Settings to modify per driver
*/
#define VOLTAGE_MON // Comment out to disable
#define STEPDOWN_MINIMUM 50 // Hidden mode level for low voltage step down
// #define MODE_MOON 6 // Can comment out to remove mode, but should be set through soldering stars
// #define MODE_LOW 12 // Can comment out to remove mode
// #define MODE_MED 39 // Can comment out to remove mode
// #define MODE_HIGH_W_TURBO 110 // MODE_HIGH value when turbo is enabled
#define MODE_HIGH 255 // Can comment out to remove mode
// #define MODE_TURBO 255 // Can comment out to remove mode
// #define TURBO_TIMEOUT 240 // How many WTD ticks before before dropping down (.5 sec each)
#define WDT_TIMEOUT 2 // Number of WTD ticks before mode is saved (.5 sec each)
#define ADC_LOW 130 // When do we start ramping
#define ADC_CRIT 120 // When do we shut the light off
/*
* =========================================================================
And altered the code at the end where the stepdown routine is;
// Flash 3 times before lowering
hold_pwm = PWM_LVL;
i = 0;
while (i++<3) {
PWM_LVL = 0;
_delay_ms(250);
PWM_LVL = hold_pwm;
_delay_ms(500);
}
// Lower the mode by half, but don't go below lowest level
if ((PWM_LVL >> 1) < STEPDOWN_MINIMUM) {
PWM_LVL = modes[0];
mode_idx = 0;
} else {
PWM_LVL = (PWM_LVL >> 1);
}
// See if we should change the current mode level if we've gone under the current mode.
if (PWM_LVL < modes[mode_idx]) {
// Lower our recorded mode
mode_idx--;
I'm bench testing this with a partially charged cell, starting around 3.2v, & letting it run down.
I don't get the three flashes + stepdown to the defined value (50.)
Instead, it goes straight to the 10 flashes for critical voltage, but does not power off.
At no point does it step down to the predefined value (50).
What have I done wrong?
I was thinking about that also a few weeks ago, It should be fairly easy to make a voltage divider with the pot, and put it to ADC.
In order to maintain use of the full physical throw of the pot and have the full desired range of PWM levels stay available a voltage divider is no good by itself - it’s not regulated so the maximum input will go down as battery voltage declines. Instead you need a regulated voltage source, probably either an LDO or on a Zener mod driver just add a divider off of the Zener. That way you have fixed target for both high and low voltages when looking at the ADC values.
Oops, my mistake. :zipper_mouth_face:
Also look here:
if (mode_idx == 0 && PWM_LVL <= modes[mode_idx]) {
Looks like it should be:
if (mode_idx == 0 && PWM_LVL <= STEPDOWN_MINIMUM) {