Very interesting.stevieb wrote: Away from the garage last night I was careful not to let the ignition sit in position II for too long before starting - like before, firing up the engine before the warning lights go out. The outbound journey earlier was the same. On both journeys the car was healthy sounding, ran well, and mpg was good (70ish mph on the A1 was getting 30-45mpg depending on gradient). However, without thinking, I started the engine before heading back AFTER the ignition had been in position II for about 15 minutes (the engine was still warm at this point, but not so much it was showing on the temp gauge). Power-loss wasn't too bad, but the drone was deafening again and fuel consumption was horrendous. My girlfriend even commented when we got to the country roads that "she sounds very noisy again". I pulled into a lay-bay, knocked-off the ignition, took the key out and then re-started quickly. Suddenly we're back to quiet, smooth and economical mode despite a warm start.
Something is definitely happening when the key is in position II for too long. Whether it's like I said before and the ECU is having the time to re-load incorrect parameters - I've said before that I think the ECU only applies new parameters at start-up, not mid-journey, so maybe it's adjusting for the weak spark/bad ignition it detected at the oxygen sensor on the previous journey (as yours may do with the incorrect sensor) and applying those settings. Firing-up immediately might by-pass these settings and so the ECU either works with preset defaults or simply does things on-the-fly.


If key off then an immediate restart cured it, it won't be anything to do with the oxygen sensor, fuel trim (learnt from the oxygen sensor) or timing advance (learnt from the knock sensor) as those are constantly learning and adapting as you drive the car, they don't require a key off then on to take them into account. Also when you turn off the engine both tables are kept in battery backed memory and used immediately when you start the engine again (unless you take the battery off for 10 minutes or perhaps do your "ICV reset" procedure) so the fact that you cure the problem by switching it off and on tells me its not fuel trim or timing related.
I'll tell you what IS recalibrated every time you turn on the key to start the car though - the TPS idle position, and the MAP sensor barometric calibration...
For the TPS, every time you turn the key on to position two, if the TPS voltage is less than a certain threshold (I'm not sure exactly what the threshold is, but its around 0.9 - 1.0 volts from my experimentation) the ECU then calibrates this as a fully closed throttle position, until otherwise contradicted by a lower voltage reading. Typical closed throttle voltages are around 0.6 - 0.7 volts. If the voltage is above this 0.9-1.0 volt threshold when the key is turned on calibration does NOT take place as the computer assumes (reasonably) that you are pressing the throttle. Only if it is near closed will it assume that it is closed and calibrate that as the zero degree position.
This means that if you hold the throttle open slightly when the key is turned on, this is calibrated as closed throttle. I've proven this conclusively with the Lexia, where you can get a real time reading of both raw TPS output voltage AND throttle opening percentage which is derived from the voltage, taking into account idle and full throttle calibration.
For example my normal closed throttle voltage is about 0.65 volts, if I hold the throttle down slightly so that the voltage is 0.8 volts it will read about 5 degrees of throttle opening, however if I keep it held at that position and turn the key off and on then now it will show 0.8 volts as zero degrees of throttle opening even though the throttle is held open slightly. If I increase the throttle opening the opening in degrees will increase but remains about 5 degrees in error. If I reduce the throttle opening to 0.8 volts it drops to zero degrees again. If I let the throttle fully close so it drops to 0.65 volts it still reads zero degrees, but if I then open it to 0.8 volts again it will now read 5 degrees.
This proves conclusively that the calibration can change (in one direction only) while the engine is running - if it encounters a voltage that is lower than the previously seen minimum since last turn on, a recalibration occurs on the fly and the new minimum voltage becomes the new zero degree throttle opening point. Now image what happens if the connection to the TPS goes open circuit momentarily while driving allowing it to drop right down to zero volts, even for a fraction of a second...correct calibration is lost and can only be restored by turning the key off and on with the throttle not depressed, as it will not change calibration in the other direction while driving. (It will only "expand" the voltage range while driving, not contract it)
Calibration of full throttle works in a similar way - it will make an initial assumption of the full throttle voltage to begin with of around 4.3-4.4 volts (?) but if it sees a higher voltage than this during driving the new maximum becomes the new full throttle position, so full throttle is recalibrated. I THINK you can manually calibrate full throttle with the key on and engine off using the 10 seconds key on, 10 second full throttle, 10 second closed throttle technique, but I have not verified this.
Now imagine what happens if the ground wire to the TPS looses contact momentarily while driving - calibration of full throttle is mucked up as the ECU would temporarily see a full 5 volts which is outside the normal range of 0.6v to 4.5v. Key off and on should fix this if the fault was only momentary. Of course momentary loss of contact between the wiper and the carbon track when moved quickly (dead spots) is a common way that a TPS or any potentiometer can fail when it wears out, so its easy to see how a failing TPS could cause these kind of symptoms where calibration of the TPS is randomly lost until the next key on calibration.
The MAP sensor is also calibrated for local barometric pressure during key on but before cranking, on the basis that with the engine not spinning there is no vacuum, and the MAP sensor will read accurate barometric pressure even with the throttle closed. (The ICV is still half open anyway, when the key is on waiting to start) This barometric pressure reading is memorised and used to calibrate the MAP readings - since the MAP sensor is a manifold absolute pressure sensor and not a relative vacuum gauge, the same amount of relative vacuum at a different altitude would give a different MAP pressure reading.
So to work out how much vacuum there is, ambient barometric pressure needs to be known so that current measured pressure can be subtracted from it to calculate vacuum and thus engine load. Great, so how does it account for changes in barometric pressure if you climb or descend a mountain without turning the engine off and on ? The answer is that it simply waits for you to fully depress the throttle while you're driving, the MAP reading when the throttle is fully depressed is assumed to be ambient barometric pressure since there is no throttle plate restriction - even though the engine is pumping there will be no vacuum. This reading now becomes the newly memorised barometric pressure used in calculations until the next time the throttle is fully depressed. (or the key switched off and on with the engine not turning over)
Seems a bit mickey mouse, but that's what a lot / most petrol engine cars do!

A few cars do have a separate barometric pressure sensor (sometimes in the same plastic package) that constantly measures the barometric pressure directly by sampling it in the engine bay instead of the manifold - if some go to the trouble of adding a second sensor purely to read ambient pressure an accurate determination of barometric pressure must be reasonably important in the calculations...
Are you starting to see a dependence between the TPS and the MAP here ? While driving, the TPS signal is also used as a trigger to initiate a barometric pressure re-calibration, what if instead of only occurring at full throttle as it should, the MAP recalibration occasionally occurs at a condition of significant vacuum, due to a fault in the TPS or TPS wiring ? This would throw things out dramatically. Fuelling is based largely on MAP reading for low throttle openings and TPS for large throttle openings. If it thought the barometric pressure was lower than it really was, the MAP derived load figure would be way too high, which may cause the ECU to over fuel when in open loop mode...so much so that the engine could be running massively rich under some conditions.
Meanwhile if the TPS calibration is screwed up the fuelling under wide throttle may also be wrong. (The oxygen sensor isn't used when the throttle is moved quickly, nor above an engine load of around 30-40%, and again its the MAP sensor and TPS that determine the engine load) Turn the key off and on and the TPS and MAP are recalibrated from fresh and the problem goes away.
Here's the thing - I've observed the same symptoms as you many times. Performance on a long drive would get lethargic and the exhaust would start to drone and boom but there was no power. Stopping, turning the key off, waiting a few seconds then starting it like you did usually fixed it. I'd love to tell you what fixed it, but I don't know for sure - it hasn't had this symptom for over 6 months, and a lot has changed since then.
I'm reasonably sure its related to MAP and TPS signals and both of mine have been replaced, but then so to have both of yours ? I've also checked and cleaned the contacts on the ECU connector and sensor connectors.
I think the loud drone ultimately just comes from misfiring cylinders, eg cylinders that are dead weight and just pumping gases through - whether ignition misfire, lean misfire or even a rich misfire if enough cylinders are misfiring you get a drone/boom when opening the throttle. So I'm not sure that the drone helps to tell us anything other than the engine is misfiring.OR something is happening with the fuel pressure during this time - I say this because my drone was a permanent feature before I cleaned up the fuel pump terminals. This would suggest either the pump is nodding off to sleep, pressure is leaking off somewhere (my fuel drop when it's like this resembles a leak), or there's a vacuum issue at startup which is affecting the pressure regulator and continues to affect the pressure during the journey (maybe some vapour-lock somewhere). The only argument against this problem being caused by a drop in fuel pressure is that the power delivery doesn't drop too much (when I had dirty fuel pump terminals my power was very low). Maybe having the drone with low fuel pressure was a sign of that AND bad sparks.
I need to sort my other three sparks and see what changes, don't I?
