Mercedes-Benz Forum banner

R129 CEL Diagnostic Trouble Codes & Procedures (1990-1995)

126317 Views 37 Replies 19 Participants Last post by  Scotty1997MB500SL
Could anyone give a short "how to do" on the diagnostic system for the old SL's?
I've tried the search function, but can't find anything explaining how to do it with what tool and a codelist.

Thanks in advance...
1 - 20 of 38 Posts
The procedure described here works for all systems with diagnostics on the R129 through model-year 1995 except for the SRS (airbag) for '94 and '95. On some of the systems from '94 and '95 it will not retrieve as much information as an advanced scan tool would.

Each system's diagnostic output signal is wired to a specific socket of the car's main "diagnostic connector", X11/4. An additional pair of sockets in the connector provide battery voltage and chassis ground for convenience. Early cars with continuous-fuel injection have 16 sockets (picture), while later models have 38 sockets. The sockets are numbered for easy identification. When you make connections to any of the you should know that all circuits have protected outputs and nothing can be damaged by mistakes.

Codes are read sequentially one at a time. That is, you trigger the system you are checking to issue a code, you read the code, you trigger another code, and so on. With the key on and engine off, you trigger a code by electrically shorting the system's particular diagnostic socket to ground for 2 to 4 seconds using a wire. A second or two after the wire is removed, a series of electrical pulses will occur at the socket. The number of pulses corresponds to the number of a code.

There are numerous ways to view the pulses for counting and getting codes. The simplest method is to connect a 99-cent LED from Radio Shack (P/N 276-209, pictured) between battery voltage and the socket of the system being checked (the one you ground for 2 to 4 seconds to get a code) and watch it blink in sync with the pulses. A pair of banana plugs is nice for this. Be sure to have the polarity of the LED correct -- if it is wrong, you won't damage anything, but the LED won't ever turn on. In the special case of reading top controller codes on cars made through 12/93, you don't even need the LED -- just watch the top control switch on the console flash. This is possible because one side of the lamp inside the switch is wired to the diagnostic socket for the top control system.

Once you have read all of the codes you can erase them. They are erased individually one at a time. To do this, read a code, wait a few seconds, and then short the diagnostic socket to ground for 6 to 8 seconds.

For a list of diagnostic codes see post #3 below.

For diagnosing convertible top problems I believe it is best to read/erase all codes and then operate the top. When the problem occurs, continue holding the top control switch until it flashes or 80 seconds elapse -- whichever occurs first. Then read the freshly stored codes.

Attachments

See less See more
2
edutain1 said:
Thanks again Bobterry for this, I would like a set of the error codes, how should I go about getting them?
The codes are listed in a manual I have for a Baum diagnostic scanner. This is what I have been emailing to people and now realize I can attach to a thread (here). For troubleshooting procedures that follow the codes you should have either the Mercedes WIS software that can be bought from an eBay seller in the U.K. for about $10, or the R129 Tech DVD available from MBUSA for $75.

Attachments

hi i tryed but no luck i made a jumpwire between 1 and 10 2-4 sec the lamp was on i disconected the the jumpwire i got blinking ligth but the count was more then 40 then i tryed one more time same result
the hard top is on but i hade to do it manualy (the locking)
the car was fine two weeks ago now nothing is working its crasy when i lock the door the back rest goes forward so i had to remove the braker
the engeien fans dont work
the soft top dont work
roll bar same story

please help
  • Like
Reactions: 1
The procedure described here works for all systems with diagnostics on the R129 through model-year 1995 except for the SRS (airbag) for '94 and '95. On some of the systems from '94 and '95 it will not retrieve as much information as an advanced scan tool would.

Each system's diagnostic output signal is wired to a specific socket of the car's main "diagnostic connector", X11/4. An additional pair of sockets in the connector provide battery voltage and chassis ground for convenience. Early cars with continuous-fuel injection have 16 sockets (picture), while later models have 38 sockets. The sockets are numbered for easy identification. When you make connections to any of the you should know that all circuits have protected outputs and nothing can be damaged by mistakes.

Codes are read sequentially one at a time. That is, you trigger the system you are checking to issue a code, you read the code, you trigger another code, and so on. With the key on and engine off, you trigger a code by electrically shorting the system's particular diagnostic socket to ground for 2 to 4 seconds using a wire. A second or two after the wire is removed, a series of electrical pulses will occur at the socket. The number of pulses corresponds to the number of a code.

There are numerous ways to view the pulses for counting and getting codes. The simplest method is to connect a 99-cent LED from Radio Shack (P/N 276-209, pictured) between battery voltage and the socket of the system being checked (the one you ground for 2 to 4 seconds to get a code) and watch it blink in sync with the pulses. A pair of banana plugs is nice for this. Be sure to have the polarity of the LED correct -- if it is wrong, you won't damage anything, but the LED won't ever turn on. In the special case of reading top controller codes on cars made through 12/93, you don't even need the LED -- just watch the top control switch on the console flash. This is possible because one side of the lamp inside the switch is wired to the diagnostic socket for the top control system.

Once you have read all of the codes you can erase them. They are erased individually one at a time. To do this, read a code, wait a few seconds, and then short the diagnostic socket to ground for 6 to 8 seconds.

For a list of diagnostic codes see post #3 below.

For diagnosing convertible top problems I believe it is best to read/erase all codes and then operate the top. When the problem occurs, continue holding the top control switch until it flashes or 80 seconds elapse -- whichever occurs first. Then read the freshly stored codes.
Thanks for sharing the info with us. I'm new at the code thing and my sound like a dumb question but do the codes read out on the dash?
...do the codes read out on the dash?
Roll bar codes can be read by counting flashes of the malfunction lamp in the instrument cluster for '90-'95 cars, and top controller codes can be read by counting flashes of the lamp in the control switch for '90-'93 cars. All other codes require an LED, test lamp, etc.

hi i tryed but no luck i made a jumpwire between 1 and 10 2-4 sec the lamp was on i disconected the the jumpwire i got blinking ligth but the count was more then 40 then i tryed one more time same result
the hard top is on but i hade to do it manualy (the locking)
the car was fine two weeks ago now nothing is working its crasy when i lock the door the back rest goes forward so i had to remove the braker
the engeien fans dont work
the soft top dont work
roll bar same story
Late reply to an old post...

You should not have a blink count higher that 30, as only codes 1-30 are defined.
thanks a bunch

Thanks for sharing the info with us. I'm new at the code thing and my sound like a dumb question but do the codes read out on the dash?
i will be getting codes to day. Have not been able to drive my baby for the last six months
hallo. i now its an old link but i try anyway. i am working on my sl now, read out fault codes on the roof, got code 23. RB controle module (crash deployment). tried to read out on the roll bar. jumped 1 to 7. the lamp was just lighting when i jumped but didnt blink after. is there a way to erase this code or is the RB module defect? the belt retractor on the passenger side is always retracted when you buckle up. the car has been crashed and fixed. Someone who got a clue?:)
code reading

I read the code on my 500sl 1991 and I have two questions about it, on socket 7 (roll bar) and on socket 12 ( Infrared remote control locking) I have two steady light when I plug in ( no flashes), and on socket 6 (supplental restaint system/ air bag) I have a light who stay on for about two second and come off, and no flash after. Anyone have a idea of what going on.
If the LED lights but does not flash a code, there are two possible problems I can think of. First, the LED is not connected between #16 and the diagnostic socket being checked for codes. Second, a good contact is not being made continuously between the socket being checked and chassis ground for 3 seconds to trigger a read. If these criteria are being met, then possibly the diagnostic port of the relevant module is faulty.

the belt retractor on the passenger side is always retracted when you buckle up. the car has been crashed and fixed. Someone who got a clue?:)
I will guess that the seat belt's emergency tensioning device activated in the crash. If this is the case, then the seat belt must be replaced. If that is not the case, then the bowden cable that connects the seat belt buckle to the belt's take-up reel is likely jammed.

I have a good used one to sell, but I imagine it would be expensive to send to Europe.
I use a tester with three wires, and it's working fine on other pins. I will check for bad contact on those two pins, thanks anyway!
I use a tester with three wires, and it's working fine on other pins. I will check for bad contact on those two pins, thanks anyway!
This steady light case, you can use just direct wire from pin1 to another diagnose pins (work without third line of pin 16) then you count the code at speedometer for example the SRS indicator, also do the same thing for the rollbar, it's blink the code as the LED
Baum 02-01-01 Fault Code Manual for MB

The codes are listed in a manual I have for a Baum diagnostic scanner. This is what I have been emailing to people and now realize I can attach to a thread (here). For troubleshooting procedures that follow the codes you should have either the Mercedes WIS software that can be bought from an eBay seller in the U.K. for about $10, or the R129 Tech DVD available from MBUSA for $75.
FWIW, I have attached a newer version, dated 02-01-01, of the PDF that you originally attached. I'm not sure if it has anymore to offer.

Attachments

Pulling codes for first time?

After it has been cleared a couple times by my INDY eventually my check engine light comes back on and stays on. Car is running perfectly, even has the new engine harness, alternator harness to follow shortly but I digress...

I will be going to get an LED at radio shack shortly, but of the 38 holes how do I even no where to begin?

Also I have the connector in there with the LED on it, I had key on, engine off, and when I press button it just stays lit.

Do I need the key in postion one or postion two. I know this is covered but I am getting lost in all the threads.
Not really a criticism, but you have started yet another thread on diagnostic codes which you have pointed out ' you are getting lost in'!!

In one of these threads that was started, I advised step by step on how to read codes using the diagnostic sheets and how to clear them.

It's there somewhere ...... now after three...... Seek and ye shall find :D
I found your answer here.

http://www.benzworld.org/forums/r129-sl-class/1473600-help-code-reading-w-led-issues.html

Why do some people like the guy who responded to you mention the 3rd wire (post #3in thread above), as I read your post, I can connect and clear between the #3 and whatever pin I am testing with the LED and no 3rd wire. I am sorry if I am missing something. Bob Terry seems to say go between #3 and pin tto be tested. Count pulses, to clear go between ground and that pin for 8 seconds. No 3rd wire mentioned?

I cannot get to radio shack till later but I do have the push button LED as part of my car. After holding for three seconds I get 5 pulses. Same thing upon repeat just to be sure. I know this means I need to check Pin 5 as soon as I get the LED later. Baby steps!
See less See more
It's not like "Der dritte mann" :D
The third wire is in fact a splice of the test wire you would place in say pin #6, in other words in the attached PDF the Black and the Yellow wire are connected together with the black wire as the shorting/grounding wire, the Red wire would stay connected to pin #3.

Example: To check Pin #6. ASR

Red wire is connected to pin #3 (Battery)
Yellow wire is placed into pin #6 (38 pin socket)
Black wire (spliced to Yellow wire) is held on Pin #1 or any grounded position for around four seconds and removed. LED will blink code.
To clear that code, the black wire is then grounded for around ten seconds.

You would then repeat this process until all codes on PIn #6 have been read and possibly cleared. You would then move on to the next pin of the 38 pin socket and repeat the previous process.

The black and yellow wire can be interrupted by placing something like a bell push between them so that the black wire can be permanently grounded.


All this talk of 'Der dritte mann' :D

Attachments

See less See more
Very Funny :D To be clear though. Using your #6ASR example.


Connect LED straight between #3 and #6, count code.

Then, Connect LED straight between #6 and #1 for 8 seconds to clear code.

In this scenario 3rd wire (man) is not needed.
No, you need 'der dritte' wire because the Yellow wire needs to stay connected to pin#6 during the process.
OK thanks, I will get radio shack LED #276-209 and some small banana plugs and fab one up later. I can connect yellow and black wire directly to negative side of led, I don't need to separate them correct.

A switch in between would just allow you to pull the ground without removing, correct?
1 - 20 of 38 Posts
This is an older thread, you may not receive a response, and could be reviving an old thread. Please consider creating a new thread.
Top