FlyingEagle
Staff member
Link newbie. I mean 100%, totally bobbing for apples with a set tweezers. Not my cup of tea just yet. That aside ... there are chappies here that have seen some issues ... here is mine.
ECMLink v3 running the latest version - 3.29.64, not the stable version listed as 3.27.92.
Front o2 does not swing, now sitting at 0.2V. New Denso sensor, only idle time for maybe an hour total, installed in 2015.
Car overheated in the spring of 2015 and I tore down the cooling system and updated a bunch of wiring, but nothing near the cylinder head (already performed that in 2014 at which point the 02 swing was fine on another laptop and at the time of the overheat). Fan blew off the motor because my motor tilted too far forward making contact - long story, tight tolerance at the time - sorted now. See radiator threads ...
Thought maybe my newly installed ECU was bad (bought this season and just installed - passed by ECMLink guys before PO shelved and then shipped it to me), installed another spare ECU and swapped link chip. Same issue in both datalogs, 0.2V flat line.
Installed new Bosch o2 sensor, plugged it into the connector but not into the housing/exhaust stream but key forward and link logging, same issue 0.2V flat line.
The sensor installed into the o2 housing could possibly be ruled out as having suspect/pulled wires at the sensor wire intake area, as the wiring from the Bosch sensor would have meant a clean section up to the factory plug at the corner of the cylinder head.
Nothing wrong with the sensor output last season before the rebuild. Wires to the o2 sensor could have been pulled at the sensor end with my radiator fitment being so lengthy, but again the Bosch sensor was installed temporarily in place of those.
I could have sworn I was running the latest version of Linkv3 when the car was last running and the chip should therefore have it.
I did borrow a laptop from my pops, and the software listed in the first sentence is running for the first time on that. Every other data point is working as it should,
including the fact that I know I have some data values not nearly dialed in as they should be. Another story .. focusing on the o2 sensor now.
Short of pinning the wires and checking resistance, could I have a strange code issue? Reboot required? How to transfer old setting without writing it down ....
Sitting at 0.2V is a strange sort of output/reading isn't it?
Shorted should be a different value or worse I just did damage to multiple boards - never seen an 02 sensor problem take out an ECU yet thought.
Resistance, should still swing but out of range, but not peg at one voltage in the somewhat the median?
My Innovate MTX-L sensor is installed just below the exhaust downpipe flange, and swings just like it should. Thus I know the AFR is not pegged one way or the other, as the engine is operating. Almost forgot that reference point, so just added it.
Brand new exhaust gasket at that downpipe flange, so things are indeed leak free in the vicinity, up or down of the sensors.
Straws ... grasping ... me.
Any ideas?
ECMLink v3 running the latest version - 3.29.64, not the stable version listed as 3.27.92.
Front o2 does not swing, now sitting at 0.2V. New Denso sensor, only idle time for maybe an hour total, installed in 2015.
Car overheated in the spring of 2015 and I tore down the cooling system and updated a bunch of wiring, but nothing near the cylinder head (already performed that in 2014 at which point the 02 swing was fine on another laptop and at the time of the overheat). Fan blew off the motor because my motor tilted too far forward making contact - long story, tight tolerance at the time - sorted now. See radiator threads ...
Thought maybe my newly installed ECU was bad (bought this season and just installed - passed by ECMLink guys before PO shelved and then shipped it to me), installed another spare ECU and swapped link chip. Same issue in both datalogs, 0.2V flat line.
Installed new Bosch o2 sensor, plugged it into the connector but not into the housing/exhaust stream but key forward and link logging, same issue 0.2V flat line.
The sensor installed into the o2 housing could possibly be ruled out as having suspect/pulled wires at the sensor wire intake area, as the wiring from the Bosch sensor would have meant a clean section up to the factory plug at the corner of the cylinder head.
Nothing wrong with the sensor output last season before the rebuild. Wires to the o2 sensor could have been pulled at the sensor end with my radiator fitment being so lengthy, but again the Bosch sensor was installed temporarily in place of those.
I could have sworn I was running the latest version of Linkv3 when the car was last running and the chip should therefore have it.
I did borrow a laptop from my pops, and the software listed in the first sentence is running for the first time on that. Every other data point is working as it should,
including the fact that I know I have some data values not nearly dialed in as they should be. Another story .. focusing on the o2 sensor now.
Short of pinning the wires and checking resistance, could I have a strange code issue? Reboot required? How to transfer old setting without writing it down ....
Sitting at 0.2V is a strange sort of output/reading isn't it?
Shorted should be a different value or worse I just did damage to multiple boards - never seen an 02 sensor problem take out an ECU yet thought.
Resistance, should still swing but out of range, but not peg at one voltage in the somewhat the median?
My Innovate MTX-L sensor is installed just below the exhaust downpipe flange, and swings just like it should. Thus I know the AFR is not pegged one way or the other, as the engine is operating. Almost forgot that reference point, so just added it.
Brand new exhaust gasket at that downpipe flange, so things are indeed leak free in the vicinity, up or down of the sensors.
Straws ... grasping ... me.
Any ideas?
Last edited: