ANDURIL USER MANUAL & LIST OF LIGHTS

Many thanks ToyKeeper for your detailed reply.

I’ve done something similar, which allows me instant access to #1 my most-used level, #2 Moon, #3 High. No other UI allows this AFAIK, because they all allow only automatic memory (which I hate, I don’t want my most-used level superseded by a Moon or a High because this is what I last used).

But I chose to set Floor to 3/150, hence avoiding the LED extinction after going down from High to Moon.

A bit risky if you don't react quickly enough, and your next level after Moon is a bright one (e.g. few steps in stepped ramping mode). I think I'll get used to make a very short "Hold", hence going to Floor and staying at this level before the ramping up starts.

A nice addition to Anduril 2 (maybe it is already planned?) would be a third menu option for the Ramp Config Mode / smooth ramping: ramp speed adjustment. N clicks ==> N seconds between Floor and Ceiling when ramping up.

One more reason for me to plan a future upgrade. I've entered the Anduril world only a few days ago, and I already feel addicted, this UI is so great and configurable that I don't feel anymore like buying lights with a different UI (apart from tiny AAA or 10180 lights). I regret I haven't ordered the reflashing kit from Hank, together with the light. BTW, which lights (apart from Emisar and Noctigon) have a board compatible with this reflashing kit?

Here are the results of a few more measurements:

  • Very hot flashlight (1 min @ Turbo): Anduril: 3.3V going up quickly to 3.5V / Fluke 3.60V
  • After letting it cool down to allow the battery to recover: Anduril: 3.4V / Fluke 3.62V
  • After charging the battery, right off the charger: Anduril: 3.9V / Fluke 4.15V. Same values after a two-hour rest.

The latter value is surprising: I remember doing a battery check immediately when I received my D4v2 with a full battery, and Anduril measured 4.1V.

You are right, for some reason I thought that it use the same MCU…
Anyway I have A17-DD driver with attiny25, so at least swapping it for 85 should be easy :slight_smile:

I don’t know if this is right topic for my questions, but it seems like, so here they are.

1) I got D4V2 with KR4 CC 5A driver (LED - Nichia 219c) and have noticed that it seems like main channel and FET are active together when FET is active (config file - cfg-noctigon-kr4-219.h) - why it is like that? I may be wrong, but shouldn't it be like FET only?

// don't turn off first channel at turbo level
#undef PWM1_LEVELS
#define PWM1_LEVELS 0, ... ,1023


2) I have compared config files for kr4 (cfg-noctigon-kr4.h) and original driver d4v2 (cfg-emisar-d4sv2.h) and found those difference, which makes me question why it's like this (exept differences in configs that I can undestand, like AUX LED in button, soft reset with button and so on - wich root cause are hosts possibilities)

D4V2:
// stop panicking at ~30% power or ~1200 lm
#define THERM_FASTER_LEVEL 105

KR4:
// stop panicking at ~25% power or ~1000 lm
#define THERM_FASTER_LEVEL 100
#define MIN_THERM_STEPDOWN DEFAULT_LEVEL
#define THERM_NEXT_WARNING_THRESHOLD 16 // accumulate less error before adjusting
#define THERM_RESPONSE_MAGNITUDE 128 // bigger adjustments

So, I see different thermal settings and the question is - this difference due to bigger kr4 thermal mass, or the driver itself? In other words, should I change them for my light like in original d4 config (remove them, so ones from fsm will be taken)?

Why 51 for 100/150?

Because 1 is 150.

For 1), this is a totally different driver than a FET+1 - the main LED PWM is not PWM'ing output directly, like it does on 7135's. The very last level has both turned ON probably for a good reason that TK would know best.

For 2), I assume she custom tweaked the settings for the KR4, as she did for the Emisars. Driver and light are both important

If it was me, my best guess would be for your setup of a KR4 driver in a D4V2, I'd go with the KR4 settings.

Thank you for your answer!

For 1 - I tried it myself (disable 1st channel when turbo on and get very weak turbo - so that’s the reason
For 2 - I’ll tried both config entryes and see no difference, so I continue with KR4 config

Hi, i have not found another place for my question. If it’s wrong place i am so sorry, please move. So…

(Fireflies E07)
I measured my room temperature with Fluke… 21C°
I want to calibrate temperature so 21 clicks in current temperature mode.
I left the light overnight.
Next day i want to measure temperature and this is happen…
The first cycle of blinks are 21C° , the second cycle are 16… between the first cycle and second i do not shut off the light… the room temperature is 21

(FW3A)
Now I have set the temperature to 18 (room is 18C°)
Shut off the light…3 clicks than temperature mod… 21 blinks :person_facepalming:

Why?
is correct?
The thermal sensor must give me the room temperature or the light temperature?
I don’t understand so ask to community

Thank you

Before you set room temp in the flashlight, you must do your best to get the flashlight at room temp - that means leaving it sit off for maybe an hour or 2 before setting the temp, and even when you do be sure the light never accidentally goes to a hi mode. What I do is to be sure to press&hold to turn it on at the lowest, ramp up very slightly - turn it off. This assures a lo output when doing the 3 clicks to get into voltage display, then 2C's from there.

Also the first blink of temp is not accurate - thought TK fixed this in a more recent Anduril, maybe just in Anduril2? Not sure. Let it blink out temp 2 times to get a good reading.

I leave overnight… maybe 8H

Why?

Not mine I think

The sequence you described was leaving it over night "after" it was calibrated - you need to stabilize the flashlight temp before calibrated.

Yes, because I have already calibrate one time before i write the first post

I am so sorry for my English… I will try another time and upload thread.

When I was calibrating my SC31pro, just holding it in my hand had the temp increase (on blinkout) 1° and then 2° in just a minute or two, so you need to do it fast. And keep the light overnight right next to a thermometer so you can see at a glance the temperature and let both equilibrate.

Next day or however long, go immediately to the temp blinkout and verify what it tells you vs the thermometer temp. If too different, then again, immediately do the calibration, and another temp blinkout to verify that it stuck.

21°C, holding it in a 37°C hand, it’ll warm up a few degrees very quickly.

Ahh, ok. I forgot the details but I think the first reading was perhaps a bug.

As LB said, it's very sensitive. All these calibration issues go away with the Atmel 1-series (1616, 3216) since they are factory calibrated.

Hi! Could you tell me, https://bazaar.launchpad.net/~toykeeper/flashlight-firmware/fsm/view/head:/ToyKeeper/spaghetti-monster/anduril/cfg-ff-rot66g2.h applied for any ROT66 II on factory (with any Leds?)
And please, could you tell me config for EDC18 and Astrolux HL01

Thank you!

Damn God.
In ~toykeeper/flashlight-firmware/trunk : contents of PRODUCTS at revision 249 HL01 should be Anduril / cfg-mateminco-mt07.h
BUT in ~toykeeper/flashlight-firmware/trunk : files for revision 247 no such cfg file

So, is there any way to discover settings for Astrolux HL01?

Sorry, don't own a HL01, if I did, you'd have the info you want. Dunno if anyone did a tear down to provide details on the driver. Once we know the driver, could probably get the proper Anduril build for it. Unfortunately, Astrolux hasn't communicated well back the the community so TK probably isn't aware of the HL01's Anduril setup.

For the EDC18, I'm sure I have, or could make an Anduril cfg file for it. Just checked - back in April 2019 I did a custom config for Anduril 1.1 on the EDC18, adding support for the AUX/switch LED. I rewired the switch LED so Anduril controls it.

Thank you for your answer. Is this modding reviewed anywhere here in detail?

Hhhmmm, good Q. Here's my EDC018 pic album: https://app.photobucket.com/u/TomE2012/a/a12dfc4e-d6a7-4530-8520-0dbfc3591a50

It shows the mod.

you just add this wire to 1 leg of controller?