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

[328 Power 04]

So for your exhaust side, it's requesing a crankshaft degree position of -105, and it gets a reading of -79.88. That number needs to be closer to -105.
Not sure who is to blame yet.

Do those exhaust and intake values change accordingly with more rpm?

[mcassict]

I don’t know that it matters but I am hooked up through the 16 pin under the dash so that I can actuate the throttle. At idle it is running 775-790....ramping it up to 2500 i see absolutely nothing changing to any of the analog values in the VANOS. Everything remains just is in the previous screen pics.


Sent from my iPhone using Tapatalk

[mcassict]

Well after letting the car sit all night I thought I’d take it for another spin cold just to see how she ran cooled back down. She ran great. So whatever this issue is that is causing it run rough and bog down is only after it has gotten warm. I drove about 4 miles and it never did it. Also, I drove it with the laptop hooked up so that I could see if there were any other changes to the VANOS readings. Nothing changed there. Never saw even the slightest fluctuations.


Sent from my iPhone using Tapatalk

[328 Power 04]

Those values should change, especially while driving. Dual VANOS is quite active.

Even aged VANOS plunger seals wouldn't cause zero movement.

[mcassict]

Any ideas why then why we would be getting static results?


Sent from my iPhone using Tapatalk

[328 Power 04]

How sure are you that the camshaft position sensors are working?

[mcassict]

Honestly, I can't be sure at this point if the camshaft sensors are working properly or not. I will probably try and take them out and see if I can bench test those tomorrow night and see if I can eliminate them as a primary cause. I have had a couple of interesting developments today though in two of these mysteries.

1) Regarding the EWS issue I was having that you helped me resolve, it happened again today (Good thing I had the laptop with me...LOL). If you remember, I had a theory that it may have happened when my son forced the key a couple of times on our first trip out. Today may have proved that theory wrong. We took it out again today to test drive and to give him another opportunity to practice driving the a stick. He went to turn into a parking stall and when he brought the car to a stop, he forgot to push in the clutch. Thats when the "stall" happened. He turned the car off and then a few minutes later I went to start it again, and nothing.....EWS. Reset it with INPA and good to go. Talking about it with him though, he is 100% sure that when it happened the first time, he had done the same thing, brought the car to a stop in gear without the clutch depressed. Now I can't imagine why it would be doing it under that situation but I can't imagine that it is supposed to. That may be something else worth researching a bit.

2) Concerning the rough engine and bogging down, it drove like a charm today, at least for most of the day. I drove it about 8 miles this morning, never getting on the highway and just keeping it to regular city driving. Drove it again a little later about the same conditions and she ran great. Then the 3rd time I drove it, everything was the same except I did hop on the highway for about a quarter mile. About half a mile after I exited the highway, she began to misfire and bog. I drove it about 2 miles more to my destination like that, shut it down, went into a meeting for about 10-15 minutes, came back out and started her up and took off. She ran great again from that point on for the next 10 miles or so. I made one more stop after that and shut her off for about 15 minutes. Drove about 4 miles on city streets, and then it bogged down again. Drove it like that for another 3-4 miles to the next destination and then that is when the EWS activated. After resetting that she drove great again. So the best I can tell, it seems to me that the bogging down and misfire, must have something to do with 1) Temperature OR 2) RPM. Whatever it is, the issue clears up after shutting the car off and letting it sit for even just a few minutes.

[328 Power 04]

I hope you got that car for cheap?

Because fixing it correctly will take some work and investigation. EWS and DME falling out of sync can be either an issue with the ews module, the DME, or the wiring between them.
I can easily make you another dme (from used).. ews is just a little bit harder. It would really depend on which module didn't update its rolling code.


And then we still can't know if the VANOS issues come from sensors, the vanos actuators, or the dme itself.

DME failure for MS42 is very rare, but since you just got the car, anything could have happened. Shorts, mice, corrosion, etc.

- - - Updated - - -

I would make a new thread in the Z3 section here to document everything, instead of in this thread.

[mcassict]

Well it’s a good thing I’m patient, love to learn, and love to fix things then I suppose. As far as cheap enough, won’t know until we are done I suppose. Other than the issues mentioned, the car looks in great shape. Has 158,000 miles which I don’t think is bad for a 20 year old car. Picked it up for $3800. One way or another it will be fun to fix and drive....


Sent from my iPhone using Tapatalk

[Z3nki]

Im having some trouble coding with ncsexpert so ive decided to reinstall the softwares per instructions in post #1, but when I get to the the end dos (command prompt) window, I get a bunch of failed or warning values. Whats going on here? Running windows 10. thanks

inpa install error.jpg

[328 Power 04]

Run the registry file (".reg" file) included.

[Z3nki]

Thank You. Its embarrassing how easy that was, but my previous coding issues are still present.

Car is a 96 z3. Im changing out the zvm with a used, presumably already coded, one. Following the instructions for a single module replacement, everything is fine till i actually execute the SG_Codieren job on the ZVM. Then it just gives me an "error changing ZCS" message with this long error log:

[12:40:36.814] [2019-05-07] [SERIE] 2020 Error LFCDHDIA.CPP (A_KMB36.IPS/IPO) CDHapiResultText 1
[12:40:36.814] [2019-05-07] [SERIE] SG antwortet nicht IFH-0009: SG nicht angeschlossen oder meldet sich nicht C_KMB


[12:40:36.918] [2019-05-07] [SERIE] 2020 Error COAPI2.CPP coapiRunCabd 6
[12:40:36.918] [2019-05-07] [SERIE] SG antwortet nicht ZCS_LESEN


[12:40:36.921] [2019-05-07] [SERIE] 2020 Error COAPI.CPP coapiReadZcs 4
[12:40:36.921] [2019-05-07] [SERIE] SG antwortet nicht ZCS_LESEN: A_KMB36


[12:40:36.941] [2019-05-07] [SERIE] 2000 Error LFCDHDIA.CPP (A_KMB361.IPS/IPO) CDHapiResultText 1
[12:40:36.941] [2019-05-07] [SERIE] Fehler in EDIABAS oder in SG-Beschreibungsdatei IFH-0006: Interface akzeptiert nicht das Kommando C_KMB36


[12:40:37.048] [2019-05-07] [SERIE] 2000 Error COAPI2.CPP coapiRunCabd 6
[12:40:37.048] [2019-05-07] [SERIE] Fehler in EDIABAS oder in SG-Beschreibungsdatei ZCS_LESEN


[12:40:37.051] [2019-05-07] [SERIE] 2000 Error COAPI.CPP coapiReadZcs 4
[12:40:37.051] [2019-05-07] [SERIE] Fehler in EDIABAS oder in SG-Beschreibungsdatei ZCS_LESEN: A_KMB361


[12:40:37.386] [2019-05-07] [SERIE] 2020 Error COAPI2.CPP coapiRunCabd 6
[12:40:37.386] [2019-05-07] [SERIE] SG antwortet nicht ZCS_LESEN


[12:40:37.388] [2019-05-07] [SERIE] 2020 Error COAPI.CPP coapiReadZcs 4
[12:40:37.388] [2019-05-07] [SERIE] SG antwortet nicht ZCS_LESEN: A_EWS


[12:40:37.390] [2019-05-07] [SERIE] 1000 Warning COAPI.CPP coapiReadFgNr 9
[12:40:37.390] [2019-05-07] [SERIE] Fehler EWS


================================================== ==============================(1)
[12:40:51.307] [2019-05-07] [SERIE] 2000 Error LFCDHDIA.CPP (A_ZVM.IPS/IPO) CDHapiResultText 1
[12:40:51.307] [2019-05-07] [SERIE] Fehler in EDIABAS oder in SG-Beschreibungsdatei IFH-0006: Interface akzeptiert nicht das Kommando C_ZVM36


[12:40:51.412] [2019-05-07] [SERIE] 2000 Error COAPI2.CPP coapiRunCabd 6
[12:40:51.412] [2019-05-07] [SERIE] Fehler in EDIABAS oder in SG-Beschreibungsdatei CODIERINDEX_LESEN


[12:40:51.413] [2019-05-07] [SERIE] 2000 Error COAPI.CPP coapiReadCodierIndexFromSg 5
[12:40:51.413] [2019-05-07] [SERIE] Fehler in EDIABAS oder in SG-Beschreibungsdatei CODIERINDEX_LESEN: A_ZVM


[12:40:51.415] [2019-05-07] [SERIE] 2000 Error COAPI.CPP coapiChangeZcs 5
[12:40:51.415] [2019-05-07] [SERIE] Fehler in EDIABAS oder in SG-Beschreibungsdatei


I take it I have a file issue? Also I can not write the vin (FGNR_Scheiben) on the zvm because it doesn't show up as a listed job for that module...

[BillMRoadster]

Hopes this post works, I'm new to this forum. I have a 2000 BMW Roadster. I am trying to get INPA to work. I bought a cable that one member on this forum used successfully from Amazon "LZLRUN INPA K+CAN K+DCAN Car Diagnostic Tool Cable" along with a "20 pin to 16 pin cable". The cable has the FT232RL chip. I downloaded the software from this forum and performed the installation. I can connect to the engine modules with the odb connection inside the car. I can only connect to the airbag module when connected to the 20 pin cable. I get "inpa IFH-0009 no reponse from controlunit" when trying to connect to other modules. I checked that the com port matches both in the odb.ini and in the device manager, also set parameter to "1 ms". I read various posts about soldering different pins together but from other posts I believe my car is exempt from this due to the year. I appreciate any help.

[328 Power 04]

Hopes this post works, I'm new to this forum. I have a 2000 BMW Roadster. I am trying to get INPA to work. I bought a cable that one member on this forum used successfully from Amazon "LZLRUN INPA K+CAN K+DCAN Car Diagnostic Tool Cable" along with a "20 pin to 16 pin cable". The cable has the FT232RL chip. I downloaded the software from this forum and performed the installation. I can connect to the engine modules with the odb connection inside the car. I can only connect to the airbag module when connected to the 20 pin cable. I get "inpa IFH-0009 no reponse from controlunit" when trying to connect to other modules. I checked that the com port matches both in the odb.ini and in the device manager, also set parameter to "1 ms". I read various posts about soldering different pins together but from other posts I believe my car is exempt from this due to the year. I appreciate any help.

What other modules are you trying to diagnose?
It is normal that only engine is reachable via OBD port.

ABS/ASC needs a special interface called ADS for your specific car, as well as the instrument cluster.
Others, such as EWS, airbag, and general body module should work fine via 20-pin port and K+DCAN cable.

No soldering needed for when you use the 20-pin port.

- - - Updated - - -

Thank You. Its embarrassing how easy that was, but my previous coding issues are still present.

Car is a 96 z3. Im changing out the zvm with a used, presumably already coded, one. Following the instructions for a single module replacement, everything is fine till i actually execute the SG_Codieren job on the ZVM. Then it just gives me an "error changing ZCS" message with this long error log:


================================================== ==============================(1)
[12:40:51.307] [2019-05-07] [SERIE] 2000 Error LFCDHDIA.CPP (A_ZVM.IPS/IPO) CDHapiResultText 1
[12:40:51.307] [2019-05-07] [SERIE] Fehler in EDIABAS oder in SG-Beschreibungsdatei IFH-0006: Interface akzeptiert nicht das Kommando C_ZVM36


[12:40:51.412] [2019-05-07] [SERIE] 2000 Error COAPI2.CPP coapiRunCabd 6
[12:40:51.412] [2019-05-07] [SERIE] Fehler in EDIABAS oder in SG-Beschreibungsdatei CODIERINDEX_LESEN


[12:40:51.413] [2019-05-07] [SERIE] 2000 Error COAPI.CPP coapiReadCodierIndexFromSg 5
[12:40:51.413] [2019-05-07] [SERIE] Fehler in EDIABAS oder in SG-Beschreibungsdatei CODIERINDEX_LESEN: A_ZVM


[12:40:51.415] [2019-05-07] [SERIE] 2000 Error COAPI.CPP coapiChangeZcs 5
[12:40:51.415] [2019-05-07] [SERIE] Fehler in EDIABAS oder in SG-Beschreibungsdatei


I take it I have a file issue? Also I can not write the vin (FGNR_Scheiben) on the zvm because it doesn't show up as a listed job for that module...

I am not sure exactly what may be going on..

Does that module diagnose fine with INPA? I don't have any cars with ZVM modules to test if it needs ADS connectivity or not.

There is no need to try writing the vin.
If module comes from exact same car setup, it wouldn't even need coding.

[BillMRoadster]

Thanks for the quick response

Examples
Engine is not on , key in position II, using 20 pin connector


Engine


MS 41.0 for M52
MS 41.0 for M52 US with ODBII
MS 41.0 for M52 NEW


All three do not work for the 20 pin - IFH-0009 errors
One of them worked on the 16 pin
Do you use different options depending on 20 or 16 pin?







Body


Airbag -This works
Seat occupation detection - Several IFH-0009 errors No reponse from controller
On board computer BC5 - IFH-0006 command not accepted
On board computer / clock UHR/BC E36/7 - IFH-0006 Command not accepted
Anti-theft alarm system DWA4 - "DWA4 not found"
Convertible soft top module IFH-006 Command not accepted
EWS - This works
Automatic air conditioning IHKA - IFH-0009
Air conditioning IHKR - IFH-0006 Command not accepted
Instrument cluster - Needs ADS?
Cruise control GR2 - IFH - 0009 Cruise control need to be on
Thermal Oil Level Sensor - TOENS IFN-0009
Roll over sensor - Many IFH-0009 errors - some of the menu comes up but constant IFH-0009 errors
Central body electronics ZKE4 - IFH-0009 errors
Central locking module ZV36 - IFH-0006 Command not accepted


At the moment, I would like to get the auto bleed to work. Can you point me to the ADS info?
Your help is much appreciated.

[328 Power 04]

Make sure you have the OBD port cap in place when you try to diag engine module at 20-pin port.
Your engine ecu is MS41 for M52 US with OBDII (shared with the S52).

Most of the other modules you listed under body are not equipped on Z3s, so you will not get a response back.

There is the TinyADS module.. but it requires a true serial port on a Windows laptop with x86 (32-bit) windows. It's a bit of a hassle. I would try to pressure bleed it a few times before going through the task of getting ADS to work correctly.

It will always be easier to find someone with an ICOM interface (the dealer's interface) and proper setup, if it's just for bleeding brakes.

ICOMs are available to buy.. most that you will search and find will be Chinese clones of very variable quality. They connect to laptop via Ethernet cable and there are no requirements for Windows version.

[Z3nki]

I am not sure exactly what may be going on..

Does that module diagnose fine with INPA? I don't have any cars with ZVM modules to test if it needs ADS connectivity or not.

No actually. Through INPA, I can connect and read engine, ews, abs, and airbags fine. But when i try to connect to the zv36 I just get a "Variant Checking" error:

IFH-0006 COMMAND NOT ACCEPTED. Program will be stopped!

There is no need to try writing the vin.
If module comes from exact same car setup, it wouldn't even need coding.

Thats what I thought, so I made sure to do that. Seller even provided donor car vin to verify. Only difference is donor car was auto, and mine is manual. Didn't think it'd make a difference. Weird thing is, car wont even start with new/used zvm plugged in. Hence why i thought it needed coding.

On top of that mess, I cant even check my original ZVM b/c its shorting out my 20 pin DLC, hence why I thought it needed changing

[BillMRoadster]

Was not aware that I needed the ODB cap on when using the 20 pin so that was one of my issues (Thanks). I made sure that the OBD cap was on and I still have the problem. My problem may be with the 16 to 20 pin connector. The 20 pin connector does not have the 17 pin wired to the 20 pin.

I read in this forum.... One of the late night sessions at ZFest last weekend was configuring a recalcitrant INPA installation. We finally traced the issue to the 16-20 pin adapter. I finally got a chance to look at the "bad" adapter. Turns out TxD2 isn't wired up at all. Since this particular installation was from an eastern European country, I'm guessing they used an adapter that didn't take the US-centric TxD2 line into consideration. So if you have an installation that gives an error 0009 with the 20pin, but connects to the DME okay with the 16 pin, open the adapter and bridge pin 17 to 20.

Tried to solder the connector and things didn't go well. I melted the plastic connector while soldering and the pins moved a little and did not match up well to the port on the car. I have ordered another 16 to 20 pin connector from another vendor hoping that resolves the issue.

If I get this working, might move on to trying TinyADS. I current have an old PC Windows 7 32 bit laptop with a serial port that is dedicated to car maintenance.

I pressure bled my brakes after installing new pads and rotors but not getting the "bite" on the brakes it once had so I wanted to try the assisted bleeding with the software although the pedal is firm. No emergency, my M is a third car rarely driven the last 18 years.

Looked a little bit at ICOM - will look at it more later. In general, what do you consider to be the best overall diagnostic tool for the 2000 M Roadster - INPA, INPA with TinyADS, ICOM, or all three? Will post if the new connector fixes issue. Thanks again.

[BillMRoadster]

Received the replacement 16/20 pin cable. It also did not have pin 17 bridged to 20. Cable description said it was compatible with my car. Soldered the connection and used a heat sink on the pin this time and did not burn up the plastic connector. The new cable worked. On the 20 pin, I can now get MS 41.0 for M52 US with ODBII , ASC5, EWS, Airbag and that's about it. Would getting TinyADS working give me all the available diagnostics for my car or my car just does not have the intelligence for much more info. Would ICON give me more than TinyADS? Much Thanks.

[328 Power 04]

I would only get an ICOM if you have multiple BMWs you plan to diagnose. It works on all BMWs from 1986 to 2020+. No need for old Windows or serial ports. Just an ethernet port.

Yes TinyADS is able to communicate to all available modules in cars from ~2001 and older. It's just slightly inconvenient when it comes to needing a true serial port and 32-bit windows.
Since I got my ICOM, the TinyADS just collects dust.


If you can already communicate with your ASC5 via the USB cable with adapter, then you already have most of what you need. You just can't talk to instrument cluter... which isn't a great loss, as there isn't much a casual home tinkerer can do.

[BillMRoadster]

Thanks for the info. Changed out the seat bushings last week and was able to use INPA to reset the airbag light... nice. Thanks again for all your help.

[Z3nki]

Hmm, Ive pulled out my old dell d630 laptop with win xp sp3 and a native serial port to try with a tinyads cable, but not sure im installing inpa correctly.
After running the inpa install via ads bundle on pg. 7, i get this message after everything loads:

20190602_144526.jpg

Then If I try to open inpa, i just get "cannot find API.DLL" twice, then a "cant run 16 bit windows program: cannot find file c:\inpa\bin\inpaload.exe"...

Im assuming i have some file paths incorrect? thanks

[solimans]

Abel, not sure if I ever thanked you...got an old laptop working with inpa...

Sure it will come in handy as I work through this car. Baby steps


Sent from my iPhone using Tapatalk

[328 Power 04]

Hmm, Ive pulled out my old dell d630 laptop with win xp sp3 and a native serial port to try with a tinyads cable, but not sure im installing inpa correctly.
After running the inpa install via ads bundle on pg. 7, i get this message after everything loads:

20190602_144526.jpg

Then If I try to open inpa, i just get "cannot find API.DLL" twice, then a "cant run 16 bit windows program: cannot find file c:\inpa\bin\inpaload.exe"...

Im assuming i have some file paths incorrect? thanks

Since this is on XP, you need to add that path to the windows system environment variables. I touched briefly on this in the installation pdf on the first page.

[Z3nki]

Since this is on XP, you need to add that path to the windows system environment variables. I touched briefly on this in the installation pdf on the first page.

Yes, I see that now, thank you. INPA installs fine now and opens, just looks a little different than the obd cable version on my win 10 comp (doesnt have an e36 quick key). Ill try connecting to the car later, until then, i noticed a few things after install.

1.) when I run the ADSsetup as admin, nothing happens, screen just blinks for a hot second, but no program window or confirmation. is that right?

2.) under the c:ediabas\bin folder, I see the ediabas text file. It says ADS under interface, but under default, it says EDIC instead of STD:OBD. Should I change to STD:OBD or is that indication that something went wrong with the install?

3.) Also, under c:\ediabas\bin I dont see the OBD.ini file at all, only the .dll files

Sorry for all the questions