it does get hot very fast tho.
Have you tried contacting Zebralight regarding the fast stepdown?
Edit: I see your in EU so that could be a problem with warranty/shipping
it does get hot very fast tho.
it does get hot very fast tho.
same issue reported today, here:I have two zebras SC65 HI and one of them has a weird issue where the output starts dropping from the moment I turn it on
Have you tried contacting Zebralight regarding the fast stepdown?
Edit: I see your in EU so that could be a problem with warranty/shipping
I'm looking for some feedback from SC700d HI owners who have had issues with the light turning off unexpectedly. I'm trying to separate two issues here.
One seems to be in firmware, where any SC700d HI or newer SC65c HI can be turned off at any time by a fast enough double click, which long-term Zebralight owners may run into while doing things like programming that require a lot of double clicks.
The other is when the light turns off after specific actions in specific UI states; in particular, double clicking between H1 and H2 or M1 and M2, scrolling to M or H and releasing the switch (but strangely not double clicking to M from off?), and sometimes single clicking to H. These are all in the regular G5 mode group, but probably apply to equivalent outputs in G6 and G7. It's essentially behaving as if it registered an extra click, sometimes with a bit of a delay. The issue may be exacerbated by the driver being hot, and the frequency of occurrence varies wildly.
I've seen several mentions of SC700d HIs unexpectedly turning off. I thought it was people getting used to the double click timing thing, but now I'm wondering if it was actually the second issue. I'd be interested to heard some updated experiences now people have had their lights for some time.
your opinion... you're entitled to that.I can't help, but the old song title comes to mind:
"Welcome To My Nightmare"
If it's prevalent in G5 mostly, I don't expect it would be noticed much. I'd like to think that well over 90% of ZL users don't use G5, knowing the flexibility that G6 and G7 bring.I'm looking for some feedback from SC700d HI owners who have had issues with the light turning off unexpectedly. I'm trying to separate two issues here.
One seems to be in firmware, where any SC700d HI or newer SC65c HI can be turned off at any time by a fast enough double click, which long-term Zebralight owners may run into while doing things like programming that require a lot of double clicks.
The other is when the light turns off after specific actions in specific UI states; in particular, double clicking between H1 and H2 or M1 and M2, scrolling to M or H and releasing the switch (but strangely not double clicking to M from off?), and sometimes single clicking to H. These are all in the regular G5 mode group, but probably apply to equivalent outputs in G6 and G7. It's essentially behaving as if it registered an extra click, sometimes with a bit of a delay. The issue may be exacerbated by the driver being hot, and the frequency of occurrence varies wildly.
I've seen several mentions of SC700d HIs unexpectedly turning off. I thought it was people getting used to the double click timing thing, but now I'm wondering if it was actually the second issue. I'd be interested to heard some updated experiences now people have had their lights for some time.
that is not how I understand what McBob wrote:If it's prevalent in G5 mostly, I don't expect it would be noticed much. I'd like to think that well over 90% of ZL users don't use G5
iow, any problem in G5 probably applies to G6 and G7 alsoThese are all in the regular G5 mode group, but probably apply to equivalent outputs in G6 and G7
Yeah, really. So you're in the 10%, using my unscientific analysis. Nothing wrong with that.So far no noticable issues in my 53ns, 65s, or the SC700HI that just arrived. I imagine the 65s are the missing-components version but that seems to only be significant at H1*, which I hardly use. No premature step-down or flickering. No double-click or mode-sequencing shutoffs - yet.
"I'd like to think that well over 90% of ZL users don't use G5"?
Really? I was all about playing around with the other setups but now? I just can't be bothered. G5 is fine. Also, it doesn't help that I have over a dozen ZLs, at least four in regular use at any time, and, since I don't write it down, no idea HOW I configured the other groups after a month or so. On the 53s I think it was G7=low modes in order and G6=M1 or M2 for high, and one step down from there. "Alkaline battery" mode. But the lithium ones? Bah, never remember. And, I've been using them since the SC51 so, no, I'll keep the H,M,L mode order.
*I know there's a few percent efficiency difference on most modes, but H1 is like 20% less efficient, IIRC. I don't care about 2% on an 18650, not enough to return the lights, anyway.
Assertion, not analysis. I'd bet I'm in the majority, if you count the ZL users who _aren't_ on this forum But, who knows.Yeah, really. So you're in the 10%, using my unscientific analysis. Nothing wrong with that.
I have no double click issues with two SC65c HI and one SC53c N.Assertion, not analysis. I'd bet I'm in the majority, if you count the ZL users who _aren't_ on this forum But, who knows.
Anyway, I'm happy to not have any double-click shut-off issues in G5 on any of the three new flashlight models (53n,65hi,700hi) that I bought.
I'll sleep better now.your opinion... you're entitled to that.
Agreed..... With pleasure of not having the issue. It sucks for those that do. I don't really use my ZL collection, with the exception of my SC64 Hi, which I EDC.Assertion, not analysis. I'd bet I'm in the majority, if you count the ZL users who _aren't_ on this forum But, who knows.
Anyway, I'm happy to not have any double-click shut-off issues in G5 on any of the three new flashlight models (53n,65hi,700hi) that I bought.
goodI'll sleep better now.
FYI, my comment was based less on opinion, but rather far more a matter of perspective, and I can assure you mine is different from yours. Both are subjective, but in this case are distinctly different things.
My comment was also addressing the difficulty of the task of analysis of the reported issues, and not the product(s) overall, and any inference to the contrary is false.
My comment was also not a general post, but rather a direct 'reply' to a specific post.
Are you speaking for Bob?