E-switch UI Development / FSM

212 posts / 0 new
Last post
ToyKeeper
ToyKeeper's picture
Offline
Last seen: 11 hours 13 sec ago
Joined: 01/12/2013 - 14:40
Posts: 6400
Location: (469219) 2016 HO3
goshdogit wrote:
I’ve been using Andúril on a BLF Q8 and an Emisar D1 for a few days now.

Thanks for the detailed feedback! Smile

goshdogit wrote:

Ramping
  • option to disable click & hold for ramping down? (ramp changes directions like Narsil)
  • option to disable blink at max regulated output?

Reversing — perhaps a compile-time option. After using reversing for a few years and non-reversing for a month or two, I’ve found I like non-reversing better. But it would be a good option at build time.

Blink at max — also a compile-time option. I already added one for blink at moon and blink at channel boundaries, so this fits right in.

goshdogit wrote:

Good Night mode
  • option to adjust starting output level?
  • option to adjust time until power off?

Maybe, if there’s room.

goshdogit wrote:

Possible bug
  • dimming bike flasher to minimum enables an unbelievably low steady output

Already fixed. This happened because it picks the burst ramp level by multiplying the steady ramp level by 2. At the very bottom of the ramp, though, levels 1 and 2 are actually the same thing, so the burst didn’t change the brightness at all. Easily fixed by using a floor level of 2 instead of 1.

I also increased the bike flasher ceiling so it can run brighter than before.

goshdogit wrote:

I’m not sure what TempCheck is telling me. On a Q8:
  • room temperature light – 8 long blinks
  • after 15 sec turbo – 1 long blink, 1 short blink
  • after 30 sec turbo – 1 long blink, 2 long blinks
  • after 1.5 min turbo – 1 long blink, 7 long blinks
  • after 3 min turbo – 1 long blink, 9 long blinks

It should blink out the MCU temperature in C. So, it thinks your room temperature is 8 C, and after 3 minutes on turbo it got up to 19 C. The attiny85 sensor isn’t calibrated though, so this value can be off by quite a bit. Mostly it’s useful as a way to find out what the MCU sees, which can help with setting a temperature limit. But on a Q8, it’ll take quite a while to get hot enough for thermal regulation to activate.

goshdogit wrote:
How about a ‘Muggle Mode?’ I’d like to hand the light to someone and say “Click to turn it on and off. Hold the button to adjust the brightness.”

If there’s room. Perhaps on an inconvenient click sequence, like 8 clicks from off?

goshdogit wrote:
An optional beacon mode at ‘power off’

It’s something I want to try, at least. Not sure if it’ll be in a build for production purposes.

goshdogit
goshdogit's picture
Online
Last seen: 14 min 20 sec ago
Joined: 12/03/2015 - 21:28
Posts: 402

ToyKeeper wrote:
Thanks for the detailed feedback! Smile
You’re very welcome! Thank you for the excellent UIs!

ToyKeeper wrote:
Reversing — perhaps a compile-time option. After using reversing for a few years and non-reversing for a month or two, I’ve found I like non-reversing better.
I think I prefer non-reversing too. If it’s a compile-time option, would it be universal or could reversing be enabled independently for muggle mode?
goshdogit wrote:
option to disable blink at max regulated output?

ToyKeeper wrote:
Blink at max — also a compile-time option. I already added one for blink at moon and blink at channel boundaries, so this fits right in.
I meant, “could the blink at channel boundaries be removed?” Compile-time option is fine. I think I’d prefer no blinks at moon, turbo, or boundaries but that’s just me. I know some folks are particular about knowing what circuit they’re on. Big Smile

ToyKeeper wrote:
It should blink out the MCU temperature in C.
That’s what I thought, but the scale and the short blink was throwing me off. I think I understand now that a short blink is a zero. One long, one short = 10 C?
goshdogit wrote:
How about a ‘Muggle Mode?’

ToyKeeper wrote:
If there’s room. Perhaps on an inconvenient click sequence, like 8 clicks from off?
Sounds good. Can it be disabled only by power cycling, like momentary?
goshdogit wrote:
An optional beacon mode at ‘power off’

ToyKeeper wrote:
It’s something I want to try, at least. Not sure if it’ll be in a build for production purposes.
Ok!

Thanks again for being open to feedback. As I said before, I’m more than thrilled with Andúril as it is! Thumbs Up


You seem to have omitted any mention of additional blinky modes. I know you mentioned ‘defective light bulb mode’ somewhere but now I can’t find it…
Party

ToyKeeper
ToyKeeper's picture
Offline
Last seen: 11 hours 13 sec ago
Joined: 01/12/2013 - 14:40
Posts: 6400
Location: (469219) 2016 HO3

I pushed some fixes just now:

  • Added reversing to Anduril. Made EV_tick always send 0 while in “hold” state.
  • Rearranged some build options and made sure the build still works if some are turned off.
  • Fixed issue where double-click-from-off followed by double-click-to-true-turbo would overwrite memory with the ceiling level. (should make Agro happy)
  • Fleshed out build options to blink at floor, ceiling, and channel boundaries.
  • Adjusted bike flasher floor and ceiling: floor high enough to make sure it always blinks, ceiling can be higher than halfway up the ramp.

The reversing thing is slightly different than Narsil and Ferrero Rocher. I wanted to make it more predictable without having to remember anything, so if it has been more than a second since the last user input, a “hold” will always go up. However, if the last “hold” went up, there is a 1-second window where the next hold will go down instead. Also, “hold” at the ceiling level always goes down.

So… it reverses, but it doesn’t stay reversed long enough to confuse a goldfish.

I’ll probably leave it enabled by default, since it no longer has the issue with forgetting what direction it’ll go.

As for muggle mode, I’m thinking it’ll be similar to momentary mode where it has no exits (even for “off”). It’ll be very very limited. The tricky part is figuring out where to put its config settings, if it has any.

OTOH, momentary mode makes a pretty decent muggle mode if set to a medium level.

ToyKeeper
ToyKeeper's picture
Offline
Last seen: 11 hours 13 sec ago
Joined: 01/12/2013 - 14:40
Posts: 6400
Location: (469219) 2016 HO3
goshdogit wrote:
You seem to have omitted any mention of additional blinky modes. I know you mentioned ‘defective light bulb mode’ somewhere but now I can’t find it… Party

I’m not sure there will be room for extra glitch modes. At least, I’m not prioritizing those.

goshdogit
goshdogit's picture
Online
Last seen: 14 min 20 sec ago
Joined: 12/03/2015 - 21:28
Posts: 402

ToyKeeper wrote:
…if it has been more than a second since the last user input, a “hold” will always go up. However, if the last “hold” went up, there is a 1-second window where the next hold will go down instead.
I think I like this. So after 1-second, reversing is still activated by a click then hold, but the first click ramps up a little bit first?
ToyKeeper wrote:
As for muggle mode, I’m thinking it’ll be similar to momentary mode where it has no exits (even for “off”). It’ll be very very limited.
Nice! How about muggles get access to only on/off and ramping. No blinkies, strobes, or other complex operations.
ToyKeeper wrote:
OTOH, momentary mode makes a pretty decent muggle mode if set to a medium level.
I agree, but I can already hear my friends whining… “There’s only one brightness?” “Why do I have to hold the button?” Big Smile
ToyKeeper wrote:
I’m not sure there will be room for extra glitch modes. At least, I’m not prioritizing those.
I’ll hush up about the blinkies, just don’t take away lightning mode! Big Smile
ToyKeeper
ToyKeeper's picture
Offline
Last seen: 11 hours 13 sec ago
Joined: 01/12/2013 - 14:40
Posts: 6400
Location: (469219) 2016 HO3
goshdogit wrote:
ToyKeeper wrote:
…if it has been more than a second since the last user input, a “hold” will always go up. However, if the last “hold” went up, there is a 1-second window where the next hold will go down instead.

I think I like this. So after 1-second, reversing is still activated by a click then hold, but the first click ramps up a little bit first?

The “click-release-hold” action is unchanged. It always goes down.

The regular “hold” action still goes up… unless:

  • The user completed a ramp-up less than one second ago.
  • … or the brightness is already at the ceiling.
goshdogit
goshdogit's picture
Online
Last seen: 14 min 20 sec ago
Joined: 12/03/2015 - 21:28
Posts: 402

I just reflashed a Q8 with this newest version of Andúril.

Sometimes a hold from off will remain at moon and not ramp. At first I thought this was only occurring shortly after powering off, but I’ve seen it happen after the light has been off for 30+ seconds. It seems intermittent. I can’t replicate this with my D1 running the previous version of Andúril. Could this be caused by the new ’1-second’ ramping reverse rule, like it’s trying to ramp down from moon?

Other ramping functions seem normal.

I’m also getting some faint flickering during the ‘steady’ phase of bike flasher mode. It’s very faint, and seems to go away at some brightness levels along the ramp.

ToyKeeper
ToyKeeper's picture
Offline
Last seen: 11 hours 13 sec ago
Joined: 01/12/2013 - 14:40
Posts: 6400
Location: (469219) 2016 HO3

Hey, good catch. Fixed.

If turned off while reversed, it could then try to reverse a hold from off. The amount of time it was off doesn’t matter for that, since it doesn’t measure time while off.

About the bike flasher… it runs at ~4 kHz PWM now instead of 15.6 kHz, as a side effect of some power management changes I added a few days ago. I’m not sure if it’s worth fixing or not, since the fix would cost a fair amount of space. Basically, all interruptible “delay” operations run at 1/4 CPU speed. This affects modes which use those, such as biking, battcheck, and beacon. It doesn’t slow down PWM in other modes though, like ramping and goodnight, which have no need for explicit delays.

The upside of this is that things like beacon are now much more efficient for longer runtimes. The downside is that the PWM on a few blinky modes might be visible or audible in some circumstances.

goshdogit
goshdogit's picture
Online
Last seen: 14 min 20 sec ago
Joined: 12/03/2015 - 21:28
Posts: 402

ToyKeeper wrote:
Hey, good catch. Fixed.
Thumbs Up

ToyKeeper wrote:
About the bike flasher… it runs at ~4 kHz PWM now instead of 15.6 kHz, as a side effect of some power management changes I added a few days ago. I’m not sure if it’s worth fixing or not…
Eh, probably not. I only noticed the faint flicker while ceiling bouncing the Q8 to check out the new brighter bike flasher levels. I doubt it would be visible on a bike.

I just reflashed the Q8 again. It sure is nice not needing to fire up the soldering iron!

Agro
Offline
Last seen: 6 hours 52 min ago
Joined: 05/14/2017 - 11:16
Posts: 903
Location: Ślōnsk
ToyKeeper wrote:
Agro wrote:
time limit to mode memory

The driver can’t measure time while it’s off, so making memory time out isn’t very feasible unless I increase the standby power significantly to keep the WDT active. There are features I’d like to try which require this though, like an alarm clock mode and a locator flash, so it’s on the todo list.


I’ve got some thoughts about it.
1. How about clearing mode memory on lockout? You do this on physical lockout already and doing the same on software one seems logical.
After all if I lock it out, I will probably not use it in a moment.
2. Independently, time-related functions need to increase power consumption only when they are running. So when mode memory is cleared, you can go back to deep sleep.
bwings
Offline
Last seen: 2 hours 47 min ago
Joined: 01/31/2016 - 04:42
Posts: 89
Location: South Sumatra, Indonesia.

Hi TK, can I have Andúril .hex file? I got tons of error when trying to build with Atmel Studio.
Thanks..

___________________________________________________________________________

Sorry for my poor English

goshdogit
goshdogit's picture
Online
Last seen: 14 min 20 sec ago
Joined: 12/03/2015 - 21:28
Posts: 402

bwings wrote:
I got tons of error when trying to build with Atmel Studio.
Most of the errors are probably due to missing header files.

The complier is looking for a several .c and .h files. You need to download these from TK’s repository.

Some are located here.

Some are located here.

You need to put these files in your project’s folder.

When you create a new Amtel Studio project, it creates a directory structure based on the name of your project. Right click the tab at the top left of Amtel Studio and click “Open Containing Folder.” Drop the .c and .h files into here and run the compiler again.

Another error you are probably encountering is, “Hey, you need to specify ATTINY” in the tk-attiny.h file. Double click the error, then scroll up a few lines and remove the // from one of the lines reading “#define ATTINY” and change the number to the proper ATtiny model number (13, 25, 85 etc.).

Hope this helps!

goshdogit
goshdogit's picture
Online
Last seen: 14 min 20 sec ago
Joined: 12/03/2015 - 21:28
Posts: 402

I’ve got Andúril running on a Q8, D1, and D4 now. I love having several lights with the same awesome UI!

I have an EagleEye X6R with a TA driver running Narsil that I’d like to reflash, too. It has a forward-clicky tailswitch and an e-switch on the head.

I’d like it to light up at the memorized level when powered up, so I can use the tailswitch as momentary.

I found this piece of code but I’m unsure what changes to make:

void setup() {
// blink at power-on to let user know power is connected
set_level(RAMP_SIZE/8);
delay_4ms(3);
set_level(0);
load_config();
push_state(off_state, 0);
}

Am I on the right track?

Also, how can I format code to read properly when posting here? It becomes a mess if I insert spaces at the start of a line.

ToyKeeper
ToyKeeper's picture
Offline
Last seen: 11 hours 13 sec ago
Joined: 01/12/2013 - 14:40
Posts: 6400
Location: (469219) 2016 HO3
goshdogit wrote:
I’d like it to light up at the memorized level when powered up, so I can use the tailswitch as momentary.

For that, it will need to save the memorized level to eeprom so it can remember after power loss. And given how often that level changes, it should probably be wear-levelled. This means bringing in the EEPROM_WL code, which isn’t otherwise used in Anduril, and making changes in a few places. It’ll cost more than a few bytes.

goshdogit wrote:
I found this piece of code but I’m unsure what changes to make:

void setup() {
// blink at power-on to let user know power is connected
set_level(RAMP_SIZE/8);
delay_4ms(3);
set_level(0);
load_config();
push_state(off_state, 0);
}

Am I on the right track?

Also, how can I format code to read properly when posting here? It becomes a mess if I insert spaces at the start of a line.

Yes, that’s one of the places which will need changes. It’ll need “push_state(steady_state, value_from_eeprom)” instead of going to the “off” state. And, um, get rid of the initial startup blink. Smile

The other changes are larger though… I should probably add another compile-time option for it, because this is a request which will probably come up frequently.

As for posting code, BLF isn’t very good at that. It can be done, by using a <pre> in the fancy post editor, but usually I don’t bother.

goshdogit
goshdogit's picture
Online
Last seen: 14 min 20 sec ago
Joined: 12/03/2015 - 21:28
Posts: 402

Thanks, TK! I’ll wait for a possible compile-time option for ‘power on at memory.’

In the meantime, would a ‘power up on turbo’ option be less complicated? Possibly something I could add/modify myself? Lexel enabled that in the previous install of Narsil when I ordered the TA driver.

ToyKeeper
ToyKeeper's picture
Offline
Last seen: 11 hours 13 sec ago
Joined: 01/12/2013 - 14:40
Posts: 6400
Location: (469219) 2016 HO3

I pushed an update with dual-switch support. It costs 172 bytes, if enabled at compile time, mostly due to bringing in wear-levelling functions.

The current method goes to the memorized level at boot, unless the e-switch is held. Then it goes to moon instead. (er, the bottom of the current ramp, whatever level that is, so it varies per-ramp)

ToyKeeper
ToyKeeper's picture
Offline
Last seen: 11 hours 13 sec ago
Joined: 01/12/2013 - 14:40
Posts: 6400
Location: (469219) 2016 HO3
Agro wrote:
1. How about clearing mode memory on lockout? You do this on physical lockout already and doing the same on software one seems logical. After all if I lock it out, I will probably not use it in a moment. 2. Independently, time-related functions need to increase power consumption only when they are running. So when mode memory is cleared, you can go back to deep sleep.

Personally, I like having memory after lockout. If anything, I’d prefer to make it time-related, not lockout-related.

As for time-related forgetting, I’d probably want to set the time to something pretty long, like a few hours. I haven’t tried the half-sleep mode yet to find out how much power it uses, but hopefully it’s not much.

I get the impression that perhaps the desired solution would be no memory at all, so it always turns on at a specific level. This might be do-able, and I’ve been trying to leave room for a memory option, but I haven’t thought of a way to fit it into the UI yet… at least, not a way that I’m happy with.

goshdogit
goshdogit's picture
Online
Last seen: 14 min 20 sec ago
Joined: 12/03/2015 - 21:28
Posts: 402

ToyKeeper wrote:
I pushed an update with dual-switch support. It costs 172 bytes, if enabled at compile time, mostly due to bringing in wear-levelling functions.
Wow, you work quickly! You’re spoiling me. Party

ToyKeeper wrote:
The current method goes to the memorized level at boot, unless the e-switch is held. Then it goes to moon instead. (er, the bottom of the current ramp, whatever level that is, so it varies per-ramp)
Very nice! I’m gonna update my dual-switch light right now.
ToyKeeper
ToyKeeper's picture
Offline
Last seen: 11 hours 13 sec ago
Joined: 01/12/2013 - 14:40
Posts: 6400
Location: (469219) 2016 HO3
goshdogit wrote:
Wow, you work quickly!

Are you familiar with how the wizard character class works in D&D?

Every morning, they prepare their spells. Specifically, they take a guess at what spells they’ll need that day, and then they prepare each one. They cast 99% of each spell, leaving off only the last word or two, so that later in the day they can speak a few syllables and cause something big to happen.

FSM is the first 99% of a bunch of spells, leaving only the last little bit to be completed.

Agro
Offline
Last seen: 6 hours 52 min ago
Joined: 05/14/2017 - 11:16
Posts: 903
Location: Ślōnsk
ToyKeeper wrote:
Agro wrote:
1. How about clearing mode memory on lockout? You do this on physical lockout already and doing the same on software one seems logical. After all if I lock it out, I will probably not use it in a moment. 2. Independently, time-related functions need to increase power consumption only when they are running. So when mode memory is cleared, you can go back to deep sleep.

Personally, I like having memory after lockout. If anything, I’d prefer to make it time-related, not lockout-related.

As for time-related forgetting, I’d probably want to set the time to something pretty long, like a few hours. I haven’t tried the half-sleep mode yet to find out how much power it uses, but hopefully it’s not much.

I get the impression that perhaps the desired solution would be no memory at all, so it always turns on at a specific level. This might be do-able, and I’ve been trying to leave room for a memory option, but I haven’t thought of a way to fit it into the UI yet… at least, not a way that I’m happy with.


Personally, I desire memory for very short periods, like a minute or two.
I stop by the trail, turn off the light, empty my bladder, turn the light on.
Other than this…I’m yet to find use for it.
I did some searching on how others use it….I’m surprised I can’t find anything useful really. There are many comments where people just state that they like mode memory or not. Some say that they use it to make sure the light starts on low. The only other that I found was:
Quote:
On a flashlight I usually have a preferred mode that runs 90% of the time and it is nice not to have to switch to that mode every single time you turn on the light.

But this is a workaround for not having a configurable default mode and mode memory is ill-suited for the task.
ToyKeeper
ToyKeeper's picture
Offline
Last seen: 11 hours 13 sec ago
Joined: 01/12/2013 - 14:40
Posts: 6400
Location: (469219) 2016 HO3
Agro wrote:
I desire memory for very short periods, like a minute or two.

I forget; do you have firmware flashing tools? If not, it might be a good idea to get some. I think you would probably enjoy being able to tweak behavior exactly how you like it. At minimum, it would give you access to change compile-time options, but you could probably make deeper changes too.

It’s not something I recommend for everyone, but I think you’re probably serious enough about lights to get some benefit from it.

Agro
Offline
Last seen: 6 hours 52 min ago
Joined: 05/14/2017 - 11:16
Posts: 903
Location: Ślōnsk
ToyKeeper wrote:
Agro wrote:
I desire memory for very short periods, like a minute or two.

I forget; do you have firmware flashing tools? If not, it might be a good idea to get some. I think you would probably enjoy being able to tweak behavior exactly how you like it. At minimum, it would give you access to change compile-time options, but you could probably make deeper changes too.

It’s not something I recommend for everyone, but I think you’re probably serious enough about lights to get some benefit from it.


They are on the way.
goshdogit
goshdogit's picture
Online
Last seen: 14 min 20 sec ago
Joined: 12/03/2015 - 21:28
Posts: 402

ToyKeeper wrote:
FSM is the first 99% of a bunch of spells, leaving only the last little bit to be completed.
Big Smile

I went for a two hour hike last night with a friend and five flashlights running Andúril. Two Q8s, Emisar D1, Emisar D4, and EagleEye X6R.

My friend was very impressed with the Q8 and got the hang of ramping very quickly. It was fun to keep handing him lights to try without needing to explain a different UI with each one.

I set the ramp ceilings to turbo-1 for all but the D4, which I set to turbo-55. He ramped the D4 to the ceiling and said, “Wow!” I told him to double-click and he about fell over. LOL

Is there a way to set Andúril’s ramp ceiling to turbo, or is turbo-1 the max value? Would this be a compile-only option? What if the ramp value was set to ‘turbo-(N-1)’ instead of ‘turbo-N’ when using ramp config? Must ramp ceiling and turbo remain non-equal?

BTW, dual-switch support seems to work great. I really like the ‘hold e-switch and click tailswitch’ to override memory.

ZozzV6
ZozzV6's picture
Offline
Last seen: 29 min 33 sec ago
Joined: 03/24/2016 - 12:19
Posts: 996
Location: Near to my soldering iron.

I find this Andúril more and more interesting. I need to build a triple or quad X6R and try it in that. Or in my Q8 if it ever reach me from china. Ordered it in the first 100 and I’m just waiting and waiting patient.

ToyKeeper
ToyKeeper's picture
Offline
Last seen: 11 hours 13 sec ago
Joined: 01/12/2013 - 14:40
Posts: 6400
Location: (469219) 2016 HO3
goshdogit wrote:
Is there a way to set Andúril’s ramp ceiling to turbo, or is turbo-1 the max value? Would this be a compile-only option? What if the ramp value was set to ‘turbo-(N-1)’ instead of ‘turbo-N’ when using ramp config? Must ramp ceiling and turbo remain non-equal?

It already does “turbo – (N-1)”… or, more specifically, “151 – N”. I should probably update the UI diagram to make that more clear.

To check whether the ceiling is set to turbo or if it’s lower, double-click from off, then double-click again. If it goes up, they weren’t equal. Smile

goshdogit
goshdogit's picture
Online
Last seen: 14 min 20 sec ago
Joined: 12/03/2015 - 21:28
Posts: 402

ToyKeeper wrote:
It already does “turbo – (N-1)”… or, more specifically, “151 – N”. I should probably update the UI diagram to make that more clear.

To check whether the ceiling is set to turbo or if it’s lower, double-click from off, then double-click again. If it goes up, they weren’t equal. Smile

Got it! I was worried about missing out on that one last ramp level. Big Smile

BTW, your UI diagrams are works of art in their own right.

ToyKeeper
ToyKeeper's picture
Offline
Last seen: 11 hours 13 sec ago
Joined: 01/12/2013 - 14:40
Posts: 6400
Location: (469219) 2016 HO3
goshdogit wrote:
your UI diagrams

I need to stop adding things… I have no idea how to fit them into the diagram! Smile

Specifically, muggle mode. It’ll probably need a whole new section, but there’s no space left on the page.

I’m thinking 6 clicks from off to enter muggle mode, or 6 clicks from ramp to enter muggle config mode. Settings include floor and ceiling levels only. Will probably default to floor=15/150 (~7 lm) and ceiling=100/150 (25% power). Ish. Not sure if I’ll try to fit a 4-bar battcheck mode into it or if it’ll be limited to just ramping.

goshdogit
goshdogit's picture
Online
Last seen: 14 min 20 sec ago
Joined: 12/03/2015 - 21:28
Posts: 402

ToyKeeper wrote:
I’m thinking 6 clicks from off to enter muggle mode, or 6 clicks from ramp to enter muggle config mode. Settings include floor and ceiling levels only. Will probably default to floor=15/150 (~7 lm) and ceiling=100/150 (25% power). Ish.
This sounds great! No turbo for muggles, right?

I vote to omit battery check, or make it a compile-time option. I can already hear my button-mashing friends… “WHY’S IT BLINKING?!” Facepalm

Speaking of muggles, it seems the first thing they do when I hand them a new light is unscrew the tailcap to look at the battery. I’ll have to let them get that over with before I enable muggle mode. Big Smile

joechina
Offline
Last seen: 15 hours 9 min ago
Joined: 03/05/2016 - 08:23
Posts: 561
ToyKeeper wrote:
goshdogit wrote:
your UI diagrams

I need to stop adding things… I have no idea how to fit them into the diagram! Smile

Specifically, muggle mode. It’ll probably need a whole new section, but there’s no space left on the page.

I know this, I have the same problem with Tom and the NarsilM cheat sheet. Smile

goshdogit
goshdogit's picture
Online
Last seen: 14 min 20 sec ago
Joined: 12/03/2015 - 21:28
Posts: 402

TK, I’d like to shorten (nearly eliminate) the delay before ramping when holding the switch from off. I want ramping to start almost immediately.

I poked around in several of the .c and .h files but couldn’t determine where I should make changes.

Could you point me to the code I would need to modify to accomplish this? Thanks!

Pages