Hondata

Hey what do you guys do for tuning in column one and two. I am getting really weird reading of negative 20 to negative 70 in column two, and negative 100 to negative 800 in column one, what do you guys do about this. Thanks for your help.

What do you mean "negative"?

that can't be good... do you idle in columns 3 and 4?

are you tuning with by using target a/f?? even if so, i can't imagine it being THAT far off.
more info would help. i don't think any of us know what you are talking about :(

I'm sorry for not being more specific. I idle in column 2 and three. I use a wideband for my tuning. What I mean is that in the delta lambda menu for the fuel maps, the window that shows how many parts of fuel you are away from the target. This is the window where I am getting my huge negative values in column 1 and 2. Just to be more clear, when the delta lambda hits zero, you have reached the desired lambda that you are trying to achieve. For idle I would imagine 14.7 afr is the target, but for some reason I'm leaning out a little at idle and getting the huge negative values, like I have way too much fuel. Just wondering if anyone else has this problem, someone told me to ignore column one and two because of this but I'd rather tune it properly.

gSIr wrote:I'm sorry for not being more specific. I idle in column 2 and three. I use a wideband for my tuning. What I mean is that in the delta lambda menu for the fuel maps, the window that shows how many parts of fuel you are away from the target. This is the window where I am getting my huge negative values in column 1 and 2. Just to be more clear, when the delta lambda hits zero, you have reached the desired lambda that you are trying to achieve. For idle I would imagine 14.7 afr is the target, but for some reason I'm leaning out a little at idle and getting the huge negative values, like I have way too much fuel. Just wondering if anyone else has this problem, someone told me to ignore column one and two because of this but I'd rather tune it properly.

my car idles in one and two.. i dunno.
anyway, first: are your target A/F ratios set right? i.e. if they are set at 1000:1 then of course it would be off.
posting your config file would help, also.

they are set to 14.7 to 1 all the way across to column 7, i don't see why i would be getting numbers like that far off, is there a way i can record it and show it to everyone

This is a small datalog file i have, see what i can do to fix it, I still have a lot of work to do with this map

oh yeah and heres my map, this might help. lol

You can ignore the unusual spikes. As long as you view the 2d graphs ad they are relatively smooth and your A/F for the most part is smooth, then you dont' need to make any changes. You must remember that when you let off, there is a split second where the wideband will read rich before showign the fuel injectors shut off.

oh ok, so when the injectors are shut off the smanager doesn't log that, it makes sense of why it would read so rich, is there anything i can do to solve this?

The problem is that your lambda sensor is showing full rich upon overrun, whereas it should show full lean. Look at around 1:10 in your datalog - the injectors are off, but the lambda is cycling back and forward between full rich and full lean. This is a lambda sensor issue.

when the lamba meter sees a really lean condition, it switches to a percentage of oxygen and that switch throws off column one and two, thanks everyone for your help

In Settings, Sensor Overlay, Sensor Overlay 1 (Lambda), try setting the minimum overlay value to 11 and the maximum overlay value to 19. This should filter out some of the rich/lean cycles. You could also set the mimum TPS to 5% which should do the same thing.