Perhaps.
For now, it just syncs the indicator to the main emitters. An option to control what it does during use would be a good idea though, since “stay off” seems to be a pretty common thing people want. Not sure where to put it though, unless I add another explicit config mode somewhere.
I haven’t done it yet, but it looks like the Q8 needs a different ramp than the D4. I was hoping they’d be close enough to use the same values, but the ramp on my Q8 looks pretty not-linear with FSM. The mid-ramp elbow is pretty noticeable. I did at least make it use a different voltage adjustment factor for Q8 though, so battcheck should be closer to accurate.
I also need to fix thermal regulation again, since the last time I tried it on a D4 I got weird results. It’s probably okay on a Q8 due to its extra mass, but that needs testing too.
There’s also the blinking indicator thing to add, and maybe an alarm clock function, which both need a half-sleep mode. And perhaps a goodnight config mode. Maybe change “goodnight” to “sunset”, and “alarm clock” to “sunrise”. And perhaps a super-simple muggle mode (and muggle config mode to set safe limits).
With all that, I might actually run out of space. It still has about 1000 bytes left, but space is definitely starting to become a concern. Maybe I can refactor the existing config modes into a single common function — same UI but smaller code.
Kinda just thinking out loud here.
Oh, and one of Dale’s Q8s was acting up; sounds like an extra-noisy switch or something. That could probably use some attention. I have some theories, but can’t test them with my hardware because it’s not misbehaving that way.
And I was doing some “bump testing” to see how the Q8 reacts to being hit during use, and a couple times I managed to get it into a state where it wouldn’t respond… and afterward once it acted like eeprom had gotten slightly corrupted (it had an invalid ramp floor setting, which made a couple things act weird). Not sure what I can do about that.