Hello all!

I have a bit of an issue here.
I was helping out to swap a damaged E87 ECU to a second-hand unit.

Hardware is 1:1 as the previously installed and corresponds to EPC part number for this VIN.

All went well, VIN and PIN got rewritten with car data, and reloaded correct calibrations.
Re-synced immo data for ECU..
Next step is Config & Setup - and here is the problem!
ECU refuses to proceed.
As I understand, this could be related to power-class data stored from the previous vehicle - DID27 Engine Performance Identifier.
It was previously installed in a car with A17DTC (81kW) engine, and now is installed into car with A17DTS (96kW).
Owner states that it does fill more sluggish than before - so, maybe, this value does change something in how ECU performs with the engine.

Does anyone know how to solve this, beside reading ECU with flashtools and editing the data?

Maybe my sequence was incorrect?
I do not want to waste time on "Prepare to remove" procedure and then re-syncing ECU again, if this won't fix this..


Also, what's weird, there is no seed/key data in XML File..
I've also tried to adjust it to info from utility file, but it gave the same error and couldn't proceed further.
Both files attached here:
util.binXMLFile.xml

I have noticed just now, that there was "false" value for "Use security access"..

Does modifying XML to these values could resolve the issue?
like this:

<useSecurityAccess>True</useSecurityAccess>

<SecurityAlgoTableNo>01</SecurityAlgoTableNo>

<SecurityAlgoNo>17</SecurityAlgoNo>

5 hours ago, pupu14 said:

I have noticed just now, that there was "false" value for "Use security access"..

Does modifying XML to these values could resolve the issue?
like this:

<useSecurityAccess>True</useSecurityAccess>

<SecurityAlgoTableNo>01</SecurityAlgoTableNo>

<SecurityAlgoNo>17</SecurityAlgoNo>

Get both original and SH E87 VIN XML securityalgo and then see if it the same, if not, you can change them and to a ecu configuration in DPS

@Adelin good idea, XML p/n for donor VIN is different..

Security access from utility file is correct for this ECU, otherwise it would have not been programmed with correct cals.

I will try with original XML again, when owner comes back - because, although I have put correct algo inside it, I have not noticed that it was set as "false" too for security access at the time..

Maybe someone can make sense of the replies from ECU from this log?
I have tried applying original to donor ECU XMLfile - both with added security access and untouched one..
Still both get same error!

E87 config error.Txt

My understanding is that the ECM recognises the command but rejects the requested value as out of range or not permitted in its current state. It may be that DID 27 becomes locked after VIN/PIN programming or immobiliser synchronisation, and can only be changed when the ECU is virgin, reset, or placed into a “prepare to remove” state. (?)

I also checked the utility file. It contains the correct security algorithm and several RAM download and programming routines, but I could not find a specific alternative write routine for DID 27.

It will be good to confirm whether “Prepare to Remove” will unlock or reset DID 27, or whether this value must be edited directly in the flash/EEPROM?

Funny thing is, it wants to perform some sensor learn procedure during this setup stage (after writing XML data).. Which you cannot do, unless you have correct calibrations programmed and also without immo - because it requires to start the engine to learn the data...

It could be possible, that it is a "one shot" ECU programming, and requires a fully virgin ECU to work.

I have read a full dump from original and donor ECU, but it turned out that I cannot write full backup back to donor (limitations of the programmer app I have, apparently) - so even if someone could edit the data, I cannot load it back to donor..

I will try to perform reset procedure on it and try to config again...

I have performed "Prepare Control Module for Removal" function and it have not changed anything..

Guess, the only way is to write full backup from old ECU (aka 1:1 cloning)..
If anyone know how to do this remotely (via USB sharing over Web) - hit me up, I have both backup files. 😅

I have cloned eeprom+flash from original ECU. Now configuration procedure can be performed.
Case closed.

So, in summary - if you need to replace an E87 ecu - make sure it came from a vehicle with the same engine code/power rating.
Otherwise - need to use some 3rd party ECU flashing tools.