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.
  • jon_slider@lemmy.worldEnglish
    3·
    1 year ago

    Thank you very much! With your new chart, you have succeeded in adding all the features I used to use the manual for.

  • lowprofile@lemmy.worldEnglish
    3·
    1 year ago

    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.

    • containerfan@lemmy.worldOPEnglish
      1·
      1 year ago

      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!

  • CapitalLong@lemmy.worldEnglish
    2·
    1 year ago

    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! ;)

  • lowprofile@lemmy.worldEnglish
    2·
    1 year ago

    For your consideration, here are some more suggestions (Advanced UI):

    1. Add 4H for Momentary Turbo, possibly below the present 3H for Tint Ramp OR Momentary Turbo on the very left; cf. text manual. This 4H is esp. for channel modes that use 3H for Tint Ramp, but I have checked this 4H for Momentary Turbo to work in all channel modes, including those with already 3H for Momentary Turbo, i.e. without Tint Ramp.

    2. In the Strobe Mode Actions, add Police Strobe at 1H: Brighter/Faster and 2H: Dimmer/Slower before Lightning, in order to read (except Police Strobe and Lightning), cf. text manual.

    3. Believe it or not, 3C for Next Channel Mode also works in Tactical Mode (6C from OFF), I checked. I suppose this is covered by “Any Mode” in the text manual. So 3C for Next Channel Mode should also be added to Tactical Mode.

    4. 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.

    5. 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 at 3C from ON, 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 added 3H box for Lockout Mode.

    6. Relating to #5, possibly place the 3H from Lockout Mode below 1H and 2H, visually somewhat separated from 10H, 7C, and 7H, as this 3H not only refers to Lockout Mode, but extends to ON as well.

    7. Use 15+C instead of presently 15C from OFF for Version Check, cf. text manual. I am always glad to not have to count to exactly 15 when doing a version check.

    8. While at it, in Ramp Extras Config, Item 1, use 1+C instead of presently 1C = disable ..., cf. text manual “(doesn’t matter what value the user enters at the prompt)”.

    • containerfan@lemmy.worldOPEnglish
      2·
      1 year ago

      I’m still in the process of making changes, but here’s what I’ve done so far…

      1. Added 4H for Momentary Turbo
      2. Added Police Strobe before Lightning
      3. Added 3C for Next Channel Mode from Tactical Mode.
      4. Took your advice and trimmed Next Channel Mode down to save space.
      5. Took your advice and trimmed Next Channel Mode down to save space. Enlarged the Ramp image to use some of that space.
      6. I agree with your recommendation, but I just can’t squeeze the Next Channel Mode in there.
      7. Changed 15C to 15+C
      8. Changed 1C to 1+C

      Excellent recommendations, and I appreciate your help. Now working on the channel modes…

      • lowprofile@lemmy.worldEnglish
        2·
        1 year ago

        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 from OFF, momentary Turbo, now does not point to the same level as the arrow from 2C 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 from OFF as well as from 5C from Lockout 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 to 1H Up pointing down to Floor, and the arrow next to 2H 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 in Sunset Timer and in Beacon Frequency. Maybe straighten the Candle Timer symbol again?

        e. Totally unrelated, this also caught my eye: With the slightly changed visual arrangement, the text 3H (mode memorized) from OFF for the Strobe Modes has meanwhile come very close to the text Disconnect power to exit for Momentary. Maybe move the text 3H (mode memorized) a bit to the left to visually separate the two texts?

        • containerfan@lemmy.worldOPEnglish
          1·
          1 year ago

          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.

          • lowprofile@lemmy.worldEnglish
            2·
            1 year ago

            Awesome, thanks! I am happy to help.

            And I did not notice an impact on the diagram in ToyKeeper’s latest four revisions either.

  • lowprofile@lemmy.worldEnglish
    2·
    1 year ago

    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.

    • containerfan@lemmy.worldOPEnglish
      1·
      1 year ago

      This is going to sound silly, but I didn’t realize that I could post in-line images. I added both per your suggestion, and it’s much more functional. Thanks for getting me to finally look into it!

  • jon_slider@lemmy.worldEnglish
    2·
    1 year ago

    I also wanted to be able to keep it up to date

    thanks for all your efforts, very helpful

    fwiw, I just received an Emisar D2 and did a version check that resulted in:

    2021 12 13 0135

    it uses 3H to change channels, not 3C…

    I am trying to learn to reflash the D2 to a later version, but have not figured it out yet. I also dont know which hex file to update to, yet. update, found it: http://toykeeper.net/torches/fsm/anduril2/anduril.2023-04-25.emisar-2ch.hex

    Do you have a flow chart for the existing stock firmware on the D2? (I dont know what revision that would be)

    • containerfan@lemmy.worldOPEnglish
      1·
      1 year ago

      Unfortunately, I have not been keeping historical versions of the diagrams. I checked the file on Dropbox, and it only goes back a month (to a July 9th version of the diagram for r725 which still uses 3C to change channels). Someone once suggested that I use GitHub to track changes for things like this, so I may look into it in the near future.

      I don’t have a D2, but I believe that it uses the same firmware as the D4V2 dual-channel. This would be the latest version from earlier this week (08/07). Once you get on the latest version, my diagrams should apply.

  • lowprofile@lemmy.worldEnglish
    2·
    1 year ago

    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.

      • lowprofile@lemmy.worldEnglish
        2·
        1 year ago

        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!

        • containerfan@lemmy.worldOPEnglish
          1·
          1 year ago

          I originally saved the file as a PDF in Visio, and as you noted, the results were not good. Then I tried printing it to PDF in a couple of different ways, and I think the result is much better. Take a look at it again, and let me know what you think. The Simple UI diagram will always be smaller because that’s how the source is. When Visio saves it to a PNG file, it chops it down to just the canvas size needed for the diagram. Then when you print it, it gets enlarged to cover the whole page.

          • lowprofile@lemmy.worldEnglish
            2·
            1 year ago

            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.

            • containerfan@lemmy.worldOPEnglish
              1·
              1 year ago

              Yes, maybe if I had Adobe Acrobat Professional, I might be able to produce high-quality PDFs. But the cost is insane, and I just haven’t had a need for it. Perhaps I’ll have better results if I can ever get the diagrams switched over to an open-source alternative for Visio.

              • lowprofile@lemmy.worldEnglish
                2·
                1 year ago

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

  • lowprofile@lemmy.worldEnglish
    2·
    1 year ago

    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”.

  • lowprofile@lemmy.worldEnglish
    2·
    1 year ago

    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 from Lex-Perpetua, so it should read Lux-Perpetua's and Lux's.

    This actually does kind of make sense in this context, as in Latin, “lux” means light, whereas “lex” means law. :-)

    • containerfan@lemmy.worldOPEnglish
      1·
      1 year ago

      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.

  • lowprofile@lemmy.worldEnglish
    2·
    1 year ago

    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?

    • containerfan@lemmy.worldOPEnglish
      1·
      1 year ago

      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.

  • lowprofile@lemmy.worldEnglish
    2·
    1 year ago

    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:

    1. 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 … :-)
    • containerfan@lemmy.worldOPEnglish
      1·
      1 year ago

      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.

  • lowprofile@lemmy.worldEnglish
    2·
    1 year ago

    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:

    1. 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.
    • containerfan@lemmy.worldOPEnglish
      1·
      1 year ago

      Thanks for the additional feedback. Unfortunately, I won’t have access to my PC to make edits for about two weeks, so it’ll be a while until I can integrate your suggestions.

      • lowprofile@lemmy.worldEnglish
        3·
        1 year ago

        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. :-)

        • containerfan@lemmy.worldOPEnglish
          2·
          1 year ago

          Yeah, one of the reasons that ToyKeeper suggested that I use build dates rather than code revision numbers is because the multi-channel and single-channel code bases will eventually merge. She’s also working on getting everything moved over to GitHub which will be really nice. So I may not spend much time trying to update the original single-channel Anduril 2 diagram if everything is going to get merged anyway.

          • lowprofile@lemmy.worldEnglish
            1·
            1 year ago

            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.

    • containerfan@lemmy.worldOPEnglish
      1·
      1 year ago

      OK, I finally got a chance to make an update…

      1. Done
      2. Done. Also added the “bubble” around the descriptions in the Simple UI diagram to be consistent aesthetically with the Advanced UI diagram.
      3. I’m a little lost on this one - especially in the context of #4. If I’m already on the stepped ramp style, the 7H from ON allows me to set the number of steps (third flash). It applies to the Advanced UI, and not only the Simple UI. How else would you configure the number of steps for Advanced UI?
      4. Done. Managed to squeeze “(config current ramp)” in there.
      5. Done.
      6. Done.
      • lowprofile@lemmy.worldEnglish
        2·
        1 year ago

        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. :-)

        • containerfan@lemmy.worldOPEnglish
          1·
          1 year ago

          OK, now I understand what you were saying. I figured it was a misunderstanding on my part. I never realized that you couldn’t configure the smooth ramp for the Simple UI - likely because I never use the Simple UI. Thanks for pointing this out. I updating the diagram now…

          • lowprofile@lemmy.worldEnglish
            1·
            1 year ago

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