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.

Yes, makes sense; and as these are great diagrams with high-quality PNG files, all is looking just fine to me.

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.

Thanks for the update! I checked the new PDF version, and I have to say that I am still not convinced.

The frame is gone now, which is good, but the diagram size appears to have remained the same. Simple UI is still quite small and located in the upper right corner only, just as you stated, but also Advanced UI is (still) not centered on the page, but is located somewhat low; this results in not being able to have it scaled to the largest possible size when printing.

I guess that both diagrams would need to be scaled to and centered on the respective page in MS Visio before exporting/printing as PDF. Maybe the PDF format is not a strength of MS Visio in general? In any event, this probably would require an extra effort with each new diagram revision, depending on how MS Visio is handling this.

Furthermore, the graphic elements in the PDF version appear smoother on-screen now, but when printed, they still look pixelated, actually more pixelated than in the printed PNG version.

So, for the time being, I would still suggest to keep on going with the established PNG files exclusively.

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.

All looking great, thanks!

Thank you very much for adding the .pdf version!

Unfortunately, as far as I can tell, there are several issues with the .pdf version that would need to be addressed, and I am not sure if that is worth the trouble, as this could turn into a project of its own. :-)

Obviously, it would be fantastic to have a source file from an open source, cross-platform software, so everyone could modify it as needed, and export/print it as needed. But that is a different topic.

Some thoughts:

• First off, as expected, the font print is very crisp in the .pdf version, and as there is much text, that is great. But several graphic elements apparently are pixel graphics and do not scale cleanly (.png is a raster-graphics file format based on a pixel grid; this is for example also why the newly added link to the diagrams cannot be marked and copied from the .png version, but it can from the .pdf version).

• Then, for some reason, there is a frame around both diagrams, and when printed with this frame, the diagram size shrinks, as opposed to the established .png version, which makes the .pdf version less readable. Moreover, the Simple UI .pdf version only appears in a small size in the upper right corner, instead of being displayed on the entire page.

While these issues might be addressed easily, I am not familiar with MS Visio, and there might be tricky details involved. Therefore, for the time being, I would suggest to remove the .pdf version again and to just go ahead with the established .png versions. These are high resolution and can also be printed just fine (although not as clearly as in .pdf format), and they are great for on-screen viewing and editing, so they already cover a wide range of use cases on their own.

Thank you very much again for all your efforts!

Question/suggestion: If not too much hassle (I am running Linux, and I am not familiar with MS Visio), would it be possible to add a .pdf version of the diagrams below the .png versions?

The .png files are high resolution and are great esp. for on-screen viewing, but for printing, esp. in larger formats given the diagram complexity, .pdf will still be more suitable than .png.

Actually, this could be one single .pdf file with 2 pages, one for Simple UI and one for Advanced UI, and this .pdf file could then be printed double-sided, or one specific page only, as preferred.

Some further details:

1. Advanced UI: Layout detail: For consistency, the new additions to Ramp Config, three times "(7H and 10H)" and "(only 7H)", should probably be written in italics as well, just like "(only 10H)" at the end.

2. Simple UI: Layout detail: It caught my eye that with 13H on the arrow to Factory Reset, the H is visually very close to the (4C) arrow line to the right of it. Possibly, this 13H could be moved slightly to the left? This is the only visual instance like this that caught my attention.

3. Simple UI and Advanced UI: As an idea, possibly a link to the diagrams, at present lemmy.world/post/1038159, could be added, so everyone could easily locate the current diagram revision. A place to put this link as an extra line could be below the Diagram Revision line in the Anduril 2 "bubble". To maintain the "bubble" size, maybe a little smaller font size(s) could be used at the top; furthermore, as the multi-channel and the single-channel branches apparently are going to be merged, there might soon be no need anymore for the Multi-Channel specification, opening up some more space in the Anduril 2 "bubble".

All looking very good to me, thanks! #4 is very clear this way, and suitably located.

OK, I see, great! I noticed one layout detail, which I will include in a new comment, to keep the overview.

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.