+- Bimmer Scene - Latest BMW Coding / Retrofits / Maps (https://www.bimmerscene.com)
+-- Forum: Bimmer Scene Coding & Navigation (https://www.bimmerscene.com/forumdisplay.php?fid=1)
+--- Forum: BMW F / G Series Coding & Retrofits & Diagnostics (https://www.bimmerscene.com/forumdisplay.php?fid=3)
+--- Thread: Coding after Feature Installer (/showthread.php?tid=6754)
Coding after Feature Installer - pharnos - 08-12-2024
Hi everyone,
Quick question - If you have enabled carplay via Feature Installer, can you then use EsysPlus etc to make some coding changes (set auto start/stop off, change iDrive startup animation etc.) Or will any HU_NBT2/KOMBI/FEM_BODY related NCD codings wipe the carplay setup from the Feature Installer process?
Cheers!
Steve.
RE: Coding after Feature Installer - spacepl - 08-13-2024
You can use whatever you want. The magic is in FSC codes, that Feature installer inject in NBT, not the coding.
RE: Coding after Feature Installer - Memedalji_ - 08-13-2024
(08-12-2024, 04:14 AM)pharnos Wrote: Hi everyone,Yes of course you can use ėšÝ§ then to code
Quick question - If you have enabled carplay via Feature Installer, can you then use EsysPlus etc to make some coding changes (set auto start/stop off, change iDrive startup animation etc.) Or will any HU_NBT2/KOMBI/FEM_BODY related NCD codings wipe the carplay setup from the Feature Installer process?
Cheers!
Steve.
RE: Coding after Feature Installer - pharnos - 08-14-2024
Thanks guys, managed to successfully change region, setup carplay and maps, and make FDL/NCD option changes.
Here's the process I went through in case anyone else is curious:
=================================================================
1. FULL BACKUP
=================================================================
- so we have original files:
FA (from reading vehicle order, Salapa options etc)
SVT (from reading ECU modules)
NCDs (from CAFD files)
used plain ėšÝ§ v3.30 for this (set up with latest psdz data files [lite])
=================================================================
2. FEATURE INSTALLS
=================================================================
- use Feature Installer program to apply Feature Installer code obtained from Rob on this forum
=================================================================
3. FA/VO CODING
=================================================================
- to change Salapa options
a) change region from Japan to NZ (807 to 810)
b) change language to English (852 to 853)
c) change service interval to 8,000kms / 12mths (8KL to 8KP)
coded against 3 ECU modules -> KOMBI, HU_NBT2 and DME [engine off for DME coding]
(right-click on each ECU module folder and choose 'Code')
used plain ėšÝ§ v3.30 for this (set up with latest psdz data files [lite])
=================================================================
4. FEATURE INSTALL
=================================================================
- I think the above FA/VO coding against HU_NBT2 causes carplay to stop allowing connections, or something did so had to apply again
(a message about "feature installer already applied do you want to revert to OEM for dealer visit" will appear, it's ok to just choose no and apply the FI code over the top, no need to revert to OEM then apply Feature Installer again)
=================================================================
5. Maps
=================================================================
- download maps and extract to USB stick (only used 16GB USB stick because NZ/Aus maps are about 5GB extracted)
- copy FSC generated via Feature Install process above into FSC folder on USB stick
- plug into centre console armrest usb port to load
=================================================================
6. Coding
=================================================================
- use ėšÝ§ with a launcher, I used ESysPlus 3.8 (obtained from this forum) with latest psdz data files [lite]
- always ensure after saving the NCD, back on the coding screen in ėšÝ§, to click 'Code NCD' (with the same CAFD file selected).
- DO NOT CHOOSE 'CODE' or right-click on the ECU module and choose 'Code' - this is only for VO/FA coding Salapa options.
- DO NOT CHOOSE 'CODE DEFAULTS' - this equals a potential trip to the dealer.
=================================================================
* NOTES
=================================================================
- sometimes after coding an ECU module you'll see warning lights on instrument panel / iDrive etc - don't worry they should go away.
- after VO/FA coding the KOMBI module I had the language change to German in the instrument panel (but still English in iDrive) - easy fix just go to iDrive settings and change the language to something else then back to English, it'll update in the instrument panel. Likewise for the time, just update it in the iDrive settings to something other than what it is and on save it'll update in the instrument panel too.
- I haven't written any FA back to the car, so if an ECU module is coded again without checking the FA/Salapa options (not FDL/NCD coded, but the 'Code' option) then region/language/serviceinterval will revert and potentially require going through this process again.
This is what worked for me (Japanese 2017 BMW 320i Estate LCI with NBT EVO ID5 [K version]). There may be some unnecessary steps above, or something not quite as efficient as it could be; but it's what worked for me after a few attempts where iDrive went black screen etc (that was before applying Feature Installer VO Coding Fix and Region Unlock etc).