The Z3 Diagnostics Thread: Instructions, Experiences, Discussions, Experimentation

[pepsih]

Check engine not illuminating suggests a power issue to the ecu. Check that you are getting 12V power to it.
Check the fusible link on the power wires after the battery.

This is probably not an ews issue at all.

Im not sure if I should open a new thread with my analysis, however yesterday I spent some time on the car.
The z3 was connected via jumper cables from another car.
Please see the picture.

75a5dbb5-24a5-421a-b030-d998405d1a79.jpeg


Basically :
Pin 87 and 88 Continuity OK from 20 pin connector.
Pin 26=12V
Pin 27= 12V
Pin 54= 0V

Removed and tested relay= OK

Bridged relay at 30/87, DME Pin 54 V=4.16V
So i came to a conclusion that somthing is "taking" the V.
i STARTED to unplugg several connection on that Cable....

Once I unplugged the Hot film air mass meter B6217
V at pin54 DME=12v with the cable bridged on relay at 30/87
V at pin54 DME= 0.25v with Relay installed

Screen Shot 2020-06-18 at 06.52.53.pngScreen Shot 2020-06-18 at 06.52.58.png

[pepsih]

Im not sure if I should open a new thread with my analysis, however yesterday I spent some time on the car.
The z3 was connected via jumper cables from another car.
Please see the picture.

75a5dbb5-24a5-421a-b030-d998405d1a79.jpeg


Basically :
Pin 87 and 88 Continuity OK from 20 pin connector.
Pin 26=12V
Pin 27= 12V
Pin 54= 0V

Removed and tested relay= OK

Bridged relay at 30/87, DME Pin 54 V=4.16V
So i came to a conclusion that somthing is "taking" the V.
i STARTED to unplugg several connection on that Cable....

Once I unplugged the Hot film air mass meter B6217
V at pin54 DME=12v with the cable bridged on relay at 30/87
V at pin54 DME= 0.25v with Relay installed

Screen Shot 2020-06-18 at 06.52.53.pngScreen Shot 2020-06-18 at 06.52.58.png

Edit: well i realized something.
DME was removed so probably no ground... get back later when i test ir

[Z3C Tblau]

A bit overdue, but as promised:

How to calibrate the Z3 DSC Lateral Acceleration Sensor (aka Transverse Acceleration Sensor) using Tool32. For Z3 non-M with DSC system, not ASC.
Sensor must be installed fully, and car on a level paved ground for this.

See attached pdf (click on thumbnail to download).

No DIS or ISTA needed.

Thanks a lot 328!

I had the code 163 "Lateral acceleration Sensor electrical failure" come back after five years since the first and only time it appeared (solved at the time by just clearing it).
This time it was permanent, so I had to dig a bit more and found your tutorial for calibration (had to digest NCS and Tool32, thanks you for that too! ) (to be fair I previously had to, to recode my SRS and disabling my side airbags, as one of my side impact sensors went bad... was fun too! )

No DSC isn't really a problem as most of the time, the first thing I do after starting the car is to deactivate it, but I got an inspection coming, so...

So I applied your method, but there was still a fault (read through Tool32/DCS_E46/ fs_lesen_kb90) coming up :
code 167 : Druck Sensor unplausibel.
Seeing there's a calibration for the pressure sensors (just above : drucksensor_dsc_abgleichen), I applied it but then the fault changed to
code 88 : Outlet valve rear right ('ABS Auslass Ventil hinten rechts' in Goethes Sprache)

That didn't make sense...

I read the values using the status_sensoren_lesen command, and all seemed okay-ish (-1.3 and -0.5 bar on each pressure sensors at idle... a bit low but the values didn't move, so I guessed it was ok (read around 80 bar when pressing on the brakes))
I also activated the valve through INPA. It worked, but the fault was still there...

I was kinda stuck there until I checked the Tool32/DSC_E46 commands list again and seen that there was one named 'abgleich_dsc_sensoren'.
Tried it, and voilà : no more faults!

In addition, I previously had the DSC coming on for like... no reason at all (exiting small speed bumps on dry road for instance), and it is now activating much later during hard cornering (as it should).
I guess 20 years of high Gs while speeding on roundabouts had put some strain on the sensors...

Thanks again!


Also, if I may, I'm now looking for a way to put my fuel tank gauge at a fixed value (broken sender card... the empty tank light has been on for more than 150 000km) but didn't find an easy way in NCS (I still also have to check if someone already documented a way to do so, and also have a reread of the NCS 'how to' maybe...)

[cushjbc]

I have similar symptoms to Z3C Tblau in post #879 so I attempted the use of Tool32 to calibrate my lateral acceleration sensor using 328 Power 04's tutorial pdf. I have a good INPA connection. Step 1 hangs up opening the DSC_E46.PRG file . . . I have a popup Results window with a Windows wait timer and no data. I am unable to proceed to step 2.

Apologies if this piggy back is a foul.

[328 Power 04]

Run Tool32 as administrator. It will work then.

[cushjbc]

Run Tool32 as administrator. It will work then.

Thank you for the quick response - I am one step closer running Tool32 as Administrator. I was able to open the DSC_E46.PRG file and see the list of jobs. Attempted step 2 but had a connection error. INPA is able to connect to the DSC . . .screenshots attached.

Tool32 Screenshot 2.jpgTool32 Screenshot 3.jpgINPA Screenshot.jpg

[LannVouivre]

Do you definitely have the right module selected? And that the module is plugged in, etc? Are you able to talk to any of the other modules? Are you going through the pacman port in the engine bay (can't remember if they still used them in the 2002 year models)?

Just going through a quick, general troubleshooting list.

[cushjbc]

The INPA screenshot in post #882 makes me believe it is a MK60 DSC. I am able to read/clear errors on the DSC using INPA (there were no errors). I seem to have full functionality using INPA but struggling to connect with Tool32. I am using the connector in the engine bay.

[LannVouivre]

Thank you for your patience with the simple questions. I'd expect to see it to indicate no communication if the wrong DSC module is selected etc. Can Tool32 communicate with any of the other modules? That could clear up whether Windows is being... Well, I can't word it nicely.

[cushjbc]

Can Tool32 communicate with any of the other modules?

Good question - I will make another attempt tomorrow to see about this.

[Z3C Tblau]

Use the DSC_MK60.prg file and you should be okay
Don't know if the available commands will be the same though...
Good luck!

[cushjbc]

Use the DSC_MK60.prg file and you should be okay

Thanks - makes sense and I'll give it a try.

[cushjbc]

I made another attempt re-calibrating my DSC lateral acceleration sensor this morning. I was able to verify a Tool32 connection with the DSC using DSC_MK60.PRG file and the fs_lessen job.

Tool32 DSC_MK60 fs_lessen.jpg

Step 3 of the instructions in "BMW Z3 (E36) Lateral Acceleration (aka Transverse Acceleration)Sensor Calibration with Tool32.pdf" calls for selecting job "login_dsc". This job is not in the list of DSC_MK60.PRG. I did not see a job that I thought was relative so I attempted step 4 of the instructions which calls for running "querbeschleunigungssensor_dsc_abgleichen". The job list in DSC_MK60.PRG has a slightly different title "querbeschleunigung_dsc_abgleichen". Skipping step 3 produced a predictable result:

Tool32 DSC_MK60 querbeschleunigung_dsc_abgleichen.jpg

I think Tool32 is successfully communicating with my DSC - just need to figure out a replacement for "login_dsc" in the DSC_MK60.PRG joblist. One step closer but still no success on re-calibration.

I used INPA to check DSC errors after this session - none were present.

[Z3C Tblau]

Cool preliminary results!
Try the 'diagnose_mode' just before '..._abgleichen' command, maybe putting a 'diagnose_weiter' between the two.
Don't forget to do 'diagnose_ende' before exiting.
I use these kind of commands at work on ECUs (SCR, diesel depollution using AdBlue) for accessing a different communication protocol (XCP / UDS). We usually have to cyclically (every 4 seconds max) send a 'diagnose_weiter' for the ECU to stay in 'diagnose mode'. So maybe be quick between opening diagnose mode and asking for the 'abgleichen'...
'Conditions not correct' is a dreaded ECU answer for me (at work) as it leaves many (undocumented ) possibilities open...
Please report and if it doesn't work give us also a snapshot (or two, the list looks long) of the other commands in the list.

[cushjbc]

I see the ECU logic you describe - will re-attack with coffee in the morning and report back.

[328 Power 04]

You should try the calibration even without the login, it's not always necessary. At worst it will just deny the calibration command.

[cushjbc]

You should try the calibration even without the login, it's not always necessary. At worst it will just deny the calibration command.

I thought the same - unsatisfactory results are posted in middle paragraph of post # 889

[328 Power 04]

I thought the same - unsatisfactory results are posted in middle paragraph of post # 889

Ah, well that answers that!

[cushjbc]

Ah, well that answers that!

Thank you for even looking at this - I wish I understood better what that middle screenshot results pane is telling us.

[cushjbc]

give us also a snapshot (or two, the list looks long) of the other commands in the list

4 screenshots to show the list of jobs available in the DSC_MK60.PRG file

Tool32 DSC_MK60.PRG Job List 1.jpg

Tool32 DSC_MK60.PRG Job List 2.jpg

Tool32 DSC_MK60.PRG Job List 3.jpg

Tool32 DSC_MK60.PRG Job List 4.jpg

[cushjbc]

Try the 'diagnose_mode' just before '..._abgleichen' command, maybe putting a 'diagnose_weiter' between the two.
Don't forget to do 'diagnose_ende' before exiting.

I just completed what was suggested by @Z3C TBlau above. There is definitely a time constraint in this sequence; may very well be 4". My first attempt was running 'diagnose_mode' followed by '..._abgliechen' job. This attempt failed. I cannot say if it failed because I was too slow in the sequence or for another reason.

My second attempt was running 'diagnose_mode', 'diagnose_weiter', then 'querbeschleunigung_dsc_abgleichen' as quickly as possible. Unfortunately, I could not take screenshots until the end. It looks like this worked:

Tool32 DSC_MK60 querbeschleunigung_dsc_abgleichen - OKAY.jpg

Taking this screenshot caused me to fail the 'diagnose_ende' job. I ran 'diagnose_mode' followed quickly by 'diagnose_ende' with success:

Tool32 DSC_MK60 diagnose_ende - OKAY.jpg

After all this, I ran 'fs_lessen' producing no errors. I also checked INPA for DSC errors before unplugging, starting the car and making sure DSC light did not illuminate. Last step is a test drive to find the limit of DSC activation. I know just the place to do this.

[Z3C Tblau]

Hope the result will last !
Should have asked you to run 'fs_lesen_detail', just to see if there was an indication of the error there.
Weird that there was none in the non-detailed 'fs_lesen' answer, but still giving a DSC light on...
Glad I could be of help

[cushjbc]

but still giving a DSC light on...

My DSC light was never on constant. My symptom started after I had to use the spare last summer to get a tire repaired in Louisville. Afterwards, the DSC activated way earlier than I was accustomed to in corners with speed (i.e. transitions from one freeway to another with no traffic - where this car likes to perform).

Thanks for your assistance. I like using this thread to investigate problems on our cars.

[Z3C Tblau]

Soooo... is it better now?
Might be confirmation bias, but I felt as if the car was more 'planted' (or less jittery if that makes sense) during a 400 miles trip this last weekend on small roads / freeway / highway mixed in equal portions

[328 Power 04]

If that sensor lost calibration on its own, it will do it again, and slowly it will fail and it will need to be replaced. It's not terribly hard. I've been there with that one.