TK's Emisar D4V2 review

1916 posts / 0 new
Last post
azhu
azhu's picture
Offline
Last seen: 12 hours 38 min ago
Joined: 09/24/2015 - 06:48
Posts: 229
Location: Los Angeles, CA

mikekoz wrote:
I just got one of these. How do you turn off the rainbow mode when the light is off??? It is annoying!! Angry

7 quick clicks will cycle through the different secondary modes.
6 quick clicks with a 7th click/hold will cycle through the colors.

Example to change through the modes:
click-click-click-click-click-click-click, pause. Repeat to go to the next mode.

Example to cycle though the colors of the current mode:
click-click-click-click-click-click-click and hold, release when desired color is showing.

Need Nichia 219b r9080 Emitters? (。◕‿◕。)

“The Light shines in the darkness, and the darkness did not comprehend it.” John 1:5

ikkentobi
Offline
Last seen: 6 hours 42 min ago
Joined: 11/18/2016 - 13:02
Posts: 72
Location: Bavaria

And there is a similar configuration for locked out mode.

For off mode I use the battery indication mode, which I find quite useful. It displays blue aux LEDs as long as the battery is well charged, and after this displays green or even red.

DarkShot
DarkShot's picture
Offline
Last seen: 9 hours 52 min ago
Joined: 02/11/2019 - 16:15
Posts: 76
Location: Canada
ToyKeeper wrote:
Unheard wrote:
I’d flash your Andúril-version for Nichia before swapping emitters.

That might still run too hot though, since it’s calibrated for 219C instead of 219B. The newer emitter can handle a lot more power.

Just for reference in case anyone else is wondering, I’m running a 60% FET max build on a FW3A with D220 219Bs without any issues and plan on running a 60% build on my D4v2 when I swap in a set of 219Bs. The 219 build variant posted in FSM is limited to 75% FET max iirc.

mikekoz
Offline
Last seen: 2 months 6 days ago
Joined: 10/03/2013 - 09:32
Posts: 18
Thanks! That did the trick!! Thumbs Up

Cranston B. Snord

ToyKeeper
ToyKeeper's picture
Offline
Last seen: 1 hour 2 min ago
Joined: 01/12/2013 - 14:40
Posts: 10245
Location: (469219) 2016 HO3

FWIW, I’m hoping to make it default to voltage mode instead of rainbow mode.

Rainbow was a way to show off the RGB feature, but voltage mode is a lot more useful.

bquinlan
Offline
Last seen: 13 hours 43 min ago
Joined: 04/19/2018 - 01:07
Posts: 100
Location: Madison, Wisconsin, USA
ToyKeeper wrote:
FWIW, I’m hoping to make it default to voltage mode instead of rainbow mode.

I like this plan! That is the auxiliary mode I normally use on all my lights.

Unheard
Offline
Last seen: 2 days 16 hours ago
Joined: 01/16/2019 - 11:38
Posts: 395
Location: Germany
DarkShot wrote:
ToyKeeper wrote:
Unheard wrote:
I’d flash your Andúril-version for Nichia before swapping emitters.

That might still run too hot though, since it’s calibrated for 219C instead of 219B. The newer emitter can handle a lot more power.

Just for reference in case anyone else is wondering, I’m running a 60% FET max build on a FW3A with D220 219Bs without any issues and plan on running a 60% build on my D4v2 when I swap in a set of 219Bs. The 219 build variant posted in FSM is limited to 75% FET max iirc.


Thanks a lot! Do you know the current that 60% translates to?

Now I have to find someone building the binary for me Facepalm

Unheard
Offline
Last seen: 2 days 16 hours ago
Joined: 01/16/2019 - 11:38
Posts: 395
Location: Germany

ToyKeeper wrote:
FWIW, I’m hoping to make it default to voltage mode instead of rainbow mode.

Rainbow was a way to show off the RGB feature, but voltage mode is a lot more useful.


Yes!

Is the 0-8-15 temperature regulation code already implanted in your sources?

Agro
Agro's picture
Online
Last seen: 1 min 10 sec ago
Joined: 05/14/2017 - 11:16
Posts: 5767
Location: Ślōnsk
bquinlan wrote:
ToyKeeper wrote:
FWIW, I’m hoping to make it default to voltage mode instead of rainbow mode.

I like this plan! That is the auxiliary mode I normally use on all my lights.


Same here.
trakcon
trakcon's picture
Offline
Last seen: 45 min 24 sec ago
Joined: 01/23/2019 - 15:50
Posts: 249
ToyKeeper wrote:
Mark M wrote:
Yes, older lights do not have LVP for aux LEDs. TK corrected me below.

You got it right the first time. Smile

Older lights don’t have LVP for aux LEDs. That’s new.

The missing-clicks thing is an old issue though. It just seems to be a bit more noticeable when it wakes up to check voltage, since that takes longer than the usual sleep ticks.

I’m hoping to get to the bottom of it soon though, since I should finally have hardware which is capable of triggering the issue in a reliable manner.

Forgive me if I missed this somewhere, but is this still an issue? I’ve noticed that my D4V2 Ti misses clicks sometimes. It’s kind of annoying when I try to unlock it, but instead change the aux mode. I love the light (and Anduril) otherwise, though!

Nav88
Offline
Last seen: 2 months 4 days ago
Joined: 10/30/2017 - 19:51
Posts: 32

I’ve noticed what may be considered a bug in Anduril. It occurs with my D4v2 and my FW1A. The issue is related to shortcutting to turbo from a ramping mode and then shortcutting back to ramping from turbo.

If the light is on at an arbitrary ramping level, a double click switches to turbo and then a second double click returns to ramping at the level it was last at. This seems to be the behavior regardless of the ramping level.

However, if I double click from off to shortcut to the highest ramping level, then double click a second time to turbo, and finally double click a third time to return to ramping, it sends me to the default ramp level (the single click from off level) rather than back to the highest ramp level from which I came.

Is Anduril supposed to behave this way?

SammysHP
SammysHP's picture
Offline
Last seen: 39 min 24 sec ago
Joined: 06/25/2019 - 14:35
Posts: 271
Location: Germany
Nav88 wrote:
Is Anduril supposed to behave this way?

Yes. Double click from off is a shortcut to temporary max ramp. The level is not remembered and next time you switch on the light it will return to the last used level (or to the manual memory level). When you return from turbo it will also return to this level.

ToyKeeper
ToyKeeper's picture
Offline
Last seen: 1 hour 2 min ago
Joined: 01/12/2013 - 14:40
Posts: 10245
Location: (469219) 2016 HO3
trakcon wrote:
ToyKeeper wrote:
The missing-clicks thing … when it wakes up to check voltage

Forgive me if I missed this somewhere, but is this still an issue? I’ve noticed that my D4V2 Ti misses clicks sometimes. It’s kind of annoying when I try to unlock it, but instead change the aux mode.

I rewrote all the interrupt-related code in November to fix this and several other things which could occasionally happen. Any firmware from 2019-11-20 or newer should be a lot more reliable about the first click from off.

Those changes had an effect on thermal regulation though, so I’ve been working on replacing all the thermal code too.

trakcon
trakcon's picture
Offline
Last seen: 45 min 24 sec ago
Joined: 01/23/2019 - 15:50
Posts: 249
ToyKeeper wrote:
trakcon wrote:
ToyKeeper wrote:
The missing-clicks thing … when it wakes up to check voltage

Forgive me if I missed this somewhere, but is this still an issue? I’ve noticed that my D4V2 Ti misses clicks sometimes. It’s kind of annoying when I try to unlock it, but instead change the aux mode.

I rewrote all the interrupt-related code in November to fix this and several other things which could occasionally happen. Any firmware from 2019-11-20 or newer should be a lot more reliable about the first click from off.

Those changes had an effect on thermal regulation though, so I’ve been working on replacing all the thermal code too.

I read through the thermal regulation discussion earlier in the thread. I’ll wait until that’s sorted to update the firmware.
Thanks, TK!

Nav88
Offline
Last seen: 2 months 4 days ago
Joined: 10/30/2017 - 19:51
Posts: 32
SammysHP wrote:
Nav88 wrote:
Is Anduril supposed to behave this way?

Yes. Double click from off is a shortcut to temporary max ramp. The level is not remembered and next time you switch on the light it will return to the last used level (or to the manual memory level). When you return from turbo it will also return to this level.

The issue is that, at least in manual memory mode, the light always returns from turbo to the last ramping level it was at, unless that ramping level is max and the max ramp level was accessed via the shortcut from off. That, to me, is inconsistent and unexpected behavior.

If the light returns from turbo to max ramp if I accessed max ramp by ramping up, it should also return from turbo to max ramp if I accessed max ramp via the shortcut from off. There should not be two different flavors of the state “on and at max ramp”.

brewster
Offline
Last seen: 1 hour 24 min ago
Joined: 07/19/2019 - 23:29
Posts: 41
Location: Australia

It is not only at max ramp. When you double click to turbo, then double click to return, Anduril will return to the remembered ramp level. That remembered level is not overwritten by any shortcut. So you will see the same behaviour if you reset the light (to cancel any previous remembered level) then click-hold to minimum ramp, then go to turbo and back. You will return to the default level after the reset, which is at the top regulated level in standard Anduril. That seems just fine.

Nav88
Offline
Last seen: 2 months 4 days ago
Joined: 10/30/2017 - 19:51
Posts: 32

Sorry, I’m not following.

Going back from turbo takes me to the last ramp level I was at unless that ramp level is max ramp accessed via shortcut. This creates two scenarios where the beginning state and set of actions are the same but the outcome is different.

Scenario 1:
Start at max ramp (by ramping up). Go to turbo and back, and I’m brought back to max ramp.

Scenario 2:
Start at max ramp (by double-click from off). Go to turbo and back, and I’m brought to the manual memory level I have set.

I’m failing to see the logic in this. I would think that if I’m at max ramp, the light should behave the same going to and from turbo regardless of how I got to max ramp.

Another way of putting it is that, with the current behavior, the shortcut to max ramp is not really a shortcut to max ramp but a shortcut to some special transient mode that happens to have the same brightness as max ramp and whose existence is forgotten when you go to turbo. I’m not sure why this is desirable.

ToyKeeper
ToyKeeper's picture
Offline
Last seen: 1 hour 2 min ago
Joined: 01/12/2013 - 14:40
Posts: 10245
Location: (469219) 2016 HO3
Nav88 wrote:
The issue is that … the light always returns … to the last ramping level it was at, unless that … level was accessed via the shortcut from off. … I’m not sure why this is desirable.

Yes. It remembers the brightness level unless it was accessed by a shortcut.

The reason is because that’s what people asked for.

When the Emisar D4 first came out, it worked how you wanted. It remembered the last brightness level… period. Didn’t matter if it was reached by a shortcut. From off it had min, max, and mem… but people couldn’t access min or max without overwriting mem. This led to inconvenience, confusion, and even burns. Inconvenience because people kept having to manually reset the memorized level to what they wanted. Confusion because if they used moon mode last night then tried to turn the light on the next day, it was too dim and looked like nothing happened. Burns because it’d come on at turbo level in their pockets. It got a reputation as a “nut roaster”.

So a bunch of people asked me to fix it. Specifically, to fix it by making it not remember the brightness if it was accessed via a shortcut.

… and that’s where things are now.

Nav88
Offline
Last seen: 2 months 4 days ago
Joined: 10/30/2017 - 19:51
Posts: 32

Thanks for the explanation, that makes sense.

I notice now that it also forgets the min ramp if it’s accessed with the shortcut.

kamots
kamots's picture
Offline
Last seen: 1 week 2 days ago
Joined: 01/25/2020 - 15:15
Posts: 32
Location: The Internet

ToyKeeper wrote:
I rewrote all the interrupt-related code in November to fix this and several other things which could occasionally happen. Any firmware from 2019-11-20 or newer should be a lot more reliable about the first click from off.

Those changes had an effect on thermal regulation though, so I’ve been working on replacing all the thermal code too.

May I suggest adding a blink mode that blinks the firmware version? Smile

Also, what programming cable do you recommend buying? I bought one of these to tinker with the open source firmware so I want to make sure I get the right interface for it.

atobe
Offline
Last seen: 8 hours 30 min ago
Joined: 09/14/2019 - 23:27
Posts: 251
Location: California

kamots wrote:
ToyKeeper wrote:
I rewrote all the interrupt-related code in November to fix this and several other things which could occasionally happen. Any firmware from 2019-11-20 or newer should be a lot more reliable about the first click from off.

Those changes had an effect on thermal regulation though, so I’ve been working on replacing all the thermal code too.

May I suggest adding a blink mode that blinks the firmware version? Smile

Also, what programming cable do you recommend buying? I bought one of these to tinker with the open source firmware so I want to make sure I get the right interface for it.

After the oct firmware it does blink the firmware date with 15 clicks.
Hank sells the programming cable.

ᕦ(ò_óˇ)ᕤ

kamots
kamots's picture
Offline
Last seen: 1 week 2 days ago
Joined: 01/25/2020 - 15:15
Posts: 32
Location: The Internet

Thank you atobe Smile

Discharger
Offline
Last seen: 4 hours 29 min ago
Joined: 02/16/2020 - 03:57
Posts: 7

This is a question that maybe only ToyKeeper can answer – by the way, a big thank you to her from a happy D4V2 user for the fantastic firmware.

(Low) power consumption being one of the considerations that possibly drove the selection of the levels of illumination for the currently available modes of the aux LEDs, I was wondering if it is physically possible in the existing hardware configuration of the D4V2 to make the aux LEDs even brighter than available using the current “High” mode.

Maybe having the aux LEDs on red (using a brighter “High” setting) could be useful as a source of illumination that preserves night vision for those times when a specialized red light flashlight is not in hand?

If it is indeed possible to have those aux LEDs even brighter, maybe a possible future revision of the firmware could have 4 modes for the aux LEDs – heartbeat,low, high, and turbo, the last mode corresponding to the physically highest possible level of illumination?

SammysHP
SammysHP's picture
Offline
Last seen: 39 min 24 sec ago
Joined: 06/25/2019 - 14:35
Posts: 271
Location: Germany

Brightness levels of the aux LEDs are defined by the hardware.

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

Yeah, I’m also dissatisfied with the levels in my D4SV2, particularly low red which is far too low. But can’t help that without a hardware mode. Sad

trakcon
trakcon's picture
Offline
Last seen: 45 min 24 sec ago
Joined: 01/23/2019 - 15:50
Posts: 249

I know we each have different goals and uses for the aux LEDs. Personally, I like the lows being super low. It can be an alternative to trit vials that isn’t too bright on my nightstand. It would be cool if the brightness was adjustable, though.

kat
Offline
Last seen: 6 hours 31 min ago
Joined: 04/21/2018 - 11:29
Posts: 206
Location: Europe

Does the titanium version step down faster than the aluminium version when using Turbo?

Johm
Online
Last seen: 9 min 48 sec ago
Joined: 08/14/2012 - 04:41
Posts: 418
Location: Greece
kat wrote:
Does the titanium version step down faster than the aluminium version when using Turbo?

Yes, heat can’t escape the emitter/driver area as fast.

trakcon
trakcon's picture
Offline
Last seen: 45 min 24 sec ago
Joined: 01/23/2019 - 15:50
Posts: 249
trakcon wrote:
ToyKeeper wrote:
trakcon wrote:
ToyKeeper wrote:
The missing-clicks thing … when it wakes up to check voltage

Forgive me if I missed this somewhere, but is this still an issue? I’ve noticed that my D4V2 Ti misses clicks sometimes. It’s kind of annoying when I try to unlock it, but instead change the aux mode.

I rewrote all the interrupt-related code in November to fix this and several other things which could occasionally happen. Any firmware from 2019-11-20 or newer should be a lot more reliable about the first click from off.

Those changes had an effect on thermal regulation though, so I’ve been working on replacing all the thermal code too.

I read through the thermal regulation discussion earlier in the thread. I’ll wait until that’s sorted to update the firmware.
Thanks, TK!

TK,

Are the pre-complied .hex files dated 12/17 & 12/3 ok to use or are those the revisions that needed some thermal code changes? I want to update my Emisar’s and FW’s, but I’ll wait if there are improvements coming.

Thanks.

ToyKeeper
ToyKeeper's picture
Offline
Last seen: 1 hour 2 min ago
Joined: 01/12/2013 - 14:40
Posts: 10245
Location: (469219) 2016 HO3
Discharger wrote:
I was wondering if it is physically possible in the existing hardware configuration of the D4V2 to make the aux LEDs even brighter … maybe a possible future revision of the firmware could have 4 modes for the aux LEDs – heartbeat,low, high, and turbo…?

Aux LED brightness is determined by the resistors soldered onto the aux LED board. The firmware does not control that.

What the firmware controls is two things — whether the LEDs have power, and whether the MCU’s internal resistor is active. This allows for 4 states:

Power OnPower Off
Resistor Onaux lowaux off
Resistor Offaux highaux off

That is the full extent of the aux LED brightness levels available while the MCU is asleep.

trakcon wrote:
Are the pre-complied .hex files dated 12/17 & 12/3 ok to use or are those the revisions that needed some thermal code changes? I want to update my Emisar’s and FW’s, but I’ll wait if there are improvements coming.

Those should be fine if you’re careful to avoid letting it overheat, but the thermal regulation in those versions tends to react too slowly.

I’ve been making some pretty good progress with a thermal rewrite, but it’s not done yet. The most recent unpublished code regulates to a stable level very quickly on an Emisar D4, but it’s pretty bumpy on lights with a lower power-to-mass ratio.

Pages