If I understand correctly, what I have is the first production run. The second batch, I think, will have some firmware updates based on what I’m doing.
It’s pretty nice, but in the first batch you should manage the temperature yourself instead of relying on the built-in thermal protection.
I don’t expect a driver retaining ring. It would make the light longer.
Normally I’d be more upset about the driver glue, but it wasn’t difficult to remove and didn’t really make modding any harder in this case.
The switch PCB is not easily accessible. I haven’t attempted to remove it. However, if you do manage to get it out, the driver already has an unused pad to control an indicator LED. This makes it compatible with Narsil’s indicator features.
If I understand correctly, that’s what I’m doing?
I’m calibrating it for this specific host, but I plan to try it on a SRK and a Convoy triple too… the idea is to update bistro and crescendo with the same algorithm, and maybe Narsil if Tom is okay with that. If things go well, it shouldn’t need much (or any) modification to work in different lights, but that might be overly optimistic. It does at least adjust proportional to the rate of change though, so it will react slower on lights with less power or more thermal mass.
Anyway, I’m not done yet. I hope I can get it to produce a nearly-flat runtime graph for the whole life of the battery, aside from the initial hot peak. It looks promising so far… like, on that last graph, I changed hands to give it a fresh heat sink, and about 15 seconds later it stepped up a bit.
It’ll be interesting to try this underwater, or touch it with ice mid-test.
Oh, also, tiny85 chips don’t use a calibrated sensor. They vary by at least 10 C between individual pieces. So I think I need to convert that thermal toggle function into a thermal calibration function like in bistro.