Hondata

Ok, Thank you for clearing that up. So when logging the "fuel adjustment values" that are populated by the ecu, those percentage corrections are based off of the "Target Lamda tables" still though? If that is true, then I guess I can disregard the Com Lamda channel that I was seeing in the log not ...

But is the target lambda table the reference for Com Lambda? When I'm log compiling data in the fuel correction table, it is not matching what I have for Com Lambda. It's .99 throughout, and .85 Wot or boost. My lambda in the logger is matching my gauge, just not the commanded for some reason.

I think its a V1 or V2 serial # 05002865 I have an Aem Wideband installed through the Eld pin. In my datalogs I am seeing Lambda being recorded in my logs.

No ideas on this?

When I graph the log it is flatlined at .85 which is .0015 lamda from being exactly 12.5 afr. And also doesn't follow the low cam test cruise section that is set at 1.08 lambda. It is Reading .99 as target, and .85 at Wot.

I was not stating that Wot Compensation was the same as Commanded Lambda. That is the only thing that I can see that is listing a 12.5 or .85 lambda when at Wot. So I was asking if that somehow is causing my Commanded to not match what is in my Target Lambda tables. Spunkster, here is a log of the ...

Here is the tune file I have been using. Granted it is not tuned yet, as I'm trying to get the Commanded to match while logging. I upload this file, and as soon as I hit the datalog button, it changes from no Wot compensation, to the default of 12.5. I'm not sure if that is what is causing it or not.

I'm just reopening the last tune file from logging and making changes. Then uploading that saved tune to Kpro.

When logging and populating the air fuel error table, I have noticed my commanded air fuel is locked at .99 lambda, and when I got Wot on a boosted setup, it appears it is defaulting to the "Closed Loop Advanded"> "Full Load fuel Compensation" "fixed at .85 lambda or 12.5 a/f" Even when I deselect ...

I like to run what people would consider milder cams when boosted, and I I spec my turbo a little larger. Reason being is I use the more mild cams to get the turbo spooled a bit quicker, i like having a but of headroom on the turbo side if things. If I was racing in a class with limits on inducer ...

Ended up finding it while looking through Kmanager. Was under Options>Sensors>AF and edit units under AF and AfCmd. Set your upper and lower limits and change the display name and description. Just in case anybody wants to know...

Previously you were mentioning the difference in cam angle N/a vs. boosted. What is the general consensus on stock Tsx cams when running boosted vs. Na? More or less cam angle?

Why is there not an option to log Lambda instead of just A/f? I can have my settings setup for Lambda everywhere else, but in the logger when I'm logging , there is only a/f not Lambda, unless I'm doing something wrong. So it does me no good when the logger is recording A/f when I'm set up for ...

Honestly, I haven't noticed. I usually just let the logger record, then make changes when I'm stopped or not in the car. So busy right now, so I can't get my car on the dyno, so I've been chipping away at it on the way to and from work. Since your own car is never a priority to customer's cars, Haha ...

Brian, If you want to just test the theory of being tuned on a different size injector, an easier way to do it is just add "fuel trim" under the fuel trim tab. You can globally add and subtract fuel from there and not chase the cam angle maps, then you don't have to worry about messing up the "tuned ...