ABS/DSC - Calling any INPA experts!...

[DomS]

Evening,

I have an ABS/DSC issue (lights stay on) on my 06/2000 model 3.0 Z3 and have set up a laptop with INPA 5.0.2 to try and diagnose the problem, as (from reading other people's experiences) there appear to be umpteen possible causes.

I've been using the ADS interface to allow me to communicate with the ABS module and although I can access many other modules (engine, body and even steering angle sensor), I can't communicate with the one I need - the ABS/DSC module. I have tried all the "Chassis" modules in the E46 and E36 sections and they either come up with the
"IFH-0009: NO RESPONSE FROM CONTROLUNIT. Program will be stopped!"
error, or the
"SYS-0012: IDENTIFICATION ERROR Program will be stopped!"
error.

I initially had the problem in the car over a year ago and started researching the good info here and various other forums. After many cable purchases, RS232 port adaptors and software installs later, I have a diagnostic setup that appears to work other than the problem above.

The actual ABS/DSC unit on the car is an ATE unit with these part nos:
ECU:-ATE
OE:- 6 753 603
DSC3 - ES
ATE:-10.0947-0806.3

PUMP:-
34.51 - 6 753 598
DSC
ATE:- 10.0204-0299.4

I'd like to know if anyone knows which option I need in INPA to access that particular ABS/DCS module...

I did think it could be a faulty control unit, so I sent it away to ECU Testing Ltd., who couldn't find any basic fault with it (although they were unable to do a full functional test on that particular model).

Any help appreciated (and apologies for the long post)!

Cheers,
Dom

[Brian H]

Does the link below help?

http://www.zroadster.net/forum/viewtopi ... 39#p332639

FYI My car is a 11/2001 and I use DSC MK60

[Robert T]

Some more info on module compatibility here - the data for the 3.0 is from Brian's car: http://www.zroadster.net/forum/viewtopi ... =5&t=38095

With a car as late as a 3.0 I don't think there is any need to use ADS - I have been able to access the ABS module on all the cars I have tried it on using a USB interface and 20-pin adapter. I take it you have never been able to connect to the module even before the fault developed? It might be worth a shot with a USB interface to see if you can get it to respond - we know for sure that the BMTechnic cable and lead can talk to the ABS module of a 3.0.

I was going to suggest that it was the control unit, but by the sound of it, they will have connected to it using something similar to what the car uses internally. The only other possibility I can think of is that there is a wiring fault between the car and the control unit and this is causing both the fault and preventing you accessing the module.

Cheers R.

[DomS]

Thanks gents.

Brian, that's useful thanks. I've since found that yours would have the Teves MK60 as it was made after 09/2000. My car is likely to have the Teves MK20 as it was made before that in 06/2000 and therefore I'll need a different INPA script - probably the "ABS Mk 20 (DS2)" one. My unit has ATE on it and nothing about Teves, but from what I now know, ATE started life as a subsidiary of Teves.

Robert, I spoke to Chris at BMTechnic last year and he said that if I have a voltage present on pin 15 in the 20-pin round connector (with ignition off), I would need the ADS interface (with RS232 serial port) to access all modules (ABS being one of those) and his kit wouldn't do the trick. The engine module and some other modules are accessible with the BMTecnic kit via the OBD2 connection and a USB lead, but unfortunately not all modules on my car. I did try with the USB/OBD2 setup originally and found I could only access a few modules. That was before contacting BMTechnic and and also reading up that I'd need the ADS interface for certain modules (see here: http://www.bimmerforums.co.uk/forum/f99 ... ed-t85191/).

Having said that, I can't access the ABS module with apparently the right ADS interface either! So it's looking like one of these things:
1. I don't have the right INPA script (I think this is unlikely as I now know I have a ATE/Teves MK20 unit).
2. I have a problem with my INPA setup using the ADS/serial interface to access ADS-only modules.
3. There's a fault somewhere between the 20-pin interface and the module on the car as you suggested Robert.
4. The control unit is faulty after all.

If I can confirm which other modules on my car require the ADS interface through INPA, I should be able to confirm my ADS setup is OK and rule out no.2.

I'm beginning to think it is the control unit after all, as it appears to be a fairly common fault and also, although ECU Testing weren't able to find a fault, they weren't able to fully test it either!

That's a very useful INPA knowledgebase you're compiling Robert and I hope I can contribute to it if I get these issues sorted out...

Cheers,
Dom

[Brian H]

Hi Dom,

There is a list of members with diagnostic kit, link below. Maybe worth a PM to a local member to see if they can connect to your unit?

Members with diagnostic kit

Brian

[Robert T]

Hi Dom,

Your input into my spreadsheet of what modules can be accessed by various means would be appreciated. It would be very useful to see the differences between OBD and ADS adapters on your car - shame you are such a long way from me, otherwise you could have used my cable.

One thing that puzzles me with this is that your car is over 12 months younger than my 01/99 M44 1.9, and yet I can read my ABS/ASC module using a USB/OBD adapter, and activate its self-test mode. I would have thought that the newer ABS/DSC module would have been OBD compatible, rather than the older ADS. Of course, BMW did not develop DSC just for the Z3, so it may be that the later ASC modules contain newer electronics than the early DSC modules, but it does seem a bit weird.

Cheers R.

[Brian H]

Dom it is maybe worth putting you VIN number in to the link below, hopefully this should show ASC or DSC in the build data.

@Robert, does your car show ASC on your original build data?

Edit: Link now added

http://www.bmwarchive.org/vin/bmw-vin-decoder.html

[Robert T]

@Brian - No ASC listed on my spec sheet - it was standard equipment, with a button labelled ASC and a label on the unit that says ASC - mine is pre-facelift, but with the later instruments.

Cheers R.

[Brian H]

@Brian - No ASC listed on my spec sheet - it was standard equipment, with a button labelled ASC and a label on the unit that says ASC - mine is pre-facelift, but with the later instruments.

Cheers R.

Interesting Robert, I have option S210A - Dynamic Stability Control listed

[Jonco]

............One thing that puzzles me with this is that your car is over 12 months younger than my 01/99 M44 1.9, and yet I can read my ABS/ASC module using a USB/OBD adapter, and activate its self-test mode. ............

For info - mine is 12months older again (12/97 build) and I can read it using BM Technics INPA - ABS/ASC 4G option.
Archive says I have - S214A Automatische-Stabilitäts-Control (ASC+T) Automatic stability control (ASC+T).

HTH

[Robert T]

Nope, definitely not listed, and it isn't on the next two VINs either, which are both M44s.

Cheers R.

[BladeRunner919]

My 1988 M44 does list it:

S214A - Automatische-Stabilitäts-Control (ASC+T) Automatic stability control (ASC+T)

[Robert T]

My 1988 M44 does list it:

Blimey! Does it also list a flux capacitor?

Cheers R.

[BladeRunner919]

It's a very early model!! I meant '98, of course.

[Brian4]

This may not help in reading the codes but I had been having trouble with the DSC light staying on. This was occasionally accompanied by the ABS module operating the brakes. Ours is 06/2000 build.

The local BMW specialist accessed the module via the 20 pin connector but this was the BMW kit.

After much playing around and the steering angle sensor being reset a few times I found that the front control arm bushes were worn and allowing the wheel speed sensors and steering angle sensor to confuse each other so the DSC turned off. I found the bushes were worn when tightening the wheel nuts and there was some movement in the wheel but not picked up by the MOT.

Replaced bushes and reset the steering and so far 3 months no light.

To rest the steering either disconnect the battery for and hour or turn the steering from lock to lock twice with engine running.

[DomS]

Thanks again Roberts and Brians etc!

@Robert, I agree it is a little odd that my later car requires the ADS interface and your older one is able to use OBD2. As expected, Brian's later (post 09/2000) 3.0 model can use OBD2.

@Brian H, my car has DSC according to the website (and more importantly as confirmed by the actual unit in the car!).

@Brian4, that's an interesting fix! Thanks for the info as it's always good to hear what has worked for some people.

One of the problems is that the MoT has expired, so I can't do things like take it for a test drive after clearing the fault codes or making other changes. I suppose I could take "the scenic route" to an MoT station, but I'd prefer to book it for an MoT when I know I've cleared the fault and am confdent it will pass.

I had been running some new 18" wheels with new tyres before taking it off the road and I'd read that a small change in the wheel/tyre rolling circumference could possibly upset the ABS system. I still have the original 17s, but the rear tyres are worn and would probably fail an MoT, so I can't really just put them back on and go for a spin ...aaagh!

The ABS light would come on intermittently before I changed the wheels so I can't remember when it stayed on constantly (before or after changing them). I checked the ABS sensors and replaced the two front ones (with non OEM ones) when I first looked into this. I've heard of people having problems with non OEM ones, but before I get anything else, I really want/need to try and communicate with the ABS module. Perhaps the only solution is to book it for an MoT at a local dealer and ask for a diagnostic test too ...although that seems a bit like giving in!

Cheers,
Dom