Anduril ... 2?

[Rayoui]

Reading the full manual is good for learning the UI, but I like having a full diagram with all functions for quick reference.

[jp9mm]

@grzybek337

Personally, I feel its really overwhelming at first sight.
I suppose you should simplify it by, for example, moving the “Version check” and “Factory reset” to the bottom of the diagram, leaving more space for the Simple UI stuff.

Another thing would be deleting things like arrows 5C and 4H from lockout. Diagram for the Simple UI should contain the basic functions for the light in that mode, where the more advanced knowledge can be obtained from reading the manual. That way, learning the Simple UI will be easier and… simpler.

Some people will probably only use the Simple UI, so it would be important to not get them discouraged, just by looking at the diagram itself.
Other than that, I think you covered most and not if all the things that needed to be in the Anduril 2 diagram.

Too many words in this post, i’m overwhelmed. Please reduce by 50% and i will consider reading :innocent:

[grzybek337 (Grzybek)]

@goki

The diagram for the Simple UI can be found on Post #2. What you're looking at is the diagram for the full UI w/c is meant to visualize all of the light's function.

Oh thank you for the link. Those photos weren't loading for me before. Now I can see them.

I totally agree. Now, as I look at the Lux-Perpetua's diagram, it doesn't seem as bad as I previously mentioned.

[Tom_E]

Think this is a better Simple UI diagram here: https://www.ff-light.com/index.php?route=product/product&path=64&product_id=77

For some reason I'm not seeing any of TK's pics/png's, so not sure what is in post #2.

Using the FF link directly:

[Lux-Perpetua]

Maybe it’s best to derive a separate UI diagram for SIMPLE UI only. The one taken from the FF website is nice but lacks some important features like tint ramp, access to moonlight/low, access to Advanced UI or factory reset. Moreover, the grey part for turbo can be removed as it is inaccessible in SIMPLE UI.

Eventually, a small cheat sheet with the SIMPLE UI on the front side and the ADVANCED/FULL UI on the back side might be the best outcome? I have seen that Fireflies sends the lights with a small printed card of the Andúril UI. Maybe this could be a nice option for Hank‘s lights, too.

[SammysHP]

@Tom E

For some reason I’m not seeing any of TK’s pics/png’s, so not sure what is in post #2.

It’s the same image. BLF now uses https and your browser blocks mixed content.

[mgflax]

@Lux-Perpetua

So, ToyKeeper did not reply to my PM so far. I have now completed the entire Andúril 2.0 UI diagram, reflecting all features mentioned in the text manual from TK. Double-lines are meant to indicate functionalities for Advanced UI only. Single lines apply for any of both UIs. This is my first draft. Feel free to comment, to rant, to unleash all your criticism...

Supplemental information: I did not manage to do this in Inkscape until now. Not sure if Copy 'n Paste from Powerpoint will do the job or if everything needs to be done from scratch again.

Thank you! A few suggestions:

1. What do you think of an arrow from "Momentary Mode" down to "Off" labelled "unscrew to remove power" (or something like that)? Also, you have two "Momentary Mode" nodes -- perhaps you can have a single one if the upper one is moved further down the page?
2. You probably want a "1C" arrow from "Strobe Modes" back to "Off".
3. The "Momentary Lockout" node could just be replaced with the "lock" icon.
4. How about something like "Floor Level - while light flashes rapidly, click n times for level n, or press 0 times to proceed to next option"?
5. I'm wondering if Momentary Strobe mode should be a separate node, since 2C doesn't do anything special except flash the strobe twice.

[lionheart_2281]

Is TK okay? I haven’t seen her around for a while.

I hope she hasn’t been taking peoples suggestions and comments to heart and is feeling overwhelmed at this

[Tom_E]

I don't know much but she has not been feeling well and hasn't been able to keep up on things here. Really really hope she improves and gets better - I'm sure we all do.

[mgflax]

@Tom E

I don't know much but she has not been feeling well and hasn't been able to keep up on things here. Really really hope she improves and gets better - I'm sure we all do.

100%!

[Lux-Perpetua]

@mgflax

Thank you! A few suggestions:

1. What do you think of an arrow from "Momentary Mode" down to "Off" labelled "unscrew to remove power" (or something like that)? Also, you have two "Momentary Mode" nodes -- perhaps you can have a single one if the upper one is moved further down the page?
2. You probably want a "1C" arrow from "Strobe Modes" back to "Off".
3. The "Momentary Lockout" node could just be replaced with the "lock" icon.
4. How about something like "Floor Level - while light flashes rapidly, click n times for level n, or press 0 times to proceed to next option"?
5. I'm wondering if Momentary Strobe mode should be a separate node, since 2C doesn't do anything special except flash the strobe twice.

Thanks a lot to everyone here for your feedback and thanks for your suggestions above. That’s very helpful to improve the diagram and make it more comprehensible.

[gchart]

This is just a matter of taste, but those squiggly borders make it seem cartoonish to me.

[Lux-Perpetua]

Okay, will try to offer a less „childish“ version with the next update. :-D

[mgflax]

@Lux-Perpetua

Okay, will try to offer a less „childish“ version with the next update. :-D

I must say that I do like some sort of "undulating" border for the non-constant modes.

[sunsethiker]

I was hoping the tower beacon/obstruction mode would make it into Anduril 2.

[mgflax]

@sunsethiker

I was hoping the tower beacon/obstruction mode would make it into Anduril 2.

In all honesty, as long as your flashlight has flashing pads, it really isn't hard at all to build your own firmware image and flash it yourself. My expectation is that ToyKeeper will carefully control which features are part of the default build, but is open to including new features which are hidden behind conditional compilation flags -- so they would only be available in custom builds.

[SammysHP]

Also ToyKeeper was very busy recently and probably hasn’t even looked at the tower beacon code yet.

[Bart07]

Hello. First post. I’ve been reading the forum for weeks, playing with flashlights.

I have a question, can the changes to the fsm-main.c file made for Astrolux ft03 be used with other flashlights, or do I have to compile it separately? Bartosz.

[Tom_E]

Depends. Not familiar with the change. But if you think it can apply to the other lights, then yes - you would have to re-build the app with the proper cfg file for the light you want.

In anduril.c, you change the one line of code that configures the build for a specific light. For example, this is for the first model ROT66:

#define CONFIGFILE cfg-ff-rot66.h

[SammysHP]

The Astrolux FT03 has a different channel mapping and currently requires a small patch: Fix output configuration · SammysHP/flashlight-firmware@68e36b3 · GitHub

This is specifically for the FT03 and won’t work with other flashlights (except they have the same output configuration).