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.
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.
So I think NarsilM acts as you want it to act.
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.
I tried NarsilMv10-32S.HEX on L6.
It can work properly. 
but,
In the MF-01, only when the power on, blink twice, and then e-switch can not operate, even turn on the flashlight.
MF-01 driver, I will reassemble one to test.
Weird - should always be on pin #2 for the switch. Again, not familiar with this board though.
I did check the MF01 board layout again, it is identical to SRK 46mm build
To identify any faults its recommended to measure connection from the MCU to the other components, as well check the supply voltage behind the LDO
@Tom & TK: thanks for the answers. I was just providing my limited experience feedback about the D4… Glad to hear those issues have been ironed out. :+1:
Still, i believe ramping should be constrained to the ‘safe range’ - where the light will handle the heat. Turbo should be an extra step the user decides to take for a short lapse of time - not something you run into just because you keep you finger pressed on the switch half a second too long.
I found where is the problem.
The switch on the PCB is not grounded.
Now, NarsilM can operate
However, When ramp to the lowest brightness, can not drive all 18 LED, so no brightness.
Thanks Tom, Lexel
You should be able to turn up the brightness of moon mode in the settings.
That's probably a sympton of the 7135, the worse 7135's don't do well at low PWM's. In my 16X XHP50 light, the low PWM's work fine in lighting up all 16 LED's. I'm working right now on a similar setup - the MT03, 3 XHP70.2's and this driver: https://budgetlightforum.com/t/-/40540/67.
yeah you are right I didnt check the switch ground, for some reason all automatic checks did not notice it
new fixed layout
Those 2S drivers should definitely have a C3, as recommended by DEL. I also have a C4 on the one I just did.
This post has his Yezl Y3 2S board with the C3: https://budgetlightforum.com/t/-/44006/152
DEL's take:
Both help to suppress the inductive spike seen at FET (and even 7135) turn-off. They do not seem to be necessary for 1S lights, but both you and Tom had failed 7135s with 2S.
Here: https://budgetlightforum.com/t/-/44006?page=6, post #189
I did also add C3 and C4 pads to Q8 2S driver
30mm TA driver
oh, ok, cool!!
Just fired up the MT03 - all seems to work ok so far. Not getting big power, but didn't bypass any springs yet. Wasn't sure how crazy the amps would get. Measured 14,600 lumens at turn on with VTC6's at 4.15V, drops to low 13,000's in 30 secs. Was expecting to break 20K, but guess I gotta least bypass springs. Not sure about their battery MCPCB's, and the setup in general.
Hhmm. Tried VTC5A's at 4.19V, did better, but from the 30 second test, I got about 100 lumens with the switch off, and it's staying that way... Sounds like I fried the 7135, so dunno bout the C3 and C4 helping...
Hi Tom E.
As I just posted in the TA drivers thread, last night I finished my MT03 mod successfully.
I’m using an TA46-LDO driver with only the FET (no 7135), flashed with NarsilM.
This combo is working fine, with battery voltage reading, LVP, temperature reading/control and custom modes for the MT03.
Perhaps this setup could be interesting to yours needs.
I would be glad if could help you.
Yea, you read my mind, or, guess I read yours! That's exactly what I was thinking, but I'll let DEL know - he's been helping me out with these high powered lights. My 16X XHP50 light seems pretty stable now - I did have to replace the 7135 once.