[browny23]

Hi so I've just bought a 330d e90 2006 and it has the abs and DSC warning lights on with a code which says the vin isn't correct.
I have used NCS expert to change it to the correct vin however when I used my mpps to read the ECU map it is saying the engine ECU has a different vin. But the car starts and drives and the CAS has the correct vin so can I use winkfp to change the engine ECU vin without it affecting the starting of the vehicle
please help

[dpaul]

Originally Posted by browny23

Hi so I've just bought a 330d e90 2006 and it has the abs and DSC warning lights on with a code which says the vin isn't correct.
I have used NCS expert to change it to the correct vin however when I used my mpps to read the ECU map it is saying the engine ECU has a different vin. But the car starts and drives and the CAS has the correct vin so can I use winkfp to change the engine ECU vin without it affecting the starting of the vehicle
please help

I have little experience with diesels but in general, VIN matching between CAS and DME (or DDE in your case) is not required for EWS alignment. Car will start regardless. In fact, VIN matching is not important for most (although not all) modules.

What exactly are the codes you read and how exactly did your read them?

You say you "have used NCS expert to change it to the correct vin"? Change it in which module?

[browny23]

So first I used NCS expert to change the vin in the DSC module as I thought it was wrong then when I read the ECU map with mpps I realised it's actually the ECU vin which is incorrect and needs changing to match the rest of the car

[dpaul]

Originally Posted by browny23

So first I used NCS expert to change the vin in the DSC module as I thought it was wrong then when I read the ECU map with mpps I realised it's actually the ECU vin which is incorrect and needs changing to match the rest of the car

And what are the exact codes that you read?

[browny23]

in the dsc ecu it says the vin is incorrect the vehicle has had a replacement engine ecu,cas and key so starts and drive but vin in engine doesn't match rest of vehicle

[dpaul]

I'm not asking for your interpretation of the errors. I'm asking what are the actual BMW error code numbers that INPA reports

[browny23]

I know you are but they are irrelevant as I know the vin number in the engine ECU is different to the rest of the car so all I'm asking is if I use ncsexpert to change the vin will it stop the vehicle starting or anything like that

[browny23]

I'm not with the car right now so can't get the exact codes pretty sure they are 5e40 5dd2 5e1f

[dpaul]

Originally Posted by browny23

I know you are but they are irrelevant as I know the vin number in the engine ECU is different to the rest of the car so all I'm asking is if I use ncsexpert to change the vin will it stop the vehicle starting or anything like that

I gave you the answer to that. And since you know my other questions are irrelevant, I guess you don't need any more help. Best of luck with your car

[browny23]

I apologize just getting a little stressed I do need your help

[browny23]

I am with the car and from doing the uif with inpa the CAS and engine ECU have the incorrect vin

[dpaul]

I find it pretty hard to follow your story so let me review it and you tell me if I’ve got it straight:

First: You bought a car that ran but with ABS/DSC warning lights on.

Second: Because you believed an error code (which you did not actually specify) was telling you that the DSC VIN number was not correct, you coded the original car VIN to the DSC using NCSExpert. You did this without actually checking to see what VIN was encoded to the DSC in the first place.

Third: Since that did not eliminate the ABS/DSC warning lights, you decided to check the DDE VIN numbers and found that it did not match the original car VIN. You didn’t read the CAS VIN initially but now believe that both CAS and DDE have the (same) incorrect VIN. On this basis, you believe that the CAS, DDE and presumably key were obtained from another car and installed in this vehicle before you bought it and that the DSC probably had the correct VIN in the first place.

Fourth: You believe that encoding the same VIN in DME and DSC should eliminate the ABS/DSC warning light. One way to do that is to change the DDE VIN to the original vehicle VIN. However, you are wondering if the vehicle will start if you do that.

Fifth: you are not sure, but you believe the error codes you obtained were 5e40 5dd2 5e1f.

If that is an accurate restatement of events, then;

Yes, you could code the original vehicle VIN to the DDE. That should eliminate the 5e1f code. It will not affect the ability to start because the DSC is not a part of the EWS system - that involves the DDE and CAS. In addition, VIN numbers are not part of the EWS system – identity is conferred by a 16 bit ISN stored in both modules in a part of memory you don’t have access to without special tools. As long as those match, your engine will start.

However, I doubt that VIN recoding will turn off the ABS/DSC warning lights. It is possible that you have a DSC hardware fault and that the DSC needs to be replaced. But maybe not; you may only need to recalibrate the steering angle sensor – that’s what 5e40 is about. Sometimes just turning the wheel lock to lock a few times will do this. Other times, you need to use software to accomplish it. I’d start with the lock-to-lock turns, then if needed default code the DSC with NCSExpert (no VIN change) and then if needed, use INPA to recalibrate the steering angle sensor.

Edit: another thing to watch out for is the presence of the "tamper dot" on the instrument cluster (KOMBI). If the CAS is replaced without clearing/resetting the EEPROM, the mileage mismatch between the KOMBI and CAS will set the tamper dot. In addition, if the replacement CAS mileage is higher than original, the KOMBI will adopt and display the higher value. Won't stop the car from running but will affect your ability to code the KOMBI and some functions may be affected. CAS will propagate the incorrect mileage to the key fob and the DME.

[browny23]

Yes all correct thank you and yeah the tamper dot is present however I used tool32 to write vin to DSC and do the steering angle calibration and this fixed the abs DSC light problem. So how can I get rid of the tamper dot.
Also after speaking with previous owner he told me it has had a second hand Dde CAS and key

[browny23]

Also the vin on the CAS is correct when read with ncsexpert but on the uif readout it shows the vin it originally came from or incorrect

[LMB335IS]

Originally Posted by dpaul

Edit: another thing to watch out for is the presence of the "tamper dot" on the instrument cluster (KOMBI). If the CAS is replaced without clearing/resetting the EEPROM, the mileage mismatch between the KOMBI and CAS will set the tamper dot. In addition, if the replacement CAS mileage is higher than original, the KOMBI will adopt and display the higher value. Won't stop the car from running but will affect your ability to code the KOMBI and some functions may be affected. CAS will propagate the incorrect mileage to the key fob and the DME.

One thing, mileage mismatch doesn't trigger the tamper dot, VIN mismatch does.

[browny23]

So can I change the vin in the CAS and DME using tool32

[dpaul]

The first VIN entry in the AIF of some DMEs cannot be changed with BMW standard tools although subsequent AIF slots can have new VINs encoded with NCSExpert, Tool32 or WinKFP. Apps like MHD (not relevant in your case) read the 1st entry. Don't know if it presents a problem in your case.

I think the same applies for CAS - which may explain why NCSExpert reports the "new" VIN and whatever other method you used to read it reported the "old" one.

I have only one experience with tamper dot issues which required virginizing the KOMBI to eliminate (using an external EEPROM programmer to zero out the mileage and FF out the VIN).

Perhaps LMB335IS can provide a more informed suggestion.

[browny23]

Thank you for your help