|
Hi,
I'm new to BMW coding, but have done some diagnostics and programming of keys and modules on other makes previously.
My older E90 has recently had a full DIY makeover; I have been collecting parts for some years now, and finally got it running with a year 2012 S65 M3 drivetrain and wiring harness, where I have swapped all modules from an M3 wreck into another base model body shell. My car is now driveable, but I am fixing some VIN mismatches since one seat, and DSC were crushed in the wreck and are bought second-hand from other vehicles to complete the parts from the wreck. One of the remaining tasks is programming of correct VIN in the DSC. (At this point I intend to run my car with all modules showing the VIN from the parts donor vehicle, I'm not attempting to update ALL modules to my body shell physical VIN at this point, perhaps in the future).
I've been using ProTool for about 2 days now. (The diagnostics license, not yet the Coding license). The advertising for ProTool is suggesting it could do most things, but perhaps not?
I have managed to change to matching VIN in the Roof module, and change to matching VIN in the driver seat module with the ProTool. I have used a $20 cable from China, and it has worked ok so far.
But I have noticed one surprising thing about my car, when I turn on the ignition it appears as if it doesn't wake up the DSC module and Park Assist Module. Only after I start the engine the scan tool can 'find' these modules. It seems to be an issue with my car, not with ProTool, as the same happens when I try a year 2012 version of INPA also.
(Key pushed in /ignition on = I can see 19 modules). (Start button ON, engine running, I can see 21 modules). I though I should be able to see the DSC just by pushing in the key in the key without engine running? Can someone confirm if this is normal, or a fault with my car? Do I need to enter any special programming mode to wake up all modules? (or is that one of the differences between a $20 cable and professional programming interface?)
The second hand DSC module still has a different VIN and is not operational due to the VIN difference. Anyway, when the car is running I can read live data and other parameters from it. However I can't manage to replace VIN in the DSC module by using ProTool. It says 'successful', but the VIN remains the same.
Today I have done electric trouble shooting of the wiring and fuses, to confirm all fuses etc are OK. There are 3 different power supplies to the DSC, two thick wires, and one small wire. I found that these are all powered with 12V at all times. (perhaps not when the entire car goes fully asleep) So my measurements today confirms the supplies to the DSC are working, and are alive even before the key is put into the slot. Therefore it looks like some 'wake-up' problem?
If anyone has ideas that would be helpful.
Today I have replaced a faulty front wheel speed sensor, so the errors from the DSC are now cleared, except for two errors for 'calibration of pressure sensors'.
My next attempt will be to try to write correct VIN with Tool32 or WinKFP to the module while the car is running? Not sure if its a good idea, but one of the next things I can think of.
The second-hand DSC shows the following data: Hardware: DSC_87, ZB# 7846816, software date 06.12.2011. It is same make 'ATE' as my original module, and came out of a LHD M3 in the US. (Mine is RHD, but shouldn't make a difference).
Cheers,
|