Narrowband Tuning Tool

[steveo]

please demonstrate why it isn't working for you

but imo you're trying to do something that shouldn't need to be done, my program analyzes the whole data set, why would you only want a small portion?

edit: in the background of your screenshot i see your attempt to make a nonesnse table. i am glad that my software wouldn't let you make it.

[steveo]

tutorial: http://fbodytech.com/trimalyzer/trimalyzer-how-to/

[steveo]

bump for more beta testers! so far it's working pretty well, i tried it on a friend's tpi car that trims were out to lunch (didnt have time to reprogram with the changes, but the analysis looked sane..)

if you can't test it for me, at least throw me some CSV logs from your own driving and let me parse them so i can ensure it's working with maximum number of environments.

if you make a custom table that works properly, please screenshot (and tell me what mask it's for) it so i can add it to presets too

[Chewy1576]

Here is a screenshot for my headers and filters with $0E. I would attach the log I'm using but it's forced open loop for WBO2 tuning. The $0D table you already have configured works for $0E also. I'm going to be swapping the intake, throttle body, and injectors soon so I would be starting all over anyway.

Capture1.JPG

[Stokes1114]

1.PNG

Ive only ran 2 logs through it so far, but seems to be giving very uniform results. I am using $E6 for 16168625.. the screenshot is for the off idle VE table. Its the same setup as the $0D mask. I could load old datalogs csv if you would like to try for yourself. Ill do some more logs and post results tomorrow evening.

[steveo]

Ive only ran 2 logs through it so far, but seems to be giving very uniform results. I am using $E6 for 16168625.. the screenshot is for the off idle VE table. Its the same setup as the $0D mask. I could load old datalogs csv if you would like to try for yourself. Ill do some more logs and post results tomorrow evening.

cool! those are some huge trims, can you send me that log? that might be a good test case to see if my algorithm is tuned properly..

[dud]

Love the program. Using the "Loose Cell" setting, it pretty closely matches what my spreadsheets come up with. What I like the most is that it is quicker than excel when loading several datalogs. And I don't need a separate tool for ALDLdroid and TunerPro.

Thanks for the source too. I use linux for pretty much everything I do and I have been able to compile the program on linux and it works great. Just have a bug when trying to copy contents of the clipboard into TunerPro(running on wine). I think it has to do with the way X11 (linux) sees the clipboard. Not a biggie though. I can use a native linux text editor to do the hand off. The clipboard works fine if I'm running both programs, Trimalyzer & TunerPro, with wine.

I'm no programmer by any means, but I have edited the dictionary to include some extra terms so the "Field Mappings" will be auto detected. I also edited the "definition" files trying to get more filters to be auto detected. No joy on that one though.

I too am using the $E6 mask.

I've attached some screenshots of the way I set it up.

[Stokes1114]

cool! those are some huge trims, can you send me that log? that might be a good test case to see if my algorithm is tuned properly..

Here is the csv log file that I ran through. This was the first change from the stock bin. Please let me know if it looks to be doing right. Before this one tune I would run rich all the time, 105-120..now Im seeing some in the low to mid 130's at highway steady speeds. Im going to keep running logs through. Great tool, and thanks for making this for everyone!