Anduril ... 2?

156 posts / 0 new
Last post
Dekzter
Offline
Last seen: 14 hours 14 min ago
Joined: 01/30/2020 - 17:51
Posts: 19
ToyKeeper wrote:
There’s also a question of what 2H should be. It’s currently “go to ceiling and ramp down”, but maybe it doesn’t have to be. It’s nice for symmetry and consistency, but I never really use it and I’m not sure if anyone else does either. Perhaps it could be mapped to something else instead. There’s no shortage of other functions which could benefit from a shorter button mapping.

This is a great idea TK! The 2H shortcut is so easily accessible but it currently does something mostly useless (IMO). Perhaps this could be used to go straight to Turbo from Off?

Klayking wrote:
Stepped ramp: 3 levels. Low is level 25 (~20Lm), high is level 105 (~1000Lm). This puts the middle level squarely on the max regulated level of 65 (~150Lm).

The customization options of Andúril are fantastic.

Pretty slick setup Klayking! I’m constantly tweaking mine as well. I like what you’ve got going on here and I’ll probably adopt something similar. I’ll likely use stepped mode to have a dedicated max regulated level as that will let me take advantage of the efficiency without having the blink in smooth ramp. I’d like more than 3 steps though so I’ll have to do some math Smile

Agro
Agro's picture
Offline
Last seen: 57 min 10 sec ago
Joined: 05/14/2017 - 11:16
Posts: 6169
Location: Ślōnsk
ToyKeeper wrote:
Lux-Perpetua wrote:
toggle between a safe, conservative and a high performance setting…
M4D M4X wrote:
Muggle mode could have a lower (fixed) Templimit

Not sure about having two temperature limits in regular modes, but perhaps it could do something like set the Simple UI temperature limit 5C or 10C lower than the Advanced UI limit?

However, given the issues with factory calibration (or lack thereof), that means a much higher chance that the Simple UI would think it was always overheating. So it could be a significant usability issue for the people the update is intended to help the most.

It’s something to at least keep in mind though, since a lower limit in simple mode would help with the goal of safety.

bquinlan wrote:
Put the change from ramping to steps into the configuration menus so that it’s harder to toggle by accident.
Anthon wrote:
no more 3 clicks from on to change between stepped /smooth ramping

I’d like to keep that one easily accessible, in part because I use it a lot. It’s supposed to be quick and easy to switch between ramp styles. Have heard from a few other people who switch back and forth a lot too, like what Klayking mentioned earlier.

Klayking wrote:
the ability to explicitly set stepped levels.

This is much more tricky.

Probably won’t happen in Anduril, because the UI for it would be a huge pain to use. A big part of why it works the way it does now (floor, ceiling, number of steps) is to avoid setting the levels explicitly. I’ve never seen a UI implement that well without requiring a separate configurator app, and a configurator isn’t feasible on most of the lights Anduril supports.

If you can think of a really slick way to configure the levels though, perhaps it would be feasible.

Lux-Perpetua wrote:
immediately step down when placing something in front of the flashlight

Agro wrote:

  • include cell to make sure it’s a good one
  • include charging so there’s little incentive to remove the cell
  • lock the cell inside so it can’t be removed without a special tool
  • make physical design that makes accidental activation unlikely
  • add features like the already mentioned output reduction when the light is close to some object.

varbos wrote:
How about an app – PC or phone – where you choose your UI preferences

YogibearAl wrote:
program from the USB port?

I can’t add these with a firmware update. They require hardware features which don’t exist on most (or all) of the lights Anduril supports.


Yes. But your feedback matters to manufacturers.
If you feel something listed above makes sense you can communicate that to them – and it’s likely that some future hosts will get such support.
Klayking
Klayking's picture
Offline
Last seen: 1 week 1 day ago
Joined: 12/17/2018 - 09:54
Posts: 154
Location: England
ToyKeeper wrote:
Klayking wrote:
the ability to explicitly set stepped levels.

This is much more tricky.

Probably won’t happen in Anduril, because the UI for it would be a huge pain to use. A big part of why it works the way it does now (floor, ceiling, number of steps) is to avoid setting the levels explicitly. I’ve never seen a UI implement that well without requiring a separate configurator app, and a configurator isn’t feasible on most of the lights Anduril supports.

If you can think of a really slick way to configure the levels though, perhaps it would be feasible.

I agree, coming up with a slick system for this on a single button UI is tricky. Here’s the simplest I can think of:

  1. Enter step config mode with whatever shortcut is used and the light will flash once then start buzzing as it currently does.
  2. In config mode, press nothing: the buzzing will stop and config will exit.
  3. In config mode, press once to set the lowest step at output level 1, and keep clicking to raise the level of this lowest step.
  4. When happy with the lowest step’s output level, wait a moment and the light will flash twice to indicate step 2 config is starting, followed by more buzzing.
  5. Step 2’s config will start at the same level you clicked to when setting the first level. Clicking nothing will cause the config to exit and save your single step. Clicking once will advance to one level beyond the first step, and more clicks will keep moving up in brightness.
  6. Repeat the process of adding more steps, each brighter than the last until you no longer want any more steps. Allow config to exit.

Thanks to continuing on from the last step, I don’t think this will be anywhere near as painful to config as my initial idea of bashing out a number of steps, then a number between 1 and 150 for each step. I can’t see this taking appreciably longer than the current step setup to configure, though there is indeed a slight increase in complexity. As this would be located within the advanced mode though, I think the extra control over your stepped levels would be worth it. I’m interested to hear what everyone else thinks about this though.

Poguche
Offline
Last seen: 8 hours 42 min ago
Joined: 11/18/2018 - 10:23
Posts: 47
Location: Spain

ToyKeeper wrote:

This is much more tricky.

Probably won’t happen in Anduril, because the UI for it would be a huge pain to use. A big part of why it works the way it does now (floor, ceiling, number of steps) is to avoid setting the levels explicitly. I’ve never seen a UI implement that well without requiring a separate configurator app, and a configurator isn’t feasible on most of the lights Anduril supports.

If you can think of a really slick way to configure the levels though, perhaps it would be feasible.

I think this is neat, and have an idea.

First, to have less levels only for this menu (let’s say 30, with a known level for each mode that doesn’t use PWM, so you have a reference. Maybe with a formula you can relate the levels from the 30 ramp and the 150 ramp, like multiplying by 5, except level 1 that remains the lowest). This reduces the ammount of clicks and still allows room for enough choice.

You enter configuration and on the first ‘buzz’ you enter the number of modes (also allowing a single mode, that would be nice). Now it asks as many ‘buzzs’ as modes you have put, and you just click from 1 to 30.

If you configurate more modes than you had previously, it remembers the modes you had on first place (if you don’t touch anything during the buzz), and adds more on top. If you eliminate modes, it eliminates starting from up, and deleting the highest ones. You can also edit just one mode, leaving the rest as it was just like you can do now.

For a typical 4 mode configuration, let’s say that you need about 4 + 2 + 7 + 12 + 25 = 50 clicks as an example. With the current interface, seleting 4 modes, floor on level 10 and ceilling on level 125 you need 4 + 10 + 26 = 40 clicks. Not that much of a difference and you get to choose with more flexibility, although you give up your 150 levels (just for stepped, not for ramp). You can’t stop that precisely on the ramp anyways.

In addition, you can even configure special modes, such as candle mode, to numbers higher than 30, or with holds instead of clicks. The brightness of said candle mode (or freq of strobe or beacon…) would be adjusted from the original special mode location.

Maybe this last thing is overcomplicating it Silly .

treellama
Offline
Last seen: 43 min 39 sec ago
Joined: 12/08/2018 - 21:20
Posts: 183
Location: Pittsburgh

I’d like to see LVP for indicator lights. I think it was on your list before, pending a rewrite, and this is a rewrite Smile

JaronRH
Offline
Last seen: 46 min 40 sec ago
Joined: 04/06/2020 - 14:29
Posts: 32
Location: PA, USA

If we’re talking about breaking changes, I’d like to really push the envelope and suggest something really different! As more and more flashlights are including built-in charging via USB, I think it would be great to use the USB interface for configuration as well. The most versatile method would be to have the USB interface mountable as a flash drive. That drive could contain 1 (or more) configuration files (JSON?) that define the configuration, available modes, etc. This way, anyone could use their computer to modify the configuration (directly or using a GUI). Could even allow developers to flash updates over the USB interface too!

This would solve the problem of accidentally getting into configuration mode, allow for broader updates, and allow for easier control of the configuration. Not to mention, you could share configuration templates.

RB2021
Offline
Last seen: 3 weeks 2 days ago
Joined: 07/07/2020 - 23:59
Posts: 6

JaronRH wrote:
If we’re talking about breaking changes, I’d like to really push the envelope and suggest something really different! As more and more flashlights are including built-in charging via USB, I think it would be great to use the USB interface for configuration as well. The most versatile method would be to have the USB interface mountable as a flash drive. That drive could contain 1 (or more) configuration files (JSON?) that define the configuration, available modes, etc. This way, anyone could use their computer to modify the configuration (directly or using a GUI). Could even allow developers to flash updates over the USB interface too!

This would solve the problem of accidentally getting into configuration mode, allow for broader updates, and allow for easier control of the configuration. Not to mention, you could share configuration templates.

While that sounds amazing, I think it would require some significant hardware changes. If there’s no flash storage/USB controller built in and I doubt any lights on the market have this, then there’s nothing to program this feature set for. I’m not an expert on flashlights though just my take as a computer nerd.

JaronRH
Offline
Last seen: 46 min 40 sec ago
Joined: 04/06/2020 - 14:29
Posts: 32
Location: PA, USA
Quote:
While that sounds amazing, I think it would require some significant hardware changes. If there’s no flash storage/USB controller built in and I doubt any lights on the market have this, then there’s nothing to program this feature set for. I’m not an expert on flashlights though just my take as a computer nerd.

You are right. There would need to be a USB host added to handle the communications (such as the MAX3421E). There is storage available though it is probably just EEPROM and not flash. (I personally have no experience with flashlight firmware – although I’ve looked at the Arduino code. I primarily work with ESP8266 and ESP32 chips which have WiFi. I can store files on the flash as well as host a full website for configuration.)

Additional ideas: – Add support for OLED display’s to show things like level, battery, etc.

mr_magoo
Offline
Last seen: 2 days 21 hours ago
Joined: 08/31/2018 - 14:01
Posts: 131
Location: Colorado

First of all, thank you for all of your hard work bringing us these awesome U/Is!

I love anduril and have gotten really used to it but would still love to see you offer a second version. We would get used to it pretty quickly im sure.

I havent yet read through all the comments so I dont know if this has been mentioned.

Could we pretty please have a simple version of anduril that:

1) Is always automatically locked out after turning off? Unlock would be a double click, which also turns it on to a level you can choose. Always just a double click to turn on the light. This will solve all accidental turn ons and eliminate so many button presses for theose who use lockout regularly. (Another way of putting is is one click is batt check, 2 clicks turns on light to memorized mode)

2) Still has quick, easy access to full brightness?

This would be achieved by using the following:

From off:
•One click would give a moonlight level bat check and would be a notice that light is locked out.

Momentary with hold down when locked out, as usual.

•3 short clicks, instead of being batt check from off, goes to top of ramp.

•3 click +1hold goes to strobe.

•4 clicks from off goes straight to turbo.

From on:

•One click turns off.

•Double click toggles between turbo and memorized mode.

•3 clicks to toggle stepped /smooth ramping just like old anduril.

•2 clicks +1 hold= tint ramping just like old anduril.

All other functions gone, or in a more advanced u/i that is hard to access.

I dont like lights that have a hard to access buttons like in zebralights. Though they are nice for keeping the light from turning on accidentally, they are hard for my fat fingers to operate easily when there are multiple button presses needed, especially when cold and/ or when wearing gloves (which is the case alot here in the icebox of Colorado) so that’s why I like the fw series so much. But the accidental turn ons are an hourly thing with me if I dont lock out. Its a little tedious having to click 5 times each time i want to use the light (quad click to lock or unlock,+ one click to either turn on or off, plus another to adjust brightness if neccessary. Thats alot of clicking every time I want to use my light (which is alot, every day).

Whezzel
Whezzel's picture
Offline
Last seen: 19 hours 5 min ago
Joined: 03/29/2019 - 22:15
Posts: 5
Location: Texas
manithree wrote:
I’ve actually considered doing #1 myself, but I still haven’t gotten the source from banggood for the EC03.

Check out this post: http://budgetlightforum.com/node/73469

It has info related to the firmware that runs on different lights, and how to find the source code.

patmurris
patmurris's picture
Offline
Last seen: 3 hours 1 min ago
Joined: 12/22/2014 - 15:54
Posts: 1596
Location: Nice, France

Thanks Toykeeper for all the work and dedication on these flashlight Uis, and thanks also for reading and pondering all our comments.

I like Andùril, but am far from being an expert. I barely use the basic stuff – long press to floor, ramping, double click for turbo, three clicks for battery check… I sort of memorized how to set aux leds or start candle mode, but have never gone into any setting adjustment or calibration. Frankly i feel like i’ve dropped into a geek fest of some sort here.

If i may deviate a bit from the accepted logic that everyone can click, click hold, long click or double/triple/quadruple click or else… i’d say that in my experience, a lot of people cannot distinguish a single fast click from a long or “hold” one. I see people pressing the button like they want to squeeze something out of it and it will register as a 1H although it was supposed to be a 1C.

A lot of people don’t expect a flashlight to have different modes or brightness. They just grab it because they need light, press the button, sometime with a very strong intention, and expect to have a decent amount of light to help them right now, without learning a UI diagram or practicing how to properly click that button. If they don’t get what they want they’ll click again until.

A simple UI should take that into account IMO.

PS: i agree with not renaming it. Andùril 2 or something would be more appropriate and productive then a totally new name.

slowtechstef
slowtechstef's picture
Offline
Last seen: 3 weeks 4 days ago
Joined: 02/17/2018 - 12:39
Posts: 219
Location: the Netherlands

Plasticity, in the philosophical sense as “a capacity to receive form and a capacity to produce form”. In my view, that is what makes Andúril both unique and challenging, relative to current flashlight firmwares. One of the derivates of plasticity is the issue of programmability as a double-edged sword. I will try to elucidate this when I have more time.

loneoceans
loneoceans's picture
Offline
Last seen: 2 weeks 23 min ago
Joined: 01/08/2017 - 00:18
Posts: 205

ToyKeeper,

Thanks so much for your continued development on Anduril and other flashlight firmwares. It's a lot of work and I'm sure the community has benefited greatly from all your work! 

I'll leave the UI suggestions to more experienced members here, but generally I like the list of proposed changes already. The only items I can suggest are not quite UI based, but just from some of the work stemming from the Lume flashlight drivers... so I'm not sure if they are that relevant or not for this thread.

  • Native support for enable pin in a more granular fashion - the current Anduril implementation for some of the new Emisar lights has most of the functionality but leaves EN high when it doesn't need to be, for example during FET usage. For the Lume driver I had to add some custom conditionals in code to turn it off when not being used. 
  • Support for external algorithms in separate cfg file, e.g. a temperature management system - I'd like to implement a fuzzy logic temperature compensation for example
  • Support for external sensors in separate cfg file e.g. external temperature sensor which is implemented for Lume driver, with custom temperature formula definition

That said, Anduril is already super full-featured; anything additional is just a bonus Smile

Thank you

www.loneoceans.com/labs/

lume1 - Constant Current BuckBoost + FET Anduril Driver for FW3x
High Power Boost Drivers - GXB100 100W GAN FET Driver // GXB172 50W 17mm Driver
GXF22 - CC+FET for Emisar D4 // GFS16 - 1milliOhm FET Switch System // Older: GXB17 & GXB20

Lexel
Lexel's picture
Offline
Last seen: 3 weeks 3 days ago
Joined: 11/01/2016 - 08:00
Posts: 5889
Location: Germany

SKV89 wrote:
OMG, that’s exactly what I’ve been waiting for! 8 clicks and Hold to get into config would be perfect! My kids love to keep clicking on/off/on/off/on/off… on some of my flashlights. This way there’s no way someone can accidentally enter config.

Also I would still love to have a way to get directly to turbo from off. Double click to turbo or maybe double click to top of ramp and triple click to turbo.

You can change the config clicks to 10 or so in the code quite easily, CRX does that on his lights so ramp config is more hidden

the main question is if this means going to another MCU with more memory in the end as 8kb are too small then

BurningPlayd0h
BurningPlayd0h's picture
Online
Last seen: 4 min 2 sec ago
Joined: 06/22/2018 - 02:16
Posts: 1372
Location: MN
ToyKeeper wrote:
It could perhaps do “low-floor high-floor” when manual memory is off, or “low-floor manual-mem” when manual memory is on?

That would be perfect IMO!

Agro
Agro's picture
Offline
Last seen: 57 min 10 sec ago
Joined: 05/14/2017 - 11:16
Posts: 6169
Location: Ślōnsk

loneoceans wrote:
  • Support for external sensors in separate cfg file e.g. external temperature sensor which is implemented for Lume driver, with custom temperature formula definition


  • That said, Anduril is already super full-featured; anything additional is just a bonus Smile


    Thank you


    Some time ago I suggested moving them to FSM to simplify building of other UIs.
    I still think it would be a good idea.
    sochi111
    sochi111's picture
    Offline
    Last seen: 2 days 22 hours ago
    Joined: 02/21/2017 - 14:59
    Posts: 237

    It would be great to have a lightshow sequence just like the Tesla Party

    Crazy…
    Klayking
    Klayking's picture
    Offline
    Last seen: 1 week 1 day ago
    Joined: 12/17/2018 - 09:54
    Posts: 154
    Location: England

    Put microphone in flashlight, make it flash to music.

    Then Facebook will buy it out and use it to spy on you.

    tekwyzrd
    tekwyzrd's picture
    Offline
    Last seen: 24 min ago
    Joined: 11/14/2015 - 01:15
    Posts: 1261
    Location: Northeastern Ohio

    if it hasn’t been said fork it. anduril and simplified version with new name ( i’d suggest Mjölnir ).

    Nothing travels faster than the speed of light with the possible exception of bad news, which obeys its own special laws. – Douglas Adams

    ToyKeeper
    ToyKeeper's picture
    Offline
    Last seen: 12 hours 37 min ago
    Joined: 01/12/2013 - 14:40
    Posts: 10433
    Location: (469219) 2016 HO3

    Have been making some good progress today…

    • Removed muggle mode, and replaced it with a “simple UI” overlay which restricts which actions are available
    • Made simple UI enabled by default (and after each factory reset)… unless the config file specifies otherwise (so it can be default or not, per build target)
    • Made it so the simple UI use a smooth or stepped ramp
    • Created configurable floor/ceiling/steps vars for simple UI, but didn’t add a menu to actually configure it yet
    • Refactored a lot of ramp-related code
    • Made battcheck exit after one readout, when in simple UI
    • Added 4C from lockout to on (mem)
    • Added 4H from lockout to on (floor)
    • Added 5C from strobes to momentary
    • Moved all aux LED / button LED config actions to 7C / 7H, to make it consistent
    • Moved all config modes / menus to 7C, to make them harder to reach by accident (also, more consistent with aux config)
    • Removed beacon config mode… basically, instead of “click N times” to set the timing in a menu, it’s “hold for N seconds” to set the timing whenever beacon mode is active
    • Reduced overall size by 190 bytes

    There is still much more to do, but this has been a good start.

    BOMBAY
    Offline
    Last seen: 2 hours 35 min ago
    Joined: 04/24/2016 - 10:07
    Posts: 185
    Location: Polska

    add the best function from the Narsil software, i.e. the ability to disable thermal control will save a lot of trouble for some models and their users

    lionheart_2281
    lionheart_2281's picture
    Offline
    Last seen: 3 days 14 hours ago
    Joined: 10/25/2012 - 18:32
    Posts: 3033
    Location: Brisbane, Australia

    I’m scared of the idea that it’ll change because to me it’s soooooooooooo perfect already

    ikkentobi
    Offline
    Last seen: 1 day 11 hours ago
    Joined: 11/18/2016 - 13:02
    Posts: 80
    Location: Bavaria

    This sounds very promising.

    Quadrupel
    Quadrupel's picture
    Offline
    Last seen: 33 min 40 sec ago
    Joined: 12/03/2017 - 10:40
    Posts: 249
    Location: Lithuania

    In stepped mode would be nice to have ability to control space in between steps. Fo example 1ma- 5mA – 20mA 50mA – 350ma – 1A – 3A

    jon_slider
    jon_slider's picture
    Online
    Last seen: 5 min 20 sec ago
    Joined: 09/08/2015 - 12:20
    Posts: 3228
    Location: The Land of Enchantment

    Quadrupel wrote:
    In stepped mode would be nice to have ability to control space in between steps. Fo example 1ma- 5mA – 20mA 50mA – 350ma – 1A – 3A

    my understanding is individually programmable modes (steps) are not something Anduril is going to offer.

    see
    http://budgetlightforum.com/comment/1673525#comment-1673525

    Quadrupel
    Quadrupel's picture
    Offline
    Last seen: 33 min 40 sec ago
    Joined: 12/03/2017 - 10:40
    Posts: 249
    Location: Lithuania

    UI with individually programmable modes will be the best and ultimate UI ever made . Everyone will be happy LOL

    Rexlion
    Offline
    Last seen: 2 hours 16 min ago
    Joined: 05/18/2019 - 16:59
    Posts: 702
    Location: Okla.

    I think ‘simple’ mode should be more simple. Really basic. Click on, click off, or hold to ramp. That’s it. After all, that is really the only thing a muggle will be interested in. We flashaholics are so used to fantabulous features, we’ve forgotten what it was like to be a muggle. Anything but on/off/change levels is more than they want to absorb.

    Not that I loan out my flashlights enough to make it matter to me personally. But I gave away a Nitecore EA41 recently along with a copy of the instructions, and the couple was intimidated by the fact that “it’s so complicated, it comes with instructions.” Facepalm That really made me stop and think. The EA41 UI is not complicated.

    Personally, I think it’s getting to a point where we may soon need to add in a feature where we click/hold a certain number and the light projects (in the beam on a white wall) the instruction manual! LOL

    ToyKeeper
    ToyKeeper's picture
    Offline
    Last seen: 12 hours 37 min ago
    Joined: 01/12/2013 - 14:40
    Posts: 10433
    Location: (469219) 2016 HO3
    Quadrupel wrote:
    In stepped mode would be nice to have ability to control space in between steps. Fo example 1ma- 5mA – 20mA 50mA – 350ma – 1A – 3A

    The steps aren’t individually-programmable, but they do accelerate up along a curve like what you described. They are spaced evenly along the ramp, but the ramp itself is curved.

    The curve shape is different for each light though, calibrated to make it feel similar despite large differences in the underlying hardware. Except, of course, on lights where the manufacturer didn’t bother doing that and just copied firmware from another light. Those end up with weird ramp shapes and sub-par thermal response.

    Quadrupel wrote:
    UI with individually programmable modes will be the best and ultimate UI ever made . Everyone will be happy LOL

    There are lights which work this way. They typically either come with a separate configurator app (which isn’t possible for most Anduril-based lights) or they take a long time to program… like an hour tapping buttons with the manual. Most people never bother configuring those because it’s too complicated.

    However, a separate UI could be created which allows each step to be whatever the user wants. It could also allow user-defined button mappings similar to the YLP Unicorn. I think Inferion had a good idea there, and really put a lot of functionality into a small space. But if something like that is made, it would be a different UI, not Anduril.

    One of the things I’m doing with Anduril2 is to break the code into smaller pieces so it’ll be easier to maintain and easier to reuse parts in other UIs. So that may be helpful when attempting to create something more configurable for power users.

    ToyKeeper
    ToyKeeper's picture
    Offline
    Last seen: 12 hours 37 min ago
    Joined: 01/12/2013 - 14:40
    Posts: 10433
    Location: (469219) 2016 HO3
    Rexlion wrote:
    I think ‘simple’ mode should be more simple.

    That’s a big part of why I made this thread. I’m hoping to answer the question of “what should the simple UI be like?”

    The old muggle mode was just click for on/off and hold to ramp. Or a longer button sequence to exit. Nothing else. But people often said it was too simple, and they wanted to be able to check the battery status or lock the light or configure the ramp so it wasn’t stuck at factory settings.

    So for now, that’s basically what the new simple UI is. The currently-enabled functions are:

    • Ramp:
      • Click for on/off
      • Hold to change brightness (or press-release-hold to ramp down)
      • Double click to go to/from the top level (no turbo)
    • Battery check (3C)
    • Lockout (4C)
    • Long button sequence to go to advanced mode
    • Even longer button sequence to check the firmware version
    • Factory reset (hold button a few seconds while inserting battery)

    It also respects settings configured in advanced mode, like the smooth/stepped ramp style, manual memory vs automatic memory, and (eventually) floor/ceiling levels. But those require going to advanced mode and back, so they don’t really affect anything for muggle purposes.

    Are these the right features to have in simple mode? I don’t know. That’s what I’m hoping to find out.

    ikkentobi
    Offline
    Last seen: 1 day 11 hours ago
    Joined: 11/18/2016 - 13:02
    Posts: 80
    Location: Bavaria
    ToyKeeper][quote=Rexlion wrote:
    Are these the right features to have in simple mode?

    I’d remove the lockout. It is not really necessary, and might be a pain for beginners to get out again.
    However, the battery check is a very useful feature, and not problematic when activated unintentional.

    Pages