Conflicting lambda overlay values vs. Display AF:1
Edit: think I may have came up with a better question; I just entered 7 psi and changed it to inches and it came up as a negative number, just under Col on the map it has a " thing so I have been going back and fourth between the two thinking its either in psi or inches but number are correlating correctly, could the corrections be off because the #'s on map arent psi or inches? I have tried them both so not sure about that since #'s so far off either way but maybe I have it set to wrong setting.
Messing around with partial throttle under 5k rpms I changed the WOT determination on TPS to 39% for low fuel table but MAP still determines WOT box is checked also so I dont know if it matters what %age I put in there anyways also doesnt say at what map value it has to be at to determine WOT?? So first question
1: if box is checked for MAP determines WOT, what value does it have to hit to determine WOT?
Im trying to get ECU to just go off of tuned cells inbetween lets say pretty much -17 to +3
////I was just going off of Display AF's by graph datalogs scrolling, they look good but tuning each individual cell after a datalog was getting cumbersome (but better!)but me learning I was only making very small adjustments at a time so when I think I got this lambda overlay down and took some datalogs and started looking at what it wanted me to change it to; Im seeing conflicting information. So I'm thinking maybe Im not actually in open loop and the ecu in the lambda overlay corrections are still telling me to make corrections to a ECU still in closed loop maybe? but box is checked and then I also moved low fuel table TPS % down to like 39% just so I knew like no matter what I would be targeting open loop.
2: datalogs on lambda overlay want me to richen -vac up theres like some 100 samples of it being not in tgt lambda but when I actually scroll through graph of datalog the AF:1 Display shows a different AF in a GOOD limit for being in vac and or towards 0 into positive EVEN if I scroll it showing all blue on one cell (which if I understand correctly, is just pulling that # not all four correct? if it shows blue tinted in all four its interpolating from all four? vice cersa 2 or 3 whatever)
Im just putting around trying to learn; any info from some SME's would be awesome and appreciated, Thanks!
Timing is safe I just cant seem to lean it out from 10.9s:1 in positive, this is why I started looking for a smoother way and found the overlay, thinking by tuning each cell im not getting an accurate whole picture of the four cells being I guess divided up right even tho. I would go back and adjust all four to commmon trend of the map being anywhere from 4 to 6 hundred from left to right cells and anywhere from like 40 to 60 up and down the cell column, also judging and smoothing from how many cells it was pulling info from.
I started reading and loaded a datalog and it showed everywhere my datalog went, it needed corrections so I was like sweeet I can get a smooth solid 14 13 and 12 leading to eleven where I want lol or atleast more controlled #'s and then fine tune, but now its just like what do I even use this for? I dont think this could be it but could it be because I already have 2nd bank O2 off IIRC its just to verify comparing the two for a cat so Im just looking for a few Q's at this point.
3: Or does it only tune my WOT lambda adjustment Low and High tables, but no corrections come up on that window sooo?
Also low load in the settings always comes up with a positive # and high load always defaults to negative kinda confusing making me think its backwards.
Messing around with partial throttle under 5k rpms I changed the WOT determination on TPS to 39% for low fuel table but MAP still determines WOT box is checked also so I dont know if it matters what %age I put in there anyways also doesnt say at what map value it has to be at to determine WOT?? So first question
1: if box is checked for MAP determines WOT, what value does it have to hit to determine WOT?
Im trying to get ECU to just go off of tuned cells inbetween lets say pretty much -17 to +3
////I was just going off of Display AF's by graph datalogs scrolling, they look good but tuning each individual cell after a datalog was getting cumbersome (but better!)but me learning I was only making very small adjustments at a time so when I think I got this lambda overlay down and took some datalogs and started looking at what it wanted me to change it to; Im seeing conflicting information. So I'm thinking maybe Im not actually in open loop and the ecu in the lambda overlay corrections are still telling me to make corrections to a ECU still in closed loop maybe? but box is checked and then I also moved low fuel table TPS % down to like 39% just so I knew like no matter what I would be targeting open loop.
2: datalogs on lambda overlay want me to richen -vac up theres like some 100 samples of it being not in tgt lambda but when I actually scroll through graph of datalog the AF:1 Display shows a different AF in a GOOD limit for being in vac and or towards 0 into positive EVEN if I scroll it showing all blue on one cell (which if I understand correctly, is just pulling that # not all four correct? if it shows blue tinted in all four its interpolating from all four? vice cersa 2 or 3 whatever)
Im just putting around trying to learn; any info from some SME's would be awesome and appreciated, Thanks!
Timing is safe I just cant seem to lean it out from 10.9s:1 in positive, this is why I started looking for a smoother way and found the overlay, thinking by tuning each cell im not getting an accurate whole picture of the four cells being I guess divided up right even tho. I would go back and adjust all four to commmon trend of the map being anywhere from 4 to 6 hundred from left to right cells and anywhere from like 40 to 60 up and down the cell column, also judging and smoothing from how many cells it was pulling info from.
I started reading and loaded a datalog and it showed everywhere my datalog went, it needed corrections so I was like sweeet I can get a smooth solid 14 13 and 12 leading to eleven where I want lol or atleast more controlled #'s and then fine tune, but now its just like what do I even use this for? I dont think this could be it but could it be because I already have 2nd bank O2 off IIRC its just to verify comparing the two for a cat so Im just looking for a few Q's at this point.
3: Or does it only tune my WOT lambda adjustment Low and High tables, but no corrections come up on that window sooo?
Also low load in the settings always comes up with a positive # and high load always defaults to negative kinda confusing making me think its backwards.
Ok so done some reading, OEM Wideband isnt all that great richer then 13:1 // so Hondata made a AF corrections Display that corrects its inaccuracies for tgt AF's needing richer conditions. But now my AF correction is bottoming out on 12.25:1 AF is bottoming out on 10.14:1 hmmmm?
MorngWoodStewie, I skimmed over your post and all I can say with using the Hondata "autotune" recommended a/f ratios is be careful. Different things affect a sample, specifically throttle changes. If your datalog looks good at certain cells, then odds are it's probably fine. Tip in, lift, throttle changes all will affect the suggested % change.
Also, Hondata uses the AF corrected values for the suggested changes which may or may not be accurate as pointed out by Gernby. I haven't monkeyed with mine and tried to compare it with a wideband to show which is more accurate (AF vs AF corr), but perhaps one day I will. Another idea is it might not be a bad idea to install a new o2 sensor, as mine is now 10 yrs old.. I'm sure it can't hurt.
The WOT Lambda adjustment targets to my understanding apply a "correction" value to the fuel tables (which should be tuned to 14.7:1). So if you change the WOT lambda adjustment targets without altering your fuel tables, you will run richer/leaner at WOT depending on the values.
Also, Hondata uses the AF corrected values for the suggested changes which may or may not be accurate as pointed out by Gernby. I haven't monkeyed with mine and tried to compare it with a wideband to show which is more accurate (AF vs AF corr), but perhaps one day I will. Another idea is it might not be a bad idea to install a new o2 sensor, as mine is now 10 yrs old.. I'm sure it can't hurt.
The WOT Lambda adjustment targets to my understanding apply a "correction" value to the fuel tables (which should be tuned to 14.7:1). So if you change the WOT lambda adjustment targets without altering your fuel tables, you will run richer/leaner at WOT depending on the values.
From what I could gather, you can put from what vacuum to pressure you want it to tgt afr and change to. I'm talking about the lambda overlay tho in the setting and then the lambda tab not wot high n low tables.
I gave up at this point dyno tune this weekend.
Ya new oem wb would be good.
I gave up at this point dyno tune this weekend.
Ya new oem wb would be good.
Thread
Thread Starter
Forum
Replies
Last Post







