02 Sensor problem FINALY solved...
Thread Starter
|
Senior Member
Joined: Jun 2006
Posts: 520
Likes: 0
From: NJ
02 Sensor problem FINALY solved...
For the past 9 months or so I have been posting questions about 02 sensors and what causes them to fail. I've read every site on the Internet, bugged mechanics and checked everything on my 03 Ex that I could think of.
To recap- October 06 I got some TP custom tunes with the Xcal tuner. Part of tuning is datalogging. So I datalogged, not knowing much about what I was seeing. One of the parameters to log is upstream O2 voltage. So I did that, and to my untrained eye, one of the sensors was being "lazy". I enquired and found that does happen. So I changed it (both actually). Relogged... same thing. Hmmm. Swapped OEM sensors and logged... same thing.
Thus began my almost year long search to find out what was wrong with my Bank 2 side of the engine. Intake and Exhaust leaks, wiring harness voltage checks, vaccum lines, fuel pressure (I have some new tools now so all is not lost!). Nothing was wrong.
Two days ago I was re-examining my now all-to-familiar datalog files when I thought about viewing both up and downstream logs. The original TP datalogging requirements did not include the downstream 02 sensors. I had included them at a later date and just never looked at them.
What I found was that Bank 1 up and downstream BOTH looked like an upstream log- rapid switching between .1 and .9 volts. Bank 2 up and down looked like downstream readings. Each Bank up and downstream reading were indentical to themselves. In other words, they looked like both sides of the engine were performing to spec, just not showing up in the correct graphs.
Could it be that the logger was mis-labeling the datastream? I relogged the truck with a friends non-SCT logger and sure enough, both upstream O2's looked just right as did the downstream readings.
I called SCT who suggested that there might have been an error in the PID database file used by the software (not the Xcal). He suggested downloading the most recent version of LiveLink and try another log.
Sure enough, the new log shows perfect performance of my origninal 02 sensors, up and downstream.
So after all these months of searching and countless hours online and under the hood, it was a typo in the PC software used to read the datastream.
Well, at least I know my truck is ok, but I am more than perturbed by this error in a very expensive piece of equipment.
For those of you who datalog, make sure you use the most up to date version of LiveLink. There may be other errors in there - who knows. But the O2 readings are ok.
No more posts about 02's for a while - I promise.
To recap- October 06 I got some TP custom tunes with the Xcal tuner. Part of tuning is datalogging. So I datalogged, not knowing much about what I was seeing. One of the parameters to log is upstream O2 voltage. So I did that, and to my untrained eye, one of the sensors was being "lazy". I enquired and found that does happen. So I changed it (both actually). Relogged... same thing. Hmmm. Swapped OEM sensors and logged... same thing.
Thus began my almost year long search to find out what was wrong with my Bank 2 side of the engine. Intake and Exhaust leaks, wiring harness voltage checks, vaccum lines, fuel pressure (I have some new tools now so all is not lost!). Nothing was wrong.
Two days ago I was re-examining my now all-to-familiar datalog files when I thought about viewing both up and downstream logs. The original TP datalogging requirements did not include the downstream 02 sensors. I had included them at a later date and just never looked at them.
What I found was that Bank 1 up and downstream BOTH looked like an upstream log- rapid switching between .1 and .9 volts. Bank 2 up and down looked like downstream readings. Each Bank up and downstream reading were indentical to themselves. In other words, they looked like both sides of the engine were performing to spec, just not showing up in the correct graphs.
Could it be that the logger was mis-labeling the datastream? I relogged the truck with a friends non-SCT logger and sure enough, both upstream O2's looked just right as did the downstream readings.
I called SCT who suggested that there might have been an error in the PID database file used by the software (not the Xcal). He suggested downloading the most recent version of LiveLink and try another log.
Sure enough, the new log shows perfect performance of my origninal 02 sensors, up and downstream.
So after all these months of searching and countless hours online and under the hood, it was a typo in the PC software used to read the datastream.
Well, at least I know my truck is ok, but I am more than perturbed by this error in a very expensive piece of equipment.
For those of you who datalog, make sure you use the most up to date version of LiveLink. There may be other errors in there - who knows. But the O2 readings are ok.
No more posts about 02's for a while - I promise.
Senior Member
Joined: Feb 2004
Posts: 10,390
Likes: 10
Originally Posted by waterman308
For the past 9 months or so I have been posting questions about 02 sensors and what causes them to fail. I've read every site on the Internet, bugged mechanics and checked everything on my 03 Ex that I could think of.
To recap- October 06 I got some TP custom tunes with the Xcal tuner. Part of tuning is datalogging. So I datalogged, not knowing much about what I was seeing. One of the parameters to log is upstream O2 voltage. So I did that, and to my untrained eye, one of the sensors was being "lazy". I enquired and found that does happen. So I changed it (both actually). Relogged... same thing. Hmmm. Swapped OEM sensors and logged... same thing.
Thus began my almost year long search to find out what was wrong with my Bank 2 side of the engine. Intake and Exhaust leaks, wiring harness voltage checks, vaccum lines, fuel pressure (I have some new tools now so all is not lost!). Nothing was wrong.
Two days ago I was re-examining my now all-to-familiar datalog files when I thought about viewing both up and downstream logs. The original TP datalogging requirements did not include the downstream 02 sensors. I had included them at a later date and just never looked at them.
What I found was that Bank 1 up and downstream BOTH looked like an upstream log- rapid switching between .1 and .9 volts. Bank 2 up and down looked like downstream readings. Each Bank up and downstream reading were indentical to themselves. In other words, they looked like both sides of the engine were performing to spec, just not showing up in the correct graphs.
Could it be that the logger was mis-labeling the datastream? I relogged the truck with a friends non-SCT logger and sure enough, both upstream O2's looked just right as did the downstream readings.
I called SCT who suggested that there might have been an error in the PID database file used by the software (not the Xcal). He suggested downloading the most recent version of LiveLink and try another log.
Sure enough, the new log shows perfect performance of my origninal 02 sensors, up and downstream.
So after all these months of searching and countless hours online and under the hood, it was a typo in the PC software used to read the datastream.
Well, at least I know my truck is ok, but I am more than perturbed by this error in a very expensive piece of equipment.
For those of you who datalog, make sure you use the most up to date version of LiveLink. There may be other errors in there - who knows. But the O2 readings are ok.
No more posts about 02's for a while - I promise.
To recap- October 06 I got some TP custom tunes with the Xcal tuner. Part of tuning is datalogging. So I datalogged, not knowing much about what I was seeing. One of the parameters to log is upstream O2 voltage. So I did that, and to my untrained eye, one of the sensors was being "lazy". I enquired and found that does happen. So I changed it (both actually). Relogged... same thing. Hmmm. Swapped OEM sensors and logged... same thing.
Thus began my almost year long search to find out what was wrong with my Bank 2 side of the engine. Intake and Exhaust leaks, wiring harness voltage checks, vaccum lines, fuel pressure (I have some new tools now so all is not lost!). Nothing was wrong.
Two days ago I was re-examining my now all-to-familiar datalog files when I thought about viewing both up and downstream logs. The original TP datalogging requirements did not include the downstream 02 sensors. I had included them at a later date and just never looked at them.
What I found was that Bank 1 up and downstream BOTH looked like an upstream log- rapid switching between .1 and .9 volts. Bank 2 up and down looked like downstream readings. Each Bank up and downstream reading were indentical to themselves. In other words, they looked like both sides of the engine were performing to spec, just not showing up in the correct graphs.
Could it be that the logger was mis-labeling the datastream? I relogged the truck with a friends non-SCT logger and sure enough, both upstream O2's looked just right as did the downstream readings.
I called SCT who suggested that there might have been an error in the PID database file used by the software (not the Xcal). He suggested downloading the most recent version of LiveLink and try another log.
Sure enough, the new log shows perfect performance of my origninal 02 sensors, up and downstream.
So after all these months of searching and countless hours online and under the hood, it was a typo in the PC software used to read the datastream.
Well, at least I know my truck is ok, but I am more than perturbed by this error in a very expensive piece of equipment.
For those of you who datalog, make sure you use the most up to date version of LiveLink. There may be other errors in there - who knows. But the O2 readings are ok.
No more posts about 02's for a while - I promise.
Thanks for the feedback, Waterman!
Betcha learned LOTS, though LOL!
Good info.
Thread Starter
|
Senior Member
Joined: Jun 2006
Posts: 520
Likes: 0
From: NJ
I did learn alot, true. But tracking down that little issue took many, many hours away from my family time (6 kids) and more than once got me in the hole with my wife. She is unsympathetic to my continued interest in mods and upgrades after this, and rightfully so. I think I've used up my allotment of time - for the rest of the year! (not to mention money).