Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[jtypecav]

Cheers TB - I'd simultaneously checked the world's most reliable source *(eBay) seems to think so: (and a few others besides..) if true, well worth noting for other members models perhaps!

Application List
Vehicle   Year   CC   Engine Code
OPEL - SINTRA 2.2 DTI   Jul 1997 to Apr 1999   2171   X 22 DTH
OPEL - FRONTERA B 2.2 DTI (6B_ZC, 6B_VF, 6B_66, 6B_76)   Oct 1998 to Sep 2002   2171   X 22 DTH
OPEL - FRONTERA B 2.2 DTI (6B_ZC, 6B_VF, 6B_66, 6B_76)   Oct 1998 to Sep 2002   2171   X 22 DTH
OPEL - FRONTERA B 2.2 DTI (6B_ZC, 6B_VF, 6B_66, 6B_76)   Oct 1998 to Sep 2002   2171   X 22 DTH
OPEL - FRONTERA B 2.2 DTI (6B_ZC, 6B_VF, 6B_66, 6B_76)   Oct 1998 to Sep 2002   2171   X 22 DTH
OPEL - FRONTERA B 2.2 DTI (6B_ZC, 6B_VF, 6B_66, 6B_76)   Oct 1998 to Sep 2002   2171   Y 22 DTH
OPEL - FRONTERA B 2.2 DTI (6B_ZC, 6B_VF, 6B_66, 6B_76)   Oct 1998 to Sep 2002   2171   Y 22 DTH
OPEL - FRONTERA B 2.2 DTI (6B_ZC, 6B_VF, 6B_66, 6B_76)   Oct 1998 to Sep 2002   2171   Y 22 DTH
OPEL - FRONTERA B 2.2 DTI (6B_ZC, 6B_VF, 6B_66, 6B_76)   Oct 1998 to Sep 2002   2171   Y 22 DTH
OPEL - VECTRA B 2.6 i V6   Sep 2000 to Apr 2002   2597   Y 26 SE
OPEL - VECTRA B 2.6 i V6   Sep 2000 to Jul 2003   2597   Y 26 SE
OPEL - VECTRA B 2.6 i V6   Sep 2000 to Jul 2003   2597   Y 26 SE
OPEL - OMEGA B 2.6 V6   Sep 2000 to Jul 2003   2597   Y 26 SE
OPEL - OMEGA B 2.6 V6   Sep 2000 to Jul 2003   2597   Y 26 SE
OPEL - OMEGA B 2.6 V6   Sep 2000 to Jul 2003   2597   Y 26 SE
OPEL - OMEGA B 2.6 V6   Sep 2000 to Jul 2003   2597   Y 26 SE
OPEL - OMEGA B 2.6 V6   Sep 2000 to Jul 2003   2597   Y 26 SE
OPEL - OMEGA B 2.6 V6   Sep 2000 to Jul 2003   2597   Y 26 SE
OPEL - OMEGA B 3.2 V6   Feb 2001 to Jul 2003   3175   Y 32 SE
OPEL - OMEGA B 3.2 V6   Feb 2001 to Jul 2003   3175   Y 32 SE
OPEL - OMEGA B 3.2 V6   Feb 2001 to Jul 2003   3175   Y 32 SE
OPEL - OMEGA B 3.2 V6   Feb 2001 to Jul 2003   3175   Y 32 SE
OPEL - OMEGA B 3.2 V6   Feb 2001 to Jul 2003   3175   Y 32 SE
OPEL - OMEGA B 3.2 V6   Feb 2001 to Jul 2003   3175   Y 32 SE

Well I can try it!

(As an aside I did see two silver omegas with omegaowners.com stickers in Radstock near the mini roundabout when I was getting a lift to work the other week! '_' )

I'll head across tomorrow and unplug it!

[TheBoy]

I'm slightly hesitant, because normally duff MAFs, which 'almost' work tend to throw the trims out.  My initial thoughts from the 1st post symptoms were MAF, but I'm still a bit wary of the trims staying 0% ish. And thus struggling to prove to myself (let alone anyone else) that its the MAF.

I've been trying, as much as anything, to teach correct diags process on this thread, yet embarrassingly had to go on a hunch in the end (exactly what I wasn't encouraging  ) and unplug the MAF.      

The fact that it runs without error when the ECU is substituting calculated MAF values, rather than using actual readings, certainly narrows it down in that area.

I hope the MAF sorts it.

[jtypecav]

Here's an update!

It RAN smoothly until warm, and then basically seemed to go back to how it was running without MAF connected up to 4K eml (except seemed slightly higher now and with more power)! It was almost as if it bought me more time / revs.

This almost made me want to turn around on my random mission into the dark, but I've returned with a 1yr old known working MAF.

If it's any consolation, I'm now not sure about resorting to the hunch either. (see I'm learning!). But in my defence mechanic mates have been shouting ECU at me since the offset and I've chosen to at least try to be logical. (thanks to your help!)

Will fit before work tomorrow morning if I get a chance and report back by 9am. Seriously, the wave of jubilation as it pulled strongly past the previous limit was immense, only for it to be stolen five-ten minutes later again! 

Just shows I have much to learn from slow and steady wins the race. But I'm ever hopeful.   

[jtypecav]

I changed this before work in the rain and...

So far so good. Only had 60 seconds to test it but it was fantastic to see the right kind of orange flash. TC!

Will "test" tonight and feedback. Think I owe a few of you a pint (and myself for the self infliction!)

[TheBoy]

As to those mates shouting ECU, remind me not to let them touch my car.  "ECU fault" is the mechanics favourite if they don't understand the symptoms, or how the system works.


Here's hoping the MAF testing is successful

[jtypecav]

Properly * potentially* buzzing right now. I've learnt a lot more about FBW systems and how they interact with an ECU now too.

Whilst I always keep a spare ECU around for any older car (speaking of old MK2 Cavs here mind) where things like the old SRI 18SE's break regularly this never felt like the management.

Bizarrely, because the readings seemed OK they dismissed it out of hand (a proper scanner not my *cough* attempt). Regardless, a pint is owed. Come over and say hello on the MK2CAV.COM stand this year if you are going to Billing!

(even if it hasn't sorted it haha!)

[TheBoy]

Weren't the old Cavs using Lucas Jetronic injection systems, and dizzy based sparks, complete with inertia advance?  They were pretty fragile, both with the Jetronic part, and the dizzy parts.

The Bosch Motronic is a full engine management, and is, in Omega form, pretty robust from an ECU point of view.

[Kevin Wood]

I don't know what it is about the ECU build in the 2.6 but I've seen loads of weird symptoms surrounding the MAF sensor. Always on a 2.6.

On a couple, where I've had a hunch, but no conclusive evidence,  I've swapped the MAF with my 3.2's MAF (same part, different ECU config) and whilst my MAF has transformed the 2.6, my 3.2 has driven fine on the "faulty" MAF.

Last one I tried, my MAF didn't improve it, but the owner eventually bought a new one, and that did.

That config appears to be very sensitive to the performance of the MAF sensor.

[jtypecav]

Weren't the old Cavs using Lucas Jetronic injection systems, and dizzy based sparks, complete with inertia advance?  They were pretty fragile, both with the Jetronic part, and the dizzy parts.

The Bosch Motronic is a full engine management, and is, in Omega form, pretty robust from an ECU point of view.

Yup, as soon as they wen't motronic for the last few years they were transformed! Also, moving the ECU to the footwell was a good idea from the 1980's engine bays!

[jtypecav]

I don't know what it is about the ECU build in the 2.6 but I've seen loads of weird symptoms surrounding the MAF sensor. Always on a 2.6.

On a couple, where I've had a hunch, but no conclusive evidence,  I've swapped the MAF with my 3.2's MAF (same part, different ECU config) and whilst my MAF has transformed the 2.6, my 3.2 has driven fine on the "faulty" MAF.

Last one I tried, my MAF didn't improve it, but the owner eventually bought a new one, and that did.

That config appears to be very sensitive to the performance of the MAF sensor.

This makes a lot of sense in the context of everything else that's gone on with this 2.6!

[jtypecav]

Goddammit.

All we've done is given the car the ability to rev through the range in 1st gear.

It still behaves exactly the same in 2nd still. 

From now on will only get excited if I can keep the light off for a whole day.

ahh-bugger. Help!

[Kevin Wood]

This sounds similar to an issue Taxi Al had. Boot it and it's fine until a certain speed when it goes into some sort of limp home with a lot of retard. Runs like a dog until you restart engine, then fine again.

Unfortunately we haven't got the the bottom of that yet. Vaguely knock sensor related, IIRC.

[TheBoy]

Weren't the old Cavs using Lucas Jetronic injection systems, and dizzy based sparks, complete with inertia advance?  They were pretty fragile, both with the Jetronic part, and the dizzy parts.

The Bosch Motronic is a full engine management, and is, in Omega form, pretty robust from an ECU point of view.

Yup, as soon as they wen't motronic for the last few years they were transformed! Also, moving the ECU to the footwell was a good idea from the 1980's engine bays!

Only its still in the engine bay


Bugger. Any new codes?

[jtypecav]

Yeah, they moved it back. Just put it in a box!

As for codes. No, but I have a "pretty" image with a couple of questions! Please don't run away though(!) Areas around the RED / YELLOW in the right hand margin are where things look like they are going awry!



1). Speed pulse disappearing about same time as TPS Invalid and other things
2). Is it speed related as revs cleanly in 1st but not in second / third etc.
2). Engine load sounds like a very low number generally?
3). Do intake valve openings look appropriate?

Obviously happy to come to some arrangement if we get this sorted!

[Andy H]

This sounds similar to an issue Taxi Al had. Boot it and it's fine until a certain speed when it goes into some sort of limp home with a lot of retard. Runs like a dog until you restart engine, then fine again.

Unfortunately we haven't got the the bottom of that yet. Vaguely knock sensor related, IIRC.

Could a trapped/damaged knock sensor cable cause these symptoms? Quite common for the cable that runs in the cable duct in the cam belt cover to get damaged during a cam belt change IIRC.