Ive checked out the cables from O2 sensor to the ECU pin D7 and also the earth pin D6 . I have mauled and waggled all the cabling without producing a loss of continuity. Ive had the plugs off the ECU for a little light WD40 spray wipe over and reseted them well.
As i am waiting for the new O2 sensor delivery ( possibly this morning) I thought id do an elanscan from cold with my N0.2 O2 sensor in place .
As i have had the battery disconnected for the ECU work, all the faults are cleared . So to start i had to keep blipping the throttle until it would run evenly. Spluttering a bit while idling until coolant reached 82c or just over . Then running smoothly.
Looking at my scan , i can see the O2 sensor worked initially then stopped and didnt work again until the coolant reached the 82c mark. I had a voltmeter across the O2 sensor feedback cable at the O2 socket and the engine as earth . the reading correspond with those of the elanscan . I tried across the O2 heater and that should around 13v with little deviation. So i think the heater was energised OK but just not hot enough to work. Although it appears to have worked immediately..
There is also a at 1460 secs a quick blip of the throttle just to see if the engine recovers to idle OK afterwards. It did but the elan scan trace showed the O2 sensor feedback voltage dropped .. From the manual i think the scan stops at wider throttle openings and maybe that's what happens here ??
Anyway its cooling off now and my next trace will be the new sensor i hope.
Just to clarify my elanscan is on an old acer notebook running windows 7 . I have a 2nd version on a desktop PC running windows 11 but used only for viewing results, not recording
I may see if i can run the latest updated elanscan on my notebook but feel sure I'll have a battle getting the port to sample correctly afterwards. So i wont try yet .
Thanks again for all the advice and insights.
Chas54
after check ECU O2 connection S2.zip
You do not have the required permissions to view the files attached to this post.