Advanced UI
Simple UI
Background: This was 100% inspired by Lux-Perpetua’s Andúril 2 UI diagram on BLF. In fact, Lux’s diagram is so good, that I would have been happy to just use it except for one thing: the source isn’t published, so you can’t modify it. I also wanted to be able to keep it up to date with u/ToyKeeper’s code. So I created my own…
This is where I intend to store all of my Anduril 2 UI diagrams, and any updates to them. Since ToyKeeper split off the multi-channel version of Anduril 2, I have created two new diagrams for it:
Anduril 2 Multi-Channel Advanced UI (PNG)Anduril 2 Multi-Channel Simple UI (PNG)
Diagrams now hosted on GitHub.
Yeah, it got complicated enough that I could no longer fit the Advanced and Simple UI diagrams on a single page, so I had to split them.
As always, you are free to do whatever you want with these diagrams. I make these for myself, and I’m happy to share them with the community. You can find the source MS Visio file here. Feel free to make your own copy and modify it to your heart’s content. The Visio file contains several pages:
Single-Channel - Advanced/Simple UI diagram for the single-channel version of Anduril 2. I still need to update and post it.Multi-Simple - Simple UI diagram for the multi-channel version of Anduril 2.Multi-Advanced - Advanced UI diagram for the multi-channel version of Anduril 2.Diagram Parts - Various bits and pieces that I use in the various UI diagrams.
If you find any errors, please post a comment here. I try to keep the diagrams as accurate and up-to-date as possible, but you know, life happens. Enjoy!
Updates:
- 2023-07-06: Fixed several issues pointed out here. Thanks @lowprofile!
- 2023-07-09: Fixed a few more issues pointed out here. Thanks again @lowprofile! Also trying to get the wording in a few places more inline with the text manual.
- 2023-07-15: Updated for r728 which added channels for red, yellow, green, cyan, blue, purple, and white. Added 4H from ON to Momentary Turbo. Added 3C from Tactical Mode to Next Channel Mode. Several other minor fixes. Huge thanks to @lowprofile for continuing to provide valuable feedback. This multi-channel diagram has been a journey!
- 2023-07-17: Multiple visual enhancements/fixes thanks to @lowprofile. Incremented the version to r732 even though there were no material impacts to the diagram.
- 2023-07-20: Modified the ramp part of the diagram to reflect the default Anduril 2 configuration (2C to Ceiling). Thanks again to @lowprofile for feedback. I also switch from revisions to build dates as suggested by ToyKeeper.
- 2023-07-22: Made several corrections to the Simple UI diagram that I had been neglecting. Also made a slight wording change to the ramp config boxed on the Advanced UI diagram. Thanks to @lowprofile for all corrections. Finally, I incremented the build date to 2023-07-21, although there were no material impacts to the diagrams.
- 2023-08-06: Several cosmetic fixes to the Simple and Advanced UI diagrams thanks to feed back from @lowprofile. Also incremented the build date to 2023-08-04, although there were no material impacts to the diagrams.
- 2023-08-07: Several clarifications thanks to feedback from @lowprofile. Also incremented the build date to 2023-08-07, although there were no material impacts to the diagrams.
- 2023-08-10: Several cosmetic fixes to the Simple and Advanced UI diagrams thanks to feed back from @lowprofile.
- 2023-10-03: I’m embarrassed to admit that I missed an update from the 2023-08-27 release in which “smooth steps” were added (see the Ramp Extras Config). Other than that, there have been no material changes to the diagrams.
- 2023-11-07: I finally got around to making a couple of updates suggested by @lowprofile. In the Strobe Modes on the Advanced UI diagram, you’ll notice that 3C allows you to save the channel mode per strobe mode. Very cool!
- 2024-01-01: Last update here on Lemmy. Lemmy is great, but it makes more sense to host the diagrams on GitHub when I can issue diagram releases corresponding with ToyKeeper’s Anduril 2 releases. From now on, please access the diagrams there. It’s a fairly significant update, so please be sure to read the README.
Nice work, thanks for the diagrams.
Thank you very much! With your new chart, you have succeeded in adding all the features I used to use the manual for.
You did it!
You know anduril 2 would not be manageable without you at the moment. It’s great that toykeeeper holds a changelog and repo, but without this, I would just have had convoys or something instead.
Please post the same link on r/flashlights if you haven’t already, just to inform people that there is an update graphicalized, and. That there’s a new Reddit in town! ;)
Yeah, I added a final update to my post on Reddit to let folks know that everything has moved here.
Here are some additional details:
-
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 read3C: Next channel mode (except Police Strobe)
. -
Advanced UI: In Strobe Modes, Actions, instead of presently
4C: Previous mode
, it could read4C: Previous strobe mode
, to clearly distinguishstrobe mode
fromchannel mode
. This wording would also be in line with the text manual. -
Advanced UI: In line with #2, in Strobe Modes, Actions, instead of presently
5C: Momentary for selected mode
, it could read5C: Momentary for selected strobe mode
. -
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.
Fixed all. Might be a little wordy on #4, so let me know what you think. I think it’s a really useful add, and I wanted it to be clear. Thanks!
All looking very good to me, thanks! #4 is very clear this way, and suitably located.
-
Great work, thank you very much! A couple of details I noticed in this detailed diagram (Advanced UI):
-
If I am not mistaken, for 3C from ON, Change Channel,
50/50
comes before, not afterTint Ramp
, so the present order should be corrected. -
For the Strobe Modes,
Police Strobe
andTactical Strobe
should be in the opposite order, asTactical Strobe
comes beforePolice Strobe
. -
Furthermore, in Strobe Modes, the
Actions
could include3C: Change Channel
. -
Also, for Lockout Mode,
3H
forChange Channel
could be added, possibly below 1H and 2H. -
Finally, maybe it is useful (if not too much detail) to specify what the two
Momentary Floor
, 1H and 2H in Lockout Mode, refer to. For1H
it could readMomentary Floor (lowest Floor of Smooth vs Stepped)
, and for2H
it could readMomentary Floor (highest Floor of Smooth vs Stepped), or Manual Memory if set
.
Thanks so much for the feedback. I corrected #1, 2, 3, and 5 in the diagram for the Advanced UI. I can’t get #4 to work on my dual-channel D4V2. It looks like it’s changing channels, but it switches back to the original channel almost immediately. Are you able to get this working on a light? How is it supposed to behave?
The updated diagram is looking very good, thanks! And yes, I had #4 working just fine, but I checked again, and it is not working with every Anduril 2 version. I do not want to overcomplicate this, but as the Anduril 2 multi-channel branch is in active development, a little extra detail seems to be in order here:
I am checking this with two D2s (but apparently, so far I only checked 3H in Lockout Mode with the first one of them):
-
First D2: Running
anduril.emisar-2ch-aux.hex
by SiteRelEnby, as referred to in this Reddit post (there is also a Lemmy post, but that one does not include the GitHub links added at the top), version0135-2023-07-03
(new version format). -
Second D2: Running
anduril.2023-04-25.emisar-2ch.hex
from ToyKeeper’s /torches/fsm/anduril2, version2023-04-26-0135
(old version format); please note: at the same site, also the newer versionanduril.2023-05-30.emisar-2ch.hex
is available.
Back to #4:
3H
in Lockout Mode forChange channel
works with the first D2, but not with the second D2.(By the way, the newer Anduril 2 version of the first D2 also added aux LED channels to
Change Channel
,3C
fromON
. This might be another addition to the diagram in the future, adding seven more channels, one each for red, yellow, green, cyan, blue, purple, and white aux LEDs. For example, I disabled all the aux LED channels via9H
fromON
, but for the blinky modes,3C
fromBattCheck
, I set white aux LEDs.)As
3H
from Lockout toChange channel
is in ToyKeeper’s text manual, which is my point of reference, I guess it should also be in the diagram; cf. the UI Reference Table at the end:Lockout Any 3H Next channel mode (if more than one enabled)
And on to #3: Arguably, this should read
3C: Change channel
rather than presently3C: Change channel for strobe modes
, as this channel change is not limited to the strobe modes, but extends toON
as well. The same goes for3H
fromLockout
, #4, which accordingly should also readChange channel
. Both of these only show the enabled channels, not the disabled ones.And both of these differ from
3C
fromBattCheck
, which shows all the channels, enabled as well as disabled ones, and which is indeed limited to the blinky modes, so the present additionfor blinky modes
inSwitch channel for blinky modes
is correct. Cf. also the(for number blinks only)
in the UI Reference Table at the end of ToyKeeper’s text manual:Batt check Full 3C Next channel mode (for number blinks only)
Thanks for the continued feedback. I somehow missed 3H from lockout in the text manual the first time around. Even though I can’t get it working properly on my D4V2 at the moment (hex compiled directly from ToyKeeper’s r725 code), I included it. I assume it’ll be fixed soon.
I also changed the wording slightly for channel switching to be more inline with the text manual, so now it reads “next channel mode” in a few places.
I’m a little confused about the feature to use 3C to cycle through the aux LED colors. So on my D4V2 which has RGB aux, would 3C turn on, for example, the red aux as the main emitters? For now, I added “Aux LED Channel(s)” to the Next Channel Mode boxes, but I don’t know if that’s appropriate. Take a look, and let me know what you think. Thanks!
Excellent, and thanks again for your work! This is the only diagram I am aware of that is displaying the (many) new Anduril 2 multi-channel features, and I consider this diagram to be a great contribution to the community.
As there are so many details to pay attention to, and things can get somewhat confusing, I will go along the individual points. For each of them, I will lay out what the two D2s at my end are doing.
The first D2 has remained as described above, running
anduril.emisar-2ch-aux.hex
from SiteRelEnby, version number0135-2023-07-03
.The second D2 is now updated to the latest version from ToyKeeper’s site, running
anduril.2023-05-30.emisar-2ch.hex
, version number0135-2023-05-30
.3H
in Lockout Mode forNext Channel Mode
: First D2: working. Second D2: working (but not for the aux LED channels).
The wording
Next Channel Mode
looks good to me, also for3C
fromON
, and it is in line with the text manual.The
Aux LED Channel(s)
work in the first D2, but not in the second D2. The aux LEDs indeed work as the main emitters in this situation, and as far as I have observed it is ON/OFF with one (high aux) brightness. As to whether to include theAux LED Channel(s)
in the diagram for3H
fromLockout
and for3C
fromON
, I would suggest: presently No. Although ToyKeeper’s text manual apparently does not specify the channel modes, cf.A light can have many different channel modes, so don’t be shy about turning off any modes you don’t use. It makes all the others easier to reach.
at least for the .hex from ToyKeeper’s site these seem not be included at present, so including them might cause unnecessary confusion. They could simply be added at a later point in time. Then, for consistency, also the
Channel Mode Config
,9H
fromON
, would have to include the aux LED channels (seven, adding up to 12 channel modes).3C: Next channel mode
in Strobe Modes: First D2: working. Second D2: working.
All fine here (one detail I observed is that the police strobe runs with red and blue aux LEDs in the first D2, but with Channel 1 and 2 in the second D2, just an observation, nothing to be included in the diagram).
3C
from Batt Check forNext channel mode (for number blinks only)
: First D2: working. Second D2: sort of working (?).
Again, the new wording looks good to me, and it is in line with the text manual. Actually, it is clearer than before, when it referred to the blinky modes rather than the number blinks, as this channel change only applies to Batt Check and to Temp Check, not to Beacon and SOS. Within the
Blinky/Utility Modes
I had interpretedBlinky
to refer to Batt Check and Temp Check, andUtility
to refer to Beacon and SOS, but I might have misconstrued that. However that may be, referring to(for number blinks only)
in the diagram clears that up.The first D2 cycles through all the channel modes, enabled as well as disabled ones, and choosing a channel mode is indeed limited to the number blinks only (and also includes e.g.
Version Check
,15C
). This is in line with the text manual.But with the second D2,
3C
fromBatt Check
works just like3C
fromON
,3C
inStrobe Modes
and3H
inLockout Mode
, i.e. it only cycles through the enabled channels, and choosing a channel change extends toON
etc. and is not limited to the number blinks only. This is not in line with the text manual.In this case, I would suggest to give priority to the text manual and leave the current wording in the diagram as it is.
PS: With the latest revision 728 from yesterday, 2023-07-10, as far as I can tell, ToyKeeper now integrated the 7 aux LED channel modes into the emisar-2ch build.
With this, I would now suggest to include the aux LED channel modes in
Next Channel Mode
,3C
fromON
, and leave the presentAux LED Channel(s)
, or ratherAux LED Channels
, in the diagram; there might be no need to individually specify the 7 aux LED channel modes: Red, Yellow, Green, Cyan, Blue, Purple, White.And for
Channel Mode Config
,9H
fromON
, to save space by not adding 7 additional points, there could e.g. be one additional point6+) Release after sixth+ flash
andConfigure channel 6+
.Moreover, I noticed a couple of other details in the diagram, and I will post a new comment for those. With all the current additions, I figure it is expected to take a little while to get everything up to speed.
UPDATE 2023-07-14: I checked with r728 (hex compiled directly from ToyKeeper’s code), and indeed, the 7 aux LED channel modes are now integrated into the emisar-2ch build. One difference I observed compared to SiteRelEnby’s version from above is that the 7 aux LED channel modes are not enabled, but rather disabled by default (which I would have suggested as well).
Yes! It’s working on my D4V2! I updated the Channel Mode Config as you suggested (mostly). I’ll have the updated version posted shortly. Thanks again for the recommendations!
Excellent, looking very good! Thanks again!
-
-
This is beautiful, thank you
Superb work, reminds me that I should update my lights again sometime.
Excellent work! This is super useful
Some further details:
-
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.
-
Simple UI: Layout detail: It caught my eye that with
13H
on the arrow to Factory Reset, theH
is visually very close to the (4C) arrow line to the right of it. Possibly, this13H
could be moved slightly to the left? This is the only visual instance like this that caught my attention. -
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 theDiagram 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 theMulti-Channel
specification, opening up some more space in the Anduril 2 “bubble”.
All excellent suggestions as usual. I’m updating the diagrams now.
All looking great, thanks!
-
Still my favorite diagram. Thx containerfan !
For your consideration, here are some more suggestions (Advanced UI):
-
Add
4H
forMomentary Turbo
, possibly below the present3H
forTint Ramp OR Momentary Turbo
on the very left; cf. text manual. This4H
is esp. for channel modes that use3H
forTint Ramp
, but I have checked this4H
forMomentary Turbo
to work in all channel modes, including those with already3H
forMomentary Turbo
, i.e. withoutTint Ramp
. -
In the Strobe Mode Actions, add
Police Strobe
at1H: Brighter/Faster
and2H: Dimmer/Slower
beforeLightning
, in order to read(except Police Strobe and Lightning)
, cf. text manual. -
Believe it or not,
3C
forNext Channel Mode
also works in Tactical Mode (6C
fromOFF
), I checked. I suppose this is covered by “Any Mode” in the text manual. So3C
forNext Channel Mode
should also be added to Tactical Mode. -
As to the diagram layout for #3, to save some space, it might be sufficient to just write
Next Channel Mode (3C to cycle)
for Tactical Mode, without listing all the individual channel modes once again. -
Relating to #4, as to the diagram layout, to save some space, it might also be sufficient to just write
Next Channel Mode (3H to cycle)
for Lockout Mode. The individual channel modes are already listed at3C
fromON
, so they might not have to be repeated here again. At the same time, this would free some space for the Ramp image, which has been shrinking quite a bit due to the added3H
box for Lockout Mode. -
Relating to #5, possibly place the
3H
from Lockout Mode below1H
and2H
, visually somewhat separated from10H
,7C
, and7H
, as this3H
not only refers to Lockout Mode, but extends toON
as well. -
Use
15+C
instead of presently15C
fromOFF
forVersion Check
, cf. text manual. I am always glad to not have to count to exactly 15 when doing a version check. -
While at it, in Ramp Extras Config, Item 1, use
1+C
instead of presently1C = disable ...
, cf. text manual “(doesn’t matter what value the user enters at the prompt)”.
I’m still in the process of making changes, but here’s what I’ve done so far…
- Added 4H for Momentary Turbo
- Added Police Strobe before Lightning
- Added 3C for Next Channel Mode from Tactical Mode.
- Took your advice and trimmed Next Channel Mode down to save space.
- Took your advice and trimmed Next Channel Mode down to save space. Enlarged the Ramp image to use some of that space.
- I agree with your recommendation, but I just can’t squeeze the Next Channel Mode in there.
- Changed 15C to 15+C
- Changed 1C to 1+C
Excellent recommendations, and I appreciate your help. Now working on the channel modes…
Great, thank you very much! What a beast of a diagram, and all is looking fine to me.
Possibly, if not too much hassle, as to #5 and in particular as to the Ramp image, a few visual suggestions, since to me the Ramp image looked a little clearer in previous diagram revisions:
a. Am I correct in assuming that the arrow from
2H
fromOFF
, momentary Turbo, now does not point to the same level as the arrow from2C
from Ramp anymore on purpose? This might just take a little while to get used to, yet visually, this might look like the two arrows are pointing to differing brightness levels. Maybe have them point to the same level at the very top of the Ramp image again?b. Moreover, the arrows from
2C
fromOFF
as well as from5C
fromLockout Mode
now appear to point to a level slightly above the Ceiling level line, which might lead to a slight visual disorientation as well. Maybe have them point straight to the Ceiling level line in the Ramp image again?c. This might have come up before, but lastly, it struck me as odd that in the Ramp description, it reads
1H Up / 2H Down
from bottom to top, with the arrow next to1H Up
pointing down to Floor, and the arrow next to2H Down
pointing up to Ceiling. Maybe have it read the other way around,2H Down / 1H Up
from bottom to top?d. Speaking of visual matters: The timer symbol in
Candle Timer
has been squeezed horizontally in the current diagram revision. In previous diagram revisions, it used to have the same shape as inSunset Timer
and inBeacon Frequency
. Maybe straighten theCandle Timer
symbol again?e. Totally unrelated, this also caught my eye: With the slightly changed visual arrangement, the text
3H (mode memorized)
fromOFF
for theStrobe Modes
has meanwhile come very close to the textDisconnect power to exit
forMomentary
. Maybe move the text3H (mode memorized)
a bit to the left to visually separate the two texts?I really need to do a better job of QC on this diagram as it gets more complex…
a. You are correct, and I have fixed it.
b. Correct again. Resizing that Ramp diagram wreaked havoc!
c. I had adapted this from Lux-Perpetua’s original diagram, but I see what you mean. I changed it per your suggestion, and it does make more sense.
d. Yep, I squeezed the symbol unintentionally when shrinking the text box. Fixed.
e. Excellent suggestion! I don’t know why I had it all stacked in there. Fixed.
I also noticed that ToyKeeper has issued four more revisions since yesterday, but I don’t believe that any of them impact the diagram.
As always, thank you for the feedback on the diagram. I need folks like you to help me keep it straight.
Awesome, thanks! I am happy to help.
And I did not notice an impact on the diagram in ToyKeeper’s latest four revisions either.
-
On to something different, this time not for the diagram itself, but rather for the post description: The diagram on BLF referred to is from
Lux-Perpetua
, not fromLex-Perpetua
, so it should readLux-Perpetua's
andLux's
.This actually does kind of make sense in this context, as in Latin, “lux” means light, whereas “lex” means law. :-)
OMG, I’m trying to give the guy credit, and I screw up his name. That’s terrible. Fixing it now. Thanks for pointing this out.
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
fromON
. Currently, the Advanced UI diagram is displaying Anduril 1 Turbo style, whereas in stock Anduril 2 Turbo style,2C
fromON
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
or6C
fromON/Ramp
, is for Advanced UI only (Full UI). Currently, the Simple UI (multi-channel) diagram includesToggle 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?
I can’t remember if I originally developed my first Anduril 2 diagram for a specific light I had (possibly my D4V2), or if the way the turbo works has just evolved over time. Either way, the point of the diagrams is to stay current with unmodified Anduril 2, and I make the source file available so that folks can adapt the diagrams to fit their specific configurations (sorry, only MS Visio for now). So you are correct about turbo, and I updated the Advanced UI diagram to be aligned with the default Anduril 2 style turbo. I’m afraid that if I try to generate multiple diagrams for specific manufacturer configurations then I’ll just fall way behind. Plus, I simply don’t have many of those models. But thank you for pointing this out because it was my intention to represent unmodified Anduril 2.
Thank you very much for clarifying. All of this makes a lot of sense to me.
Here is a wording suggestion for Advanced UI (multi-channel): For
Ramp Extras Config
,10H
fromON
, as well as forRamp Config
,10H
fromOFF
(config Simple UI), both Item 4,2C
, maybe it should readif ramped up to ceiling first
, or, if that does not fit into the line,if ramped up to ceiling
, instead of currentlyif 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 if2C
is used to go up to ceiling; in that case, although “at ceiling”, another2C
will go back to the previous brightness level, and not up to Turbo.Good clarification. Fixed! Thanks!
Thanks again!
Here are some suggestions for Simple UI (multi-channel):
-
Version Check
should be15+C
instead of15C
, consistent with Advanced UI, cf. also the text manual. -
Version Check
should be in the new formatBBPP-YYYY-MM-DD
, consistent with Advanced UI. -
In the Ramp image, the text should read, from bottom to top,
2H Down / 1H Up
, again consistent with Advanced UI. -
Toggle Ramp Style
,6C
fromON
, should be removed, as this is not a Simple UI function in unmodified Anduril 2, cf. the text manual. -
2H
fromOFF
for momentary ceiling should be added, cf. the text manual.2H
fromOFF
, for consistency with Advanced UI maybe with(momentary)
, could possibly be added below (or above)2C
fromOFF
.
UPDATE 2023-07-22:
3H
from Lockout Mode forNext Channel Mode (3H to cycle)
should be added as well, cf. the text manual. So many details to pay attention to … :-)
I had been neglecting the Simple UI diagram apparently. I fixed all points, and rearranged it slightly to make it a tiny bit more compact. Thanks again for all of the corrections.
Thanks, and the more compact style is looking very good!
-