NarsilM - configurable e-switch firmware for Multi channels, new v1.2 BETA

504 posts / 0 new
Last post
Tom E
Tom E's picture
Offline
Last seen: 6 hours 4 min ago
Joined: 08/19/2012 - 08:23
Posts: 14629
Location: LI NY

joechina wrote:
What Giorgoskok wrote. If you choose only mode #1 and enable moonlight you end up with two modes. If you choose mode set #7 (which has 7 values in the table) and enable moonlight you will end up with 8 brightness levels. (On the Q8 product page is under product detail a table where it is clear that moonlight is included, when switched on https://www.banggood.com/BLF-Q8-4x-XP-L-5000LM-Professional-Multiple-Ope... ) Tom E I guess the cube root modes are the evenly spread ones? What is the reason for 2A instead of 2.5A max? Reduced wear?

Previous post has the GT mode sets. The Q8 is different.

As the Mrs said (Steve), the intent is prolonged runtime to max at 2.0A. If you want the full 2.5A, there's a duplicate set of modes available shown above, plus in ramping, ramping max's out at 2.0A but a 2X click goes to turbo at 2.5A.

joechina
Offline
Last seen: 2 months 1 week ago
Joined: 03/05/2016 - 08:23
Posts: 1459
Location: Germany

Tom,
The Q8 in MODES:
What is the lock out comand?
(I thought 2x + click&hold )

But on my Q8 it is 4 clicks like in RAMPING.

Edit: I already did a reset to factory.

Lazy-R-us
Offline
Last seen: 4 months 2 weeks ago
Joined: 09/13/2015 - 00:30
Posts: 685
Location: Carolinas, USA

joechina wrote:
Tom,
The Q8 in MODES:
What is the lock out comand?
(I thought 2x + click&hold )

But on my Q8 it is 4 clicks like in RAMPING.


joechina, According to your cheat sheet it is 4 clicks for lockout in both ramping and discrete mode, I just verified with one of mine as well.
[edit]It does work this way, but I read the UI cheat sheet wrong. Tom has verified this is a bug.[/edit]

Lazy-R-us

Tom E
Tom E's picture
Offline
Last seen: 6 hours 4 min ago
Joined: 08/19/2012 - 08:23
Posts: 14629
Location: LI NY

In MODES operation:

  • 2 quick clicks followed by click&hold works for me (as designed)
  • 4X clicks though will restore it from lockout, as well as 2X clicks + click&hold (as designed, both ways work).
  • Just tried it: the 4X clicks to enter lockout in MODES is also working -- this was unintended. I did not want it to function like this because someone can click quickly through modes and unintentionally lockout the light. Granted though, I made the multi click operations pretty quick, so it's harder to get it occur unintentionally, but it can happen.

Ok, another bug frown

fyi: Don't have a Q8 with me, but I'm using a Manker U11 modded with NarsilM v1.0, so exactly the same as the Q8, or should be?

joechina
Offline
Last seen: 2 months 1 week ago
Joined: 03/05/2016 - 08:23
Posts: 1459
Location: Germany

Thanks for acknowledge Lazy-R-us.

But I wrote in the cheat sheet for MODES you can only lock out if the lamp is off, with 2 clicks and a click&hold.

I noted that a year ago, so maybe Tom changed it.
Tom answered above

Lazy-R-us
Offline
Last seen: 4 months 2 weeks ago
Joined: 09/13/2015 - 00:30
Posts: 685
Location: Carolinas, USA

joechina wrote:
Thanks for acknowledge Lazy-R-us.

But I wrote in the cheat sheet for MODES you can only lock out if the lamp is off, with 2 clicks and a click&hold.

I noted that a year ago, so maybe Tom changed it.


Hey, you put a lot of work into that sheet, and it has helped me figure out how to use this great light. But, apparently, I need to print it even BIGGER, because I neglected to read that the left two tables differ based on “from on” or “from off” and have left/right sections for ramping or modes.

I’ll go edit my post above.

Lazy-R-us

joechina
Offline
Last seen: 2 months 1 week ago
Joined: 03/05/2016 - 08:23
Posts: 1459
Location: Germany

I am sorry for the small size!

Your printer should have a poster mode. Print it in double size and glue it together.

Another way to use:
- put the PDF on your smartphone. There you can zoom in.
- view the PDF on your computer screen.

Yes the left part has the clicks for

- Lamp is OFF for RAMPING
- Lamp is ON for RAMPING
- Lamp is OFF for MODES
- Lamp is ON for MODES
Each row has the same klicks, it is sorted by clicks, not by actions: You see there is double click for RAMPING, but not for MODES. And if you want battery check when you are in MODES you can see you reach it only if the lamp is off.

vestureofblood
vestureofblood's picture
Offline
Last seen: 1 day 6 hours ago
Joined: 08/17/2012 - 15:21
Posts: 1987
Location: Missouri

Let me start by saying thanks so much to you all for helping me.
.

joechina wrote:
vestureofblood wrote:

Any bullet points you want me to be sure an touch on FAQ etc?

I got a few PMs and questions about the cheat sheet.
Some people seem to have problems to understand the tables and the manual.

I would point out that the normal operation in RAMPING and MODES is very different.

If you look in the first table of the cheat sheet you will see that only the commands for ON and OFF are the same.
I didn’t expect this. I thought a few commands like turbo and moon are the same.

Some people had a problem to switch OFF, lamp seems not respond to click:
Timing of click for off, hold the switch just a tad too long and the Q8 will not register it as shut down command but treat it as a very short ramp command. Your light is not broken. Please try a very fast and short click.

People did asked for examples with complete click-ology.
Best would be to have a lot of subtitles in the video.

Reset to factory in RAMPING:
3x, 2x, 2x, press&hold (for 1.2sec) till 4 blinks

Reset to factory in MODES:
1x, click&hold (for 2.5 sec), 2x, 2x, press&hold (for 1.2sec) till 4 blinks

Switch from MODES to RAMPING
(while holding, the lamp goes into strobes, that’s normal)
hold for 3.2sec, after two short blinks and one blink, 2x.
The lamp continues to blink out configuration for RAMPING.

Switch from RAMPING to MODES
(you hold for a long time, please ramp down, it’s easier on the eyes)
hold for 8sec, after two short blinks and one blink, 1x.
The lamp continues to blink out configuration for MODES.

Strobe Modes:
The normal way (RAMPING: 2x, 2x, Y clicks [Y= 1…4] ) is time sensitive because of the lock in modes. And I got PMs people are not quick enough for the Y clicks, because the Y have to be done right after the second double click.
If navigation is hard, try:

RAMPING from off/on:
Double click, double click, 4 clicks in a row. Now you are in the 5th strobe = 10 sec beacon.

MODES from off/on:
Longhold (over 1,2sec), 4 clicks in a row. Now you are in the 5th strobe

Now you can go back via click&hold. You can go back 4 times, then comes OFF.
If you go backwards you have time to do this.

For RAMPING:
If you want to remember how many clicks to go to B attery = 3 clicks
The B and 3 look quite similar.

Ups, that got lengthy
Sorry Joe

Thank you, I will be sure to incorporate these points.

giorgoskok wrote:
Matt , is moonlight mode enabled ?

If yes , modes are counted without the moonlight .


Yes, that is definitely part of the problem I had. Didn’t realize that.
Tom E wrote:

vestureofblood wrote:
Hi Tom, Working on the UI vid today. Most everything seems to be going fine, but I have one hiccup. In the “modes” group the count seems to be off some how. On the ref sheet I see that the default when switched to modes should be group 4, but I get 5 mode as default. I tried switching to the first group and I got 2 mode, the second group I get 3 mode. I thought maybe the whole thing was just off by one click but group 5 for me is single mode. I did try resetting to default, but the result is the same after ward. As far as I can tell everything else works as described in the sheet. I was able to change the moon mode levels etc. Any ideas?

Ohhh – think the mode sets are “unique” for the GT buck driver build.


I got all the info here. I’ll post.


This is directly from the code:



//——————————————————————————————————-
// Buck driver 2 channel modes
//——————————————————————————————————-

// 2.0 A max modes
// 1 mode 2.0A
PROGMEM const byte modeFetSet1[] = { 201}; // for analog control
PROGMEM const byte mode7135Set1[] = { 255}; // for LM3409 enable/PWM

// 2 modes /4 25% 2.0A
PROGMEM const byte modeFetSet2[] = { 42, 201}; // for analog control
PROGMEM const byte mode7135Set2[] = { 255, 255}; // for LM3409 enable/PWM

// 3 modes /3 11% 33% 2.0A
PROGMEM const byte modeFetSet3[] = { 26, 53, 201}; // for analog control
PROGMEM const byte mode7135Set3[] = { 255, 255, 255}; // for LM3409 enable/PWM

// 4 modes /2 12.5% 25% 50% 2.0A
PROGMEM const byte modeFetSet4[] = { 27, 42, 77, 201}; // for analog control
PROGMEM const byte mode7135Set4[] = { 255, 255, 255, 255}; // for LM3409 enable/PWM

// 5 modes cube-oot 1% 7% 22% 52% 2.0A
PROGMEM const byte modeFetSet5[] = { 25, 25, 39, 80, 201}; // for analog control
PROGMEM const byte mode7135Set5[] = { 24, 170, 255, 255, 255}; // for LM3409 enable/PWM

// 6 modes cube-root 1% 5% 15% 32% 60% 2.0A
PROGMEM const byte modeFetSet6[] = { 25, 25, 30, 51, 94, 201}; // for analog control
PROGMEM const byte mode7135Set6[] = { 24, 126, 255, 255, 255, 255}; // for LM3409 enable/PWM

// 2.5 A max modes
// 1 mode 2.5A
PROGMEM const byte modeFetSet7[] = { 255}; // for analog control
PROGMEM const byte mode7135Set7[] = { 255}; // for LM3409 enable/PWM

// 2 modes /4 25% 2.5A
PROGMEM const byte modeFetSet8[] = { 45, 255}; // for analog control
PROGMEM const byte mode7135Set8[] = { 255, 255}; // for LM3409 enable/PWM

// 3 modes /3 11% 33% 2.5A
PROGMEM const byte modeFetSet9[] = { 27, 58, 255}; // for analog control
PROGMEM const byte mode7135Set9[] = { 255, 255, 255}; // for LM3409 enable/PWM

// 4 modes /2 12.5% 25% 50% 2.5A
PROGMEM const byte modeFetSet10[] = { 29, 45, 86, 255}; // for analog control
PROGMEM const byte mode7135Set10[] = { 255, 255, 255, 255}; // for LM3409 enable/PWM

// 5 modes cube-oot 1% 7% 22% 52% 2.5A
PROGMEM const byte modeFetSet11[] = { 25, 25, 41, 90, 255}; // for analog control
PROGMEM const byte mode7135Set11[] = { 26, 185, 255, 255, 255}; // for LM3409 enable/PWM

// 6 modes cube-root 1% 5% 15% 32% 60% 2.5A
PROGMEM const byte modeFetSet12[] = { 25, 25, 31, 56, 106, 255}; // for analog control
PROGMEM const byte mode7135Set12[] = { 26, 136, 255, 255, 255, 255}; // for LM3409 enable/PWM



So what does all this mean?


First 6 sets max out at 2 amps, 2nd set of 6 are full power at 2.5A.


DEL’s cube root is percentages calculated,similar to TK’s python script that calculates lumens.


 


All these sets exclude moon mode. If you have moon mode enabled, then you’ll get the modes above, but also starting with your currently set moon mode level.


 


Does this help? 


YES! That definitely looks like what I am seeing. Will you be making a ref sheet with this outlined in it? I want to direct people to the sheets you an JoeChina have made right form the start.

In Him (Jesus Christ) was life; and the life was the light of men. And the light shineth in darkness; and the darkness comprehended it not.
http://asflashlights.com/ Everyday Carry Flashlights, plus Upgrades for Maglite.

Tom E
Tom E's picture
Offline
Last seen: 6 hours 4 min ago
Joined: 08/19/2012 - 08:23
Posts: 14629
Location: LI NY

Think we should be doing the docs - dunno how far off we are, or how finalized all this is. Waiting on replies from our contact.

vestureofblood
vestureofblood's picture
Offline
Last seen: 1 day 6 hours ago
Joined: 08/17/2012 - 15:21
Posts: 1987
Location: Missouri

awesome, thanks

In Him (Jesus Christ) was life; and the life was the light of men. And the light shineth in darkness; and the darkness comprehended it not.
http://asflashlights.com/ Everyday Carry Flashlights, plus Upgrades for Maglite.

joechina
Offline
Last seen: 2 months 1 week ago
Joined: 03/05/2016 - 08:23
Posts: 1459
Location: Germany

OK, my switch LEDs are off.

What I did:
1. Was in MODES and got “temporarily locater LED OFF” with 1x + click&hold
2. Switch to RAMPING
3. Switch LED still off

From a strict logik it’s ok this way.
As a user it would be nice if the SW LED start working.
But its also garbage user input.

I don’t know, if people fumble to much they should reset!?

JasonWW
JasonWW's picture
Offline
Last seen: 2 hours 18 min ago
Joined: 10/22/2016 - 11:41
Posts: 12860
Location: Houston Texas

Sometimes I think the complications and issues associated with the indicator light in the side switch are just not worth it. I’m mainly referring to mass production lights like the Q8.

Would it be a step backwards or an improvement to just have the side switch light stay on whenever the batteries are connected?

I’ve got two narsil lights that I’ve wired up so the switch always stays lit and it’s been super simple. No funny blinks, you always know when power is applied or if the light is locked.

Since Narsil can be quite complex, why make it even more complex with indicator functionality?

Texas Ace Lumen Tube and JoshK Sphere calibrated with Maukka lights

Click this to go to signature links. I'm still around, just not reading many new threads.

Tom E
Tom E's picture
Offline
Last seen: 6 hours 4 min ago
Joined: 08/19/2012 - 08:23
Posts: 14629
Location: LI NY

Well it's open source. It's easy to add a simple compile switch to just turn it on upon power up and stay on. I could also add this to the switch configuration settings UI. You lose some functionality of course - channel use indicator blinks, LVP blinks, etc.

LightRider
LightRider's picture
Offline
Last seen: 3 years 5 months ago
Joined: 08/05/2015 - 09:52
Posts: 2007
Location: U.P. MI, USA

To Tom or any eaqually intelligent individual:
What has been the go to way if limiting max output?

I am using the otr m3 setup and have tweaked some settings in narsilm.c but the only thing I need to do now is limit output some how. I guess I could adjust the pwm values in the mode sets but it would be hard to scale them down to keep the modes balanced. Also, That wouldn’t work for ramping.

I read somewhere along the line that mode groups and ramping can be scaled back while at the same time leaving the double click to turbo at full 255 value. This would be my preferred way of setting up this light if possible.

So, I’m sure it’s been covered but if someone can refresh me or get me started or point me to a previous discussion I will be grateful! Smile

LightRider
LightRider's picture
Offline
Last seen: 3 years 5 months ago
Joined: 08/05/2015 - 09:52
Posts: 2007
Location: U.P. MI, USA

Also, I have anew feature request.
It would be nice if the user could select between volts/tenths battcheck and 1-10 batt level via the setups file.

Just a thought. Would be nice for me, but I may be alone. Idk?

Thanks for your work Tom!

LightRider
LightRider's picture
Offline
Last seen: 3 years 5 months ago
Joined: 08/05/2015 - 09:52
Posts: 2007
Location: U.P. MI, USA

Oh yes. I also can’t find where to define the type of 7135 used. I see it referenced to in the code but can’t find where the value is set. Maybe it is a sub setting of a larger setting group defined?

LightRider
LightRider's picture
Offline
Last seen: 3 years 5 months ago
Joined: 08/05/2015 - 09:52
Posts: 2007
Location: U.P. MI, USA

Anyone have any ideas how to throttle these drivers?

LightRider
LightRider's picture
Offline
Last seen: 3 years 5 months ago
Joined: 08/05/2015 - 09:52
Posts: 2007
Location: U.P. MI, USA

Eh… no one? I guess I’ll start trying to scale the ramping tables by guessing at perceived percentages. Might take a while but I guess it should work. Atleast I’m racking up post count by conversing with myself. Silly

Tom E
Tom E's picture
Offline
Last seen: 6 hours 4 min ago
Joined: 08/19/2012 - 08:23
Posts: 14629
Location: LI NY

Ohh - sorry. Well. Have you though bout added resistance? Use 26/28 AWG long LED wires for example?

Sure you can rebuild the ramping table easy enough by running the Python script, tweaked to your needs, and redefine all the mode sets. In the source code I include the full python script options I used to build the tables (several). It's TK's pythons script: level_calc.py, in her repository.

// For FET+1: FET and one 350 mA 7135 (tested/verified to be smooth):
// level_calc.py 2 150 7135 3 0.3 150 FET 1 1 1500
PROGMEM const byte ramp_7135[] = {
3,3,3,4,4,4,5,5, 6,6,7,8,9,10,11,12,
13,14,15,17,18,20,22,24, 26,28,30,33,35,38,41,44,
47,51,54,58,62,66,70,74, 79,83,88,93,99,104,110,116,
122,128,135,142,149,156,164,172, 180,188,196,205,214,223,233,243, // 49-64
253,255,255,255,255,255,255,255, 255,255,255,255,255,255,255,255,
255,255,255,255,255,255,255,255, 255,255,255,255,255,255,255,255,
255,255,255,255,255,255,255,255, 255,255,255,255,255,255,255,255,
255,255,255,255,255,255,255,255, 255,255,255,255,255,255,255,255,
255,255,255,255,255,255,255,255, 255,255,255,255,255,255,255,255,
255,255,255,255,255,0 // 145-150
};

PROGMEM const byte ramp_FET[] = {
0,0,0,0,0,0,0,0, 0,0,0,0,0,0,0,0,
0,0,0,0,0,0,0,0, 0,0,0,0,0,0,0,0,
0,0,0,0,0,0,0,0, 0,0,0,0,0,0,0,0,
0,0,0,0,0,0,0,0, 0,0,0,0,0,0,0,0, // 49-64
0,2,3,4,5,7,8,9, 11,12,14,15,17,18,20,22,
23,25,27,29,30,32,34,36, 38,40,42,44,47,49,51,53,
56,58,60,63,66,68,71,73, 76,79,82,85,87,90,93,96, // 97-112
100,103,106,109,113,116,119,123, 126,130,134,137,141,145,149,153, // 113-128
157,161,165,169,173,178,182,186, 191,196,200,205,210,214,219,224, // 129-144
229,234,239,244,250,255 // 145-150
};

Tom E
Tom E's picture
Offline
Last seen: 6 hours 4 min ago
Joined: 08/19/2012 - 08:23
Posts: 14629
Location: LI NY

btw, DEL uses his own equation, think it's cube root, forgot. Think he gave me the Excel spreadsheet he used to implement it. Works well - the GT buck driver/NarsilM is using it.

TK's though supports multiple channels, don't think DEL's does because it didn't have to, not sure of this though...

LightRider
LightRider's picture
Offline
Last seen: 3 years 5 months ago
Joined: 08/05/2015 - 09:52
Posts: 2007
Location: U.P. MI, USA

Ok. Thanks friend. I’ll look into what that py script means.

I tried just cutting the tables short but seems there is more to it than that.
I’m also trying to figure out how to slow the ramp speed down a bit but haven’t succeeded there either.

I’ll just keep trying things. How else will I learn right? But if another week goes by, I may need to ask for some more help. I’m patient but maybe sometimes, not really. Smile

Tom E
Tom E's picture
Offline
Last seen: 6 hours 4 min ago
Joined: 08/19/2012 - 08:23
Posts: 14629
Location: LI NY

If your on a Win platform, then you need to dnld Python runtime support - not sure what I used.

Here she has ramp_calc.py - think its the same: http://bazaar.launchpad.net/~toykeeper/flashlight-firmware/trunk/files/head:/ToyKeeper/Ferrero_Rocher/

To extend the time, that gets a little more involved, but do-able. I'm using 150 levels with a 16 msec clock, so it takes: 2.4 seconds. If you want to extend the time to 3.6 secs, then you need 225 levels to keep the code the same. There's other setting in the RampingTables.h file that need to be tweaked, but I think everything is there that you would need to tweak. Of course 225 levels takes up more RAM, but hopefully should be enough spare space.

 

Ooops, no. Here's level_calc_py: http://bazaar.launchpad.net/~toykeeper/flashlight-firmware/trunk/files/head:/bin/

 

 

ToyKeeper
ToyKeeper's picture
Offline
Last seen: 23 min 41 sec ago
Joined: 01/12/2013 - 14:40
Posts: 10731
Location: (469219) 2016 HO3

LightRider, subtle timing changes require changing the size of the ramp array to change how many frames it takes. Larger timing changes involve modifying the number of frames per ramp step. The maximum ramp length is somewhere around 240, IIRC, depending on how many special modes are defined above that and how much ROM space is available.

LightRider
LightRider's picture
Offline
Last seen: 3 years 5 months ago
Joined: 08/05/2015 - 09:52
Posts: 2007
Location: U.P. MI, USA

is there a description of how to use level.calc.py anywhere? im guessing its common knowledge that im missing. Actually ive already done this once before on my system so i know its setup ok i just cant remember what i did. its very frustrating! Im too disappointed in myself to continue tonight so good nite. Angry

ToyKeeper
ToyKeeper's picture
Offline
Last seen: 23 min 41 sec ago
Joined: 01/12/2013 - 14:40
Posts: 10731
Location: (469219) 2016 HO3

Either copy/paste the command line from Narsil’s header files, or run level_calc.py by itself and follow the prompts.

LightRider
LightRider's picture
Offline
Last seen: 3 years 5 months ago
Joined: 08/05/2015 - 09:52
Posts: 2007
Location: U.P. MI, USA

Spent the whole day getting python to run and then chasing errors in the script. Now it’s obviously not working correctly but I have no more errors to guide me and since I don’t know how it’s suppose to work I can’t track what is wrong. Anyway, if anyone else has figured this out and has run level_calc.py on Windows please give me some tips!

This is what it does when I use toms example numbers above. Most of the errors corrected so far have been syntax errors related to using python 3 over 2.

Tom E
Tom E's picture
Offline
Last seen: 6 hours 4 min ago
Joined: 08/19/2012 - 08:23
Posts: 14629
Location: LI NY

 

Wonder if it's case sensitive - code checks for "FET"...

Yours looks quite strange - it generated values over 255, weird. I've done a lot of them, experimenting, etc. This is one example below. I always use .BAT files so i can capture the exact command line options:

rem for FET+1, 124 levels 4X LED's
level_calc.py 2 124 7135 3 0.3 160 FET 1 10 5000

PWM1 values: 3,3,4,4,5,6,8,9,11,13,15,18,21,25,28,33,37,43,48,55,61,69,77,85,94,
104,115,126,138,151,164,178,193,209,226,243,255,255,255,255,255,255,255,255,255,
255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,
255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,
255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,
255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,0
PWM2 values: 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
,0,0,1,1,2,3,3,4,5,6,7,8,9,10,11,12,13,14,15,17,18,19,21,22,23,25,27,28,30,31,33
,35,37,39,41,43,45,47,49,52,54,56,59,61,64,66,69,72,75,78,80,83,87,90,93,96,100,
103,107,110,114,117,121,125,129,133,137,141,146,150,154,159,164,168,173,178,183,
188,193,198,203,209,214,220,225,231,237,243,249,255

 

Tom E
Tom E's picture
Offline
Last seen: 6 hours 4 min ago
Joined: 08/19/2012 - 08:23
Posts: 14629
Location: LI NY

What exactly do you want to generate? Maybe I can help? Is it for a Q8? What's the estimate on max lumens, if it's modded?

Yep - just proved it -- it's case sensitive - must specify FET in all caps. I got the same results as you when using "fet".

ToyKeeper
ToyKeeper's picture
Offline
Last seen: 23 min 41 sec ago
Joined: 01/12/2013 - 14:40
Posts: 10731
Location: (469219) 2016 HO3

It’s probably worth mentioning that python 2 and python 3 are different languages, not simply a version bump. Python2 scripts require python 2 to run correctly, and Python3 scripts require python 3 to run correctly.

However, scripts can often be written to support both 2.7 and 3.X… and I just pushed up a new trunk revision which does so. It also checks to make sure each channel is a recognized type, to avoid the huge values it was generating.

LightRider
LightRider's picture
Offline
Last seen: 3 years 5 months ago
Joined: 08/05/2015 - 09:52
Posts: 2007
Location: U.P. MI, USA

Ok. Thank you both. Tom, I’ll give the new file a try. I did not know 2&3 were different!

I’m using it to generate a throttled back ramp with double click to full power for the m3 clone. Anyway, I’ll report back. Thank much

Pages