All Corsa Forum banner

P0130 Code After Resetting O2-Loop Block Learn Map

10K views 8 replies 3 participants last post by  gb33  
#1 · (Edited)
I recently installed a brand new Bosch O2 sensor with the factory plug. It is completely identical to the original one fitted by the factory.

A few days ago I developed a mild case of spark knock on lower rpm moderate engine load, checked the codes with Opcom, found no faults.

Thinking that the new O2 sensor might be making false readings from the 'old' map for the original worn out sensor, I reset the O2-Block Learn Map using the Opcom special functions.

After this, started the car and it ran like crap (no power, bucking) for about 1 minute, then steadily improved and I was able to do normal around-town driving without any trouble. I drove it around for about 15 minutes to let it warm up fully, and then did some full throttle, maximum acceleration runs. Each time I do this, the car hesitates, bucks and throws an EML.

I plug OPCOM back in and the first time it said:

P0130 - O2 sensor Circuit Voltage Low.
(O2) - Not Present


Cleared the code, started car again, did another full throttle test. Threw a code again, this time:

P0130 - O2 sensor Circuit Voltage Low.
(O2) - Present


My question is, is the car still just relearning the map, or is there something else wrong? Otherwise the car has been well serviced its whole life, with less than 7k miles on the spark plugs and air filter. Also, any thoughts as to what the spark knock might be from would be helpful. As stated, I didn't get any code for faulty knock sensor, but how often do they go bad?
 
#2 ·
Pinking can be caused by several things, a lean mix, timing being advanced too far, wrong plugs, carbon deposits or a bad batch of fuel.

If it develops out of the blue I'd try some fresh fuel from a different source from you last filled up - just in case it's a dud batch.

Re. the O2 codes - if (for example) the mix is out then that can throw the O2 sensor out of parameter. What voltage readings is it showing on live data?
 
#3 ·
Thanks Taurus,

I just idled the car on the driveway with a few blips on the throttle to test out the range.

At idle (during warm up) it jumped between about 150 to 750 mV, though mostly hovering in the 600+ mV range.

When I gave it some throttle (hovering around 3500 rpm) the voltage dropped to about 70-150 mV.

Engine temp got to about 90 before I shut it down.
 
#4 ·
Those readings suggest it's running lean - maybe an air leak? Worth checking.

The basic reading ought to switch between Lean/Rich about every second - but a rough guide is 0.2v is lean, 0.8v is rich. It's OK when cold, probably due to the richer mix, but when hot it might be too lean - which would cause pinking of course.
 
#5 ·
Hi Taurus, thanks for your help.

I checked for intake/vac line cracks or loose connections, everything at least seems ok.

Engine bogs badly on cold startup now, but gets better after about 30 seconds. Still getting pinking under load.

I then tried unplugging the MAF sensor and took it for a drive. On a warm engine, it ran considerably better than before. Still some pinking (combustion chamber carbon?) but the car has more power through the revs and doesn't bog.

I then let the engine idle before shutting it off, and alternated between plugging the MAF back in/out/in/out a few times. Every time the MAF was plugged IN, I noticed that the idle quality and engine vibration became noticeably worse and more ragged. When unplugged, it idles very nicely for a 3 pot and the engine vibration seems more consistent.

OPCOM still shows no codes for MAF, but I'm wondering if its already given up the ghost?? There's ~103k miles on the car and the original MAF and I know not to try cleaning them.
 
#6 ·
Well if the MAF dud then that would throw the mix out. Since you suspect it's dead then you've nothing to lose by trying to clean it - spray with carb cleaner and allow to dry thoroughly before refitting. If it fixes it great, if it kills it you're no worse off.
 
#7 ·
Cleaned MAF yesterday, let it dry overnight, refitted this morning. No luck, same terrible running with it plugged in. New Bosch MAF on the way.

Is there any way to check if the knock sensor is working properly? If I let the engine idle and tap the block lightly with a hammer, would that normally trick the ECU to retard the timing when I'm running live data?
 
#8 ·
I literally had exact same issue on my 1.0,

I replaced the Lambda sensor and still same, Then I replaced the MAF sensor and never caused a problem since. Same error codes too.
 
#9 ·
The new MAF came in this morning, plugged it in and cleared the old missing-MAF codes.

I tried giving the car an 'Italian tune up' (driving it very hard at high rpms to hopefully burn out carbon deposits) for about 20 minutes, it runs great overall with no hesitation or flat spots, but still have pinking at low rpms.

When the tank runs low enough I'll have to try a different station to see if petrol quality is an issue.

At least the bogging issue has been resolved.