Omega Owners Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

Please play nicely.  No one wants to listen/read a keyboard warriors rants....

Pages: [1] 2  All   Go Down

Author Topic: Fault code 136 (M2.8.1)  (Read 4012 times)

0 Members and 1 Guest are viewing this topic.

Omegafantasy

  • Junior Member
  • **
  • Offline Offline
  • Gender: Male
  • Oslo, Norway
  • Posts: 178
    • View Profile
Fault code 136 (M2.8.1)
« on: 28 May 2010, 19:15:38 »

Good evening folks!

Just to steer away from my topic in general about every annoying fault on my car I'm posting this specific question here.

On Motronic M2.8.1 I see the fault code 136 described as "Unknown driver output error" and a possible cause (according to Autodata) is "ECM internal short to positive".

Does anyone have a clue about what this is and why? I've been searching all over the internet, but I can't find a lot of useful info about the 2.8.1.

If a driver output (not sure if it's a discrete transistor/mosfet or a hybrid package) actually has a short to positive, could that be caused by an external connection? Maybe someone have schematics for the ECM?

Anyway, the dash light does not indicate an error, I only see it if I clip it and I can not reset it. It's there after a reset without starting the engine.

Thanks in advance folks, this place is really great for a poor Norwegian bloke like me  :)
Logged
1995 Omega 2.6 V6 Estate ("fresh" engine) Drives like a 2-litre. Grr! Gettin' dusted by a 1.8 auto Cav..
1991 Omega 3000-24v (major rust job)
(Interested in buying Vauxhall emblems/grille for my V6)

Jimbob

  • Global Moderator
  • *****
  • Offline Offline
  • Gender: Male
  • Chester / Flintshire
  • Posts: 24525
  • I like traffic lights, but only when they're green
    • E250 Est / Golf GTI
    • View Profile
Re: Fault code 136 (M2.8.1)
« Reply #1 on: 28 May 2010, 19:35:39 »

cant recall ever seeing a 136....are your sure you read it correctly?

was it from a paperclip test or code reader?

Welung666

  • Guest
Re: Fault code 136 (M2.8.1)
« Reply #2 on: 28 May 2010, 20:33:23 »

Quote
Good evening folks!

Just to steer away from my topic in general about every annoying fault on my car I'm posting this specific question here.

On Motronic M2.8.1 I see the fault code 136 described as "Unknown driver output error" and a possible cause (according to Autodata) is "ECM internal short to positive".

Does anyone have a clue about what this is and why? I've been searching all over the internet, but I can't find a lot of useful info about the 2.8.1.

If a driver output (not sure if it's a discrete transistor/mosfet or a hybrid package) actually has a short to positive, could that be caused by an external connection? Maybe someone have schematics for the ECM?

Anyway, the dash light does not indicate an error, I only see it if I clip it and I can not reset it. It's there after a reset without starting the engine.

Thanks in advance folks, this place is really great for a poor Norwegian bloke like me  :)

That's the car telling you that you can't drive ;D ;D ;D
Logged

Omegafantasy

  • Junior Member
  • **
  • Offline Offline
  • Gender: Male
  • Oslo, Norway
  • Posts: 178
    • View Profile
Re: Fault code 136 (M2.8.1)
« Reply #3 on: 28 May 2010, 20:45:06 »

Quote
That's the car telling you that you can't drive ;D ;D ;D

Can I please stop laughing now?  :D
I've never thought about it THAT way, lol!

And yes, Jimbob, I am 100% it's read correctly (with paperclip).
I don't know how many times I've read it out now, but it is correct. Will connect computer for proper diagnosis in a couple of weeks.
Logged
1995 Omega 2.6 V6 Estate ("fresh" engine) Drives like a 2-litre. Grr! Gettin' dusted by a 1.8 auto Cav..
1991 Omega 3000-24v (major rust job)
(Interested in buying Vauxhall emblems/grille for my V6)

TheBoy

  • Administrator
  • *****
  • Offline Offline
  • Gender: Male
  • Brackley, Northants
  • Posts: 107023
  • I Like Lockdown
    • Whatever Starts
    • View Profile
Re: Fault code 136 (M2.8.1)
« Reply #4 on: 28 May 2010, 22:13:26 »

From memory, isn't a 136 a telltale light issue?
Logged
Grumpy old man

RobG

  • Omega Queen
  • *****
  • Offline Offline
  • Gender: Male
  • Bristol
  • Posts: 13831
  • I might have a link, pic or part number for that
    • 16 plate Mokka. Vivaro
    • View Profile
Re: Fault code 136 (M2.8.1)
« Reply #5 on: 28 May 2010, 22:18:49 »

Quote
From memory, isn't a 136 a telltale light issue?
Nope, 135. 
« Last Edit: 28 May 2010, 22:20:54 by RobG »
Logged
All that is necessary for the triumph of evil is that good men do nothing.

UPVC windows/doors/fascias/soffit/gutters supplied/fitted

TheBoy

  • Administrator
  • *****
  • Offline Offline
  • Gender: Male
  • Brackley, Northants
  • Posts: 107023
  • I Like Lockdown
    • Whatever Starts
    • View Profile
Re: Fault code 136 (M2.8.1)
« Reply #6 on: 28 May 2010, 22:23:55 »

Yeah, 136, recommendation is to reset/reprogram Motronic ECU, if that doesn't cure, replace ECU.

Howvere, if no symptoms, and fault clears and stays clear, I would wait-and-see...
Logged
Grumpy old man

Omegafantasy

  • Junior Member
  • **
  • Offline Offline
  • Gender: Male
  • Oslo, Norway
  • Posts: 178
    • View Profile
Re: Fault code 136 (M2.8.1)
« Reply #7 on: 28 May 2010, 22:37:13 »

Well, resetting for clearing (as in battery off) does not clear it at all. It's back as soon as I turn the ignition on.

I'm not sure if it affects anything, but my engine is running with about half power and I'm not man enough to find the fault  :(

Reprogramming might be a trick, but better buy some "tuning chip" off the bay while I'm at it. Replacing the ECU is hard here in this blasted country. Noone drives a V6 and even fewer breaks them..

Think I'll take out the box, dismantle it and do visual inspection and general measurement on the output drivers. It might be obvious?! Just wish someone had schematics for the box itself.
Logged
1995 Omega 2.6 V6 Estate ("fresh" engine) Drives like a 2-litre. Grr! Gettin' dusted by a 1.8 auto Cav..
1991 Omega 3000-24v (major rust job)
(Interested in buying Vauxhall emblems/grille for my V6)

TheBoy

  • Administrator
  • *****
  • Offline Offline
  • Gender: Male
  • Brackley, Northants
  • Posts: 107023
  • I Like Lockdown
    • Whatever Starts
    • View Profile
Re: Fault code 136 (M2.8.1)
« Reply #8 on: 28 May 2010, 22:39:23 »

Battery disconnection will not reset it.

If you change ECU, and it has RF remote locking, you need to swap the engine ECU, Imobiliser and key transponders as a package...
Logged
Grumpy old man

TheBoy

  • Administrator
  • *****
  • Offline Offline
  • Gender: Male
  • Brackley, Northants
  • Posts: 107023
  • I Like Lockdown
    • Whatever Starts
    • View Profile
Re: Fault code 136 (M2.8.1)
« Reply #9 on: 28 May 2010, 22:39:59 »

If you do go down that route, plenty of breakers on this site, one may be willing to post to Norway :y
Logged
Grumpy old man

Omegafantasy

  • Junior Member
  • **
  • Offline Offline
  • Gender: Male
  • Oslo, Norway
  • Posts: 178
    • View Profile
Re: Fault code 136 (M2.8.1)
« Reply #10 on: 28 May 2010, 22:45:13 »

Quote
Battery disconnection will not reset it.

If you change ECU, and it has RF remote locking, you need to swap the engine ECU, Imobiliser and key transponders as a package...

What will reset it if removing power isn't sufficient?

Luckily I don't have immobilizer so that's sorted. I DO have the receiver on the ignition lock though.. Strange.

Yeah, might be better off buying something off you guys. As far as I know there's no difference in LHD and RHD ECU's so problem shouldn't be more complicated than shipping it :)
Will rob ebay and hopefully some of you in here in about two weeks when my account balance is on the positive side ;)
Logged
1995 Omega 2.6 V6 Estate ("fresh" engine) Drives like a 2-litre. Grr! Gettin' dusted by a 1.8 auto Cav..
1991 Omega 3000-24v (major rust job)
(Interested in buying Vauxhall emblems/grille for my V6)

TheBoy

  • Administrator
  • *****
  • Offline Offline
  • Gender: Male
  • Brackley, Northants
  • Posts: 107023
  • I Like Lockdown
    • Whatever Starts
    • View Profile
Re: Fault code 136 (M2.8.1)
« Reply #11 on: 28 May 2010, 22:46:21 »

tech2 needed for resetting/reprogramming....
Logged
Grumpy old man

Omegafantasy

  • Junior Member
  • **
  • Offline Offline
  • Gender: Male
  • Oslo, Norway
  • Posts: 178
    • View Profile
Re: Fault code 136 (M2.8.1)
« Reply #12 on: 28 May 2010, 23:03:36 »

Okay. Didn't think they got permanently stored in those old ECU's. Will see if I'm able to reset via "My Naff Code Reader" when my mate gets his computer running. Don't know of a Tech2 in the area.
Tried persuading an Opel dealer to check it for some other stuff a long time ago, but he wanted an hours labour for it, at about £80..
Logged
1995 Omega 2.6 V6 Estate ("fresh" engine) Drives like a 2-litre. Grr! Gettin' dusted by a 1.8 auto Cav..
1991 Omega 3000-24v (major rust job)
(Interested in buying Vauxhall emblems/grille for my V6)

Andy H

  • Omega Lord
  • *****
  • Offline Offline
  • Gender: Male
  • Auckland
  • Posts: 5533
    • Mazda MPV
    • View Profile
Re: Fault code 136 (M2.8.1)
« Reply #13 on: 29 May 2010, 10:52:01 »

Quote
tech2 needed for resetting/reprogramming....
I haven't seen anyone mention it recently but I thought that 25 engine starts (including warm up to full temperature) would reset most stored codes :-/
Logged
"Deja Moo - The feeling that you've heard this bull somewhere before."

TheBoy

  • Administrator
  • *****
  • Offline Offline
  • Gender: Male
  • Brackley, Northants
  • Posts: 107023
  • I Like Lockdown
    • Whatever Starts
    • View Profile
Re: Fault code 136 (M2.8.1)
« Reply #14 on: 29 May 2010, 18:40:28 »

Quote
Quote
tech2 needed for resetting/reprogramming....
I haven't seen anyone mention it recently but I thought that 25 engine starts (including warm up to full temperature) would reset most stored codes :-/
TIS recommends a reset in this particulalr scenario, before replacing ecu...
Logged
Grumpy old man
Pages: [1] 2  All   Go Up
 

Page created in 0.012 seconds with 17 queries.