NarsilM - configurable e-switch firmware for Multi channels, v1.3

I think the 7135 are only rated up to 6 or so volts and with 2S lights your above/out of spec.

–0.3V to 7V

https://www.google.de/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&ved=0ahUKEwi5rdbG2tbVAhVGb1AKHVmiCKkQFggnMAA&url=https%3A%2F%2Fwww.rcscomponents.kiev.ua%2Fdatasheets%2Fdoc000709557-datasheet.pdf&usg=AFQjCNHuyS9ZV3RNa1pK0AjczxJDaaQ7vg

the problem is there are many cheap AMCs that are not even the original manufactor with different quality

What I can dicover sometimes on drivers if I do thermal calibration when I heat the driver up they start to leak and when cooled down they are fine again

often its way below moonligh level, just a few are that bad like you see it

Yes, they still usually work above that voltage, but every once in a while you get one that seems to stay on. (According to other people that have run into this problem)

Not sure if this has already been mentioned, but I was looking through the code linked in the Google Drive and there seems to be a bug in ModeSets.h

// 6 modes 0.8-2-5-10-50-max ~0.8% ~2% ~5% ~10% ~50% max
PROGMEM const byte mode7135Set6[] = { 20, 110, 255, 255, 0, 0};
PROGMEM const byte mode7135sSet6[] ={ 0, 0, 0, 0, 255, 0};
PROGMEM const byte modeFetSet6[] = { 0, 0, 0, 0, 0, 255};

The 6 mode set does not seem to have the “5 ” output set correctly. Looks like 255, 0, 0 is repeated twice for both 5 and 10%

Yes, looks wrong there. Not sure without looking what table it is.

Line 127 of ModeSets.h

under OUT_CHANNELS == 3

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.

Definite appreciate it! Thanks!!!

Only no code has no bugs

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

All 100%

Lots of questions, but I'll start with: Exactly how to you have it setup/configured? I need all the details.

Not familiar with the MF01 driver, or exactly how it's set up. I assume its 3 channels, and 2S? I see the LDO. there.

I see lots of variables - new driver, not sure if you ever worked with NarsilM before, not sure if you know the details of setting up a 2S light.

No NarsilM worked before, L6 with NarsilM can not e-switch turnOFF also not to deal with

Setup for 2S e-switch

I guess, will it be 7135 wrong?

R1 : 360k
R2 : 47K
R3 : 100 k
R4 : 47 ohm
R5 : 4.7 ohm
R6 : 0 ohm
R7 : 0 ohm
C1 : 10uF
C2 : 10uf

U1 : ATtiny85
U2 : R404

LDO : Designed around the MIC5235-5.0YM5 LDO voltage regulator

7135 : A705NGT-350

LED arrangement, 2S3P, 3 groups, a total of 18 219C LED

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.

No, I’m not configured NarsilM.hex
Download from your link

I bought some different types of 7135.
Which is raptor claw?

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 understand a little bit …

As I use this NarsilM.hex on L6 (XHP70.2 2S), it is also wrong, and can not work.

7135 good or bad is not related?

I have to learn how to set and compile the firmware NarsilM.hex

I always thought same as TA driver.
Download .hex and flash.

Ok, I added a HEX file into the NarsilM folder on the google drive. The HEX is called: NarsilMv10-32S.hex, heres the link:

https://drive.google.com - NarsilMv10-32S.HEX.

So this is for 3 channels, 2S battery configuration. I have pre-defined header files to use for Setup.h:

Setups-1Chan.h - single output channel, 1S battery

Setups-31S.h - 3 channels (7135-7135 bank-FET) and a 1S battery

Setups-32S.h - 3 channels (7135-7135 bank-FET) and a 2S battery

Setups-Q8.h - 2 channels (FET+1, 1 7135) and a 1S battery

Please try this HEX file for the MF01 driver, and can also be used for the L6 you have, I believe.

For the 7135's, maybe they will be ok, can't be sure. You might have to crank up the PWM value for moon mode though, if it's not a raptor claw one.

Thank you very much Tom E.

I will try.

:+1:

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…