Very Very Lean at Idle

JoeJoe1 · Post by **JoeJoe1** » Sun Sep 04, 2005 9:48 pm

Just built my motor and started it for the first couple of times but can't keep it running for no more than 10 seconds because it Leans out so much the wideband can't read the AFR nomore. It starts at about 12.9 then in about 3 seconds it goes to 17.0 then it stops reading. Added more fuel to the first 2 columns and still the same??? Any suggestions??? Filter replaced, fuel pump new, injectors new.

Turbo Vtec Ef · Post by **Turbo Vtec Ef** » Mon Sep 05, 2005 3:44 am

ok what is the loop setting on: closed or open?

What input the the O2 is the ecu seeing? wideband or normal?

What motor and what basemap and what size injectors?

JoeJoe1 · Post by **JoeJoe1** » Mon Sep 05, 2005 8:05 am

I have it on open loop, but tried closed and the same happens.

How do you know what input from the O2 the computer is seeing? RomEditor is seeing wideband but I dont know if the numbers match exactly with the W.B gauge because I can't keep it on long enough to check.

It's a D16Z6 with stock injectors, also tried new venoms with 10% more flow bored .20 over Greddy turbo, kept the basemap for D16Z6 W/ Greddy kit just added a little more fuel throughout the map.

Would retarding the ignition or advancing it have to do with runing lean on idle?

Turbo Vtec Ef · Post by **Turbo Vtec Ef** » Mon Sep 05, 2005 12:39 pm

The best way to make sure the wideband matches the datalog is turn the key "on" have your wideband on but have the o2 for it unplugged. SO it will sit at 14.7 then connect to the ecu for datalogging and adjust the settings till the #'s match on the wideband and the datalogging. You must make sure if your using a wideband input to the ecu that you have it set that way on your chip.

JoeJoe1 · Post by **JoeJoe1** » Mon Sep 05, 2005 1:14 pm

Turbo Vtec Ef wrote:The best way to make sure the wideband matches the datalog is turn the key "on" have your wideband on but have the o2 for it unplugged

Unplug the signal wire or the actual sensor?

You must make sure if your using a wideband input to the ecu that you have it set that way on your chip.

Where do you set that in RomEditor?

Turbo Vtec Ef · Post by **Turbo Vtec Ef** » Mon Sep 05, 2005 2:36 pm

If you unplug the O2 sensor were it goes to the wideband this should keep it at 14.7 and also most widebands calibrate that way.

To go into setting go file, settings, then lambda. The lambda or air fuel is how you tell the ecu and rom editor what input you will be using, and the edit conversion table is how you set it up and calibrate it to your wideband.

JoeJoe1 · Post by **JoeJoe1** » Mon Sep 05, 2005 4:26 pm

I just came back from storage I have to drive like 30min to get to my car and gas is EXPENSIVE right now so I have to figure this out quick. I did that about the O2 sensor I disconnected it and saw that HondaLogger was reading 15.7 while the gauge displayed 14.7 it was .34 off so I added .34 to all the rows in the table this would be the correct action right?

Now I think it would be better to add the datalogging file so it's attached look at the sensor inputs and see if you find anything wrong.

Revs bounce up and down

Post by **Spunkster** » Tue Sep 06, 2005 10:30 am

Try the Reset proceedure for the interface box as detailed in the installatioin manual or the user's guide.

JoeJoe1 · Post by **JoeJoe1** » Tue Sep 06, 2005 10:44 am

Just came back and still the same pronlem??? the LED on the box is solid and no error codes.

Post by **Spunkster** » Tue Sep 06, 2005 2:42 pm

I would suggest takting the car to one of our dealers to be properly tuned on the dyno...there may be other issues that need to be addressed as well.

Turbo Vtec Ef · Post by **Turbo Vtec Ef** » Tue Sep 06, 2005 4:14 pm

K back up a bit here.

Your using the rom editor and your logging the the a/f ratio and percent it is off from the target right?

Hondalogger has nothing to do with this, I hardly ever use that thing.

JoeJoe1 · Post by **JoeJoe1** » Wed Sep 07, 2005 3:49 pm

Removed a vacuum line and it idled high = No vacuum leak.
Disconnected sensors one at a time, they made changes but did not remove problem = Sensors are good.
Took out ROM and made it go into limp mode - Idled fine, just rich = Tuning problem.

Had messed with fuel but not timing so I retarded the timing for idle just 4 degrees and everything ironically is fine no revs going up and down anynomore.

Hope this helps others...

turbosi92 · Post by **turbosi92** » Fri Sep 09, 2005 6:33 am

Post the .bin file.

JoeJoe1 · Post by **JoeJoe1** » Sat Sep 10, 2005 10:56 pm

From when the tuning was bad or when I fixed it? the one with the bad tuning was posted but somehow got removed is that the one you want? do you have a similar problem or something?