Hello,
i propose to open One master threads to regroup the information about the coding of theses car as they have the same architecture .
i already found a coding sheat for mini :
https://docs.google.com/spreadsheets/d/1eO-4KXfxkksCIBP_xKjMXcIwlgAyWVxFLcla5lzibnw/edit#gid=0
and i've already VO code the 6NS option to my car with this procedure !
READ IMPORTANT NOTES:
1) NEVER click "Code Default Values" it can reset important stuff and car might not start and need to get towed to the dealer to fix the software
2) Make sure you click "Code FDL" and not "Code" (clicking code will reset the car to the factory setting erasing all the FDL coding for the selected ECU)
3) Always code with the car running or with a commercial grade charger connected to it, else voltage might drop during coding and you could get unexpected errors. (if you are codding the DME ECU you can't have the car running so you will need a charger)
4) Launcher note: E-Sys Launcher Car Series MUST be set to exactly match the car's chassis type you are coding (e.g. F01, F06, F07, F10, F12, F15, F25, F30, F82, F83, etc.). If after install it defaults to F999 and it cannot be changed, change PC Date ahead 4 days, then change E-Sys Launcher Car Series, then change PC Date back to current date. DO NOT create .EST Token and PIN with PC Date advanced 4 days as the Validity Start Date for the token will be 4 days in the future."
What's Needed for coding?
Enet Cable search on ebay http://www.ebay.com/sch/i.html?_trk...S&_nkw=OBD2+ENET+Ethernet+Cable+for+BMW+F-Series+Coding+ESYS&_sacat=0&_from=R40
E-sys software (ask here http://www.bimmerfest.com/forums/showthread.php?t=638188&page=121)
NEW: Free universal token option http://www.bimmerfest.com/forums/showthread.php?t=805745
NCD CAFD tool http://www.bimmerfest.com/forums/showthread.php?t=749668
Whatever you do never ever ever press "Code Default Values" ... you have been warned
Coding 101 video
How to VO code
Connect => Read FA => Activate FA => Read SVT (VCM) => Right-Click on ECU you want to code i.e. HU_NBT (the ECU itself not the underlying CAFD) => Select CODE.
Corrupted CAFD
Just inject new CAFD into ECU, and VO Code it.
Connect => Read FA (VO) => Activate FA (VO) => Read SVT (VCM) => Left-Click on desired ECU => Click on "Detect CAF for SWE" => Select the CAFD from latest I-Level shown => Select OK => Right-Click on ECU (the ECU itself not the underlying CAFD) => Select CODE.
Read I-Level
To determine your I-Level, go to VCM Module => VCM Master Tab => click Read under I-Steps
Targets:
F001 psdzdata covers the F01/F02/F03/F04/F07 (5-Series GT is an F07 NOT an F10)
F010 psdzdata covers the F06/F10/F11/F12/F13/F18
F020 psdzdata covers the F20/F21/F22/F23/F30/F31/F32/F33/F34/F35/F36/F80/F82/F83 (There is no Z4 F-chassis yet)
F025 psdzdata covers the F15/F16/F25/F26/F48/F85/F86
F056 psdzdata covers the F45/F46/F48(BMW)F64/F55 F56 (Cooper Mini's)
I001 psdzdata covers the i3/i8
i propose to open One master threads to regroup the information about the coding of theses car as they have the same architecture .
i already found a coding sheat for mini :
https://docs.google.com/spreadsheets/d/1eO-4KXfxkksCIBP_xKjMXcIwlgAyWVxFLcla5lzibnw/edit#gid=0
and i've already VO code the 6NS option to my car with this procedure !
owners of F45/F46/F48/F55/F56 any stuff we can share, we can do it here.
READ IMPORTANT NOTES:
1) NEVER click "Code Default Values" it can reset important stuff and car might not start and need to get towed to the dealer to fix the software
2) Make sure you click "Code FDL" and not "Code" (clicking code will reset the car to the factory setting erasing all the FDL coding for the selected ECU)
3) Always code with the car running or with a commercial grade charger connected to it, else voltage might drop during coding and you could get unexpected errors. (if you are codding the DME ECU you can't have the car running so you will need a charger)
4) Launcher note: E-Sys Launcher Car Series MUST be set to exactly match the car's chassis type you are coding (e.g. F01, F06, F07, F10, F12, F15, F25, F30, F82, F83, etc.). If after install it defaults to F999 and it cannot be changed, change PC Date ahead 4 days, then change E-Sys Launcher Car Series, then change PC Date back to current date. DO NOT create .EST Token and PIN with PC Date advanced 4 days as the Validity Start Date for the token will be 4 days in the future."
What's Needed for coding?
Enet Cable search on ebay http://www.ebay.com/sch/i.html?_trk...S&_nkw=OBD2+ENET+Ethernet+Cable+for+BMW+F-Series+Coding+ESYS&_sacat=0&_from=R40
E-sys software (ask here http://www.bimmerfest.com/forums/showthread.php?t=638188&page=121)
NEW: Free universal token option http://www.bimmerfest.com/forums/showthread.php?t=805745
NCD CAFD tool http://www.bimmerfest.com/forums/showthread.php?t=749668
Whatever you do never ever ever press "Code Default Values" ... you have been warned
Coding 101 video
How to VO code
Connect => Read FA => Activate FA => Read SVT (VCM) => Right-Click on ECU you want to code i.e. HU_NBT (the ECU itself not the underlying CAFD) => Select CODE.
Corrupted CAFD
Just inject new CAFD into ECU, and VO Code it.
Connect => Read FA (VO) => Activate FA (VO) => Read SVT (VCM) => Left-Click on desired ECU => Click on "Detect CAF for SWE" => Select the CAFD from latest I-Level shown => Select OK => Right-Click on ECU (the ECU itself not the underlying CAFD) => Select CODE.
Read I-Level
To determine your I-Level, go to VCM Module => VCM Master Tab => click Read under I-Steps
Targets:
F001 psdzdata covers the F01/F02/F03/F04/F07 (5-Series GT is an F07 NOT an F10)
F010 psdzdata covers the F06/F10/F11/F12/F13/F18
F020 psdzdata covers the F20/F21/F22/F23/F30/F31/F32/F33/F34/F35/F36/F80/F82/F83 (There is no Z4 F-chassis yet)
F025 psdzdata covers the F15/F16/F25/F26/F48/F85/F86
F056 psdzdata covers the F45/F46/F48(BMW)F64/F55 F56 (Cooper Mini's)
I001 psdzdata covers the i3/i8
