The smaller zebralights like the SC60 series and SC50 series all use screwed on clips. Only some of the larger ones like the SC600 series use slip on clips.
I assume he has something like an SC64w HI, which uses a screwed on clip.
The smaller zebralights like the SC60 series and SC50 series all use screwed on clips. Only some of the larger ones like the SC600 series use slip on clips.
I assume he has something like an SC64w HI, which uses a screwed on clip.
Got it today.
I initially thought that the bright mode for the auxillaries was too bright, until I found them bright enough to help light my way to the bathroom, at night. I set lockout with bright red auxillaries so at night I can switch between Red or momentary moon. When I unlock in the morning, my auxillaries are usually in dim voltage mode.
The aux LEDs in high mode use more power than the main LEDs in moon mode. For what you described, you may as well just leave it on all night in moon mode. It would be brighter and would drain the battery less overnight.
mattlward:I wish it had the clip that the zebralight has. I am thinking about picking one up, but the idea of a pop on/off clip just hurts.
Most Zebralights use a friction clip too…
The Zebralight SC52w-L2 and Zebralight SC62w both use a very secure screw on clip. I have my D4V2 now and really like it, but would accept a couple more mm in the tail cap for a screwed on deep carry clip.
Just found this post…what’s that noise about muggle mode?
Still didn’t get mine
Just found this post…what’s that noise about muggle mode?
Still didn’t get mine
There’s an unfortunate bug in first-run Emisar D4V2s sold through International Outdoors before July 19.
When put in muggle mode (6 clicks from off) and run with a partially depleted cell (about 3.8v or lower), these lights effectively enter “self destruct mode”. After approximately 15 minutes of being off they will turn on and start flashing at full power with no ramp down from the thermal sensor.
If this is an 18650 cell, the lights may overheat, which in a couple cases caused some or all of the following: (1) plastic optic melting, (2) driver wires desoldering, (3) button boot and retaining ring popping off. Probably from expansion of the aluminum head.
As a safety measure it is recommended to avoid using muggle mode if you have one of the affected lights until fixed. The fix requires a firmware update and can be done in about 1 minute without disassembling the light, but requires special hardware and software.
Many thanks Firelight2.
Detailed and self explanatory info:)
Mine is post July 19 order so i’m ok.
id30209:Just found this post…what’s that noise about muggle mode?
Still didn’t get mineThere’s an unfortunate bug in first-run Emisar D4V2s sold through International Outdoors before July 19.
When put in muggle mode (6 clicks from off) and run with a partially depleted cell (about 3.8v or lower), these lights effectively enter “self destruct mode”. After approximately 15 minutes of being off they will turn on and start flashing at full power with no ramp down from the thermal sensor.
If this is an 18650 cell, the lights may overheat, which in a couple cases caused some or all of the following: (1) plastic optic melting, (2) driver wires desoldering, (3) button boot and retaining ring popping off. Probably from expansion of the aluminum head.
As a safety measure it is recommended to avoid using muggle mode if you have one of the affected lights until fixed. The fix requires a firmware update and can be done in about 1 minute without disassembling the light, but requires special hardware and software.
Just to confirm, every light ordered through International Outdoors after July 19 is safe? I’m literally about to pay for my order, and just want to double check.
Just to confirm, every light ordered through International Outdoors after July 19 is safe? I’m literally about to pay for my order, and just want to double check.
Straight from the Intl-Outdoor website:
D4V2 is shipped with the updated firmware since July, 19
Thanks Kazibole…
Reading comprehension was never one of my strong suites
What’s up with hank and not responding to emails or sending orders in a timely manner?
What’s up with hank and not responding to emails or sending orders in a timely manner?
He posted earlier that he is focused on getting the programming kits ready.
That may have been over in Toykeeper’s review thread.
Just joined this thread so don’t hate me (much) if this question was asked somewhere like 30 pages before…
Is 219C 5000K option 90CRI like solo emitters on Hanks site or it’s something else?
The 219C 5000K option is listed on Intl-Outdoor as 83 CRI.
I’m not sure if any other 219C versions are available. Regardless, it has a nice tint but also more heat and lower output.
anyone tried flashing their d4v2? Anyone seen or know why I get this error? A fellow BLF’s was helping out but thought I’d post here for increased d4v2 owner visibility.
CHECK CONNECTIVITY
C:\Users\user\Desktop>avrdude -p t1634 -c usbasp -n
avrdude: warning: cannot set sck period. please check for usbasp firmware update.
avrdude: AVR device initialized and ready to accept instructionsReading | ################################################## | 100% 0.01s
avrdude: Device signature = 0×1e9412
avrdude: safemode: Fuses OK (H:1F, E:DE, L:E2)
avrdude done. Thank you.
FIRMWARE UPDATE
C:\Users\user\Desktop>avrdude -p t1634 -c usbasp -Uflash:w:anduril.2019-08-05.emisar-d4v2-219.hex
avrdude: warning: cannot set sck period. please check for usbasp firmware update.
avrdude: AVR device initialized and ready to accept instructionsReading | ################################################## | 100% 0.03s
avrdude: Device signature = 0×1e9412
avrdude: NOTE: “flash” memory has been specified, an erase cycle will be performed To disable this feature, specify the -D option.
avrdude: erasing chip
avrdude: warning: cannot set sck period. please check for usbasp firmware update.
avrdude: reading input file “anduril.2019-08-05.emisar-d4v2-219.hex”
avrdude: input file anduril.2019-08-05.emisar-d4v2-219.hex auto detected as Intel Hex
avrdude: writing flash (9122 bytes):Writing | ################################################## | 100% 7.08s
avrdude: 9122 bytes of flash written
avrdude: verifying flash memory against anduril.2019-08-05.emisar-d4v2-219.hex:
avrdude: load data flash data from input file anduril.2019-08-05.emisar-d4v2-219.hex:
avrdude: input file anduril.2019-08-05.emisar-d4v2-219.hex auto detected as Intel Hex
avrdude: input file anduril.2019-08-05.emisar-d4v2-219.hex contains 9122 bytes
avrdude: reading on-chip flash data:Reading | ################################################## | 100% 5.24s
avrdude: verifying …
avrdude: verification error, first mismatch at byte 0×0020 0xff != 0×0c
avrdude: verification error; content mismatchavrdude: safemode: Fuses OK (H:1F, E:DE, L:E2)
avrdude done. Thank you.
anyone tried flashing their d4v2? Anyone seen or know why I get this error? A fellow BLF’s was helping out but thought I’d post here for increased d4v2 owner visibility.
CHECK CONNECTIVITY
C:\Users\user\Desktop>avrdude -p t1634 -c usbasp -n
avrdude: warning: cannot set sck period. please check for usbasp firmware update.
avrdude: AVR device initialized and ready to accept instructionsReading | ################################################## | 100% 0.01s
avrdude: Device signature = 0×1e9412
avrdude: safemode: Fuses OK (H:1F, E:DE, L:E2)
avrdude done. Thank you.
FIRMWARE UPDATE
C:\Users\user\Desktop>avrdude -p t1634 -c usbasp -Uflash:w:anduril.2019-08-05.emisar-d4v2-219.hex
avrdude: warning: cannot set sck period. please check for usbasp firmware update.
avrdude: AVR device initialized and ready to accept instructionsReading | ################################################## | 100% 0.03s
avrdude: Device signature = 0×1e9412
avrdude: NOTE: “flash” memory has been specified, an erase cycle will be performed To disable this feature, specify the -D option.
avrdude: erasing chip
avrdude: warning: cannot set sck period. please check for usbasp firmware update.
avrdude: reading input file “anduril.2019-08-05.emisar-d4v2-219.hex”
avrdude: input file anduril.2019-08-05.emisar-d4v2-219.hex auto detected as Intel Hex
avrdude: writing flash (9122 bytes):Writing | ################################################## | 100% 7.08s
avrdude: 9122 bytes of flash written
avrdude: verifying flash memory against anduril.2019-08-05.emisar-d4v2-219.hex:
avrdude: load data flash data from input file anduril.2019-08-05.emisar-d4v2-219.hex:
avrdude: input file anduril.2019-08-05.emisar-d4v2-219.hex auto detected as Intel Hex
avrdude: input file anduril.2019-08-05.emisar-d4v2-219.hex contains 9122 bytes
avrdude: reading on-chip flash data:Reading | ################################################## | 100% 5.24s
avrdude: verifying …
avrdude: verification error, first mismatch at byte 0×0020 0xff != 0×0c
avrdude: verification error; content mismatchavrdude: safemode: Fuses OK (H:1F, E:DE, L:E2)
avrdude done. Thank you.
yay! i finally found the problem. I’ll post it in the d4v2 firmware update thread.
Does anyones d4v2 make a high frequency noise on high? Also the noise is not so loud on turbo
BTW this is with a samsung 20R
It does not make this noise with an 18350 efest V2 High drain
Does anyones d4v2 make a high frequency noise on high? Also the noise is not so loud on turbo
BTW this is with a samsung 20R
It does not make this noise with an 18350 efest V2 High drain
Do you have a magnetic tail cap installed? Does it do it with the non-magnetic one as well?
Some of the talk around the issue was EM fields interfering and making magnetic tail or other small parts vibrate or resonate.
No magnetic tailcap I did not get it because I have a d4s with one to work on stuff with
I’ve done some research and it seems it’s quite commonplace wuth these lights having inductors
Has anybody had any luck putting the V2 stainless bezel on a V1 light?
I have a V1 and V2. The aluminum bezels can be easily swapped between the two. Stainless bezel threads onto the V2 easily, but won’t thread onto the V1. It goes on approx 1 turn and then stops, as if it’s the wrong thread pitch. I don’t think the threads are different though because the aluminum bezels interchange without an issue.