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..
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..
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
unofficial lambda-oriented wideband CSV file now on this page
http://fbodytech.com/eehack-2/eehack-extras/
i'm thinking i'll make the default view level for the parameter selector 'extended', it makes more sense now that it's 'searchable'
I know...I was just daydreaming. My thoughts were simply for ease of one app to tweak/fine tune.
Definitely not asking for full blown tuning!
Fully understand your reasoning on why not to do it.
Your call/choice. I personally just thought it would be a handy addition.
I yanked the WB from my Jeep, so I'll try to get it installed in the Caprice asap.
Been meaning to, now I have more motivation.
Thanks for the fixes!
Edit: I can reprogram the Innovate WB pretty easily, so what you wrote above regarding Lambda display request should be doable?
It took some playing with TunerPro, but I believe it was pretty dead on accurate.
That was ~3yrs ago, so I'll have to find my thread and refresh my craptastic memory.
Last edited by babywag; 10-24-2016 at 03:29 AM.
Tony
'88 Jeep Grand Wagoneer (aka Babywag)
'67 Jeep J3000
'07 Dodge Magnum SRT8
i'd like for you to test the definition file i posted above, and try to get your wideband in lambda mode working with the latest beta. that'll prove it can be done. otherwise i'll make more changes until you get it working.
honestly though once you try eehack with patched bin and afr target percentage calcuations in the analyzer, you might not want it (it relates AFR target to perceived AFR directly, and builds you a percentage of correction required table vs ve or maf)
I just prefer lambda, today's fuel isn't 14.7, honestly I doubt it's consistent w/ 14.13 either.
You've got different blends for summer/winter, the added ethanol, and all the additives the dump in to supposedly decrease emissions.
Not to mention the different additives that individual brands use, supposedly cleaning valves etc.. etc.
I like seeing lambda on the WB display, I think it's more accurate. When mine was set to AF display it's a calculated number, and I just don't think it is as accurate.
Tony
'88 Jeep Grand Wagoneer (aka Babywag)
'67 Jeep J3000
'07 Dodge Magnum SRT8
The definition file works, and a minor adjustment to trim the voltage puts it in (what appears to be) sync with the actual gauge.
But, as you mentioned above AFR is already working.
Using lambda on analyze page doesn't yield much in terms of useful tuning calculations.
I'm sure this could be changed?
When run it simply shows all 1.0, or if changed to percentage 93%
Since it already works using AFR, unless you want to pursue/test lambda more, I can just use AFR.
Tony
'88 Jeep Grand Wagoneer (aka Babywag)
'67 Jeep J3000
'07 Dodge Magnum SRT8
Bookmarks