Finally got around to trying this. Used Win10 on the work laptop since I don’t have an android phone and don’t feel like installing Xcode or homebrew on the iMac.
Two verification fail errors using reading glasses and pushing halfway down. Then, using the Optivisor and pushing all the way down on the pogo pins: success. Yay.
Not sure if I did the factory reset properly. Held it down waiting for a flash, but it did a bunch of things and I just kept holding it down until a few seconds after it stopped doing anything different. I hadn’t changed it from defaults apart from aux settings. Those reset, so I guess it all did.
How to do thermal config? Tried the diagram and could get into config mode but failed at setting anything properly. Haven’t played with anything but Zebralights for a long time now. I use the FW3A more than my 3 Emisar D4, but in only the most basic way. The D4V2 has spent the last months in aux high blue mode on top of a clear plastic decoration. It is very pretty. I have the D4S, with cyan aux LEDs on the other side of the decoration. Even prettier. Before that, I mostly used the D4V2 in candle mode with an hour timer to go to sleep. Beautiful, but now I seem to have a large collection of LED candles vs just the one, so not so much need.
Now I see there’s a D4SV2, along with a FW21 I just ordered (bah, no 3000 or 4000K option). Lovely.
So, anyway, had to dig up the text manual for Anduril and now I get it. Wonderful, no more bug in a mode I never use, but since I waited so long I get … some other fixes. And satisfaction. I’ve been playing a lot with an Arduino Mega and the much nicer ESP32 (built in WiFi!) but command line is a bit more hardcore than the Arduino IDE. There is a GUI for avrdude but I haven’t played with it. I’d kinda like to flash my two D4 to Anduril but I’m not taking them apart to get to the chip.
The D4S has pads in a different arrangement I think. And I have no idea if it is D4 type or Anduril type interface. Probably will leave it alone unless I could buy a set of pogos (or a kit thereof) that fit it.
Anyway, thanks to all involved. Cool light, and had fun with the little bit of effort it took to reprogram it.
For anyone else, here’s the bit of instructions I need that wasn’t in this thread (or I didn’t see it):
Every config mode has the same interface. The menu has one or more
options the user can configure, and it will go through them in order.
For each menu item, the light will follow the same pattern:
- Blink one or more times, corresponding to the item number.
- Stutter or “buzz” quickly between two brightness levels for a few
seconds. This indicates that the user can click one or more times
to enter a number. It will keep buzzing until the user stops
clicking, so there is no need to hurry.
- Pause, and then go to the next option.
After the light has gone through all of the menu options, it should
return to whatever mode the light was in before entering the config
mode.
If the user doesn’t press a button during a menu item’s “buzz” phase,
that item remains unchanged from its previous value.