Yea, I didn't know about this one - definite bug, though it's hard to speculate what 5% and 10% mean on a particular light mod or build, since LED's and FET's make such a huge difference. For example in a 7X parallel XPL2 light, maybe you hit 25A is 100% at 10K lumens, so 10% being 0.35A is much lower than 10%...
I'll have to fix this/change this to something reasonable. Think I was using ~1,500 lumens max (typical max single XM-L2 or XPL moderately configured) as a guideline for rating the percentages.
I'm working on NarsilM v1.1 now (GT Buck driver support merging), so will get it in before I forget, so when it's released, it will be there.
Really, all these mode sets should be tweaked build/mod by build/mod since there's so many variations of build/mods. Unfortunately this is what you get when working with fixed amp output (7135's) and variable amp output (FET's) combined in one driver.
It was discussed to not use percentages, but just state what it is: one max 7135, 20% of a 7135, 45% of the FET, etc.
Yup completely understand the percentages are guesstimates. Just wanted to bring this to your attention since it seems obvious that two modes shouldn’t be identical.
I try to make another use of the NarsilM firmware driver.
Not working properly still.
After installing the battery, direct light high, and then will not light up again.
7135 using A705NGT-350 SOT-89
Flash firmware on Attiny85
FET 404
85fuses.bat:
REM BOD disabled:
Wp hvc
REM BOD enabled at 1.8V: Avrdude -p t85 -c usbasp -Ulfuse: w: 0xe2: m -Uhfuse: w: 0xde: m -Uefuse: w: 0xff: m
85M.bat:
Rem 85NarsilM - downloads NarsilM (Tiny85 Multi-channel e-switch UI configurable)
Rem Avrdude -p t85 -c usbasp -u -Uflash: w: NarsilM.hex: a
Maybe you can send me the source code you have? I assume you configured/set it up yourself?
You really, really need the raptor claw 7135's - I don't trust any other out there, but what you have happening - not sure if that's the problem.
I assume you have the Mateminco from Alibaba or taobao?
Again -- I would only use raptor claw 7135's, but also with this super high amps, I would only use FET+1 designs, never a 3 channel design - these 7135's can't take it. DEL has proposed using a C3 and C4 cap as well to handle spike from the FET hitting the 7135's. Our simple designs actually don't run the 7135's properly to the spec.
Truthfully if you can't get the raptorclaw 7135's, I would use only one channel for this light - the 404 FET, or maybe the better Hyperion.
Uhhh, well, it has to be configured for your driver. It's a very flexible driver, supporting several configurations, but has to be configured for the driver. So you just used the .HEX from the download? Then that's for a FET+1 driver, like the BLF Q8 - the HEX file won't work.
Let me review the driver - I could post up a HEX file pre-compiled for this driver, I think... Let me check.
The raptorclaw is the 7135 in the upper right - the symbol looks like an eagle claw, or raptor claw. The sailboat (bad one) is in the upper left - symbol looks like a sailboat.
steel - I assume you can download and program, but you can't compile the code? You don't have the Atmel studio installed?
I’m not sure how related those comments can be regarding NarsilM…
I just had my first experience with a Narsil based UI - a stripped down ramping only version as i understand, with the Emisar D4 and i have a few issues. Here is what i reported in the D4 thread:
On a similar note, while ramping i can double click to turbo, but then the only option is to ramp back down. I would have expected a single click to go back to the previous level.
Once again i’ve no idea whether this is relevant to NarsilM which i haven’t had the chance to try. Waiting for the Q8 and FW3A…
I developed the D4 firmware under a pretty strict set of requirements. With NarsilM, I don't have any restrictions. When ramping was added, there was a great deal of discussions goin on the BLF Q8 thread on it, so I implemented a lot of those suggestions, most of them, including that turbo and moon won't be "remembered", unless you ramp to them.
A double-click goes to turbo, and another double-click goes back to the previous level.
On the D4, if you single-click at turbo, it shuts off and remembers turbo as your memorized mode. But on my newer stuff, turbo and moon are only remembered if you manually ramp to them. And NarsilM has done it that way for months.
More generally, NarsilM is a newer, upgraded version of the D4 code which does almost everything better. I added a few things to the D4 which aren’t in NarsilM yet, but not much.