new $EE tuning thing!

**steveo** · 10-18-2016

... also any feature requests or anything? i hate to push out a release for three bug fixes...

**Terminal_Crazy** · 10-23-2016

Originally Posted by steveo

... also any feature requests or anything? i hate to push out a release for three bug fixes...

Yes. Analyse CL Performance BLM Average. Can we have L & R BLM averages please.

Thanks
Mitch

**steveo** · 10-23-2016

Originally Posted by Terminal_Crazy

Yes. Analyse CL Performance BLM Average. Can we have L & R BLM averages please.

you mean the population analysis?

i intended this analyzer module to be used to evaluate cell data distribution to determine more efficient rpm/map boundaries, have you found another reasonable use for it?

it would be fairly easy for me to add a left and right column, so i will.. just curious...

**Terminal_Crazy** · 10-23-2016

Originally Posted by steveo

you mean the population analysis?

i intended this analyzer module to be used to evaluate cell data distribution to determine more efficient rpm/map boundaries, have you found another reasonable use for it?

it would be fairly easy for me to add a left and right column, so i will.. just curious...

Readjusting the VE Tables since i milled the inlet manifold.
BLM's are running 120's - 128. MIles more stable than before. RHS BLM's are pretty much 128 in most cells. LHS varies between 122 & 132. Your average shows the average blm's running around 125.
I've since written some code to average L&R Blm's so i know where they both sit.

I wonder if others have struggled with split BLM's due to the manifold leaking underneath the ports. The stock LT1 was a far better fit when measured than the Edelbrock.

Thasnks
Mitch

**steveo** · 10-23-2016

ah ok for splits, i've always preferred graphing for that, but i see your point. i'll add the column.

edit: don't forget the analyzer has 'use leanest bank' designed specifically for tuning splitty engines based on trims..

**steveo** · 10-23-2016

please test

http://fbodytech.com/4-61-beta/

Code:

Fix bug that prevented 'silence extra modules' setting from working
Fix bug that sometimes prevented 'dump ram' setting from working
Stop counting errors during initial connection (unnatural serial events may be normal...)
Allow crazy values in linear voltage to AFR mapping (for lambada or edge cases)
Seperate left and right BLM values in the closed loop performance analyzer

**steveo** · 10-23-2016

unofficial lambda-oriented wideband CSV file now on this page

http://fbodytech.com/eehack-2/eehack-extras/

**babywag** · 10-23-2016

Originally Posted by steveo

... also any feature requests or anything? i hate to push out a release for three bug fixes...

Tuning module? To edit/flash timing tables and MAF tables?

Haven't installed my Innovate MTX-L yet, but ability to use/log/see lambda vs. AFR?
Last time I used WB for tuning, I preferred to use lambda vs. AFR by simply changing .adx in TunerPro to display lambda.

**steveo** · 10-23-2016

Originally Posted by babywag

Tuning module? To edit/flash timing tables and MAF tables?

this gets asked for a lot

theoretically if eehack did tune...

one choice is to write something that'd be weaker than tunerpro, no graphing, math, crappy table editing. it would only be good for people that like eehack and do not like tunerpro (a type of person that i don't really deal with often). the advantage is that it could certainly could work alongside the analyzer to input data, but if i add a 'propogate fuel changes button', im afraid noobs would blindly trust the analyzer data without sanity checking it, making their car run worse and worse with every pass, and blaming eehack for it.

... or it would be a superior or equal tool to tunerpro and consume my life for easily a year or more, but i would want it to be general purpose (so it'd edit any bin) so that wouldn't make any sense to put into eehack, unless eehack also started working for other vehicles for all functions, this is something called 'scope creep'.

neither of those scenarios make any sense, that's why as a design decision, eehack is an EE datastream tool and not more. it wont even change your bin on disk if you patch. that's a major reason why when i did require some slight bin changes to enable advanced features, i made them passive, to ensure i didn't cross the line into bin editing of any kind.

Haven't installed my Innovate MTX-L yet, but ability to use/log/see lambda vs. AFR?
Last time I used WB for tuning, I preferred to use lambda vs. AFR by simply changing .adx in TunerPro to display lambda.

lambada display is already almost possible. there is very little except some 'labeling' of the field as AFR.

to get a decent display, you can easily turn off the :1 suffix yourself, and increase the precision in the definition file. it's a human readable csv file easily edited in a spreadsheet program.

unfortunately the stopping point is that i've restricted the linear scaling configuration (the low/high point thing) to some 'sane' values for AFR. if i unrestrict them, that'd make it happen for you, you'd just have to determine lambada @0v and 5v or whatever.

would that be alright?