binder

iTrader: (8)

Ok, here is a pic of my dual wideband log.

I was looking at it and noticed they aren't the same and look quite a bit off based on the lines BUT if you look at the reading they are only .1 away from each other.

So, wideband 1 is on the 13 a/f line and wideband 2 is on the 14.5 line but the numbers say wideband 1 is 14.6 and wideband 2 is 14.5.

What the H is going on with this thing?

Dynosty

iTrader: (27)

Two different axis? Click on the logged channel to update the axis to that channel.

binder

iTrader: (8)

I'm confused. Is there an update area when I click on the channel? If u mean to just select it ived clicked back and forth between the two and nothing has changed in the logs.

Dynosty

iTrader: (27)

Send me the log, I'll have a look.

rcdash

iTrader: (18)

Weird - looks like a bug in the data logger.

binder

iTrader: (8)

that's what i thought. so i'm not sure which to trust, the lines or the display numbers. I've been trusting my displays because currently i don't have any gauges hooked up so i've been rolling around with my laptop.

i just rebooted my laptop so i'll check the log again and see if it makes a difference.

binder

iTrader: (8)

nope, after the reboot it didn't change anything. I actually found another place too.

This picture shows that the a/f is exactly 14.0 on each channel but the lines are a whole point off. Kind of strange.

I'm wondering now if my bank to bank differences that i've always had was just the fact that the trace lines are off and i never checked the actual a/f level.

Later today i'll try to uninstall and re-install the haltech software.

str8dum1

iTrader: (11)

why not look at the raw csv file.

binder

iTrader: (8)

That's what this is from. Do you mean look at it in another program?

str8dum1

iTrader: (11)

open the file in excel and see if they are 14.5 or not in the same spot

binder

iTrader: (8)

ya, i opened it in excel and none of the log channels are labeled and i have no idea what units it is in so it's basically pointless. It says "lambda" has a max/min of 2000. Last i knew lambda was set at 1 and then goes up and down from there. Plus i have no idea which column it refers to since they aren't labeled.

binder

iTrader: (8)

here is the csv file if you want to look. There is nothing in that mess of numbers that resembles the a/f i'm seeing in this log.

Dynosty

iTrader: (27)

Jeff, just checked out your csv in log viewer... it is an axis difference. Click the "Calibrations - O2 sensor" up top to change which line is bolded and the corresponding axis is displayed.

O2 1 is 10.5 - 16, and O2 2 is 10.5 to 18.

binder

iTrader: (8)

ok, so i change the filter on them to match?

hmm, once would think it should match them when you do an overlay but i guess not.

This looks even worse now that i have them lined up. Some places are 2 points difference in a/f between banks. what is really going on with this car now....

str8dum1

iTrader: (11)

weird, when i opened my csv logs, it was all labeled. i used excel to make my charts over the logger.

binder

iTrader: (8)

Idk, maybe my Excel is messed up. Take a peek and see if they are properly labeled on your Excel.

Boosted Performance

iTrader: (14)

I recently had issues with a/f ratios between the banks. It turned out to be an exhaust leak, on bank two, three bolt flange. It caused all kinds of issues when it comes to a/f ratios.

binder

iTrader: (8)

Ya, I've thought about that but I've had these on and off about 5 times now with new Gaskets and this last time.even used copper gasket spray as well has my 1/2" drive breaker bar to tighten them down. It would be strange that I had the same Af differences after doing the exhaust multiple times unless the leak isn't at the gasket.

str8dum1

iTrader: (11)

ohh duh, i'm thinking about my cipher logs...

no way to make the axis the same. when you adjust so 2 points match their numerical value, the next spot down the log doesnt match up.

By numerical value, there is no difference. That's what I would go by

binder

iTrader: (8)

Ya, I'm just going to use.numerical value. I did find some points that were 2 full points off though. Wasn't in boost so I don't think I should worry much.