I was hoping there was an existing preference I could modify?
fwiw, Ive heard there is no Thermal Regulation on Blinkies, but I seldom use most of them…
I read about one guy that set Candle Mode to Maximum, plus he installed a Diffuser, and left the light tailstanding (so he could not tell it was getting hot).
The shrink wrap on the battery melted, and he burned his hand when he reached for the light… so maybe for someone like that, Thermal Regulation might have reduced the risk.
I occasionally use Bicycle mode, and if I do not use too high a brightness, only one LED turns on, so that is pretty much OK w me. If there is no existing option to prevent both LEDs from coming on, it is not a big enough concern for me to ask you to build a custom Hex for me.
I dont use party nor tactical strobes, so the fact they use both LEDs is not a big concern. The lack of Thermal Regulation for blinkies is not a big concern for me either, but it presents a risk that might benefit from some coding change, for some people…
Maybe it is just as well that Bicycle mode only uses both LEDs above a certain output. I might just consider it a safe limit, in terms of Heat, not to turn the Bike flasher up so high that both LEDs come on…
As to my original befuddlement, as to why Both LEDs turn on above the 130 ceiling… well, if there is no available option I can change without need for a custom hex… its OK… I dont actually need the ceiling to be higher than 130/150…
I was mostly just asking if there is an existing option that I have overlooked, that would prevent both LEDs from turning on, in any dual channel mode, when Turbo is disabled.
Thanks… I have disabled Turbo, but that does not prevent both channels from coming on above ceiling 130…
anyway, thanks for confirming that turning off Turbo, does not prevent both channels turning on if ceiling is above 130.
Not that I know, but perhaps there is something in the latest multi-channel branch (@ToyKeeper is adding features to it all the time), and even if there isn’t yet, I think it would be good that she hears about your need so she can consider it or otherwise tell us why it’s not a good idea
The reason why the other LED turns on at turbo is because you’re in a channel mode with “max 200%” power. It does that because people specifically wanted it to work that way.
To fix it, use a channel mode which stops at “100%” power. This is the default when using a newer version of the emisar-2ch build, so an update would fix it.
I recall you’ve been avoiding updates because you want 3H to change the active LED instead of 3C, but the newer version can do that too. Or you could make some small code changes to do it instead. Either way works. But what doesn’t work is the old version, because it doesn’t have a “max 100% power” ramp. You’re kinda out of luck unless you flash new firmware.
That part of the code was written when attiny85 was the only supported MCU, and there wasn’t any ROM left to add more thermal regulation code. Also, the gradual brightness adjustments it relies on for thermal regulation in ramp mode … are incompatible with blinkies and strobes. So it’d need one or more new mechanisms instead, which would each be a pain to get working.
But I supposed it’ll need to happen eventually… and newer MCUs have the space needed for it.
