About a 3000K+5000K mix, thatâd probably be do-able but would require some redesigning. The driver is going to have two channels regardless, whether thatâs for low and high power or warm and cool CCT. But in the latter case itâll need two equal sets of 7135 chips, a new MCPCB, and the firmware will need some significant changes.
If a second button is used, it would need even more changes, including the host design, and Iâll definitely need some 2-switch hardware to use for firmware development. It could maybe be something like one switch for regular controls, one switch strictly to control color temperature. I have a mechanism in FSM which allows input events to âfall throughâ top layers where theyâll be handled by lower layers, which would make it pretty easy to make the two buttons completely independent of each other regardless of which mode the light is in. The second button would just fall through to something which handles tint changes.
Color change functionality could still be done on only one button though. Itâs mostly just a matter of how to map it into the UI, and what (if anything) to remove to make room. Like, maybe in regular output mode, âclick, click, holdâ, which is currently unused, could be used to ramp back and forth between tints. And then itâd apply globally to all modes. Or that could fall through as described earlier, so thereâd be a single action for tint changes which applies to all* modes.
* âClick, click, holdâ is already used during the âoffâ state and âlockoutâ state, so those mappings would collide. Also, all mappings are used in âmomentaryâ mode, so tint adjustments would not work there either. It would otherwise be global though.
Oh, um, also, going from two LEDs to four will probably increase the price a bit. But since XP-L isnât really necessary, that helps. XP-G2/3 or Nichia 219c costs less than XP-L.