Retrofitting NBT-Evo ID6 unit into a 2015 F22 stock equip. w/ ENTRYNAV+ConnectedDrive |
Post Reply |
|
Thread Tools | Search this Thread |
03-05-2023, 09:57 AM | #1 |
Private
17
Rep 87
Posts |
Retrofitting NBT-Evo ID6 unit into a 2015 F22 stock equip. w/ ENTRYNAV+ConnectedDrive
Hi all,
Thanks a lot in advance for reading. I'd especially like to tap into shawnsheridan 's extensive knowledge of coding, if he was so kind to provide support. Here's a very quarky project I'd like to embark on: I have a 2015 F22 (pre-facelift, Typschluessel 1J11) equipped with an ENTRYNAV head unit w/ ConnectedDrive. I'd like to retrofit an NBT Evo ID6 and flash/code all that needs to be flashed/coded. I'm not so concerned with feature unlocking through FSC codes at the moment, as I'd like to figure out the basic steps to get the HU to work at all first. I will get a used NBT Evo ID6 unit, so VIN will not match my car at first. Display and iDrive controller will also be changed to match donor HU. Please note that I have the Connected Drive option on my original ENTRYNAV. I'm not sure if this means that my car is equipped with an ATM module or equivalent. Not sure if this complicates the coding further if I want to retain the Connected Drive functionality. Here's the steps I've figured out so far: 1. *** First and foremost *** 1.a Install E-Sys with compatible PSdzData 2. *** Now onto the new HU_NBTEvo, after its successful retrofit installation *** 2.a Connect to target via *donor* VIN 2.b Go to Expert mode --> Coding 2.c In the Vehicle Order section (top-left) click on Read 2.d Right click on FA --> Activate FA 2.e In the SVT-Actual (SVT-Ist, mid-right) section click on Read ECU **** non-mandatory steps **** 2.f Save FA from 2.c (just in case something goes wrong later) 2.g Save SVT-Actual from 2.e (just in case something goes wrong later) **** end of non-mandatory steps **** Here the part I'm not so sure about: 3. *** Writing current VIN to donor HU *** 3.a Go to Expert mode --> FSC Extended 3.b Click on Identify 3.c Add WriteDataByIdentifierVIN to job list and write *current* VIN (the original one the car came with, not the donor one) 3.d Click on Start 3.e Go to Expert mode --> Coding 3.f FA should already be activated from 2.d 3.g SVT should already have been read in 2.e 4. *** existential questions *** 4.a from the KIS/SVT Target section (middle-right) should I click on "Detect CAF for SWE", select a CAFD file from the list and then click on "Code" to code it to the NBT_HU? 4.b Should I "calculate" the CAFD in the SVT-Target section instead? 5. *** FSC code installation *** But to my best understanding I may have to worry about this at the in order to get the features I want (Maps, Fullscreen Carplay, ConnectedDrive, etc.). But I'm trying to get the donor HU to work first even without such features. One step at a time. These are many questions, I know, but it's so difficult to get this information as a newbie by scouting the web. Any help is soooo appreciated!!! |
03-05-2023, 10:44 AM | #2 |
Banned
609
Rep 2,046
Posts |
use Detect CAF for SWE to code the HU, its faster than calculating SVT target.
The steps are okay. In step 3b write 0x63 to choose NBT. 3g code the HU. After coding the NBT would work but the features would not be available. If you want you can get the FSC to activate and patch the NBT. I can get the FSC for you. If you need any assistance PM me. |
Appreciate
0
|
03-05-2023, 02:09 PM | #3 | |
Private
17
Rep 87
Posts |
Quote:
So I'll post here the steps edited to your remarks: 3. *** Writing current VIN to donor HU *** 3.a Go to Expert mode --> FSC Extended 3.b.1 write 0x63 to choose NBT 3.b.2 Click on Identify 3.c Add WriteDataByIdentifierVIN to job list and write *current* VIN (the original one the car came with, not the donor one) 3.d Click on Start 3.e Go to Expert mode --> Coding 3.f FA should already be activated from 2.d 3.g SVT should already have been read in 2.e 3.h Click on "Detect CAF for SWE", select a CAFD file from the list and then click on "Code" to code it to the NBT_HU Does it look good now? Because I'm a noob, I don't have PM capability yet. But hopefully soon I will! Last edited by boldorider4; 03-05-2023 at 02:10 PM.. Reason: formatting |
|
Appreciate
0
|
03-05-2023, 02:38 PM | #4 | |
Private
17
Rep 87
Posts |
Quote:
1. Because I haven't had the guts yet to tear my car apart, I don't know if I have a proper ATM module. Given that my ENTRYNAV HU has ConnectedDrive capabilities, I would assume I have an ATM module or equivalent. Do you know if this complicates the coding of the donor NBT Evo ID6 unit? 2. Some (or perhaps all) NBT Evo ID6 HU I find for sale online come with a flat connector below the quad lock. I'm guessing the flat connector is to wire the ATM module, but then it's unclear to me whether connecting my (supposedly existing) ATM would work when paired to a non-stock NBT Evo ID unit and if I would need a retrofit quad lock harness with an emulator module. Regardless if a retrofit harness with an emulator module is required, will I lose ConnectedDrive capabilities? 3. Some NBT Evo ID6 HU I find for sale online also have a blue connector for a GPS antenna, some do not. If I buy one with a blue connector and connect an aftermarket GPS antenna, would I be able to get a GPS signal even if an ATM module is not working properly because not matching the HU? |
|
Appreciate
0
|
05-10-2023, 04:35 PM | #9 |
Private
17
Rep 87
Posts |
Hi guys,
just letting you know this retrofit was a complete success! I will post a step-by-step tutorial also highlighting all the impediments I encountered en route (there were A LOT). If you guys need my help in getting unblocked, do not hesitate to ask! |
Appreciate
0
|
05-15-2023, 01:52 PM | #10 |
Private First Class
28
Rep 171
Posts |
Very cool. Did you end up doing this with an emulator or without? I have a similar retrofit using a emulator (with a matching donor ATM and ID6) but would be curious if there is another way!
|
Appreciate
0
|
05-22-2023, 04:46 AM | #11 | |
Private
17
Rep 87
Posts |
Quote:
So, I decided that buying an ATM and repining the TCB connector to make it compatible with the ATM, plus rewiring the emergency microphone, was going to be too much hassle, so I only retrofitted the NBTevo HU. Since I don't have to have a VIN-match between the ATM and the HU (because ATM is entirely missing!) I VO-coded the HU with my VIN and therefore did not need the emulator. |
|
Appreciate
1
Mr. F2228.00 |
03-05-2024, 08:14 PM | #12 |
Registered
0
Rep 4
Posts |
Thank you for the write up. I am about to replace my NBT ID4 on my 2016 X3 to NBT_EVO HW 4.1 with a blue gps cable.
Ideally, i would like to program the unit on the bench first but I do not think I have the proper hardware for connection. I just want to confirm, after I retrofit the hardware (New NBT EVO HU) all I need is 1. E-sys 2. ENET Cable 3. Instructions to code the vin to the new NBT EVO HU Am I missing anything? Thanks again! |
Appreciate
0
|
06-19-2024, 08:52 AM | #13 | |
Private
17
Rep 87
Posts |
Quote:
Make sure you follow my guide step-by-step, especially to get the GPS working if you route it to the blue Fakra connector on the back of your NBT EVO unit. You will need to code all this information with programs like BimmerCode or BimmerUtility. |
|
Appreciate
0
|
07-23-2024, 05:20 PM | #14 |
Registered
0
Rep 1
Posts |
I'm new in the BMW scene, I just bought a newly (used) 2016 BMW 228i, and I'm very interested in doing this retrofit as well for the carplay. I have been trying to read as much as possible but is very confusing as not all information is in a single place and is scattered in different posts. Will all 4.1 Headunits work for retrofit? I found a 2018 HW 4.1 head unit which has a Kombi port but don't know if it can be used. I know I have to upgrade the display as well.
The images attached are of my current head unit, which I understand is a EntryNAV, correct? Last edited by Yuyo; 07-24-2024 at 09:03 AM.. |
Appreciate
0
|
08-13-2024, 03:14 AM | #15 | |
Captain
282
Rep 887
Posts
Drives: 2018 F48 X1 xDrive 18D
Join Date: Nov 2022
Location: Norway
|
Quote:
For step 5., is it enough to buy just a OEM repair pack with .FSC files and load them into the HU?
__________________
Retrofits done: 2TB, 235, 313, 430 459, 508, 5DP, 322, 674 , 6CP
Other mods: Central Locking button on both sides Other info: F48 Fuseguide, CarPlay 6CP - OEM way |
|
Appreciate
0
|
08-13-2024, 05:45 AM | #16 |
General
10931
Rep 42,976
Posts
Drives: 2018 Alpina B6 650ix GC
Join Date: Feb 2010
Location: Houston, TX
|
No. OEM FSC Repair Kit contains original ENTRNAV FSC Codes, not the required EVO FSC Codes.
__________________
2018 F06 Alpina B6 650ix GC; Space Grey; Vermillion Red Nappa Leather; Executive; B&O; Driving Assistant 2017 F15 X5 xDrive50i MSport; Glacier Silver Metallic; Black Dakota Leather; Executive; B&O; Driving Assistant; RSE |
Appreciate
0
|
08-13-2024, 06:22 AM | #17 |
Captain
282
Rep 887
Posts
Drives: 2018 F48 X1 xDrive 18D
Join Date: Nov 2022
Location: Norway
|
So what do I need to do as a step 5? Buy a non-OEM FSC set & patch HU?
__________________
Retrofits done: 2TB, 235, 313, 430 459, 508, 5DP, 322, 674 , 6CP
Other mods: Central Locking button on both sides Other info: F48 Fuseguide, CarPlay 6CP - OEM way |
Appreciate
0
|
08-13-2024, 06:57 AM | #18 |
General
10931
Rep 42,976
Posts
Drives: 2018 Alpina B6 650ix GC
Join Date: Feb 2010
Location: Houston, TX
|
Yes.
__________________
2018 F06 Alpina B6 650ix GC; Space Grey; Vermillion Red Nappa Leather; Executive; B&O; Driving Assistant 2017 F15 X5 xDrive50i MSport; Glacier Silver Metallic; Black Dakota Leather; Executive; B&O; Driving Assistant; RSE |
Appreciate
0
|
Post Reply |
Bookmarks |
|
|