No you're right mate,I shouldn't be fannying with the ECU to try compensate for a problem such as a vac leak,I will have a good look when I get chance to see if an exhaust/vac/boost leak is causing my many richness.

 

You still need to adjust your injector scaling to get the wideband readings correct

At the moment the injector scaling should be 1.00 as default, you will need to tweak the injector scale to get a correct wideband reading, forget base map, forget what it should be, thats just a map to get the car started, you will need to tweak most settings to suit your car, all 440`s flow differently, breathe differently, i had to tweak my injector scale down to 0.85 to get correct wideband readings and my base map was for my setup, injector wise etc, left at 1.00 i had wideband AFR`s of 19 at cruise !!!! Ouch ran like ****e, tweaked injecotr scale, boom, down to 14.8 at cruise

 

Cool,my cruise and idle look pretty good and very close to my map,it does bounce around a little on light 10-20% throttle but I believe this is perfectly normal. LTFT look good with a pretty solid 1.0 across the board,it's my wot readings that are a fair way off,my requested AFR now set at 11.8 high load and the wb reading 10.5.
I will check for leaks and give the Maf a clean and if all is good then look at Maf calibration and injector scale.

 

Your cruise (below 3k) and idle are controlled by lambda, you could put 6 in the AFR table and it wouldnt alter the wideband reading (unless you run a later ESL and can diable closed loop ? )

 

Yes I have the closed loop option,I need to spend some more time tuning light cruise with closed loop switched off so I don't get as much coarse correction,but like you say the lambda will always try and correct my fuel to get it close to stoich.

 

Wot boost and timing u using full load
Does switching of closed loop do anything on esl

 

switch off closed loop disables the ECU's fuel corrections on cruise so that you can see the overall MAF error a bit better.

If you do some datalogging with MAFv, actual afr, expected AFR, throttle angle then you can work out what your MAF error is. Do a quick chart in excel and see if your generally lower/generally higher or a little bit hit and miss across the board. If generally your lower or higher then hit up the injector scale. If your just a little hit and miss then tweak the maf scaling points instead. Unless your speed density then just fudge the fuel map in raw mode.

 

At the moment I'm just eyeballing what the AFR gauge is saying,I'm sure there must be a way of data logging the actual AFR's using the Plx and ESL just not sure on how,I will look into that one.

 

would love to see wideband logging in esl, would make life alot easier

 

So I take it that data logging wideband is not possible with ESL
That certainly makes things a little more tricky!
Does this mean as far as road mapping goes that it's virtually impossible to line up actual AFR and requested AFR ?

 

what I normally do for this is make sure at the end of the pull you let off the throttle and keep logging - then go back to cruise and then stop your log. What you'll have then is a drop in AFR to full lean when you let off and then back to cruise/14.7ish when you go on pedal again. Use the shape in the AFR log from your plx jobbie to line up with the stock o2 read from the ESL/engine log. Should just be a matter of chopping some cells from the top of the AFR row (if you view it as CSV in excel and add the wideband data as another column).

Just keep chopping cells from the start and "move cells up" as needed until the wideband chop lines up with the standard o2 - although stock location the front o2 can't read boost very well the drop to full lean as the injectors cut out is easily spotted.

 

My view is, its nice to get the Table to line up with actual AFR`s so try and adjust injector scale etc to get a close reading but at the end of the day, its the actual wideband reading that matters, as a crazy example, you could have afr`s table of 22 24 26 19 but if the wideband was reading 12, 11, 10.4 at full throttle etc thats what matters

 

Just seen your other thread, ***** bud, sorry to hear the bad news, all this is irrelevant now

 

Wideband logging has always been available on ESL. Turn off closed loop, connect the wideband output to the lambda loom signal wire, and the Lambda range will auto select to 0-5v instead of 0-1v.

 

Is it ok drive with closed loop of as manuals shows not all time
Would the logs be volts or afr

 

closed loop is better for fuel economy as the car will always try and target 14.7 for you. With closed loop off then your corrections need to be spot on or you'll be wasting fuel that's all.

 

Ah the joys of the Later spec ESL/ECU, i dont get thes eluxuries on my ESL.

Like above, closed loop is like the auto default option, with it off, you can makefor a slighlty leaner cruise AFR or if get it wrong, eat that vpower :-)

 

I thought you were running v2.0 Rig?

We have permanently installed widebands in our cars and switch them to narrowband emulation in closed loop.

Lambda logs are voltage as it is universal. You can apply the relevant transfer function to whatever wideband you have and whatever mode you run it in. Works very well, no port contention etc.

 

Yeah, Im running v2.0 ESL but for the 95 impreza, awaiting for your skills to make closed loop enable/disable a feature Oooo as well as antilag please

 

Andy, I run an LC-2 with gauge and simulated narrowband to the ecu, which is easily switched via software. So I would be looking at a voltage reading in my logs which should equate to (Voltage x 2) + 10 = AFR. Always logged afr outside of esl as I didnt realise I could do it within.

 

Yes, that is correct, it will auto range from 0-5v if you switch to wideband mode. I will build in a set of conversion factors that can be selected for a particular wideband, but you can of course just apply the conversion to the log file.

 

Thanks again Andy!