EWS 3.0 E46

[7shadow7]

Hello.
I have and BMW e46 3.0d with a faulty EWS (power failure - no cranck) - no starter. So I did copy mcu data from the old EWS to a new EWS (donor ews - same pcb - same nubmers)
Now with the new EWS installed the car cranks but wont start.
I checked with diagnostic - and got some errors with key code on one key - ews tempering and ews no communication.
Deleted Erorrs. Car still cranks but no start.
Tryed to SYNC dme and ews but fails everytime - with multiple tools.

Can someone offer any other sollution?

Thank you.

[okest]

If car cranks then key data is fortunately OK (unless you bypassed EWS with jumper).
Did you use AK90 to copy full binary? Did you get errors? I can see your new and old binary is not exactly the same. AK90 does not copy full MCU in my experience, it is better to manually modify existing new EWS DUMP instead.
If you gave me both EWS original dump (old and new) then i can patch new EWS with old info and you only need to sync{done this many times}. But maybe this new EWS is not OK anymore after this full write and you cant write back full ori anymore, if that is the case then you need a new EWS. See if you can write back full original to new EWS and compare/verify with hex editor if it really is OK.
You do not need same code EWS3, needs to be EWS3.3 and good if its from same transmission.

[7shadow7]

If car cranks then key data is fortunately OK (unless you bypassed EWS with jumper).
Did you use AK90 to copy full binary? Did you get errors? I can see your new and old binary is not exactly the same. AK90 does not copy full MCU in my experience, it is better to manually modify existing new EWS DUMP instead.
If you gave me both EWS original dump (old and new) then i can patch new EWS with old info and you only need to sync{done this many times}. But maybe this new EWS is not OK anymore after this full write and you cant write back full ori anymore, if that is the case then you need a new EWS. See if you can write back full original to new EWS and compare/verify with hex editor if it really is OK.
You do not need same code EWS3, needs to be EWS3.3 and good if its from same transmission.

I did copy it with AK90 - I added new key to the new ews - i tought it may help but did not - so this is maybe the diff. you see? I dont know.
Here is the original dump of the new EWS i used to copy data from the old one.

[okest]

Try writing this dump in new EWS and verify if its written properly (reread and compare). If written OK then should work.
Then you need to DDE/DME-EWS sync with DIS/INPA/ISTA.
Also give feedback and if worked then thx/rep please.

[7shadow7]

I read out your file with ak90 and it has wrong km and wrong VIN number (you left the data from the donor ews not original) - and there are no keys stored.

[okest]

You do not need correct vin for engine start. You can try to rewrite vin later if you want. Keys are there but not all, only the ones currently in use and the new one you made. You can copy other as well if you want.
Why not try?

[7shadow7]

Nope, it wont even cranck now...

[okest]

The reason why it is not cranking is because your new EWS is coded for automatic transmission(Looking for park signal) but your car is manual, i checked both vin. You have to change the coding in EWS module, if you have pasoft 1.4 its good for that for example or use ncs. Or you can give +12V for the ews pin 6 for testing.

[7shadow7]

Nope, it wont even cranck now...

Solved.
Copied again old data to new EWS.
Cranck no start.
Reset EWS, reset DME - sync. ews-dme.
Car starts.

Even i did align before the car did not start - reset was needed for both ews and dme - then sync.
That is what i was doing wrong.