E92 2009 M3 w/ Mods Unable to Read Using NCSExpert or INPA

[S1RC]

I was trying to read and feature code a friends 2009 E92 M3 (Production date of the car is 2009-01-28) last week for his LCI tail light conversion but was unable to even read the car using NCSExpert or INPA. Using the same coding setup I have no issues reading and coding other cars, including my own 2008 E92 M3.

His car has a lot of mods done to it, almost anything I can think of, but there are a few that I know would interact with the ECU's. His BMW Performance Steering Wheel I know taps into some of the cables the ODB connector uses (from the DIY's I looked up), and his ESS Supercharger tune would probably have been done over ODB. Can either of these be preventing from even reading the car? NCSExpert reports a faulty VIN (I've attached the error.log below), INPA reports On and Ignition On, but when trying to read the error codes I get "Data Transmission to Interface Disturbed".

I've tried reading the car with 50.2 (30.04.2013) and 51.2 (03.07.2013). I've read & coded many cars older and newer than his without issue.

[12:20:41.673] [2015-05-01] [SERIE]   2000       Error LFCDHDIA.CPP (A_PL2FRX.IPS/IPO) CDHapiResultText     1
[12:20:41.673] [2015-05-01] [SERIE]      Fehler in EDIABAS oder in SG-Beschreibungsdatei  IFH-0003: Datenuebertragung HOST/Interface gestoert  FRM_87

[12:20:41.780] [2015-05-01] [SERIE]   2000       Error    COAPI2.CPP    coapiRunCabd     6
[12:20:41.780] [2015-05-01] [SERIE]      Fehler in EDIABAS oder in SG-Beschreibungsdatei  FA_READ

[12:20:41.782] [2015-05-01] [SERIE]   2000       Error    COAPI4.CPP coapiReadAuftrag     4
[12:20:41.782] [2015-05-01] [SERIE]      Fehler in EDIABAS oder in SG-Beschreibungsdatei  FA_READ: A_PL2FRX

[12:20:41.869] [2015-05-01] [SERIE]   2000       Error LFCDHDIA.CPP (A_PL2FRX.IPS/IPO) CDHapiResultText     1
[12:20:41.869] [2015-05-01] [SERIE]      Fehler in EDIABAS oder in SG-Beschreibungsdatei  IFH-0003: Datenuebertragung HOST/Interface gestoert  FRM_87

[12:20:41.978] [2015-05-01] [SERIE]   2000       Error    COAPI2.CPP    coapiRunCabd     6
[12:20:41.978] [2015-05-01] [SERIE]      Fehler in EDIABAS oder in SG-Beschreibungsdatei  FA_READ

[12:20:41.980] [2015-05-01] [SERIE]   2000       Error    COAPI4.CPP coapiReadAuftrag     4
[12:20:41.980] [2015-05-01] [SERIE]      Fehler in EDIABAS oder in SG-Beschreibungsdatei  FA_READ: A_PL2FRX

[12:20:42.062] [2015-05-01] [SERIE]   2000       Error LFCDHDIA.CPP (A_E65CAS.IPS/IPO) CDHapiResultText     1
[12:20:42.062] [2015-05-01] [SERIE]      Fehler in EDIABAS oder in SG-Beschreibungsdatei  IFH-0003: Datenuebertragung HOST/Interface gestoert  CAS

[12:20:42.169] [2015-05-01] [SERIE]   2000       Error    COAPI2.CPP    coapiRunCabd     6
[12:20:42.169] [2015-05-01] [SERIE]      Fehler in EDIABAS oder in SG-Beschreibungsdatei  FA_READ

[12:20:42.172] [2015-05-01] [SERIE]   2000       Error    COAPI4.CPP coapiReadAuftrag     4
[12:20:42.172] [2015-05-01] [SERIE]      Fehler in EDIABAS oder in SG-Beschreibungsdatei  FA_READ: A_E65CAS

[12:20:42.173] [2015-05-01] [SERIE]   1000     Warning     COAPI.CPP   coapiReadFgNr     9
[12:20:42.173] [2015-05-01] [SERIE]      Fehler  CAS

================================================================================(2)
[12:20:42.286] [2015-05-01] [SERIE]   2000       Error LFCDHDIA.CPP (A_E65CAS.IPS/IPO) CDHapiResultText     1
[12:20:42.286] [2015-05-01] [SERIE]      Fehler in EDIABAS oder in SG-Beschreibungsdatei  IFH-0003: Datenuebertragung HOST/Interface gestoert  CAS

[12:20:42.397] [2015-05-01] [SERIE]   2000       Error    COAPI2.CPP    coapiRunCabd     6
[12:20:42.397] [2015-05-01] [SERIE]      Fehler in EDIABAS oder in SG-Beschreibungsdatei  FGNR_LESEN

[12:20:42.401] [2015-05-01] [SERIE]   2000       Error     COAPI.CPP   coapiReadFgNr    12
[12:20:42.401] [2015-05-01] [SERIE]      Fehler in EDIABAS oder in SG-Beschreibungsdatei  FGNR_LESEN: A_E65CAS

================================================================================(2)

[wildcatcrazy]

I've seen some flash tunes cause issues, especially if it was done with a flash tablet.

[S1RC]

I contacted ESS about the ECU flash for the supercharger, you might be right. This was the response:

"Yes, the ECU is read locked on the portion that contains our software. You do no need to access this for anything else than engine calibrations which should not be touched at all. "

[wildcatcrazy]

Originally Posted by S1RC

I contacted ESS about the ECU flash for the supercharger, you might be right. This was the response:

"Yes, the ECU is read locked on the portion that contains our software. You do no need to access this for anything else than engine calibrations which should not be touched at all. "

Their response is referring to the DME, which should have nothing to do with what you're trying to accomplish. But, I still think flashes from tablets interfere with normal ECUs when it comes to coding.

[JerryK73]

Did he change the head unit? If he did that would likely be the cause.

[wildcatcrazy]

Originally Posted by JerryK73

Did he change the head unit? If he did that would likely be the cause.

Changing the HU would have no effect on coding the FRM (or others for that matter). The only problem you'd run into with a changed HU is the SOS error on the cluster/idrive.

[Scrippy]

Originally Posted by wildcatcrazy

Changing the HU would have no effect on coding the FRM (or others for that matter). The only problem you'd run into with a changed HU is the SOS error on the cluster/idrive.

The SOS can be dealt with if you use WinKFP to update the used HU and put your current VIN in. I purchased a used professional HU and my SOS was always in error. Being the obsessive compulsive I am, the service triangle had to go. I updated the head unit. I believe it was actually 2 modules. My SOS went away and my stereo sound seemed to improve too. I would do an SG-Coderein from NCSExpert after all updates are done. Then your ECU is up to date and using default values per your VO.