Anduril ... 2?

211 posts / 0 new
Last post
AEDe
AEDe's picture
Offline
Last seen: 1 day 27 min ago
Joined: 12/01/2016 - 12:07
Posts: 628
Location: Moscow

ChibiM wrote:

with a special combination. (10 clicks for example) 

It will be the first combination that kid press))
CRX
CRX's picture
Offline
Last seen: 1 hour 6 min ago
Joined: 04/02/2013 - 15:27
Posts: 4195
Location: Scotland

ChibiM wrote:
All configuration modes only reachable from OFF with a special combination. (10 clicks for example)
Yeah Thumbs Up
ChibiM
ChibiM's picture
Offline
Last seen: 4 hours 2 min ago
Joined: 05/09/2011 - 10:25
Posts: 6356
Location: Holland

AEDe wrote:
ChibiM wrote:
with a special combination. (10 clicks for example) 
It will be the first combination that kid press))

It was an example. How about 7? Wink

manithree
Offline
Last seen: 58 min 49 sec ago
Joined: 01/12/2013 - 01:08
Posts: 444
Location: Orem, UT, USA
ChibiM wrote:

AEDe wrote:
ChibiM wrote:
with a special combination. (10 clicks for example) 
It will be the first combination that kid press))

It was an example. How about 7? Wink

I’m liking the music examples. How about you have to tap the rhythm to the trumpet solo from Stevie Wonder’s “Sir Duke” to get to config.

Tap some 7/4 John Bonham for rock lock-out.

AEDe
AEDe's picture
Offline
Last seen: 1 day 27 min ago
Joined: 12/01/2016 - 12:07
Posts: 628
Location: Moscow

I like this idea)

Another opinion to enter in config by hold during twisting tailcap.

ToyKeeper
ToyKeeper's picture
Offline
Last seen: 31 min 42 sec ago
Joined: 01/12/2013 - 14:40
Posts: 10458
Location: (469219) 2016 HO3
pol77 wrote:
I would like some way to set the brightness of the auxiliary and the switch LEDs on my D4V2 Ti. The dimmer option for these is way too bright for nightstand duty

Sorry, I can’t do that in firmware. The brightness is determined by hardware, not firmware. So there are only three brightness settings:

  • High: Power on, internal resistor off.
  • Low: Power on, internal resistor on.
  • Off: Power off.

It can control whether the power is on or off… and whether the control chip’s internal resistor is added into the circuit to reduce brightness. But it can’t control how much.

ToyKeeper
ToyKeeper's picture
Offline
Last seen: 31 min 42 sec ago
Joined: 01/12/2013 - 14:40
Posts: 10458
Location: (469219) 2016 HO3
ChibiM wrote:
All configuration modes only reachable from OFF with a special combination. (10 clicks for example)

Instead of a few short menus attached to the mode they configure, at 1 to 3 items each… you would prefer one long menu with about 10 to 20 items?

At last count, there were 21 config values… of which about half are set from a menu and half are set using some other action. The number changes over time though, as things are added and removed.

AEDe wrote:
enter in config by hold during twisting tailcap.

How would people configure lights which are physically incapable of this?

It uses “hold while connecting power” for factory reset, on most lights… so it would need another way to do that. And it would need to be really easy to do, since it’s a safety net for new users.

AEDe
AEDe's picture
Offline
Last seen: 1 day 27 min ago
Joined: 12/01/2016 - 12:07
Posts: 628
Location: Moscow

ToyKeeper wrote:
AEDe wrote:
enter in config by hold during twisting tailcap.

How would people configure lights which are physically incapable of this?

It uses “hold while connecting power” for factory reset, on most lights… so it would need another way to do that. And it would need to be really easy to do, since it’s a safety net for new users.


So it is not user friendly UI I see. Easy config for lite mode is big issue for ordinary user.
ToyKeeper
ToyKeeper's picture
Offline
Last seen: 31 min 42 sec ago
Joined: 01/12/2013 - 14:40
Posts: 10458
Location: (469219) 2016 HO3
AEDe wrote:
Easy config for lite mode is big issue for ordinary user.

The idea for the simple UI is that most people won’t have to configure it… just take it out of the box and turn it on. It has no config options unless the user goes to the advanced UI.

After going to the advanced UI, they’ll be able to configure some settings for the simple UI. However, after going back to the simple UI, it will again not allow changes.

Unheard
Offline
Last seen: 27 min 35 sec ago
Joined: 01/16/2019 - 11:38
Posts: 915
Location: Germany

ChibiM wrote:
All configuration modes only reachable from OFF with a special combination.
Thumbs Up
Tom E
Tom E's picture
Offline
Last seen: 52 min 10 sec ago
Joined: 08/19/2012 - 08:23
Posts: 13127
Location: LI NY

One way to do a power-on/hold the button config and reset, is to do it in 2 timeouts:

  • 3 second hold to enter config mode
  • 5 second hold to reset to factory

At 3 seconds, you could blink, say twice, then the user releases to get into config. If they continue to hold for 5 secs, it does the reset.

Now once you get into config, defining how it works to control 21+ settings (add all those being requested), and it gets insane not sure how this could be accomplished with an intuitive UI, accept maybe use the standard UI with the current config settings. A normal power-up sequence would have no config settings.

This might actually work out well, usability wise, and be relatively easy to implement since it uses the current UI for config settings. This is kind-of/sort-of what TK is saying above with the "simple" and "advanced" UI.

Tom E
Tom E's picture
Offline
Last seen: 52 min 10 sec ago
Joined: 08/19/2012 - 08:23
Posts: 13127
Location: LI NY

TK - I'm not so clear on this. The new voltage reading code, I assume will still be in Vers 2, do you believe it to be good enough to not need individual calibration?

I still have my older Anduril variant with added voltage calib (internal ref only for 1S battery, not voltage divider use for 2S+) and wondering if it's still useful, or are you considering adding it.

 

ToyKeeper
ToyKeeper's picture
Offline
Last seen: 31 min 42 sec ago
Joined: 01/12/2013 - 14:40
Posts: 10458
Location: (469219) 2016 HO3
Tom E wrote:
The new voltage reading code … need individual calibration?

It still needs individual calibration. It’s very stable and consistent now, but if the sensor isn’t calibrated right, it’ll be very consistently the wrong value.

So I have a voltage calibration function on the todo list. It’ll probably be a numeric entry menu attached to the battcheck mode.

ferroplasm
Offline
Last seen: 3 weeks 15 hours ago
Joined: 07/18/2020 - 16:41
Posts: 1
Location: NC

My apologies if this has been suggested – I haven’t read through the entire thread. I’d like to see an option for the lighted switch to have a battery check option. So rather than a simple, steady blink, the switch will periodically broadcast the battery voltage.

To clarify, this would be under the current aux/switch options.

Flashaholics
Flashaholics's picture
Offline
Last seen: 1 week 4 days ago
Joined: 04/05/2017 - 12:46
Posts: 905
Location: Wakefield

I’d like a timer mode like candle mode but with just regular brightness, maybe swap it for one of the annoying strobe modes nobody uses or likes, oh and a working muggle mode.

My 4K Lumen Whore Reviews (MS18, X70, MS12, DX80, X80-GT, X45vn etc) - https://www.youtube.com/c/FLASHAHOLICS_GB

Rexlion
Offline
Last seen: 1 day 16 hours ago
Joined: 05/18/2019 - 16:59
Posts: 704
Location: Okla.

I’d like an Anduril feature that materializes $100 bills in the battery compartment, please. Party

bquinlan
Offline
Last seen: 8 hours 59 min ago
Joined: 04/19/2018 - 01:07
Posts: 119
Location: Madison, Wisconsin, USA
ToyKeeper wrote:
I don’t think that will fit on most attiny85 hosts, but it could be done on chips with more space.

That isn’t too surprising. The way the button-press handling works now is definitely more efficient in terms of code space.

Thought it was worth suggesting, but it is not worth splitting the UI between lights with older and newer chips.

Thanks!

ToyKeeper
ToyKeeper's picture
Offline
Last seen: 31 min 42 sec ago
Joined: 01/12/2013 - 14:40
Posts: 10458
Location: (469219) 2016 HO3

I’m adding a sunset / auto shutoff timer which works in both the ramp mode and in candle mode.

Trying to decide what the button press should be to activate it. In the old version, it was 3C to add 30 minutes… but 3C is already used in ramp mode, to change the ramp style. However, there is nothing on 4C yet, because I moved the config modes.

So this gives me a few options…

  • Use 4C to activate sunset timer. Also adds 30 minutes. (or maybe just 10 minutes?)
  • Use 4H to activate sunset timer. Adds 10 minutes per second until the user lets go of the button. Blinks each time to make it easier to keep track of.
  • Move “change ramp style” from 3C to 4C, and use 3C to activate sunset timer.

Can’t use 2H because that’s used for ramping down. Can’t use 3H because that does tint ramping. So 4H is the shortest hold action available.

For testing, I have it set to 4H… but I’m not sure if it’s the right choice.

Unheard
Offline
Last seen: 27 min 35 sec ago
Joined: 01/16/2019 - 11:38
Posts: 915
Location: Germany

There should be an easy way to adjust beacon brightness. I imagine this is a useful function e.g. when having a car breakdown or worser, an accident. But then is should be easily adjustable by press & hold and double press & hold. Right now I not even have an idea how to adjust it. I’m using manual memory. And the pulses should be shorter. While at it, it should go to the other blinkies-set with memory.

pol77
Offline
Last seen: 8 hours 13 min ago
Joined: 02/21/2019 - 07:54
Posts: 192
Location: London

4C / 4H sounds good to me. How will the config modes be activated now?

ToyKeeper
ToyKeeper's picture
Offline
Last seen: 31 min 42 sec ago
Joined: 01/12/2013 - 14:40
Posts: 10458
Location: (469219) 2016 HO3
Unheard wrote:
There should be an easy way to adjust beacon brightness.

Ramp to the brightness you want, then go to beacon mode.

ToyKeeper
ToyKeeper's picture
Offline
Last seen: 31 min 42 sec ago
Joined: 01/12/2013 - 14:40
Posts: 10458
Location: (469219) 2016 HO3
pol77 wrote:
How will the config modes be activated now?

People have asked for the config modes to be harder to access… so I’m thinking maybe 7C.

  • Ramp -> 7C -> ramp config
  • Tempcheck -> 7C -> thermal config
  • Battcheck -> 7C -> voltage calibration
  • Off -> 7C/7H -> aux LED config
  • Lockout -> 7C/7H -> aux LED config

Or perhaps 6C/6H, since that’s not used any more.

But with maybe one exception. Whatever sequence is used to go from the advanced UI to the simple UI, I’ll probably make the “hold” version of it go to the config mode for simple UI’s ramp.

The details aren’t set in stone.

Unheard
Offline
Last seen: 27 min 35 sec ago
Joined: 01/16/2019 - 11:38
Posts: 915
Location: Germany

ToyKeeper wrote:
Ramp to the brightness you want, then go to beacon mode.

Yes, I know. Still limited by the upper boundary. And just double clicking to max – off – beacon won’t give the intended result. I think this should be changed Smile
jeff51
jeff51's picture
Offline
Last seen: 1 day 17 hours ago
Joined: 03/26/2019 - 17:36
Posts: 527
Location: Middle of Texas

TK,
I vote for a shorter Sunset default. 5 minutes max, Two minutes would be even better.
Or make the initial default timeout programmable.

Just enough time to snuggle down in bed or sleeping bag.
Then extra clicks for more time if desired.
If the shortest timeout is too long, I’m not going to use it.

It needs some sort of indication that the user has activated Sunset correctly.
Also, going into Sunset, there should be no brighter blinks to blast sleepy eyes.

And I’d like Sunset to step down from whatever brightness the light is currently running at, as opposed to always dropping to a low brightness as default.
It’s easy to start the light where you want it at a useful brightness.
Starting at XX brightness – Everybody ready for bed?
Do the Sunset clicks and the ramp down starts from there.

Also I’d like a stepped down vs ramp for the fade out (an option perhaps?). Like the old Eternalight.
The steps remind me that it is going to go out and I need to be ready for that.

All the Best,
Jeff

ToyKeeper
ToyKeeper's picture
Offline
Last seen: 31 min 42 sec ago
Joined: 01/12/2013 - 14:40
Posts: 10458
Location: (469219) 2016 HO3

jeff51 wrote:
I vote for a shorter Sunset default. 5 minutes max, Two minutes would be even better.
Or make the initial default timeout programmable.

Just enough time to snuggle down in bed or sleeping bag.
Then extra clicks for more time if desired.
If the shortest timeout is too long, I’m not going to use it.

It needs some sort of indication that the user has activated Sunset correctly.
Also, going into Sunset, there should be no brighter blinks to blast sleepy eyes.

And I’d like Sunset to step down from whatever brightness the light is currently running at, as opposed to always dropping to a low brightness as default.
It’s easy to start the light where you want it at a useful brightness.
Starting at XX brightness – Everybody ready for bed?
Do the Sunset clicks and the ramp down starts from there.

Also I’d like a stepped down vs ramp for the fade out (an option perhaps?). Like the old Eternalight.
The steps remind me that it is going to go out and I need to be ready for that.

In Anduril 1, sunset used a 1 hour timer with a fixed starting brightness, and candle mode used a timer with 30-minute increments at the user’s chosen brightness level.

Currently in Anduril 2, both use the same timer. It uses 10-minute increments, and starts at whatever level the user ramped to. The process is:

  1. Go to the desired ramp level or candle level.
  2. Do a 4H action (click 4 times, but hold the last one).
  3. Hold until the desired timer duration is reached, then let go to start the countdown.
    • While holding, the light blinks once per second. Each blink adds one timer unit to the duration. If the light is in a low mode, the blinks go up in brightness… but if the light is in a high mode, the blinks go down in brightness. That is to ensure the blinks can be seen regardless of the current level.

So to get the same effect as the old default of 30 minutes, it would be: Click, click, click, press-and-hold, wait for 3 blinks, then let go. (4H, blink blink blink, let go)

The ramp and candle modes may share a timer, but they act a little differently:

  • In candle mode, it runs at the given level until the final minute… and then it gradually dims for a minute and shuts off.
  • In ramp mode, it dims slowly and smoothly during the entire sunset period. The idea is to avoid any sudden changes because that might wake someone up.

The algorithm for “dim slowly and smoothly” changed a bit from old to new versions, but it mostly still looks the same. However, when it gets close to the end, the steps are visible because the hardware’s resolution is coarse at the bottom of the ramp. So it’s usually pretty obvious when it gets to the final minute.

The user can still ramp up and down with the sunset timer active… but it’ll fight back, especially when the timer gets close to zero. So I think perhaps ramping up should also “bump” the timer, instead of continuing with the original deadline.

jeff51
jeff51's picture
Offline
Last seen: 1 day 17 hours ago
Joined: 03/26/2019 - 17:36
Posts: 527
Location: Middle of Texas

ToyKeeper wrote:

The user can still ramp up and down with the sunset timer active… but it’ll fight back, especially when the timer gets close to zero. So I think perhaps ramping up should also “bump” the timer, instead of continuing with the original deadline.

I vote for the “Bump” That makes sense to me.
(And a shorter than 10 minute ramp down – if possible).
All the Best,
Jeff
ToyKeeper
ToyKeeper's picture
Offline
Last seen: 31 min 42 sec ago
Joined: 01/12/2013 - 14:40
Posts: 10458
Location: (469219) 2016 HO3

A quick progress update:

I just hit the point where some build targets are running out of space. So I figured I’d summarize what has been updated so far:

  • Removed Muggle Mode and replaced it with a Simple UI.
    • Simple UI is enabled by default (and after each factory reset). (unless changed at compile time)
    • Simple UI uses a limited-range smooth ramp by default, like Muggle Mode. But advanced users can change this.
    • Simple UI has no turbo function. It can’t go above the ceiling level.
    • Simple UI blocks everything except a few functions: Ramping, battery check, lockout, factory reset, and version check.
    • All config modes are blocked while Simple UI is active.
    • Some settings are inherited from the main ramp: Style (smooth or stepped), aux LED config, manual/automatic memory config.
    • Button mappings:
      • Simple UI 8H -> exit Simple UI and use the full UI instead.
      • Full UI 8C -> go back to Simple UI.
      • Full UI 8H -> configure Simple UI’s ramp settings: floor, ceiling, number of steps.
      • Have been pondering whether it should use 10C/10H instead of 8C/8H.
  • Added some shortcuts for convenience:
    • Lockout 4C -> On (at mem level)
    • Lockout 4H -> On (at floor level)
    • Strobe 5C -> Momentary
  • Added a Sunset Timer in Ramp Mode and Candle Mode. Removed the original Sunset Mode.
    • In either mode, use 4H to turn the timer on and set a deadline. Each blink adds 10 minutes.
    • The time unit is not set in stone. Maybe it could be 5 minutes instead, but then long timeouts (like an hour or two) would be a pain to activate.
  • Added an auto-lock function.
    • If enabled, it goes from Off Mode to Lockout Mode after N minutes of being off, where the user can set N anywhere from 1 to 120 minutes.
    • Button mappings are similar to Manual Memory:
      • To turn on auto-lock: 5C from lockout, then enter a number into the prompt.
      • To turn off auto-lock: 5H from lockout.
    • Undecided question: Should auto-lock still work in Simple UI?
  • Moved Lockout aux LED config from 3C/3H to 7C/7H to make it the same as Off Mode.
  • Moved config modes from 4C to 7C, to make them harder to reach by accident.
  • Removed Beacon Config Mode. Instead, simply hold the button during beacon mode to configure the timing.
  • Added Voltage Calibration Mode.
    • Battcheck 7C -> Voltage Calibration Mode.
    • Allows the user to add or subtract up to 0.30V to the battery measurements, in 0.05V steps. (-0.30, -0.25, -0.20, -0.15, -0.10, -0.05, +0V, +0.05, +0.10, +0.15, +0.20, +0.25, +0.30)
  • Split the code into a bunch of smaller files to keep things cleaner and more manageable.

Three build targets have run out of space, so on these I didn’t include the voltage calibration mode: D18, ROT66G2, MF01-Mini.

Code is in the anduril2 branch if anyone wants to try it: lp:~toykeeper/flashlight-firmware/anduril2

I haven’t attempted to update the documentation yet, or the UI diagrams. I’m waiting until a few more things are decided first.

trakcon
trakcon's picture
Offline
Last seen: 2 hours 9 min ago
Joined: 01/23/2019 - 15:50
Posts: 311

I like the changes. I guess I need to wait on some mods so I don’t have to disassemble again to reflash.

jeff51
jeff51's picture
Offline
Last seen: 1 day 17 hours ago
Joined: 03/26/2019 - 17:36
Posts: 527
Location: Middle of Texas

I vote for 10C/10H, since there are others out there that use that.
I there a reason for 10C vs 10H ?
I would think that 10H would work for going back and forth without the need to remember if I needed a H or C to change things.

Not sure about having lockouts or other functions with just 4C (well maybe strobe).
Does anyone actually need quick access to strobe? Or even use it at all?

Seems like that might be too easy to activate. 4H or maybe 6H seems less likely to the muggles to find by accident.
Clearly you are heading in the right direction vs the current version – Thinks I.
Makes my head spin trying to conceive a simple interface that’s just complex enough. Without accidentally jumping into never never land.

If you are running out of room, maybe sacrifice one of the other entertainment blinkies?
I can see the future now – A-ver 4.01a, only running on 64b OS – 512K flashlights….

All the best,
Jeff

ToyKeeper
ToyKeeper's picture
Offline
Last seen: 31 min 42 sec ago
Joined: 01/12/2013 - 14:40
Posts: 10458
Location: (469219) 2016 HO3
jeff51 wrote:
I vote for 10C/10H, since there are others out there that use that.

That’s kind of the problem. I need to talk to some companies which asked for 10C as a shortcut to thermal config mode. If they don’t mind though, I’ll probably use 10C/10H for Simple UI stuff instead. Thermal config mode isn’t as important now that it can auto-calibrate during factory reset.

jeff51 wrote:
I there a reason for 10C vs 10H ? I would think that 10H would work for going back and forth without the need to remember if I needed a H or C to change things.

A big part of it is so we can tell people to use 10H to make sure they’re not in simple mode… and it won’t really matter whether they’re in it or not. Similarly, 10C to enter simple mode… and it again wouldn’t matter whether it’s already activated.

In the old version, 6C went back and forth between simple and complex. In the new version, 10H always goes toward more complex, while 10C always goes toward more simple. So there is no need to know where you are… only where you want to go.

This is to reduce confusion for both the user and for anyone trying to help the user. One-way actions are less ambiguous than two-way toggles.

jeff51 wrote:
Does anyone actually need quick access to strobe? Or even use it at all?

Some people are pretty passionate about strobe modes, and think even “click, click, hold” is too slow. It’s part of the reason why momentary mode can now also do strobes. That way, it can activate as soon as the button is pressed.

jeff51 wrote:
Seems like that might be too easy to activate. 4H or maybe 6H seems less likely to the muggles to find by accident.

Strobe modes aren’t enabled at all in the Simple UI. They’re completely blocked.

jeff51 wrote:
If you are running out of room, maybe sacrifice one of the other entertainment blinkies?

The general approach I’m using is… supported lights get as many of the new features as possible without removing old features.

Anyway, anything with attiny1634 still has plenty of room. It’s only a few tiny85-based lights which require compromises. And depending on how some other optimizations go, I might still be able to fit everything. I’ve noticed a couple more things I may be able to reduce in size…

Pages