[Dave2302]

For in depth scanning I use an Autel Diaglink with the Benz module also from AZ

Hi,

Can you please tell me, when you do a full Car scan, how many computers (ECU's Modules call 'em what you will) do you see ?

 

[Padgett]

Hoo boy, I'd have to count them but a Whole Bunch of modules in Powertrain, Body, HVAC, Chassis, and a couple of other groups. Each can display the module identification, codes, erase codes, and live data. Each code is given as a Base code and then sub-codes identifying the specific code.

For example Bas/ESP was on. "C1141-8 MIL ON & Stored & Current
Pressure sensor :Zero point offset error of component B34/1 (ESP pressure sensor 1)"

Replaced pressure sensor 1 ($18) and light is now off. Actually was a bunch of codes mostly pointing to sensor 1. Replaced and all codes went away.

Also gave:
Control unit ESP
MB number 193 545 01 32
Supplier Teves
Hardware status 33/02
Software status 33/02
Diagnosis identifier 128/5
Date of manufacture 15.09.03

Tried many but never found better that could also connect and download to a PC.

 

[Dave2302]

We are tallking R170 here (and the Chrysler version that we mustn't mention) ? Not later cars like R171 (or other OBD compliant cars 2004 up Fords, Chevys etc) ?

On Mercedes R170 I'd expect it to have ....

Motor ECU
ABS / ESP
SRS / Airbag
Transmission

I would be surprised, very surprised if it got ATA, PSE, CCM, Audio, VR, ICM, Audio and a few others I can't think of now, because I've never come across anything that can emulate HHT
I actually evaluate new machines for a local motor parts wholesaler, so I get to see all sorts and always try them on R170, W638 and any other old MB's I might have laying around waiting on parts

I came across this before with iCs and R170, an owner was seeing a list of modules but could not get any data out of most of them (i.e. fault codes / live data / actuations etc) that guy had assumed that was because there were no faults, when in actual fact the list was just a list, but no connection to the actual modules

May be worth you checking if you can get any temperature info for HVAC, door switches in ATA, stuff like that

IDK, like I say, just curious

 

[Delucas]

We are tallking R170 here (and the Chrysler version that we mustn't mention) ? Not later cars like R171 (or other OBD compliant cars 2004 up Fords, Chevys etc) ?

On Mercedes R170 I'd expect it to have ....

Motor ECU
ABS / ESP
SRS / Airbag
Transmission

I would be surprised, very surprised if it got ATA, PSE, CCM, Audio, VR, ICM, Audio and a few others I can't think of now, because I've never come across anything that can emulate HHT
I actually evaluate new machines for a local motor parts wholesaler, so I get to see all sorts and always try them on R170, W638 and any other old MB's I might have laying around waiting on parts

I came across this before with iCs and R170, an owner was seeing a list of modules but could not get any data out of most of them (i.e. fault codes / live data / actuations etc) that guy had assumed that was because there were no faults, when in actual fact the list was just a list, but no connection to the actual modules

May be worth you checking if you can get any temperature info for HVAC, door switches in ATA, stuff like that

IDK, like I say, just curious

Is not Torque Pro more so for Displaying your cars performance ,temp blah blah on your Mobile phone while driving as well as if it can read codes but debatable if it will clear many ?
a very basic basic diag and well for £4.95 App 😱😱
Prob the only nice function is to Display your cars revs, temp , Oil pressure in multitude of random Colours or layouts .

£4.95 mmmmm
My Diagnostic case costs more than that. 😎😎

 

[Padgett]

I have both, '01 SLK320 and an '04 (early) unmentionable coupe. For both I must select SLK/SLK320/LHD/6 pin. Both read the same modules (many). Pretty sure I've seen ones you mentioned. Was looking at door locks and got this:
Ecu Ver Name Ecu Ver Value
Control unit RFL
MB number 170 820 18 26
Supplier Siemens
Hardware status 47/00
Software status 22/01
Diagnosis identifier 0 / 1

Read Codes
B1000 Stored&Current
N54/3 (Radio DAS control module)

System Status
Ecu Ver Name Ecu Ver Value
MIL Status OFF
Codes Found 0
Monitors N/A 1
Monitors OK 3
Monitors INC 6

101 Tml.30 -Y-
102 RF/IR transmitter key last 8
used
103 Transponder amplitude 23.51 v
104 Partial scopes of version YES
coding inhibited
105 Writing vehicle ident nember YES
inhibited
106 Workshop proramming inhibited YES

 

[Padgett]

BTW I collect scanners and have both Torque Pro for quick and dirty & parameter display while driving. My go to scanner is an Autel Diaglink with the Benz module (note $10 coupon) that does more internal modules than I can count (think full list is on Autel's web site). And an Autel MS-906 but prefer the DiagLink. Also have some PC based scanners including the MicroPod. Am thrying to find out if my Carly for Mercedes covers R170 now but have been communicating since 23 Feb (at least 10 emails) and verified I have a license but so far have failed to receive needed credentials.

 

[LeonardoDaBenz]

This is what I got after doing my due diligence. I have little knowledge and fewer tools BUT it has helped ME resolve some issues (ie repairs that I could do) and gave me some idea about what's wrong before I took it to the shop.

At $140 CDN, it allowed me "pretty good" access on 3 rides so far (one "free" s/w download and $10 per mfg after that (covers all lines sold so all MB or all Honda or etc)

Will it work with an 2002 R170? Dunno but probably. It does work with a 2003 civic so ........

 

[Delucas]

I net you cant connect it to 170

BTW I collect scanners and have both Torque Pro for quick and dirty & parameter display while driving. My go to scanner is an Autel Diaglink with the Benz module (note $10 coupon) that does more internal modules than I can count (think full list is on Autel's web site). And an Autel MS-906 but prefer the DiagLink. Also have some PC based scanners including the MicroPod. Am thrying to find out if my Carly for Mercedes covers R170 now but have been communicating since 23 Feb (at least 10 emails) and verified I have a license but so far have failed to receive needed credentials.

Now An Autel 906 Model is a great little machine and improving on each newer model that gets released every year ,

 

[LeonardoDaBenz]

And that may very well be true but it gives OP an idea of cost he can expect not to go below

 

[Padgett]

True but 906 depends on wireless. Only have because was free. My DiagLink downloads directly to PC. Also 906 subscription is $500. Since my new car is a 2012 and go back from there, $88 Diaglink with Benz, Chrysler (Jeep), and GM modules (first free, others $10 ea) is a better choice for me.

 

[Rofa]

Regarding the Autel, I thought it would be easier to ask them. Here is the reply. The download link does list the 38 pin socket model for the R170 and the modules it will access. (It's listed after the R171).
"It needs more vehicle details to check which device can work on your vehicle, so here we attached a coverage link for your reference, please click below link, then select a model and vehicle information to check what function the device can support:
Vehicle Coverage | AUTEL

Besides, Diaglink is a basic device, and there is no further development plan for it, if in need, it is suggested take other more advanced device into consideration, such as MX808S."

PS The MX808S is about the same price I paid for SDS...... which I have still to use in anger.....

 

[Padgett]

Understand their position, they want to sell new products. As mentioned the MS-906 does everything for all cars and has a $$$ subscription available. If needed something newer for many lines then the ML629 would be my choice.
However since I have no desire for any car made after 2014 my Diaglink with 2018 Benz, GM, and Chrysler covers all of my OBD-2 cars.The current version is updated to 2023 (see link) and is still $88 with coupon and the Benz module.
BTW the MS-906 and the Diaglink both seem to have the same software for my SLK320. It is identical in setup and operation.

 

[Delucas]

Every Autel machine will do more or less more than its cheaper model as you go up the ladder and cost
try installing rear Electronic brake pads on diff Brand Cars for example or activate rear windows per side or test all rear light indicators on a SLK 171 or …..

All depends what you req it to do and you will always find it does not cover or reset x or code y module.

A cheap Diagnostic is well cheap for a reason as the ever evolving Car Electronics get more & more complicated.

Now give me Diagnostics to go in to Cars Electronic Electric car battery Banks . 😎😎

 

[Dave2302]

As mentioned the MS-906 does everything for all cars and has a $$$ subscription available

Only if they are OBD Compliant, it will not do all on R170 and similar tech Cars !!

 

[Padgett]

a) I also have the 38 pin adapter.
b) Guess you missed "I have no desire for any car made after 2014 "

 

[Dave2302]

Neither 38 pin nor the 16 pin R170 Cars are OBD Compliant. In plain English that means they do not speak the same computer language that the OBD Compliant Cars do !!

Therefore the Machine will never achieve everything that the serious DIY owner of a Mercedes car that is between 19 to 27 years old will want / need to do .......

Autel gear is very good stuff, I have Pro version, also Snap On and Delphi, but SDS they aren't !! Those that have bitten the SDS bullet will know what I mean, those that haven't probably won't be able to use it anyways, and if you have SDS then you will know what I mean.

Nowhere does it mention K Line protocol. Yes it is a good machine for OBD Compliant Cars, although, like a lot of items there are better.

I have wasted far too much of my valuable time on this, and many other posts period, end of, I'm done here !!

 

[Padgett]

Gee, dunno. My Autel worked just fine with 16 pin OBD connector for my 2000 SLK230 (gone) and 2001 SLK320 (sill have) and (unmentionable) 2004. Understand US cars got OBD-II sooner than other countries.
ps have a 38 pin, never used it.
pps just a hobby and for my personal cars. Is the best I've found for under a Benjamin.

 

[Delucas]

Gee, dunno. My Autel worked just fine with 16 pin OBD connector for my 2000 SLK230 (gone) and 2001 SLK320 (sill have) and (unmentionable) 2004. Understand US cars got OBD-II sooner than other countries.
ps have a 38 pin, never used it.
pps just a hobby and for my personal cars. Is the best I've found for under a Benjamin.

OBD ports come in circa 1995 / 1996 for UK / Europe cars. ( maybe sooner maybe a year ish ??? )

Vw introduced a monitoring system in 1968
then followed by Datsun in 1968 then …….

So the Germans were the leaders or pioneers so to speak. 🙃🙃

 

[LeonardoDaBenz]

OBD ports come in circa 1995 / 1996 for UK / Europe cars. ( maybe sooner maybe a year ish ??? )

History of OBDII
The history of on-board diagnostics goes back to the 1960s. Several organizations set the groundwork for the standard, including the California Air Resources Board (CARB), the Society of Automotive Engineers (SAE), the International Organization for Standardization (ISO) and the Environmental Protection Agency (EPA).

It’s important to note that before standardization, manufacturers were creating their own systems. The tools from each manufacturer (and sometimes models from the same manufacturer) had their own connector type, electronic interface requirements. They also used their own custom codes for reporting problems.
Highlights in OBD history:
1968 — The first OBD computer system with scanning capability was introduced by Volkswagen.

1978 — Datsun introduced a simple OBD system with limited non-standardized capabilities.

1979 — The Society of Automotive Engineers (SAE) recommends a standardized diagnostic connector and set of diagnostic test signals.

1980 — GM introduced a proprietary interface and protocol capable of providing engine diagnostics through an RS-232 interface or more simply, by flashing the Check Engine Light.

1988 — Standardization of on-board diagnostics came in the late 1980s after the 1988 SAE recommendation that called for a standard connector and set of diagnostics.

1991 — The state of California required all vehicles to have some form of basic on-board diagnostics. This is referred to as OBD I.

1994 — The state of California mandated that all vehicles sold in the state starting in 1996 must have OBD as recommended by SAE — now referred to as OBDII. This stems from the desire to perform across the board emissions testing. OBDII included a series of standardized diagnostic trouble codes (DTCs).

1996 — OBD-II becomes mandatory for all cars manufactured in the United States.

2001 — EOBD (European version of OBD) becomes mandatory for all gasoline vehicles in the European Union (EU).

2003 — EOBD becomes mandatory for all diesel vehicles in the EU.

2008 — Starting in 2008, all vehicles in the US are required to implement OBDII through a Controller Area Network as specified by ISO 15765-4.

 

[Delucas]

History of OBDII
The history of on-board diagnostics goes back to the 1960s. Several organizations set the groundwork for the standard, including the California Air Resources Board (CARB), the Society of Automotive Engineers (SAE), the International Organization for Standardization (ISO) and the Environmental Protection Agency (EPA).

It’s important to note that before standardization, manufacturers were creating their own systems. The tools from each manufacturer (and sometimes models from the same manufacturer) had their own connector type, electronic interface requirements. They also used their own custom codes for reporting problems.
Highlights in OBD history:
1968 — The first OBD computer system with scanning capability was introduced by Volkswagen.

1978 — Datsun introduced a simple OBD system with limited non-standardized capabilities.

1979 — The Society of Automotive Engineers (SAE) recommends a standardized diagnostic connector and set of diagnostic test signals.

1980 — GM introduced a proprietary interface and protocol capable of providing engine diagnostics through an RS-232 interface or more simply, by flashing the Check Engine Light.

1988 — Standardization of on-board diagnostics came in the late 1980s after the 1988 SAE recommendation that called for a standard connector and set of diagnostics.

1991 — The state of California required all vehicles to have some form of basic on-board diagnostics. This is referred to as OBD I.

1994 — The state of California mandated that all vehicles sold in the state starting in 1996 must have OBD as recommended by SAE — now referred to as OBDII. This stems from the desire to perform across the board emissions testing. OBDII included a series of standardized diagnostic trouble codes (DTCs).

1996 — OBD-II becomes mandatory for all cars manufactured in the United States.

2001 — EOBD (European version of OBD) becomes mandatory for all gasoline vehicles in the European Union (EU).

2003 — EOBD becomes mandatory for all diesel vehicles in the EU.

2008 — Starting in 2008, all vehicles in the US are required to implement OBDII through a Controller Area Network as specified by ISO 15765-4.

Mine was the short version 😂😂