LED code 17 - PeachParts Mercedes-Benz Forum

KAMAL · #1 06-25-2003, 11:51 AM

last night i checked led code on my 95 E420. It gave me 17 blinks.
I searched the code 17 on alldatadiy.com; it shows to do test scope of Serial Data Bus (CAN)

Test condition: n3/1 (connection) check resistance with iginition key off.

Nominal Value = 115-125 ohms

Possible cause/Remedy are follows:

Data line
DL control module(n1/3)

N1/3 is Ignition control module (knock sensor)

Question?

A) I opened the module lid using 5mm hex bit, but had hard time pulling the module(N3/1) out. Any sugguestion how to pull it out so I check the resistance.

B) How to solve the problem that is Data line and knock sensor? There is no mention in repair manual of data line. I have located the knock sensor. But fastlane does not have it in the stock.

Please advice
thanks & regards,

mbdoc · #2 06-25-2003, 12:08 PM

First of all, when erased does the code come back & turn the light back on. IF not then testing won't provide ANY needed info, as the problem must be current for testing to show the problem.

Second, what you should do is have the complete CAN system scanned & then see if any of the other computers see a problem as well!

KAMAL · #3 06-25-2003, 02:09 PM

How do I erase the code?

mbdoc · #4 06-25-2003, 04:30 PM

With a scan tool, or by bringing up the code again & hold the button for 8 seconds to erase that code.
OR you can disconnect the battery!

JimF · #5 06-25-2003, 08:02 PM

if the code comes back, do some t/s.

1) Code 17 is "data exchange malfunction between individual control modules".

2) Code 25 is "Knock sensors or engine control module defective"

3) The N1/3 module is the Ignition Control Module and IS NOT the KNOCK sensor. It's the complete module: check my page (click "www" icon below) and read Menu #5. The connections are shown in the figure.

When ICM fails, it gives 'strange' failures:like Crankshaft Sensor is bad, etc. I'm not saying that it's bad but as MB Doc suggested you need to read codes from the complete system and then re-evaluate.

Your car is similar to mine as far as some of the modules.

wjm · #6 06-25-2003, 10:16 PM

Hey Jim,

Too bad it's not Code 19. We could fix that, couldn't we... :-)

JimF · #7 06-26-2003, 10:35 AM

Talk about that, an update on my DTC 19 problem.

Recently changed the MAF sensor ($265) and the O2 sensor ($78). After a two months, I checked the S/A: was .8749.

At the low point, just before changing both sensors, the S/A was .8319.

My gas milage has increased to what it was when I first bought the car. So to say I'm pleased is a bit of an understatment!

Still have the "S" class Eprom installed and probably will leave it there.

KAMAL · #8 06-27-2003, 11:59 AM

I have erased the code. But now when i go check if there are any codes stored. I don't get any blinks after i hold the switch for three seconds. Is this normal? It suppose to give one blink if there is no code stored in it.

Arthur Dalton · #9 06-27-2003, 12:25 PM

<>

...After it has gone through ALL systems testings...can take several days/drive cycles...