The easiest methods are:
- Factory reset (default tint is 50% or ~4000K).
- Or turn the light down to moon level before changing the tint. The tint resolution is very low at that level, so it’s easy to see when it crosses a boundary like 50%.
No need to remove it. If the user configures a lower ceiling, the true maximum will still be available as a “turbo” mode. By default though, the ceiling is set to maximum so it doesn’t have an additional turbo above that.
The default floor for smooth ramp is level 1 of the 150 total steps.
If I understand correctly, there were too many cooks in the kitchen, or coordination was difficult due to time zones, or something like that… so they decided to do it on their own instead. We probably just had too many people in the private thread where the process was being worked out.
Ever tried to get an international project done on an entirely volunteer basis?
Some parts will be messy. And that’s okay. So far it looks like things are turning out pretty well, with only minor details not completely sorted out before the first batch.
It’s pretty common for generic manuals to be written for an entire product line, without going into detail about what is different about each one. That’s basically where things started… just a normal average manual. But people wanted to make it better, and they did. You were a part of that, and it’s very much appreciated. You helped improve it from average to uncommonly good. Thanks!
Translations are almost always difficult and incomplete or inaccurate, even with extensive tools to help, like an i18n library and a string translation database. This project didn’t have those tools, but has done pretty well regardless.
It’s a moving target, a rolling stone. The firmware runs on dozens of different lights and changes over time as development continues. However, the lantern has been classified as a “stable” build target for months, so it was ready a long time ago. Everything since than has simply been upgrades.
For example, people wanted some light painting features on the FW3A, so I added it. And now, woot, the lantern has light-painting functions. It’s kind of silly, but it’s there. A couple lights were having physical difficulties with stuck buttons, and I added some extra safety features related to that. So now the lantern has stuck-button protection. Etcetera. It’ll keep getting updates over time, because that is the nature of software.
It works with the HQ Universal ProgKey pogo pin adapter, and it might also work with a standard SOIC8 clip. The clip method remains to be seen though, since the wiring inside changed since the last prototype I saw, and I’m not sure if the wires are still long enough to pop the driver out that far.
The Q8’s driver was easy to reflash with a SOIC8 clip and a small screwdriver… no soldering required. And the lantern is based on the Q8. But we probably won’t know until production units arrive if the wires are long enough for that. Regardless, the HQ ProgKey is far more convenient aside from having to build the key first.