View Single Post
      09-19-2019, 07:41 PM   #660
Radekxpl
The General
55
Rep
124
Posts

Drives: F15 X5 35D & E46 M3
Join Date: Jan 2018
Location: USA

iTrader: (0)

Quote:
Originally Posted by Mr.47 View Post
I had a hard time trying to figure out how the hell to code this damn brakes, however after a few hours of youtube videos and sifting thru post after post, I finally figured it out and wanted to write a comprehensive coding in ESYS 3.27.1 since there isn't any pertaining to our F15 X5 M sport brake coding.

Disclaimer: I'm not responsible for any damages, injuries or death following this steps...I'm hardly an novice and more of an imbecile when it comes to coding BMW...so if your unsure on following these steps seek an expert coder for assistance.


Pre-step, Make sure your car is hooked up to an battery charger with at least 14V to prevent vehicle from going into sleep mode. Leave keys in the vehicle, and hit start button without starting engine (no foot on brakes) and connect OBD to your computer/laptop with ESYS

1. Start connection click on the Icon that is highlighted in red




2.Select F025 and click connect this is F15 X5 F16 X6 specific, this may take a moment (WHATEVER YOU DO NOT SELECT DIRECT)



3. Click read then save



4. Save it securely, you may choose any name for our example we'll use "feb 26 fa 3"



5. After saving click EDIT and it should automatically take you to FA-Editor




6. Expand all the folders and find HO-WORT, Right Click, select NEW and click on HO-WORT



8. You'll be prompted with a small text box within the drop down folders, type in SBRE and hit enter. (SBRE is for F15 M sport brake code)



9. Right click on the FA folder, then click on calculate FP



10. It should populate the vehicle profile with no error message...now if your ESYS is working properly it should show "Aftermarket Addon", in our case its folder 8, expand folder 8 and it should be another folder with 2376, which is 18in sportbrake for F15, this confirms that file is coded and ready to be written on vehicle. Besure to click the save disk (highlighted in red) to save it.




11. Look over to the left tab and click on "Expert Mode" then click on VCM and you should see a screen like this.



12. Next look down and find for vehicle order section, select file tab and click the |...| box (highlighted in red) to load the file that we saved on the FA editor. In our case the feb 26 fa 3.xml




13 Expand the FA files and find the HO-WORT to verify the SBRE is added



14. Right click on FA and click on calculate FP this should populate the Vehicle profile section with folders



15. In the Vehicle profile expand folder 8 and verify that 2376 is present (highlighted in green box), then click on the Master tab (highlighted orange box) and click on Write FA FP (highlighted red box) if all goes right there shouldn't be any errors popping up.



16.On the left tab click on expert mode thencoding (highlighted in orange), after if opens, click on Read and save, name the file diffrentely for our example i added coded in the end of file name, feel free to name it whatever you want.




17. After Read and Save, expand all the files and find Ho-wort and look for SBRE and in vehicle profile look for folder 8 and subfolder 2376 this means is has been written into the car but we still have to code into the module for it to be completed.



18. Now we need to code the new HO-WORT into the appropriate Module, click on the Read ECU (highlighted in red) and SAVE a copy.




19. In the SVT section, find DSC2 right click and select Code...this will take 1-5 mins and you'll see an ABS Warning message that will pop up for a second and disappear as it should resolve on its on (ESYS will erase the fault code automatically) it should not reappear.



20. If you did it all correctly you should have no errors and you'll get a abgeschlossen bearbeitung (process completed) dialog and a close button. (didn't get the image of it). Click close and another popup will appear and will ask you to save a text on what it did, it's up to you if you want to save it or not doesn't hurt either ways.

21. Click disconnect and your done. You now have successfully coded M Sport brake on your X5




I haven't driven it yet so I'll find out this afternoon on how it goes, it is super late lol its 0500 as of now time for some ZzZzZzZz
Hey, I'm trying to code these brakes and I have run into some trouble at the very last set to code DSC module process gets started by at the end I get this message:

Caf's suchen
Tal wird generiert
Abarbeitung wird gestartet

TAL execution started.
ExecutionID=2019/09/19-19:35:27.011
[] prepareTALExecution started
[] prepareTALExecution finished
[] prepareVehicleForCoding started
[] prepareVehicleForCoding finished
[DSC2 - 29] prepareECUforCoding started
[DSC2 - 29] prepareECUforCoding finished
[DSC2 - 29] authenticateECUforCoding started
[DSC2 - 29] authenticateECUforCoding finished
[DSC2 - 29 - cafd_00000c18-016_052_001] Transaction type: cdDeploy; Message: TA started
[DSC2 - 29 - cafd_00000c18-016_052_001] Transaction type: cdDeploy; Message: TA finished
[DSC2 - 29] finalizeECUCoding started
[DSC2 - 29] finalizeECUCoding finished
[] finalizeVehicleCoding started
[] finalizeVehicleCoding finished
[] finalizeTALExecution started
[] finalizeTALExecution finished
TAL execution finished
TAL-Execution finished with status: "Finished". [C207]
TAL execution finished. Duration: "19s". [C206]
MSM update: Read current SVT. [C194]
MSM update started. [C215]
MCDDiagService<id=378649, job=com.bmw.psdz.jobs.uds.MCD3_ReadF11DataFromMSM, service=RC_GET_PARAMETER_N11 - RoutineControll GetParameter N11, description=error: negative response : requestOutOfRange, link=MSM_ETHERNET>
MCDDiagService<id=398649, job=com.bmw.psdz.jobs.common.MCD3_ReadF11DataFromC smClients, service=RC_GET_PARAM_N11_CSM - RoutineControll GetParameter N11 CSM, description=error: negative response : requestOutOfRange, link=HU_NBT_63_ETHERNET>
MCDDiagService<id=378649, job=com.bmw.psdz.jobs.uds.MCD3_ReadF11DataFromMSM, service=RC_GET_PARAMETER_N11 - RoutineControll GetParameter N11, description=error: negative response : requestOutOfRange, link=MSM_ETHERNET>
MCDDiagService<id=378649, job=com.bmw.psdz.jobs.uds.MCD3_ReadF11DataFromMSM, service=RC_GET_PARAMETER_N11 - RoutineControll GetParameter N11, description=error: negative response : requestOutOfRange, link=MSM_ETHERNET>
MCDDiagService<id=398649, job=com.bmw.psdz.jobs.common.MCD3_ReadF11DataFromC smClients, service=RC_GET_PARAM_N11_CSM - RoutineControll GetParameter N11 CSM, description=error: negative response : requestOutOfRange, link=HU_NBT_63_ETHERNET>
MCDDiagService<id=378649, job=com.bmw.psdz.jobs.uds.MCD3_ReadF11DataFromMSM, service=RC_GET_PARAMETER_N11 - RoutineControll GetParameter N11, description=error: negative response : requestOutOfRange, link=MSM_ETHERNET>
MSM update finished. [C216]
VCM Update: Write FA to VCM. [C188]
VCM Update: Write FP to VCM. [C190]
VCM Update: Read current SVT. [C191]
VCM Update: Check current SVT with TAL. [C192]
VCM Update: Write target SVT. [C193]
VCM Update: Write FA to backup. [C189]
MCDDiagService<id=272649, job=com.bmw.psdz.jobs.uds.vcm.MCD3_WriteFAtoVCMBac kup, service=WDBI_FA1 - WriteDataByIdentifier FA Teil 1, description=error: negative response : requestOutOfRange, link=VCM_BACKUP_ETHERNET>
VCM Update: finished with error. [C196][Error in VCM Update:] There was an error, please check the log files.

[] - [Exception - VCM_BACKUP - 40] job failed with negative response error:
code: service returned global negative response
description: Service WDBI_FA1 returned a negative response with response code requestOutOfRange; LinkName: VCM_BACKUP_ETHERNET
severity: ERROR


Write FA to the Backup Partner failed. Possibly there is no connection to the Backup Partner. [C097]
job failed with negative response error:
code: service returned global negative response
description: Service WDBI_FA1 returned a negative response with response code requestOutOfRange; LinkName: VCM_BACKUP_ETHERNET
severity: ERROR
[433]
Abarbeitung beendet

I'm not sure why I'm getting this message follow everything to the T step by step If any one can help me out I will be very thankful. I heard that the pedal is mushy without coding but mine is rock solid when car is off but when I turn it on when depressed it slowly almost goes down to the floor when pumped couple times hard again that is when the car on, is that how mushy it is without coding? anyhow I would like to resolve this coding issue any help will be greatly appreciated.

Thanks
Appreciate 0