Hi, I just checked with Emisar D2, running the lastest release 2023-12-03, and all is working as displayed on the diagram. From ON, 10H leads to Ramp Extras Config (for Advanced UI), with 4 Turbo style setting. From ON, for 7H there is no 4 Turbo style setting. From OFF, 10H leads to config Simple UI, and there is 4 Turbo setting (for Simple UI). There is no redundant Turbo style setting, as one is for Advanced UI, and the other is for Simple UI.

Maybe some confusion is caused because both 7H from ON (config current ramp) as well as 10H from OFF (config Simple UI) lead to Ramp Config, but this way, some space can be saved on the diagram page layout, because there is no need to display two separate Ramp Config textboxes. In Ramp Config, after 4 Turbo style setting, in the diagram (only 10H) is displayed, indicating that this setting is only for config Simple UI, 10H from OFF.

I am hopeful that this addresses the issue, and may have clarified things. :)

Great, thank you!

Apart from the “smooth steps”, there has since been one more material change: the channel mode for the strobe modes is now individually saved per strobe mode. This allows to set a different channel mode for each suitable strobe mode.

This change was introduced with revision 753, 2023-08-24, and documented in the text manual with revision 783, 2023-10-12.

I have checked with Emisar D2, running ToyKeeper’s latest release, anduril.2023-10-01.emisar-2ch.hex, and indeed, the channel mode is saved per strobe mode. So this is working.

This would be an addition to the Advanced UI diagram: “saved per strobe mode” could be added in Strobe Modes Actions 3C, which could then for example read 3C: Next channel mode (except Police Strobe), saved per strobe mode.

In addition, here comes a slight detail for consistency in the Advanced UI diagram: in Blinky/Utility Modes, it should maybe read Thermal Config instead of currently Thermal Configuration, as everywhere else in the diagram, it reads Config.

Awesome! (and nothing silly here) :-)

Idea for the initial post (showing on top): Maybe it would be useful to also have the diagram (PNG) for Simple UI show up? As far as I can tell, there is one image that can function as a thumbnail at the very top (should probably just stay the Advanced UI PNG, as presently), but maybe in the text below, either the Simple UI PNG or both, Advanced UI PNG and Simple UI PNG, could be displayed (displaying both underneath each other would show them together and make clear that they belong together; and Anduril novices might want to start off with the Simple UI diagram and could see that one right away). This way, the Simple UI diagram would get more and immediate attention as well.

Hi, multi-channel Emisar D2 user here, Model number 0135, emisar-2ch, using ToyKeeper’s latest Anduril 2 version, anduril.2023-08-07.emisar-2ch.hex: At my end, momentary turbo 3H/4H works just fine and as expected, so I do not have the same behavior.

4H from ON for momentary turbo works with every channel mode, whether there is tint ramping or not, and 3H from ON for momentary turbo works when there is no tint ramping with the selected channel mode; all exactly as displayed in the diagram.

Sure thing!

Great! Those commands are looking just fine. Good to hear that you got this sorted.

As a D2 owner, to confirm a couple of things: My D2 originally shipped with Anduril version number 2021-12-13-0135 as well. Model number 0135 was originally named emisar-d4sv2-tintramp, and is now named emisar-2ch, cf. https://toykeeper.net/torches/fsm/anduril2/MODELS. Over there, it is also specified as attiny1634.

Scrolling down https://toykeeper.net/torches/fsm/anduril2/, you will find the latest emisar-2ch version at the bottom, currently indeed anduril.2023-08-07.emisar-2ch.hex. Over there, you will also still find anduril.2021-12-13.emisar-d4sv2-tintramp.hex.

For instructions specifically for backing up, cf. for example https://anduril.click/flashing/avrdude.html#backing-up.

Usually, I am using ZFlasher AVR via mobile phone (Android), which is very straightforward, but I just checked with avrdude (on Linux), and I had no difficulties with pinging the device, backing up, and updating, while using the instructions over at https://anduril.click/flashing/avrdude.html.

Finally, cf. https://bazaar.launchpad.net/~toykeeper/flashlight-firmware/multi-channel/view/head:/ToyKeeper/spaghetti-monster/anduril/hank-cfg.h to see which modifications Hank lights have from stock Anduril 2. Recently, a couple of functions were allowed in Simple UI, namely ramping toggle as well as aux config and strobe modes.

Here are some additional details:

1. Advanced UI: In Strobe Modes, Actions, 3C: Next channel mode is not a function for Police Strobe (which makes sense, as Police Strobe uses more than one channel on its own), so it could read 3C: Next channel mode (except Police Strobe).

2. Advanced UI: In Strobe Modes, Actions, instead of presently 4C: Previous mode, it could read 4C: Previous strobe mode, to clearly distinguish strobe mode from channel mode. This wording would also be in line with the text manual.

3. Advanced UI: In line with #2, in Strobe Modes, Actions, instead of presently 5C: Momentary for selected mode, it could read 5C: Momentary for selected strobe mode.

4. Simple UI: As an idea, maybe it would be useful to add two lines of information below (or next to) BattCheck, Line 1: Simple UI: once, cf. text manual, and Line 2: Advanced UI: continuously. This distinction can serve well in determining whether the current UI is Simple UI or Advanced UI, even the more so with the recent developments in hank-cfg.h, where the modified Simple UI now allows ramping toggle as well as aux config and strobe modes.

This is great, thank you very much!

As to #4, amazing that you managed to squeeze (config current ramp) in there. Possibly, visually the 7H could be a little larger, in line with e.g. the 10H of 10H (config Simple UI) and the other Hs and Cs around it?

As to #3, I figure it is also fine as it is. Just to clarify: the point is not to exclude Advanced UI (configuration) from Stepped Ramp, but rather to exclude Simple UI (configuration) from Smooth Ramp. The proposal is:

• Release after first flash (7H and 10H)
• Release after second flash (7H and 10H)
• Stepped Ramp (7H and 10H)
• Smooth Ramp (only 7H)
• Release after fourth flash (only 10H)

Again, the diagram is sufficiently complex already, and if this overcomplicates things, it might just be left as it presently is.

This being said, I will post another comment with some additional details. :-)

Yes, indeed, there have been a number of good developments recently. And given the already present permeability between single channel and multi-channel, all the better for not needing a separate single channel diagram anymore. After having gone “multi-channel” with a single channel D4K boost, I have also been going single channel, or one channel mode only, with a dual channel D2, and I can report that I have returned safe and sound.

Thank you for the heads up!

By the way, the Anduril 2 multi-channel diagrams have a wider scope than maybe anticipated. I noticed that ToyKeeper in r743 (2023-07-23) converted noctigon-dm11-boost, model number 0273, so I compiled the hex file for my D4K boost. This is a single channel light, but after I enabled one of the aux LED channels, it turned into a “multi-channel” light. :-)

Thanks again!

Thanks, and the more compact style is looking very good!

Some further suggestions for Simple UI (multi-channel) and Advanced UI (multi-channel):

1. Simple UI: Possibly add (3H to cycle) after 3H from Lockout Mode, to differentiate this from (3C to cycle) for 3C from ON.

2. Simple UI and Advanced UI: In Simply UI, possibly keep the current 1H from Lockout to Momentary Moon (maybe in one line), and rename 2H from Lockout to Momentary Low and remove the current Manual Memory reference, as Manual Memory is not a Simple UI function. At the same time, for consistency, in Advanced UI, possibly rename 1H from Lockout to Momentary Moon and 2H from Lockout to Momentary Low as well, keeping the additional information that is currently displayed in Advanced UI (Lowest Floor of Smooth vs Stepped and Highest Floor of Smooth vs Stepped, or Manual Memory if set). This wording would be in line with the text manual for 1H and for 2H. 1H and 2H are the same in Advanced UI and in Simple UI (of the three floors, only Smooth Floor and Stepped Floor are of relevance here, not Simple UI Floor), so they could be named the same, with Advanced UI offering more specific information on what exactly Momentary Moon and Momentary Low refer to, while Simple UI is keeping it as simple as possible.

3. Advanced UI: Ramp Config, containing multiple configurations, might be more accurate regarding which items refer to 7H from ON (config current Ramp Style) and which items refer to 10H from OFF (config Simple UI), in short to 7H and to 10H. There is esp. some unclarity regarding Item 3, of which only the Stepped Ramp applies to 10H, config Simple UI, cf. the text manual, whereas the smooth ramp speed is inherited from Advanced UI, cf. the text manual. To address this, (7H and 10H) in italics could be added for Item 1 after Release after first flash, (7H and 10H) could be added for Item 2 after Release after second flash, (7H and 10H) could be added after Stepped Ramp in Item 3, (only 7H) could be added after Smooth Ramp in Item 3, and (only 10H) could be added for Item 4 after Release after fourth flash, instead of currently (only Simple UI) (all in italics).

4. Advanced UI, related to #3: Possibly add (config current Ramp Style) or (config current Ramp) to 7H from ON, similar to (config Simple UI) already present at 10H from OFF. However, this might not be possible due to space constraints.

5. Advanced UI, typo: In Misc Config, Item 1, it should read 3+C instead of currently 3C+, cf. also 15+C for Version Check and 1+C for Ramp Extras Config, Item 1.

UPDATE 2023-07-25:

6. Advanced UI: Possibly add an arrow for 3C from ON pointing to Toggle Ramp Style, possibly to the right of the present 6C from ON arrow. This arrow could read 3C (single channel), or 3C (single-channel), cf. the text manual, also in the UI Reference Table. I checked: 6C from ON for Toggle Ramp Style always works, also for single channel, when only one channel mode is enabled. So the 6C from ON arrow can just stay as it is in the diagram. In order for an additional 3C from ON arrow to fit, possibly the Toggle Ramp Style box might need to be moved up a bit, and the Switch to Simple UI box a bit to the right. Also, this might mean that there is even less space for a possible addition of #4, so #4 might have to step back as #6 should have priority.

Here are some suggestions for Simple UI (multi-channel):

1. Version Check should be 15+C instead of 15C, consistent with Advanced UI, cf. also the text manual.

2. Version Check should be in the new format BBPP-YYYY-MM-DD, consistent with Advanced UI.

3. In the Ramp image, the text should read, from bottom to top, 2H Down / 1H Up, again consistent with Advanced UI.

4. Toggle Ramp Style, 6C from ON, should be removed, as this is not a Simple UI function in unmodified Anduril 2, cf. the text manual.

5. 2H from OFF for momentary ceiling should be added, cf. the text manual. 2H from OFF, for consistency with Advanced UI maybe with (momentary), could possibly be added below (or above) 2C from OFF.

UPDATE 2023-07-22:

6. 3H from Lockout Mode for Next Channel Mode (3H to cycle) should be added as well, cf. the text manual. So many details to pay attention to … :-)

Here is a wording suggestion for Advanced UI (multi-channel): For Ramp Extras Config, 10H from ON, as well as for Ramp Config, 10H from OFF (config Simple UI), both Item 4, 2C, maybe it should read if ramped up to ceiling first, or, if that does not fit into the line, if ramped up to ceiling, instead of currently if already at ceiling.

This would be in line with the text manual, and it would also be more accurate. This is because the brightness will indeed ONLY go up to turbo via 2C if ramped up to ceiling first, not for example if 2C is used to go up to ceiling; in that case, although “at ceiling”, another 2C will go back to the previous brightness level, and not up to Turbo.

Thank you very much for clarifying. All of this makes a lot of sense to me.

Question for clarification: In the diagrams, are you referring to stock Anduril 2, or rather to e.g. a Hank light or Hank lights?

For Advanced UI, this has an impact on the Ramp image, specifically for the Turbo style for 2C from ON. Currently, the Advanced UI diagram is displaying Anduril 1 Turbo style, whereas in stock Anduril 2 Turbo style, 2C from ON only goes to Turbo if ramped up to Ceiling first, cf. text manual and ramp-mode.h. Now, for Hank lights, there is hank-cfg.h, which sets Anduril 1 Turbo style as default, and hank-cfg.h is included in multiple cfg-files, for example in cfg-emisar-2ch.h.

So far, the Turbo style in Advanced UI might just have been a small variation, but this now becomes much more relevant for Simple UI: Some time ago, in rev 691, Extended Simple UI was added to hank-cfg.h. This means that now for Hank lights, Simple UI includes ramp style toggle as well as aux configs and strobe modes. That makes for a quite different Simple UI from stock Anduril 2 Simple UI, based on the text manual, which for example explicitly states that Change ramp style (smooth / stepped), 3C or 6C from ON/Ramp, is for Advanced UI only (Full UI). Currently, the Simple UI (multi-channel) diagram includes Toggle Ramp Style, but not aux configs or strobe modes.

With this development, cf. for example also wurkkos-cfg.h recently added in rev 731, probably some thought should be given on how to deal with these variations (later on, also the channel modes could vary more from light to light). To keep confusion to a minimum, it might be a useful approach to have diagrams for stock Anduril 2, and possibly branch out from there, maybe with one extra version for Hank (Emisar, Noctigon) lights, or for a specific light that you are using and making the diagrams for? Or to go ahead with just one set of diagrams, and specify what light(s) or model number the diagrams refer to, so everyone knows what the reference base is and that different variations (and defaults anyways) might apply to their own specific light? Or something else?