TK's Emisar D4V2 review

[Firelight2]

This has already happened to 2 people. The head of the light suffered damage such as melted optic, damaged wiring, button popping out. No other significant damage occurred. The lights did not explode and no nearby combustibles caught fire.

That said, I suppose combustibles could catch fire if something flammable happened to be in front of the head of the light.

[ZozzV6]

So. It does not work. And my D4V2 which is not mine. Bought for a friend now always starting in ramp max. No mode memory left. I flashed many lights but this is something went wrong. The flashing does not run down once. The pop up window closed immediately and now I have a flashlight not working as it shoud and someone paid me for it to order to him. And I am here with this mess. Sorry guys cancel my offer. I don’t want to ruin anybody flashlight and now what should I do?

I don’t know how TK and Hank want from unexperienced people in flashing to do this at first time.

[Mark_M]

Could there possibly be a short in your adapter? What command did you use?

[BurningPlayd0h]

@DB Custom

That’s right BurningPlayd0h, we as end users have responsibility. The very power source this light demand has it’s own level of end user responsibility, totally up to us to be safe within the parameters of the tools we purchase.

And now y’all know why I’ve never been eager to build lights on request. The sheer power of an unrestricted hot rod, especially a small quad, demands a respect I just don’t see coming from the thousands of new members. We once were a family of enthusiasts, pushing boundaries and making things happen. When we started getting manufactures to build “Custom Hot Rod” flashlights, well, our membership level flooded and the problems arose. And we have lost many a solid member in the process, tired of dealing with the inevitable growing pains.

If the early adopters learning phase were still present we would be golden, but the entitled masses are ruining the spoils. I feel it strongly myself, as one of the people that has pushed limits here for years. After spending so much time building test drivers and hot rod lights, and sharing the process openly so others could find the same results, it is very discouraging to see all the whining and carrying on over such a simple development as a bug. Y’all apparently never spent personal funds on Knucklehead PCB’s and the ensuing component list, or worked hours building experimental drivers for this forum only to have to buy the next revision and start over. Stuff happens, get over it.

I have never understood the desire for a built hot rod and a muggle mode to throttle it down for babies to play with… pretty sure I built one of the first 3000 lumen + quads, and it ran on a AA sized 14500 cell. It was promptly used to run a bear out of camp. Safe? What’s that?

If you buy a hot rod, you have the responsibility to control it. If that means Not using a mode, then don’t! All of the electronic switch flashlights exist in an open power environment, one tiny failure and they’re ON. I can’t count the number of glitchy e-switches I’ve replaced. If ultimate no brain safety is required, use an inherently safer light with a mechanical switch and either alkaline cells or protected Li-ion’s. No simple muggle mode is going to protect an idiot from himself.

+1 The more I think about it, the more sense Hank’s original desire to not have muggle mode on his lights makes more and more sense.

[Firelight2]

I don’t think that’s the issue. The bug could have happened with a different portion of the UI besides muggle mode and we’d have the same problem we have now.

Muggle Mode by itself is fine. The only problem is the bug.

[BabyDoc]

You have reflashed many lights, but had no success here? I have no experience in mods,flashing, or soldering, yet I am told that with the proper equipment, it should be easy. I saw in your previous post that you put together your setup. I’ll bet that when Hank’s setup becomes available, you can successfully reflash this light. It’s too bad your friend may need to wait for his light.

[ZozzV6]

@Mark M

Could there possibly be a short in your adapter? What command did you use?

Absolutely no shorts. Ichecked before first use multiple times. rechecked now. All wire connection goes to pins so no contact problem either. The light aux led turn red blinking when connect the pins.
This is what I used:
avrdude -c usbasp -p t1634 -u -Uflash:w:andurild4v2.hex
TK wrote this to use.

[f0xx]

@Firelight2

My take on the situation:

I like this well reasoned and thoughtful post.

[ZozzV6]

@BabyDoc

You have reflashed many lights, but had no success here? I have no experience in mods,flashing, or soldering, yet I am told that with the proper equipment, it should be easy. I saw in your previous post that you put together your setup. I’ll bet that when Hank’s setup becomes available, you can successfully reflash this light. It’s too bad your friend may need to wait for his light.

I flashed more than 200 lights.
My “friend ” messaging me every day multiple times when he can pick up his light and he wanted to came wednesday. Now I can’t tell him to wait or I can’t pay him back and we are here with a worse light than it arrived. He is not a patient guy. So I am sure if I need to wait a month again he wil messaging me every day…. That is why I usually don’t buy lights for other people. If something goes wrong I need to do warranty things or repair lights or loose money. The pin connector is OK I don’t think another one do the job. Maybe some fuse settings missing from the line. Usually flashing scripts have fuses. I don’t know why this not have.

[ZozzV6]

@Man Without Shadow

@ZozzV6

@Mark M

Could there possibly be a short in your adapter? What command did you use?

Absolutely no shorts. Ichecked before first use multiple times. rechecked now. All wire connection goes to pins so no contact problem either. The light aux led turn red blinking when connect the pins.
This is what I used:
avrdude -c usbasp -p t1634 -u -Uflash:w:andurild4v2.hex
TK wrote this to use.

specific name of the file is

anduril.2019-07-18.emisar-d4v2.hex

I know. Downloaded and renamed it to a shorter name. That name is in the command.

[Mark_M]

@ZozzV6

@Mark M

Could there possibly be a short in your adapter? What command did you use?

Absolutely no shorts. Ichecked before first use multiple times. rechecked now. All wire connection goes to pins so no contact problem either. The light aux led turn red blinking when connect the pins.
This is what I used:
avrdude -c usbasp -p t1634 -u -Uflash:w:andurild4v2.hex
TK wrote this to use.

You said it starts at Max ramp, can you ramp down? TK stated that as long as the fuse values are not changed then there is little risk to brick. Have you tried reflashing? Maybe it is set to manual memory and it was on Max ramp, did you try 5h to switch to automatic memory?

[ZozzV6]

@Mark M

You said it starts at Max ramp, can you ramp down? TK stated that as long as the fuse values are not changed then there is little risk to brick. Have you tried reflashing?

yes I can ramp down and seems other things work just it always start ramp max with short click. long click it starts moon then ramp up.
The flashing sequence not even completed once. I tried it many times and not doing the flashing sequence.

[Mark_M]

Try changing it to automatic memory.

[ZozzV6]

@Mark M

Try changing it to automatic memory.

changing what to automatic memory?

[Mark_M]

While the flashlight is on click 5 times with you holding the last click, there are two types of memory now one is manual and one is automatic.

[ZozzV6]

@Mark M

While the flashlight is on click 5 times with you holding the last click, there are two types of memory now one is manual and one is automatic.

I did not know this feature existed in Andúril. Thanks! It worked. Now I have mode memory but still have the bug firmware I think

[SKV89]

@Mark M

You don’t have a physically defective product. You have software with a bug. There is nothing wrong with the hardware in your flashlight. It seems to be a real stretch to try and argue what you are. Do you attempt to send back your PC to the manufacturer anytime Windows has an error?

:+1: :+1: :+1: OMG that’s the best reasoning I’ve seen. I remember back in the 90s when running the x86 and Pentiums that cost over $2k+, I spent more time trying to figure out DOS and Windows 3.1 crashes, bugs, hardware drivers not working, etc., than actually using my computer. Windows Xp was the first windows stable enough to use without constant fear of crashing and losing work, but it still had its fair share of problems. Apple IOS is probably the most bug free OS I’ve ever seen but it is developed by thousands of engineers and hundreds of billions of dollars, whereas Anduril is developed by a single non profit hobbyist and Emisar is likely not even a registered business operated by a single flashlight enthusiast from his home.

[Mark_M]

@ZozzV6

@Mark M

While the flashlight is on click 5 times with you holding the last click, there are two types of memory now one is manual and one is automatic.

I did not know this feature existed in Andúril. Thanks! It worked. Now I have mode memory but still have the bug firmware I think

No problem, I think it was added with this flashlight release.

[Valynor]

ZozzV6, you should probably take a look at the Anduril manual: https://bazaar.launchpad.net/~toykeeper/flashlight-firmware/fsm/view/head:/ToyKeeper/spaghetti-monster/anduril/anduril-manual.txt

esp. lines 49-65

[Aprilis]

@Valynor

@Aprilis

Could somebody help me please? I am having trouble with getting to the maximum regulated output of the flashlight. How can I get to the maximum regulated output without manually trying to catch the exact point where the light blinks? What is the easiest way to do it?

Easiest way to get there is losen tailcap (wait ~3 seconds), tighten back up again. Click to turn the light on and it will be at max regulated output.

If you want to use that level often you can save it as manual memory (5 clicks from ON while you are at that brightness).

Thank you so much!