E-switch UI Development / FSM

What would it take to support the Schoki’s MP3431 driver ?

That depends… FSM can technically run on tiny25, but only just barely. It really needs tiny45 before it can do much at all, or tiny85 if you want something fancy like Anduril. And for that, things aren’t looking good:

Older e-switch code had a smaller base footprint but used more space for each feature. It could be approximated with something like “500 bytes base + 500 bytes per feature”. FSM has a bigger footprint but makes additions significantly smaller, like “3000 bytes base + 100 bytes per feature”. Or something along those lines, anyway.

I guess, to add support, what it would take is a bigger version of the driver with a bigger MCU, preferably SOIC8 (though reflashing pogo pads or holes would work too). It could be tiny85 or tiny1634 like Mike C uses, or tiny841, for the easiest options. For tiny1616/1617 things get more difficult, and for non-AVR options things also get more difficult.

Actually now the design uses a 4x4 MCU and ATTiny85 should fit.
I wonder about the OTSM discussion that I don’t understand… :blush:

Oh, if it has tiny85 now, then I just need a driver with flashing pads/vias or SOIC8, and I could add support for it fairly easily — some way to reflash without soldering. Not necessarily for production use; just for development purposes.

As for code… I don’t know what the pinouts are, but I’d need to add a driver layout definition and probably adjust the ramp tables. Maybe change a bit of init code. And it may also need new code to measure voltage. I seem to recall some discussion about that, and I don’t know if it was ever resolved. So battcheck and LVP might not work, depending on whether there’s a way to measure the battery voltage.

The OTSM stuff is irrelevant for FSM, and for e-switch lights in general.

FSM-based apps shouldn’t need any changes, or should need only very small changes. Mostly they should “just work” after the base library gets support for the new driver. Change one line per app to select a different driver type, and maybe update anything driver-specific it does (if there is anything).

Overall, porting should be relatively easy. That’s half the point of abstacting out the hardware layer and separating it from the UI code.

Glad to read that. :slight_smile:

I flashed my driver with anduril firmware and I really like it. I have some questions:

  1. Is there a way to turn off the thermal stepdown?
  2. Can you add brighter, dimmer option to the tactical strobe?

1. Disable USE_THERMAL_REGULATION at compile time. (should compile, but is untested)

2. Perhaps. It wouldn’t be difficult. Not sure if it’s a thing many people want though; usually tactical strobes only go at the maximum brightness. On small high-powered lights this risks overheating though, so it’d probably be a good idea to lower it for those or make it configurable.

On my Q8 with Andúril sometimes in the momentary tactical mode it leave the main led on after a few presses. I didn’t know the exact press combination but playing with it and somtimes it stays on. And once I got in ramping stuck in one level and no button presses helped just when I disconnected power.

I still need to tweak the debouncing and event detection a little more, to handle extra-noisy switches. It mostly works, but can run into some weirdness when the switch bounces for an unusually long time. It’s a bit difficult to test though, since I haven’t found any really-noisy switches to test with.

Maybe I can find a noisy switch somewhere in my drawers of parts.

A scope would help too, so I could measure this stuff instead of guessing. I usually do pretty well at programming blind, but it sure is helpful to have data to work with instead of just theories.

I installed Anduril on Q8 and on tactical mode I can get it stuck switched on with the switch released just like ZozzV6 mentioned earlier.

Also there is slight delay when switching the light off. Is it there because of ramp down UI (click, click&hold)? Is it waiting second click&hold? The delay is a bit too long for my liking.

I like lightning mode. Thank you ToyKeeper!

Now I am waiting impatiently for candle mode. Googling for “led candle flicker algorithm” shows up some interesting results.

The delay is because it’s waiting to see if you’re going to click again for a double/triple click. The timing of that can be changed by re-defining RELEASE_TIMEOUT. The default value is 24 frames.

The delay can also be eliminated entirely by mapping the “off” action to EV_click1_release instead of EV_click1_complete (a.k.a. EV_1click), but this will interfere with detecting double clicks. So you’d need to have a “turn emitters off” action on button release, followed by a “go to ‘off’ state” action after the timeout happens. This should be safe, but has the side effect of making it briefly blink off after the first click, even when “off” isn’t the action you were intending.

I’m not completely happy with candle mode yet, but here’s an example graph of its output:

Mostly, it seems a bit too spastic when used at low levels, and perhaps a bit too spastic overall. It’s like a candle in a breezy environment. Perhaps I should change it from free-running waves to fading waves triggered by random disturbances. Or maybe just decrease the amplitude on the mid-frequency oscillator. Or maybe make the mid oscillator fade and refresh at random. It’ll take some experimenting. It already does a random sample-and-hold modulation on the mid oscillator frequency, which helps, but it feels like it needs further adjustments.

In another thread, ‘stephenk’ mentioned that an adjustable strobe frequency is useful for light painting.

I suggested he look into Andúril, with its adjustable-frequency ‘Party Strobe’ and ‘Tactical Strobe’ modes.

He then mentioned that a momentary strobe would also be useful.

Could Andúril’s momentary mode also work with strobe modes? If not officially supported, could it be a compile-time option?

Momentary strobe? That’s not a thing I’ve considered.

I added it as a “TODO” note in the code, but I don’t have any plans to add it in upcoming production lights. I suspect that my rainbow saber thing may be more relevant for light painting anyway, since it’s specifically designed to make pretty patterns in the air while swinging a lighted sword. It does whatever patterns the user tells it to, and has a full color palette to work with. This includes a momentary “overdrive” function, which could potentially be configured in a manner similar to what he might want.

Hmm, I just tried it by turning the brightness down all the way on a police flasher mode, hoping that it’d become momentary-only so it only lights up in overdrive. However, the brightness mod is additive instead of subtractive, so it still flashes while idle — just not as bright. Overdrive works fine, but the non-overdrive isn’t dark like I had hoped. This could be fixed by making it subtractive, but I’m not sure if that’d be a good idea outside of this momentary thing.

I’m a bit late here, but I’d like to add my two cents. First of all, you’re 100% correct that it’s impossible to create, test, and host dozens of .hex files for every hardware configuration out there. However, I do think there is good demand for an alternative to NarsilM on TA drivers. Perhaps we could talk you in to creating one “master” triple-channel.c file, a la Bistro Tripledown? You’ve made it easy enough for all of us to utilize your /bin/ files for things like ramping table calculation, etc. I’m proficient enough in C and Python to write basic programs and edit your (very well-commented) code, but I have no clue where to start when it comes to adding a third power channel.

In this case, the only change necessary to support popular hardware is to uncomment one line at the top of the file.

// Physical driver type
//#define FSM_BLF_Q8_DRIVER
//#define FSM_FW3A_DRIVER

There’s a good chance the TA drivers would work with the FW3A options.

However, adding a new driver type is a bit more tricky.

At the moment, the moon-in-lockout checks the floor for both ramps and uses whichever is lower. This makes the behavior consistent regardless of which ramp is active, but it can also make moon too low sometimes. Do people think it should instead use the current ramp floor instead of checking both? This would effectively give it the ability to change the lockout brightness by switching between ramps, perhaps with a day mode and a night mode, but it might also lead to surprises if the user forgets which ramp is active.

I think I’d prefer it use the current ramp’s floor.

I haven’t reflashed Andúril in a while. I’ve been waiting for Candlelight Mode to be perfected. :partying_face:

Has Muggle Mode been implemented? Does lockout work in Muggle Mode? I like the thought of being able to teach muggles the importance of lockout, both software- and hardware-based.

Ah, been a bit distracted by holiday stuff and fixing FW3A issues, so candle mode hasn’t changed.

Muggle mode is implemented but not published yet. There hasn’t been much consensus about how that should look, so for now it’s a simple latching on/off at 1x7135 (~150 lm) with no bells or whistles. I haven’t even made it dim for LVP yet, though I probably should. For now, it just turns off.

How hard would be to do this:
only one mode (100%), it works while you hold down the e-switch, shuts off when you let go the e-switch. Driver is nanjg 105C?

Need this for diving light that had magnetic switch and driver died so I thought to use regular nanjg 105c and replace e-switch with reed magnetic switch!

Siruis9, that should be fairly easy but it’ll need to use something smaller as a code base. The FSM library doesn’t fit onto attiny13 like the nanjg driver uses. I’d suggest using STAR_momentary or Ferrero Rocher as a base, and basically just stripping out features until it’s a one-mode momentary interface.