17mm 12x7135 drivers with custom firmware (Group Buy Interest thread)

Right. That's what I have been writing in my reviews. I used to hate blinky modes - but learned that I hate them only when they are in normal mode cycle. They are fun or useful in some cases, but the fact that I need to step through them every time I want to go from High to Low is so annoying that the negative things easily outweighs the positives => getting rid of the blinky modes was the answer. Qlite in 4-mode config was "near perfect" for me.

The whole point of TheStar is that it feels like a standard 3-mode UI. How many users will loop through all the modes twice without having even one one second break? The limit could be three rounds, but based on the feedback from testers, two rounds was chosen to be good compromise between good usability in normal cases and the accessibility of the hidden modes when needed.

Can you flash your own FW? I can send it to you by email to be tested. Or maybe some member near you could flash you one?

I guess that flashing the FW is way easier than stacking the 7135s => Maybe they can agree to 2x500pc batches.

Anyone consider a daughter card solution for maximizing 7135’s on one side of the driver?
I suspect this would make it much easier to manufacture.

Maybe it sounds more complicated than it really is. Or maybe there's just a language barrier and I can't explain it well..

I fully understand your concern. I used to think it's better to have the LowLow in the main mode cycle. But after using both 3- and 4-mode variants of TheStar for couple of weeks, I like the 3-mode (with hidden LowLow) much more - to my great surprise I like it more also in my in-house EDC-type lights like S2+.

Exactly. My original idea was to add only a strobe, but why not add more as they won't affect the usage at all (but still are there if you need them).

I don’t think it’s a language barrier issue. You’ve explained everything pretty well I think. I mean weird as in strange. EDIT: and I am not saying “bad”.

I don’t really use LL, so it’s hard for me to say. I thought we had a fair number of users who use LL as the primary mode on some lights.

Since this is an ontime firmware right now it’s not even on my radar ;-).

@The - I dont have a clip but thanks for you generous offer. Your test group and GB light participants are advanced enthusiasts so I dont think they accurately reflect the bulk of the potential buying market needed to make the sales numbers needed for this GB. While I can appreciate your UI and explanations, it will confuse the first or second time buyer/modder or casual buyer. I would have no problem buying a clip and following one of the many great “how to” posts on this forum and flashing my own. But that isnt going to help us gather the numbers we need to make this sale come to fruition. Thats why I strongly think we would have a far better chance offering two UI’s. The goal should be how to configure the driver to appeal to the largest group possible while maintaining the target price. Wouldnt you agree? If not, the GB will die.

I think the average person will view the benefits and impetus for this GB as:

  1. price, price and price
  2. 4.2A for a nice bump in lumens

3) simplicity (with the option for complexity if it can be offered in 2 UI versions) This might increase sales because people would think about buying one of each to compare. Even I will buy one with the blinkies! :smiley: :bigsmile:

4) ease of installation if they can solder or give it a try
5) 17mm
6) many custom UI choices with a clip

In the end, whatever it takes to meet the sales goal is the best decision and I’ll support whatever it takes to help push this through.

As _the_ has explained, the TheStar should be simple to operate. Based on my understanding of the operation, if you don't mention the hidden modes to your users they likely will not find them. You could print out a little card to go with the light if you felt compelled - put the technical specs and the advanced driver operation instructions on it.

_the_ can correct me if I'm wrong, but there is no "flashy mode group" to get stuck in. Turning the light off and back on from any flashy mode should put them back into the regular modes. The worst thing that could happen to an end user is that they might one day play with the light until they see a flashy mode - and not be sure how to get back to that mode in the future.

I'm warming up to the concept at least a little.

I don't think two firmwares is a good idea. As you and I have both stated, anyone who's purchasing drivers by the tens or twenties is obviously purchasing them to build and distribute lights with (resale, gifting, whatever). Whatever we decide is "simple" enough for that should be on all the drivers from this GB whether it's TheStar or something else. We've got a lot going on here (stacking, replacing some default Nanjg-clone firmware), no need to add more avenues for error to that. Anyone who wants a different firmware has plenty of options to get it done!

Well.. Yes, and no. :)

There is no "flashy mode group", but the current flashy mode is remembered like any other mode => From strobe, turning the light off and on again will turn it on on the strobe mode. First mode change (= two clicks) will return to first standard mode.

K.I.S.S. for “stock”

3-4 modes w/ hidden blinky

That quote made me to quickly write an off-time version of TheStar.. ;)

Unfortunately I don't have any caps, so I can't test it right now. :( Anyone willing to be a lab rat?

Is there a way to just have L~~M~~>H

Hidden fast access LL
Hidden fast access Turbo
Hidden fast access strobe (maybe with tab through SOS and alpine beacon for strobe modes)

I think this would be most simple, most useful and cover all bases in some way.

All simple users want L/M/H, all advanced users want Turbo and LL AND want to get there instantly, but may not want to go through/confuse simple users. Fast access strobe with strobe selections is a bonus but…not necessary?

With electronic switch there is. Without.. Well.. At least I can't instantly figure out how that could work. Maybe with some kind of timed double/triple click logic?

OK wait, maybe I read wrong. So what you are saying below is Turbo WILL be accessible in all configs as a hidden mode?!?

Thats awesome if so, my pet peeves are PWM speed, no turbo, blinkies/LL you have to go through in mode changes, this would solve ALL of them! :slight_smile: My only addition in this case would be a FAST access hidden turbo: LL, then turbo then disorienting strobe? I’m quite certain LL and turbo would be the most used and desired hidden options.

B42, it sounds like you may still have one misunderstanding. Turbo is in the normal 3 mode group that _the_ described.

The "normal modes" are:
L - M - T

where:
L = 2% mode
M = 25% mode
T = 100% mode w/ stepdown

What's hidden is LL, all the blinkies, and a Turbo that never steps down. There is an additional pseudo-level which _the_ refers to as "high" but you can't select it - it's just what Turbo steps down to.


I think I've got that stuff right.

Yeah I realized I may have misunderstood in the first post. Based on your reply, I may be misunderstanding something different: are “hidden” modes enterable from “off”? If this is true, a Turbo (never stepping down) would be a useful hidden mode just like the disorienting strobe, and used more than at least 7 of that list of 9 modes and should be easier access than #9 priority. Thats what I was getting at. If not…I’m confused…

I see what you are getting at now. Based on my current understanding, here’s the situation:

  • to initially get to never-step-down-turbo rather than regular turbo you need to click through the standard 3 modes twice, then click through LL and the blinky modes. So approximately 14 fast taps after the initial turn on in order to get to never-step-down-turbo.
  • I assume that never-step-down-turbo will be memorized just like the blinky modes are (see post #72). So as long as you don’t change modes it will stay in that mode the next time you turn it on.

My assumption is that this firmware is geared towards having the ability to set a small-bodied light down and then pick it back up without getting scalded.

I’d holler at 15-20 at the right price. Already having the 7135’s added would save a ton of time. As far as modes, simpler would be more preferable. 4 modes (moonlight~~low~~>med->turbo), turbo ramps down to med after 90 or 120 sec. Blinky modes are utterly pointless. Especially a hidden strobe. For a strobe to actually be useful it needs to come on first always, or at a minimum come on easily by holding down (or somehow otherwise preselecting it). An assailant/intruder/giant murderous bad guy isn’t going to wait for you to cycle through to access your strobe mode. Are there any other uses for strobe (I can’t think of any)?

Anyway. That’s all to say that at the right price with simple UI, I’ll take 15-20 pretty please.

How about starting a poll on what kind of mode group would everyone prefer?

The hidden blinky modes are potentially useful as beacons. For that purpose it generally would be OK even if it took you a few minutes to get it into the mode you wanted… (Several of the ones in TheStar are even called beacon. :-p)

My dad said he saw a wrecker guy using his to get peoples attention at night…but I guess the HUGE truck with yellow flashy lights did a better deal than his blinky light

Truthfully if you could build a two group Nanjg style setup, one group L>M>H, 2nd group L>M>H>Blinkies but fix the daggum PWM on it…if people want other than “custom” let them flash them themselves