For my LT1 I’m tempted to find all the places the ramp levels are referred to as 8bit, swap those to 10 or even 16 bit, speed up the ramping, and add in a 1000 step ramp to really smooth it out. I’m worried that we’re nearing the memory capacity of the attiny85 though
Oh yeah, definitely. I'm surprised you got a 250-step ramp table in there, did you disable anything else? Especially with PWM levels >8 bit every ramp level requires two bytes of flash...
Calculations are done with two bytes in the integer domain. 255 minutes are 15300 seconds. Ramp table has a length of 150 entries. 15300*150=2295000. 32 bit calculations need a lot of additional memory. And because we have no floating point operations we can’t calculate the ratio beforehand.
I just meant that instead of counting down minutes (like the original code does) one should count down seconds, to be able to use every step available in the ramp table in the first place. Getting values in between ramp table steps is a different beast again of course...
Is it feasible at all to maybe include a transfer function in the code instead of a large (250ish steps) ramp table and calculate the needed PWM levels on the fly?
That’s what I meant as well. Using a single calculation with seconds overflows 16 bit and can’t be calculated easily. But one could manage just a single 16 bit counter for seconds and split it into minutes and seconds if required.
Doesn’t make sense when other firmware don’t behave like that though. Take the Sofirn SP36 with NarsilM for example, it steps down at it’s set temp and the BLF Anduril version doesn’t. Then there’s the Astrolux MF02S V2 with SBT90.2 where my thermal gun reads the same temp, more or less, as it shows in the manual. That light gets hot quick with a 30 sec step down
You did well coding NarsilM, if it had stepped ramping instead of mode sets, it would have been perfect.
Hhmm, yeah - actually I started converting NarsilM to stepped ramping but punted on it because I started my own improvements to Anduril. Actually one of the really big reasons why I stopped NarsilM mods was to see TK adopt some of my prefs:
- voltage calib in the UI -- this really really bugged me having to do it at compile time
- a quicker acting OFF -- NarsilM had a quick off but suffered from the dbl click flicker with the first click
- having temp display immediately follow voltage reading
I'm sure there's more, can't think of them all.
Not sure if this will stir up things but I wonder if TK or anyone else were open for some food for thought in terms of changes on Andúril 2:
- Advanced UI: Revert turbo mode activation to the classic Andúril 1 style (2C from ON = Turbo, level 150) as the new style (2C+2C from ON) seems to bug many people.
- Simple UI: No offense but I wonder if anyone here has really used Simple UI as it is yet. How about exchanging Simple UI by a "stripped-down" UI that follows both the essential functionalities of Andúril Advanced UI but also includes some of the best parts that we know and like from proprietary "classic" UIs such as Wurkkos FC11 or Sofirn SP33 V3? With the new AVR-1 chips like 1616-MNR there would be enough memory for two individual UIs that are both based upon the FSM code. BTW: Thermal calibration could become obsolete as these next gen chips have factory calibration. @TK: gchart has made some cool tests with this chip already (see our PM discussion about the "BLF SP10S project").
Example:
I see some benefits here: Users who like a very basic and straightforward UI can remain in this new Simple UI, e.g. ramping mode for default. Classic stepped modes could be accessed by 10C. Most commands could follow the usual Andúril style. Maybe 7C for cycling AUX/switch button illumination can be incorporated here as well. According to some feedback I have gathered in the past months it seems that many people like the basic UI that Wurkkos FC11 or Sofirn SP33 V3 offer. With some hidden command it could be possible to change the UI and switch from this Simple UI to the actual Andúril 2 UI (with Advanced UI only). Since both UIs are based upon the same code, updating or bug fixing should cause a few more efforts only. Manufacturers on the other hand could reach much more customers by offering their flashlights to both less experienced and well experienced people.
- I do not know if this was feasible but with more and more flashlights using constant current regulation (see Fireflies E12R/T9R/T1R/NOV-Mu, Astrolux MF02S V2, Noctigon K9.3, ...) it would be nice to set ramped modes not according to a brightness level (n of 150) but according to certain currents, e.g. 0.01A (moonlight), 0.5A (low), 1.5A (mid), 6A (high) and no limit for full direct drive (FET). I saw that Neven's (Led4Power) new driver generation will support this cool feature.
I like the 1st and 3rd items! I don't use simple mode, but I think this is better. The problem is I think TK targeted Simple mode to not have turbo capability, based on the popular over amped, small lights like a D4V2 for example, and keeping it safe for anyone to pick it up and use. But for lights like the K1 running a 5 amp max turbo, it makes no sense whatsoever.
Tom E : It still makes no sense not having access to a Turbo you can enable, when max ramp can be increased to max.
Many users already dislike this and have stated it would be the ideal firmware if Simple UI had Turbo
TK does a great job, but this makes no sense whatsoever
They would have to leave simple mode to configure max ramp to turbo, no? As long as it is reasonably hard to stumble into configuration mode, II is ok. I wouldn’t use simple mode.
Yes, you have to first access Advanced UI to change the max ramp, so no idea why you can’t have a setting to enable Turbo……very strange.
I never use any of the Anduril modes apart from smooth ramping, with battery check. Quite a few have stated this, even most who run 1lumen reviews. I feel that trying to make a flashlight do everything has ruined it
I’ve never really understood this point of view.
The additional modes aren’t in the way. If you don’t want or need them, simply don’t use them. Or just don’t use Anduril lights. Luckily there are many different lights available with various UIs for you to choose from.
Many people do use and enjoy the things that Anduril has to offer. It’s impossible to appease everybody.
What you’re discussing here is not about Anduril, it’s about a different UI. Anduril is not the only UI of the world. If you don’t like it or if you want something different, write your own UI. It’s base, the FSM framework, is open source so that lots of work is already done for you.
I think what LP laid out has turbo accessible in Simple, both modes of Simple. This is how I read it, I think??
I have not used Anduril-2, but have carefully read the manual and have the following question:
When at a low brightness level using the Advanced UI of Anduril-2, if I "double-click" to "Ceiling" and then "double-click" to "Turbo"; what happens when I "double-click again", do I go back to "Ceiling" or to the previous low brightness level and does the current "Memory Type" (Automatic, Manual, or Hybrid) affect this "double-click again" behavior?
Having to "double-click" twice to get to Turbo" from a low brightness level is only slightly inconvenient, but losing the ability to "double-click back from Turbo" to the previously preferred low brightness level would be very inconvenient since I would then need to re-adjust the brightness level.
The "double-click" shortcuts for "Turbo and back again to low brightness" are my favorite and probably most used operations on Anduril-1 where I check something out for only an instant when I walk my light (I don't have a dog to walk).
I use both ramped and stepped modes and appreciate having the choice to change between the two and sometimes prefer stepped mode, especially when comparing lights.
When I have two or more of the same light, I use stepped mode to compare the LED tint and tint shift at different stepped brightness levels (sometimes there is a noticeable difference) and also to simultaneously compare the brightness levels using different types of batteries (to compare the batteries) or while using the same battery at different voltages (to better understand the light's characteristics).
I also use Anduril stepped mode when comparing two different lights, or two of the same lights with different LED types. When the lights are not the identical, the stepped brightness levels may not be similar but at least they are consistent and reproducible for comparison.
Smooth and stepped ramping then.
Well, Sofirn & Mateminco never used to use Anduril and as a store they’re great bang for buck, it’s kind of ruined it now Anduril is pushed everywhere
Even if I make a note on the product about Anduril, I can’t stop someone buying something and then requesting a return.
This is besides the point though, add an option to enable Turbo on Simple UI and I’d be one happy chappie
Then stop selling lights with Anduril. Seems like nobody wants it. Or write your own firmware and sell the lights as a special edition. Problem solved.
I’m not the only one that has a request for this