pcmhacking.net

vsslpr wrote:cool- ive done that so if (looking at my log) at idle the afr commanded is 14.2 and my wideband shows say anywhere between 14.4-15.1 thats what the afr actually is it looks ok in the log the wideband afr seems to move accordingly with narrowband o2 millivolts. cheers guys

You could be seeing a commanded idle afr of 10:1 and your wideband could still be displaying between 14.4-15.1 It’s dependent on how the program is setup.

The commanded A/F is a setting that you decide it’s value based on tuning experience. It will only track your wideband sensor if you have every thing set up correctly.

A standard NB oxygen sensor in good condition switching in closed loop will give a very accurate reading of 14.7:1 on a well calibrated wideband sensor so look in your logs and note when your commanded A/F is 14.7:1 and see what your wideband is reading.

The wideband sensor will ONLY follow the commanded A/F ratio if you have setup and tuned your engine correctly. If at idle your commanded A/F is 14.2:1 your wideband should be the same.

This takes quite some time to achieve.

kojab wrote:

vsslpr wrote:cool- ive done that so if (looking at my log) at idle the afr commanded is 14.2 and my wideband shows say anywhere between 14.4-15.1 thats what the afr actually is it looks ok in the log the wideband afr seems to move accordingly with narrowband o2 millivolts. cheers guys

You could be seeing a commanded idle afr of 10:1 and your wideband could still be displaying between 14.4-15.1 It’s dependent on how the program is setup.

By program setup do you mean settings in LogWorks LM Programmer? my wideband afr range is set to just the default

kojab wrote: The commanded A/F is a setting that you decide it’s value based on tuning experience. It will only track your wideband sensor if you have every thing set up correctly.

A standard NB oxygen sensor in good condition switching in closed loop will give a very accurate reading of 14.7:1 on a well calibrated wideband sensor so look in your logs and note when your commanded A/F is 14.7:1 and see what your wideband is reading.

I've calibrated the wideband sensor as per the instructions in the innovate manual- thats why I suspect that it is inaccurate i just wasnt 100% sure how close theyre meant to be (now reading this i think mine is not accurate enough..)

kojab wrote: The wideband sensor will ONLY follow the commanded A/F ratio if you have setup and tuned your engine correctly. If at idle your commanded A/F is 14.2:1 your wideband should be the same.

This takes quite some time to achieve.

This is all so far on a stock tune havent touched the cal at all yet because i want to make sure its all good to go before i do!

VL400 wrote:It does not look miles off.

You know that the engine is richer than stoich from the narrowbands, higher than 450mv is richer and less than 450mv it is leaner than stoich. So.. RT edit the idle AFR table and get the target to 14.6 AFR,

which is the idle AFR table your refering to? The only table I can see that has afr 14.2 is: Open loop AFR vs CTS which im assume is only for idling while the other table (afr vs cylair vs rpm) is for under load?

At idle it uses "Open Loop - Air Fuel Ratio V's Coolant Temperature" after a few seconds of entering idle mode.

cheers- updated my xdf to make note that its an idle table lol

question about the bubble tracing within the fueling and spark tables- why does the bubble appear in any table that's open in TP for example if I have high and low octane spark table open theres a bubble in both? or if its idling theres a bubble in the open loop afr vs cylair and rpm table?

so you can trace the tables, especially if your realtime tuning then you an pinpoint and change in realtime.

sorry should have been more clear- i meant why is it tracing in both tables at once surely it will only be setting spark advance from 1 table at a time? I thought that it read from high octane table initially but depending on knock counts it shifted over to a less advanced table being the low octane table?

tunerpro doesn't know this though, it's only tracing the X and Y axis it's told to.

hmm.. ok so the way to tell which table its actually reading from is to look in the history tables and see which matches the closest right? btw i noticed the axes on the history tables dont match those in the cal- does that matter?

if you trying to match spark on your main tables you also have other things at play, like coolant,intake air temp,power enrichment, lean cruise spark offset tables. this will amend the spark from the main tables.

You can edit your history tables by going to the Two cogs icon on the toolbar, edit adx. history tables and edit the x or y

It could be something to look at for enhanced mod.