[boldorider4]

Originally Posted by 107H

Thanks for the speedy response dude!

Apologies haha should've said, I'm driving a 2016 BMW M235i F22 which was currently just has the 6.5" screen with EntryNav and I would like to fit a newer 8.8" Touch Screen with the newer software so I can have Apple Carplay. I believe it is almost exactly the same retrofit as you did although, I could be wrong.

My vin - https://www.mdecoder.com/decode/v353601

On second thought, I looked at your VIN and you may have a pre-LCI F22 (one of the last ones!).

Have a look at this post: https://f30.bimmerpost.com/forums/sh...38&postcount=2
I believe this is not the full super duper post I made but it summarizes the process pretty well.

Also, if you're in need of changing the KOMBI cluster, have a look at this too: https://www.2addicts.com/forums/show...8&postcount=17

[107H]

Originally Posted by boldorider4

On second thought, I looked at your VIN and you may have a pre-LCI F22 (one of the last ones!).

Have a look at this post: https://f30.bimmerpost.com/forums/sh...38&postcount=2
I believe this is not the full super duper post I made but it summarizes the process pretty well.

Also, if you're in need of changing the KOMBI cluster, have a look at this too: https://www.2addicts.com/forums/show...8&postcount=17

Thank you for all of this

I am looking for the parts that I need to get started with everything, am I right in thinking this (1) would cover it? or is it missing anything?

Thank you again dude!

(1)https://www.ebay.co.uk/itm/326231069...&ul_noapp=true

[boldorider4]

Originally Posted by 107H

Thank you again dude!

(1)https://www.ebay.co.uk/itm/326231069...&ul_noapp=true

Ok, so the NBT Evo is still on ID5 and you'll need to bring it to ID6 (that's the interface), but luckily that can be done through coding.
The good thing is that it also has DAB-L and DAB-III connectors! The bad part though is that the CID screen is not touchscreen and I also don't see the blue fakra connector in the back for GPS.

Why do you need the blue fakra in the back? Because your ENTRYNAV gets GPS straight from the back of the head unit, so your GPS is wired there. The reason why many NBT Evo's don't have the GPS connector is because usually NBT Evo is paired with a VIN-matched ATM module (for the connected services, ATM provides internet connectivity) and the ATM itself gets the GPS signal and then feeds it back to the NBT Evo through the OABR connector (more on that later).

Now, you could also get an ATM module and retrofit it, but the nasty part is that the ATM replaces the TCB module (your current connectivity module) in the trunk, so you would have to wire that blue GPS connector from your head unit bay to the trunk and then the OABR cable from the trunk back to the head unit bay....that's why many people skip the ATM module retrofit (like me) and search for a (very rare) NBT Evo with the blue connector in the back for the GPS. That way you save yourself a bunch of rewiring. You will lose the connectivity but who cares. Your ENTRYNAV has barely any connectivity functionality to begin with.

In the unlikely event that the NBT EVO has too old a software, be prepared to flash it. For that you will need a custom cable that pins the OABR connector in the back of NBT Evo to Ethernet (RJ45), so E-Sys can see it. I broke an Ethernet cable and made an ETH-to-OABR myself crimping and pinning the 4 ETH wires (TX_+. TX_-, RX_+, RX_-) to the OABR connector.

Basically, in that scenario you will have 2 ethernet interfaces on your laptop, one that goes to the ODB2 port of your car (with the so-called E-Net cable) and one that goes straight to that OABR connector...all the while your NBT is hooked up with the Quad lock connector to your car network!

Even if you don't need to flash it, you will need to inject FSC codes for CarPlay to be enabled, and for that you will use a tool called FeatureInstaller and you will need to actually buy fake FSC codes for the activation (readily available on many online coding shops for, like, 30 bucks or something). You cannot inject FSC codes with E-Sys in this case because no one is selling your the bear *.fsc and *.cert files. To get The communication between FeatureInstaller and the NBT Evo you will again need that custom OABR-to-Eth cable.

Let me know if this is all clear.

[boldorider4]

107H

This is an example of an NBT Evo with the Blue connector
https://www.ebay.co.uk/itm/313197663...Bk9SR5yQtue5ZQ

By the way, I almost forgot to mention: if you don't care about the GPS connectivity you can obviously get a less rare (and way cheaper) NBT Evo without the connector. But I like the idea of retaining the original navigation next to CarPlay, since sometimes my phone may not have network.
Either that or you get that ATM module and go through the painful GPS-to-ATM-through-OABR-to-NBT wiring.
By the way, ATM will need to stay with its original VIN or it will brick itself permanently. That means the NBT Evo will also need to match that VIN (so you will need to VO-code the NBT with E-Sys with that foreign VIN from the ATM). In this case, for the NBT to communicate gracefully with the other ECU's you will need to install a VIN activator (which essentially is a message filter) between the Quad lock harness from your car to the Quadlock harness of the NBT.
Sounds really crazy but this is all much clearer once you get your hands dirty on this project. There's also a really good video about NBT+ATM retrofit by the mighty Nikolas Gorke. It's on an F30 but the process is identical. Just don't take his coding steps word for word because for you, coming from a pre-LCI F22 it'll be a little different.

[107H]

Originally Posted by boldorider4

107H

This is an example of an NBT Evo with the Blue connector
https://www.ebay.co.uk/itm/313197663...Bk9SR5yQtue5ZQ

By the way, I almost forgot to mention: if you don't care about the GPS connectivity you can obviously get a less rare (and way cheaper) NBT Evo without the connector. But I like the idea of retaining the original navigation next to CarPlay, since sometimes my phone may not have network.
Either that or you get that ATM module and go through the painful GPS-to-ATM-through-OABR-to-NBT wiring.
By the way, ATM will need to stay with its original VIN or it will brick itself permanently. That means the NBT Evo will also need to match that VIN (so you will need to VO-code the NBT with E-Sys with that foreign VIN from the ATM). In this case, for the NBT to communicate gracefully with the other ECU's you will need to install a VIN activator (which essentially is a message filter) between the Quad lock harness from your car to the Quadlock harness of the NBT.
Sounds really crazy but this is all much clearer once you get your hands dirty on this project. There's also a really good video about NBT+ATM retrofit by the mighty Nikolas Gorke. It's on an F30 but the process is identical. Just don't take his coding steps word for word because for you, coming from a pre-LCI F22 it'll be a little different.

Honestly dude, thank you so much for your help with all of this - I would be so confused otherwise haha. I have just found this from the same supplier and given all of the work I would need to do it doesn't seem all that bad a price to have some coding pre done? I would love to learn coding but it looks as though it wouldn't even save me much money in the end. I am definitely not bothered about that ATM module fuss, seems like too much work for something I won't require/utilise all that much.

Correct me if I am wrong but this bundle does not seem badly priced given how much the other components would cost me alone unless I have missed something on the listing, I realise it is not a touch screen panel - again, I am unsure how much I would use this anyways, have you found yourself actually using your touch screen often or moreso using the controller?

https://www.ebay.co.uk/itm/265969990...KM4GV03CPTD0YT

[boldorider4]

Originally Posted by 107H

I would love to learn coding but it looks as though it wouldn't even save me much money in the end.

Up to you! I had a lot of fun learning how to code. It is definitely not a hard skill to craft. Flashing requires a little more caution, though.

Originally Posted by 107H

I am definitely not bothered about that ATM module fuss, seems like too much work for something I won't require/utilise all that much.

Sure, I made the same decision. Just make sure you buy an NBTEvo with a GPS connector then.

Originally Posted by 107H

Correct me if I am wrong but this bundle does not seem badly priced given how much the other components would cost me alone unless I have missed something on the listing, I realise it is not a touch screen panel - again, I am unsure how much I would use this anyways, have you found yourself actually using your touch screen often or moreso using the controller?

I didn't go with the touchscreen because at the time it was way too expensive. I like the iDrive controller actually.
As far as price, what you're looking at is ok, within market bounds. Bear in mind, any small hardware feature on the NBTEvo unit is going to result in a big price difference. Here you're looking at a unit with a built in GPS connector, but DAB is missing. I pointed you to one that had both DAB and GPS, that's why it was pricier.

I agree that bundles are usually cheaper than buying the parts individually.
As far as pre-coding, they should be able to pre-code the device, but I'm wondering if they go as far as FDL coding individual parameters after the so called VO-coding. The VO-coding will set the foundation parameters and will set things like the basic options of your vehicle (SA options), your VIN, your Chassis code (F22), car paint color, production date, etc. But with NBTEvos there are many small nuances that you can only code with FDL coding, meaning setting individual parameters outside of VO-coding. That is usually hard to do unless the device is hooked to the vehicle and the effects of the parameters are observed. But maybe they are experts of this device and the different BMW configurations and they will still know exactly what to do.
Another thing they can definitely do is install the FSC codes (which go on top of VO-coding and FDL-coding) to the NBTevo for things like map updates, CarPlay activation, etc. but they will charge you for that.
You should ask them what kind of services they do with coding.

[boldorider4]

Originally Posted by 107H

I would love to learn coding but it looks as though it wouldn't even save me much money in the end.

You know, there's actually another caveat I just thought of if you want to have the coding done by someone else. You will also have to ask them to flash this NBTEvo unit with exactly (and I mean exactly) I-Step 03-18 (that's the firmware version notation used by BMW). That's specifically because you're planning on buying this with a NON-touchscreen CID display.

03-18 and prior support non-touchscreens, whereas 07-18 onwards only fully support a touchscreen CID. When I say fully support I mean that if you fit a non-touchscreen to a non-fully supporting FW version (>=07-18), the screen will stay black circa 1/3 of the times you start the car, prompting you to reboot (long mute button press) the head unit to revive the screen. This happens seemingly at random because it's due to how the FW >=07-18 handle wake-up signals.

and why not leave an older than 03-18 FW on, you ask (e.g. the unit you buy comes with an older FW)? Because starting from 03-18 the FW was updated to support fullscreen CarPlay. Otherwise you'll be stuck with CarPlay on half the screen. So in other words, 03-18 is the sweet spot and you need to either ask the coder to flash that FW (with an upgrade or a downgrade). After that, only after that, the coder can install FSC codes for paid features like CarPlay and then later do VO-coding and if necessary (as is likely) individual FDL-parameter coding to fit the quirkiness of your specific trim.

One of the positive aspects of an NBTEvo retrofit is that after fiitting this unit you will be very experienced with coding and coding any other module in the car will be a piece of cake.

[107H]

Originally Posted by boldorider4

You know, there's actually another caveat I just thought of if you want to have the coding done by someone else. You will also have to ask them to flash this NBTEvo unit with exactly (and I mean exactly) I-Step 03-18 (that's the firmware version notation used by BMW). That's specifically because you're planning on buying this with a NON-touchscreen CID display.

03-18 and prior support non-touchscreens, whereas 07-18 onwards only fully support a touchscreen CID. When I say fully support I mean that if you fit a non-touchscreen to a non-fully supporting FW version (>=07-18), the screen will stay black circa 1/3 of the times you start the car, prompting you to reboot (long mute button press) the head unit to revive the screen. This happens seemingly at random because it's due to how the FW >=07-18 handle wake-up signals.

and why not leave an older than 03-18 FW on, you ask (e.g. the unit you buy comes with an older FW)? Because starting from 03-18 the FW was updated to support fullscreen CarPlay. Otherwise you'll be stuck with CarPlay on half the screen. So in other words, 03-18 is the sweet spot and you need to either ask the coder to flash that FW (with an upgrade or a downgrade). After that, only after that, the coder can install FSC codes for paid features like CarPlay and then later do VO-coding and if necessary (as is likely) individual FDL-parameter coding to fit the quirkiness of your specific trim.

One of the positive aspects of an NBTEvo retrofit is that after fiitting this unit you will be very experienced with coding and coding any other module in the car will be a piece of cake.

Apologies I have taken a while to get back to you this time, had some stuff on that took priority haha.

I have been looking and have found some options, just torn at what approach to take now. On one hand I have found a bundle with a touchscreen, HU with DAB, blue fakra connecter for only £900 agreed with the seller, all fully coded to VIN and aftersales support if any issues arise.

Or... I could spend a total of around £700 - £800 on the individual parts, not including FSC codes or any cables I might need.

It is looking as though a bundle will definitely be the more cost effective way of doing so strangely enough, I really thought coming into this that it would be cheaper to buy the parts and code myself but I have been proven wrong by my own searching haha

Here is the bundle I found where the seller has agreed £900 with full coding and a DAB unit - https://www.ebay.co.uk/itm/126875970776

[boldorider4]

107H

No worries.

Bundles make a lot of sense. Bear in mind that even if they will pre-code everything for you, you may need to do some tweaking of parameters with a coding tool like BimmerUtil (99 USD I believe).

Or you could send the parameter list to the seller.
Here's the parameters I tweaked that most likely will work for you.

Most of these are very optional and actually will already be set once they VO-code the unit.
The ones in bold are essential though. Also, ask them if the CID screen is APIX1 or APIX2. If it's the latter CID_APIX_MODE (apix2), CID_COLOR_DEPTH (24), CID_COM_MODE (mii) need to be set accordingly. The GPS_FROM_NAVI, GPS_FROM_NAVI and TELEMATIC_ECU are super important too if you have the blue connector in the back.

This list was days or weeks of manual attempts and research. Didn't find anyone who had these ready. You're welcome

    FDL:
    --- HU_NBT2 ---
    *** carplay ***
    CARPLAY_SWT                  --> aktiv (appears after flash w/ BimmerUtility)
    CARPLAY_FULLSCREEN           --> aktiv
    *** hw features ***
    ZBE_HARDKEY_LAYOUT_NEW       --> aktiv (because I have new iDrive Controller)
    CID_TOUCH                    --> nicht_aktiv (because it's non-touch CID)
    CID_APIX_MODE                --> apix1 (if CID was new it would have to be 'apix2')
    CID_COLOR_DEPTH              --> 18 (if CID was new it would have to be '24')
    CID_COM_MODE                 --> spi (if CID was new it would have to be 'mii')
    CID_DISPLAY_RES              --> 1280_480
    CID_DISPLAY_SIZE             --> 8_8
    CID_HMI_ACTIVATION_VIA_TOUCH --> nicht_aktiv
    CID_HMI_TOUCH                --> nicht_aktiv
    (search for other TOUCH related parameter)
    HIGH_BEAM_ASSISTANT          --> aktiv (strangely stayed nicht_aktiv after VO-coding 5AC)
    ECO_CONF_SAILING             --> aktiv
    GLOBAL_CONF_SAILING          --> nicht_aktiv (this would enable a sailing override check box in the eco pro setting that is uselss)
    GPS_FROM_NAVI          --> aktiv (changed from nicht_aktiv after flash, it used to be called SYSTEM_RECEIVER_GPS)
    TELEMATIC_ECU                --> nicht-aktiv (changed from atm after flash)
    CDMM_ANALOG_AUX              --> aktiv (maybe...if aux port works with Evo, otherwise it would be nicht_aktiv)
    CDMM_AUX_SIMPLE_1            --> aktiv (maybe...if aux port works with Evo, otherwise it would be nicht_aktiv)
    CDMM_AUX_SIMPLE_2            --> aktiv (maybe...if aux port works with Evo, otherwise it would be nicht_aktiv)
    CDMM_USB_PORTS               --> usb1 (changed from usb1_sia after flash)
    AUX1_IN_HU                   --> leave it alone (21/255)
    MICROPHONE_NUMBER            --> wert_1 (disables usage of emergency
    *** legal ***
    MACRO_CAM_LEGALDISCLAIMER    --> kein_ld
    LEGAL_DISCLAIMER_TIME        --> kein_ld
    *** navigation ***
    GPS_FROM_NAVI                --> aktiv
    ECO_PRO_ROUTE_ALPINE         --> aktiv (for eco pro route in navigation)
    NAVI_TRIP_EXPORT             --> aktiv
    NAVI_DEST_EXPORT             --> aktiv
    NAVI_DEST_IMPORT             --> aktiv
    NAVI_MYPOI_EXPORT            --> aktiv
    HMI_VERSION                  --> id5 (if id4_plus_plus and id5 are the only options)
    HMI_ID_VERSION               --> id6_lite (if HMI_VERSION was set to id5)
    *** steering wheel buttons ***
    MFL                          --> aktiv (MFL buttons on steering wheel)
    DCC                          --> aktiv (DCC buttons on steering wheel)
    SLD                          --> aktiv (LIM button on steering wheel)
    *** kombi ***
    FPK_COMING_ROAD_BMP          --> nicht_aktiv (or maybe aktiv?)
    CALMING_KOMBI                --> aktiv (or maybe nicht_aktiv?)
    DRIVE_MODE_KOMBI             --> nicht_aktiv (or maybe aktiv?)
    LOUPE_TACHO_KOMBI            --> nicht_aktiv (or maybe aktiv?)
    MFID_KOMBI_VARIANT           --> nicht_aktiv (or maybe aktiv?...should correspond to FPK...full panel kombi?)
    KOMBI_AUFLOESUNG             --> nicht_aktiv (should correspond to either kombi L6/L7 mid/high for nicht_aktiv or some other kombi otherwise)
    KOMBI_CIC                    --> kombi_mid (or high...doesn't really make a difference, but specifies what info to pass over MOST)
    KOMBI_RES                    --> mid (or high...doesn't really make a difference, but enables MOST for kombi high...)
    EXTERNER_MOST                --> aktiv (activates MOST communication...EXTERNE_MOST_DIAG is somehow missing, though)
    *** multimedia ***
    VIDEO_HANDBRAKE              --> nicht_aktiv
    API_IPOD_VIDEO               --> both
    ENT_VIDEO                    --> aktiv
    ENT_CODEC_OGG                --> aktiv
    ENT_CODEC_XVID               --> aktiv
    ENT_CODEC_VCD                --> aktiv
    ENT_MC_VIDEO_SUPPORT         --> aktiv
    ENT_MC_WLAN_STREAM_DMP_COVER --> aktiv
    ENT_MC_WLAN_STREAM_DMP_VIDEO --> aktiv
    ENT_MC_WLAN_STREAM_DMP       --> aktiv
    ENT_MC_PLAYLIST_IMPORT       --> aktiv
    ENT_MC_SONG_BOOKMARK         --> aktiv
    ENT_MC_COVER_SCALE           --> aktiv
    OFFICE_MESSAGES_SPEEDLOCK_C  --> noneS
    PIM_DRIVING_TEXT_LENGTH       --> whole_text
    *** rdc ***
    RDC                          --> aktiv
    RDC_FORTSCHRITTANZEIGE       --> aktiv
    RDC_SAFETY                   --> aktiv
    RDC_BELADUNGDESIGN           --> 4_sitze
    REIFENUEBERWACHUNG_RDC_RPA   --> rdc (it used to be aktiv on these notes...no idea what the difference is)
    RDC_DRUCK_TEMP               --> druck_und_temperatur
    *** speedlocks ***
    SL06_IBA_1                   --> nicht_aktiv
    SL16_ADD_CEDEVICE            --> aktiv
    SPEEDLOCK_TEXT_LENGTH        --> whole_text
    SPEEDLOCK_HMI_TUNER          --> nicht_aktiv
    SPEEDLOCK_SPEEDVALUE_MIN     --> nicht_aktiv
    SPEEDLOCK_SPEEDVALUE_MAX     --> nicht_aktiv
    SPEEDLOCK_X_KMH_MIN          --> 0xFF
    SPEEDLOCK_X_KMH_MAX          --> 0xFF
    *** climate control ***
    HVAC_POPUP_AUTO_TOGGLE       --> nicht_aktiv (used to be aktiv, but in reality no popup is available)
    HVAC_POPUP_SEATCLIMATE       --> nicht_aktiv (used to be aktiv, but in reality no popup is available)
    HVAC_POPUP_AIRDISTR          --> nicht_aktiv (used to be aktiv, but in reality no popup is available)
    *** other ***
    MOMENTDISTRIBUTION_MENU      --> nicht_aktiv
    X_VIEW                       --> nicht_aktiv
    WLAN_CLIENT                  --> nicht_aktiv
    APPLE_ENHANCEMENTS           --> aktiv
    CLOCK_CHANGE_AUTOMATIC       --> aktiv
    EFF_DYN_SPORT_CID            --> aktiv
    EFF_DYN_SPORT_UNIT           --> aktiv
    EFF_DYN_SAILING              --> aktiv
    AKT_AUTO_LENKRADHEIZUNG      --> nicht_aktiv (because it doesn't work but it would be cool, otherwise set to aktiv)
    AKT_AUTO_SITZE_FRONT         --> nicht_aktiv (because it doesn't work but it would be cool, otherwise set to heizung)

[scaramanga]

Hi! I need some advice as I’d like to upgrade the small (basic?) nav screen in my daughter’s F23. The VIN is VC26518.

Would be very grateful in case some can let me what I need ?

Ideally I’m trying to install CarPlay, and would prefer to replace with official BMW parts and keep the connected drive functionality.

Thanks in advance for any help!

[DanMacDon]

Originally Posted by boldorider4

107H

No worries.

Bundles make a lot of sense. Bear in mind that even if they will pre-code everything for you, you may need to do some tweaking of parameters with a coding tool like BimmerUtil (99 USD I believe).

Or you could send the parameter list to the seller.
Here's the parameters I tweaked that most likely will work for you.

Most of these are very optional and actually will already be set once they VO-code the unit.
The ones in bold are essential though. Also, ask them if the CID screen is APIX1 or APIX2. If it's the latter CID_APIX_MODE (apix2), CID_COLOR_DEPTH (24), CID_COM_MODE (mii) need to be set accordingly. The GPS_FROM_NAVI, GPS_FROM_NAVI and TELEMATIC_ECU are super important too if you have the blue connector in the back.

This list was days or weeks of manual attempts and research. Didn't find anyone who had these ready. You're welcome

    FDL:
    --- HU_NBT2 ---
    *** carplay ***
    CARPLAY_SWT                  --> aktiv (appears after flash w/ BimmerUtility)
    CARPLAY_FULLSCREEN           --> aktiv
    *** hw features ***
    ZBE_HARDKEY_LAYOUT_NEW       --> aktiv (because I have new iDrive Controller)
    CID_TOUCH                    --> nicht_aktiv (because it's non-touch CID)
    CID_APIX_MODE                --> apix1 (if CID was new it would have to be 'apix2')
    CID_COLOR_DEPTH              --> 18 (if CID was new it would have to be '24')
    CID_COM_MODE                 --> spi (if CID was new it would have to be 'mii')
    CID_DISPLAY_RES              --> 1280_480
    CID_DISPLAY_SIZE             --> 8_8
    CID_HMI_ACTIVATION_VIA_TOUCH --> nicht_aktiv
    CID_HMI_TOUCH                --> nicht_aktiv
    (search for other TOUCH related parameter)
    HIGH_BEAM_ASSISTANT          --> aktiv (strangely stayed nicht_aktiv after VO-coding 5AC)
    ECO_CONF_SAILING             --> aktiv
    GLOBAL_CONF_SAILING          --> nicht_aktiv (this would enable a sailing override check box in the eco pro setting that is uselss)
    GPS_FROM_NAVI          --> aktiv (changed from nicht_aktiv after flash, it used to be called SYSTEM_RECEIVER_GPS)
    TELEMATIC_ECU                --> nicht-aktiv (changed from atm after flash)
    CDMM_ANALOG_AUX              --> aktiv (maybe...if aux port works with Evo, otherwise it would be nicht_aktiv)
    CDMM_AUX_SIMPLE_1            --> aktiv (maybe...if aux port works with Evo, otherwise it would be nicht_aktiv)
    CDMM_AUX_SIMPLE_2            --> aktiv (maybe...if aux port works with Evo, otherwise it would be nicht_aktiv)
    CDMM_USB_PORTS               --> usb1 (changed from usb1_sia after flash)
    AUX1_IN_HU                   --> leave it alone (21/255)
    MICROPHONE_NUMBER            --> wert_1 (disables usage of emergency
    *** legal ***
    MACRO_CAM_LEGALDISCLAIMER    --> kein_ld
    LEGAL_DISCLAIMER_TIME        --> kein_ld
    *** navigation ***
    GPS_FROM_NAVI                --> aktiv
    ECO_PRO_ROUTE_ALPINE         --> aktiv (for eco pro route in navigation)
    NAVI_TRIP_EXPORT             --> aktiv
    NAVI_DEST_EXPORT             --> aktiv
    NAVI_DEST_IMPORT             --> aktiv
    NAVI_MYPOI_EXPORT            --> aktiv
    HMI_VERSION                  --> id5 (if id4_plus_plus and id5 are the only options)
    HMI_ID_VERSION               --> id6_lite (if HMI_VERSION was set to id5)
    *** steering wheel buttons ***
    MFL                          --> aktiv (MFL buttons on steering wheel)
    DCC                          --> aktiv (DCC buttons on steering wheel)
    SLD                          --> aktiv (LIM button on steering wheel)
    *** kombi ***
    FPK_COMING_ROAD_BMP          --> nicht_aktiv (or maybe aktiv?)
    CALMING_KOMBI                --> aktiv (or maybe nicht_aktiv?)
    DRIVE_MODE_KOMBI             --> nicht_aktiv (or maybe aktiv?)
    LOUPE_TACHO_KOMBI            --> nicht_aktiv (or maybe aktiv?)
    MFID_KOMBI_VARIANT           --> nicht_aktiv (or maybe aktiv?...should correspond to FPK...full panel kombi?)
    KOMBI_AUFLOESUNG             --> nicht_aktiv (should correspond to either kombi L6/L7 mid/high for nicht_aktiv or some other kombi otherwise)
    KOMBI_CIC                    --> kombi_mid (or high...doesn't really make a difference, but specifies what info to pass over MOST)
    KOMBI_RES                    --> mid (or high...doesn't really make a difference, but enables MOST for kombi high...)
    EXTERNER_MOST                --> aktiv (activates MOST communication...EXTERNE_MOST_DIAG is somehow missing, though)
    *** multimedia ***
    VIDEO_HANDBRAKE              --> nicht_aktiv
    API_IPOD_VIDEO               --> both
    ENT_VIDEO                    --> aktiv
    ENT_CODEC_OGG                --> aktiv
    ENT_CODEC_XVID               --> aktiv
    ENT_CODEC_VCD                --> aktiv
    ENT_MC_VIDEO_SUPPORT         --> aktiv
    ENT_MC_WLAN_STREAM_DMP_COVER --> aktiv
    ENT_MC_WLAN_STREAM_DMP_VIDEO --> aktiv
    ENT_MC_WLAN_STREAM_DMP       --> aktiv
    ENT_MC_PLAYLIST_IMPORT       --> aktiv
    ENT_MC_SONG_BOOKMARK         --> aktiv
    ENT_MC_COVER_SCALE           --> aktiv
    OFFICE_MESSAGES_SPEEDLOCK_C  --> noneS
    PIM_DRIVING_TEXT_LENGTH       --> whole_text
    *** rdc ***
    RDC                          --> aktiv
    RDC_FORTSCHRITTANZEIGE       --> aktiv
    RDC_SAFETY                   --> aktiv
    RDC_BELADUNGDESIGN           --> 4_sitze
    REIFENUEBERWACHUNG_RDC_RPA   --> rdc (it used to be aktiv on these notes...no idea what the difference is)
    RDC_DRUCK_TEMP               --> druck_und_temperatur
    *** speedlocks ***
    SL06_IBA_1                   --> nicht_aktiv
    SL16_ADD_CEDEVICE            --> aktiv
    SPEEDLOCK_TEXT_LENGTH        --> whole_text
    SPEEDLOCK_HMI_TUNER          --> nicht_aktiv
    SPEEDLOCK_SPEEDVALUE_MIN     --> nicht_aktiv
    SPEEDLOCK_SPEEDVALUE_MAX     --> nicht_aktiv
    SPEEDLOCK_X_KMH_MIN          --> 0xFF
    SPEEDLOCK_X_KMH_MAX          --> 0xFF
    *** climate control ***
    HVAC_POPUP_AUTO_TOGGLE       --> nicht_aktiv (used to be aktiv, but in reality no popup is available)
    HVAC_POPUP_SEATCLIMATE       --> nicht_aktiv (used to be aktiv, but in reality no popup is available)
    HVAC_POPUP_AIRDISTR          --> nicht_aktiv (used to be aktiv, but in reality no popup is available)
    *** other ***
    MOMENTDISTRIBUTION_MENU      --> nicht_aktiv
    X_VIEW                       --> nicht_aktiv
    WLAN_CLIENT                  --> nicht_aktiv
    APPLE_ENHANCEMENTS           --> aktiv
    CLOCK_CHANGE_AUTOMATIC       --> aktiv
    EFF_DYN_SPORT_CID            --> aktiv
    EFF_DYN_SPORT_UNIT           --> aktiv
    EFF_DYN_SAILING              --> aktiv
    AKT_AUTO_LENKRADHEIZUNG      --> nicht_aktiv (because it doesn't work but it would be cool, otherwise set to aktiv)
    AKT_AUTO_SITZE_FRONT         --> nicht_aktiv (because it doesn't work but it would be cool, otherwise set to heizung)

Hi, i have a bmw f30 LCI 2018 with entrynav2 system and want to upgrade to the NBTEvo headunit so I can have the upgraded Bluetooth and carplay and also add the G30 10.25" screen. What head unit and coding would be needed or is this even possible. Thanks in advance. This is my first time posting here.

[stevenkoiter]

Hi,

This thread has given me a lot of info on how to retrofit the NBT evo, but I'm struggling to get it working on my car.

I'll try to be as specific as possible, but my knowledge of e-sys and coding is limited.

I have an F20 from march 2013 with the entrynav system.
-E-sys 3.30.1 (with E-sys launcher PRO)
-Full psdzdata 4.36.22 (external drive mklink to C:\Data)
-NBT evo with 8.8 inch touch screen and I-drive controller and OABR adapter cable and wifi antenna.

After disconnecting the car battery I installed the NBT evo set and reconnected the battery. The screen started, touch worked, but the I-drive did not. Rebooting the HU by holding the powerbutton made the screen stay permanently black and I couldn't get it starting.

I started E-sys and connected to the car and made the following steps.
-Expert Mode > FSC-Extended - changed VIN of 0x63 to my car VIN
-Expert Mode > Coding > Vehicle Order > Read (saved)

Edit VO with FA-Editor by
-changing 606 to 609 and removed 6NH (I can later add 6CP, 6NH and 6NK) save changes
-Expert Mode - Coding > activate FA and SVT Actual - Read ECU
-Select HU_NBT > KIS/SVT Target > Detect CAF for SWE and select latest
-Right click HU_NBT > Code

This is were I get the following error

Caf's suchen
Tal wird generiert
Abarbeitung wird gestartet

Read SVT before TAL execution started.
Read SVT before TAL execution finished.

TAL execution started.
VCM Update: VCM-Update is deactivated. VCM will not be updated. [C197]
ExecutionID=2026/02/10-23:16:56.249
[] prepareTALExecution started [PROGRESS]
[] prepareTALExecution finished [PROGRESS]
[] prepareVehicleForCoding started [PROGRESS]
[] prepareVehicleForCoding finished [PROGRESS]
[HU_NBT2 - 63] prepareECUforCoding started [PROGRESS]
[] Errors during NCD generation for CAF cafd_00001ef6-006_040_006: 
DataGroup ., Function .: More than one condition parameter is active: [., .] [THROWABLE]
[HU_NBT2 - 63] There was an error during TAL execution, please check the log files. [WARN]
[HU_NBT2 - 63] - [Exception - UNKNOWN] Errors during NCD generation for CAF cafd_00001ef6-006_040_006: 
DataGroup ., Function .: More than one condition parameter is active: [., .]
[HU_NBT2 - 63] finalizeECUCoding started [PROGRESS]
[HU_NBT2 - 63] finalizeECUCoding finished [PROGRESS]
[] finalizeVehicleCoding started [PROGRESS]
[] finalizeVehicleCoding finished [PROGRESS]
[] finalizeTALExecution started [PROGRESS]
[] finalizeTALExecution finished [PROGRESS]
TAL execution finished [TAL_EXECUTION_FINISHED]
TAL-Execution finished with status: "FinishedWithError". [C207]
TAL execution finished. Duration: "12s". [C206]

Read SVT after TAL execution started.
Read SVT after TAL execution finished.
Abarbeitung beendet

I feel I'm missing some steps, but not sure which. Chatgpt gave me conflicting answers, so I'm hoping you guys can point me in the right direction.

[shawnsheridan]

Originally Posted by stevenkoiter

Hi,

This thread has given me a lot of info on how to retrofit the NBT evo, but I'm struggling to get it working on my car.

I'll try to be as specific as possible, but my knowledge of e-sys and coding is limited.

I have an F20 from march 2013 with the entrynav system.
-E-sys 3.30.1 (with E-sys launcher PRO)
-Full psdzdata 4.36.22 (external drive mklink to C:\Data)
-NBT evo with 8.8 inch touch screen and I-drive controller and OABR adapter cable and wifi antenna.

After disconnecting the car battery I installed the NBT evo set and reconnected the battery. The screen started, touch worked, but the I-drive did not. Rebooting the HU by holding the powerbutton made the screen stay permanently black and I couldn't get it starting.

I started E-sys and connected to the car and made the following steps.
-Expert Mode > FSC-Extended - changed VIN of 0x63 to my car VIN
-Expert Mode > Coding > Vehicle Order > Read (saved)

Edit VO with FA-Editor by
-changing 606 to 609 and removed 6NH (I can later add 6CP, 6NH and 6NK) save changes
-Expert Mode - Coding > activate FA and SVT Actual - Read ECU
-Select HU_NBT > KIS/SVT Target > Detect CAF for SWE and select latest
-Right click HU_NBT > Code

This is were I get the following error

Caf's suchen
Tal wird generiert
Abarbeitung wird gestartet

Read SVT before TAL execution started.
Read SVT before TAL execution finished.

TAL execution started.
VCM Update: VCM-Update is deactivated. VCM will not be updated. [C197]
ExecutionID=2026/02/10-23:16:56.249
[] prepareTALExecution started [PROGRESS]
[] prepareTALExecution finished [PROGRESS]
[] prepareVehicleForCoding started [PROGRESS]
[] prepareVehicleForCoding finished [PROGRESS]
[HU_NBT2 - 63] prepareECUforCoding started [PROGRESS]
[] Errors during NCD generation for CAF cafd_00001ef6-006_040_006: 
DataGroup ., Function .: More than one condition parameter is active: [., .] [THROWABLE]
[HU_NBT2 - 63] There was an error during TAL execution, please check the log files. [WARN]
[HU_NBT2 - 63] - [Exception - UNKNOWN] Errors during NCD generation for CAF cafd_00001ef6-006_040_006: 
DataGroup ., Function .: More than one condition parameter is active: [., .]
[HU_NBT2 - 63] finalizeECUCoding started [PROGRESS]
[HU_NBT2 - 63] finalizeECUCoding finished [PROGRESS]
[] finalizeVehicleCoding started [PROGRESS]
[] finalizeVehicleCoding finished [PROGRESS]
[] finalizeTALExecution started [PROGRESS]
[] finalizeTALExecution finished [PROGRESS]
TAL execution finished [TAL_EXECUTION_FINISHED]
TAL-Execution finished with status: "FinishedWithError". [C207]
TAL execution finished. Duration: "12s". [C206]

Read SVT after TAL execution started.
Read SVT after TAL execution finished.
Abarbeitung beendet

I feel I'm missing some steps, but not sure which. Chatgpt gave me conflicting answers, so I'm hoping you guys can point me in the right direction.

There is conflict in FA. "Changing 606 to 609 and removed 6NH" is all you did?

Did you change FA Zeitkriterium field to where 609 is an EVO ID5/6 build date, something like 0318?

[stevenkoiter]

Thanks Shawn, I'll try this and come back and post the results!

[stevenkoiter]

So I changed the "Zeitkriterium" to 0318 and continued with only changing salapa 606 to 609 and removed 6NH.

Following the same steps I get the following error.

Caf's suchen
Tal wird generiert
Abarbeitung wird gestartet

Read SVT before TAL execution started.
Read SVT before TAL execution finished.

TAL execution started.
VCM Update: VCM-Update is deactivated. VCM will not be updated. [C197]
ExecutionID=2026/02/13-20:45:22.510
[] prepareTALExecution started [PROGRESS]
[] prepareTALExecution finished [PROGRESS]
[] prepareVehicleForCoding started [PROGRESS]
[] prepareVehicleForCoding finished [PROGRESS]
[HU_NBT2 - 63] prepareECUforCoding started [PROGRESS]
[HU_NBT2 - 63] prepareECUforCoding finished [PROGRESS]
[HU_NBT2 - 63] authenticateECUforCoding started [PROGRESS]
[HU_NBT2 - 63] authenticateECUforCoding finished [PROGRESS]
[HU_NBT2 - 63 - cafd_00001ef6-006_040_006] Transaction type: cdDeploy;  Message: TA started [TRANSACTION]
MCDDiagService<id=62649, job=com.bmw.psdz.jobs.uds.MCD3_PerformECUCoding, service=WDBI_PLAIN - WriteDataByIdentifier with unlimited Data-ID (plain hex value), description=error: negative response : requestOutOfRange, link=HU_NBT2_63_ETHERNET> [DIAGSERVICE]
[] job failed with negative response error: 
 code: repeat job
 description: Service WDBI_PLAIN returned a negative response with response code requestOutOfRange; LinkName: HU_NBT2_63_ETHERNET
 severity: ERROR
 [THROWABLE]
[HU_NBT2 - 63 - cafd_00001ef6-006_040_006] Transaction type: cdDeploy;  Message: TA finished [TRANSACTION]
[HU_NBT2 - 63] -MessageID is used multiple times, so MessageText may be ambiguous-job failed with negative response error: 
 code: repeat job
 description: Service WDBI_PLAIN returned a negative response with response code requestOutOfRange; LinkName: HU_NBT2_63_ETHERNET
 severity: ERROR
 [WARN]
[HU_NBT2 - 63] - [Exception - HU_NBT2 - 63] job failed with negative response error: 
 code: repeat job
 description: Service WDBI_PLAIN returned a negative response with response code requestOutOfRange; LinkName: HU_NBT2_63_ETHERNET
 severity: ERROR

[HU_NBT2 - 63] prepareECUforCoding started [PROGRESS]
MCDDiagService<id=230634, job=com.bmw.psdz.jobs.uds.MCD3_PrepareECUforCoding, service=DSC - DiagnosticSessionControl, description=error: negative response : conditionsNotCorrect, link=HU_NBT2_63_ETHERNET> [DIAGSERVICE]
[HU_NBT2 - 63] prepareECUforCoding finished [PROGRESS]
[HU_NBT2 - 63] authenticateECUforCoding started [PROGRESS]
MCDDiagService<id=16727, job=com.bmw.psdz.jobs.uds.MCD3_AuthenticateECUforCoding, service=SA_SK - SecurityAccessSendKey, description=error: negative response : serviceNotSupportedInActiveSession, link=HU_NBT2_63_ETHERNET> [DIAGSERVICE]
[] job failed with negative response error: 
 code: service returned global negative response
 description: Service SA_SK returned a negative response with response code serviceNotSupportedInActiveSession; LinkName: HU_NBT2_63_ETHERNET
 severity: ERROR
 [THROWABLE]
[HU_NBT2 - 63] There was an error during TAL execution, please check the log files. [WARN]
[HU_NBT2 - 63] There was an error during TAL execution, please check the log files. [WARN]
[HU_NBT2 - 63] - [Exception - HU_NBT2 - 63] job failed with negative response error: 
 code: service returned global negative response
 description: Service SA_SK returned a negative response with response code serviceNotSupportedInActiveSession; LinkName: HU_NBT2_63_ETHERNET
 severity: ERROR

[HU_NBT2 - 63] finalizeECUCoding started [PROGRESS]
[HU_NBT2 - 63] finalizeECUCoding finished [PROGRESS]
[] There was an error, please check the log files. [WARN]
[] - [Exception - HU_NBT2 - 63] job failed with negative response error: 
 code: service returned global negative response
 description: Service SA_SK returned a negative response with response code serviceNotSupportedInActiveSession; LinkName: HU_NBT2_63_ETHERNET
 severity: ERROR

[] finalizeVehicleCoding started [PROGRESS]
[] finalizeVehicleCoding finished [PROGRESS]
[] finalizeTALExecution started [PROGRESS]
[] finalizeTALExecution finished [PROGRESS]
TAL execution finished [TAL_EXECUTION_FINISHED]
TAL-Execution finished with status: "FinishedWithError". [C207]
TAL execution finished. Duration: "12s". [C206]

Read SVT after TAL execution started.
Read SVT after TAL execution finished.
Abarbeitung beendet

Transaktions-Report:       Aktion: Codieren


HU_NBT2 [63]
cdDeploy FinishedWithError
   cafd_00001ef6-006_040_006 NotExecutable

Edited FA

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<faList>
    <id name="">
        <comment/>
        <ns1:fa xmlns:ns1="http://bmw.com/2005/psdz.data.fa">
            <ns1:header createdBy="" date="2026-02-13+01:00" time="20:22:22" vinLong="WBA1B71040J039199"/>
            <ns1:standardFA colourCode="0B45" faVersion="3" fabricCode="HAAT" series="F020" timeCriteria="0318" typeKey="1B71">
                <ns1:eCodes>
                    <ns1:eCode>A080</ns1:eCode>
                </ns1:eCodes>
                <ns1:saCodes>
                    <ns1:saCode>1CA</ns1:saCode>
                    <ns1:saCode>1CB</ns1:saCode>
                    <ns1:saCode>230</ns1:saCode>
                    <ns1:saCode>249</ns1:saCode>
                    <ns1:saCode>2NH</ns1:saCode>
                    <ns1:saCode>2PG</ns1:saCode>
                    <ns1:saCode>2VF</ns1:saCode>
                    <ns1:saCode>2VL</ns1:saCode>
                    <ns1:saCode>320</ns1:saCode>
                    <ns1:saCode>423</ns1:saCode>
                    <ns1:saCode>428</ns1:saCode>
                    <ns1:saCode>481</ns1:saCode>
                    <ns1:saCode>493</ns1:saCode>
                    <ns1:saCode>494</ns1:saCode>
                    <ns1:saCode>4AE</ns1:saCode>
                    <ns1:saCode>4DX</ns1:saCode>
                    <ns1:saCode>4MR</ns1:saCode>
                    <ns1:saCode>4NE</ns1:saCode>
                    <ns1:saCode>502</ns1:saCode>
                    <ns1:saCode>508</ns1:saCode>
                    <ns1:saCode>521</ns1:saCode>
                    <ns1:saCode>522</ns1:saCode>
                    <ns1:saCode>534</ns1:saCode>
                    <ns1:saCode>544</ns1:saCode>
                    <ns1:saCode>548</ns1:saCode>
                    <ns1:saCode>563</ns1:saCode>
                    <ns1:saCode>575</ns1:saCode>
                    <ns1:saCode>609</ns1:saCode>
                    <ns1:saCode>698</ns1:saCode>
                    <ns1:saCode>710</ns1:saCode>
                    <ns1:saCode>715</ns1:saCode>
                    <ns1:saCode>760</ns1:saCode>
                    <ns1:saCode>775</ns1:saCode>
                    <ns1:saCode>7VB</ns1:saCode>
                    <ns1:saCode>7VW</ns1:saCode>
                    <ns1:saCode>801</ns1:saCode>
                    <ns1:saCode>851</ns1:saCode>
                    <ns1:saCode>879</ns1:saCode>
                    <ns1:saCode>8KA</ns1:saCode>
                    <ns1:saCode>8V1</ns1:saCode>
                </ns1:saCodes>
                <ns1:hoCodes/>
            </ns1:standardFA>
        </ns1:fa>
    </id>
</faList>

All help is appreciated

[shawnsheridan]

Originally Posted by stevenkoiter

So I changed the "Zeitkriterium" to 0318 and continued with only changing salapa 606 to 609 and removed 6NH.

Following the same steps I get the following error.

Caf's suchen
Tal wird generiert
Abarbeitung wird gestartet

Read SVT before TAL execution started.
Read SVT before TAL execution finished.

TAL execution started.
VCM Update: VCM-Update is deactivated. VCM will not be updated. [C197]
ExecutionID=2026/02/13-20:45:22.510
[] prepareTALExecution started [PROGRESS]
[] prepareTALExecution finished [PROGRESS]
[] prepareVehicleForCoding started [PROGRESS]
[] prepareVehicleForCoding finished [PROGRESS]
[HU_NBT2 - 63] prepareECUforCoding started [PROGRESS]
[HU_NBT2 - 63] prepareECUforCoding finished [PROGRESS]
[HU_NBT2 - 63] authenticateECUforCoding started [PROGRESS]
[HU_NBT2 - 63] authenticateECUforCoding finished [PROGRESS]
[HU_NBT2 - 63 - cafd_00001ef6-006_040_006] Transaction type: cdDeploy;  Message: TA started [TRANSACTION]
MCDDiagService<id=62649, job=com.bmw.psdz.jobs.uds.MCD3_PerformECUCoding, service=WDBI_PLAIN - WriteDataByIdentifier with unlimited Data-ID (plain hex value), description=error: negative response : requestOutOfRange, link=HU_NBT2_63_ETHERNET> [DIAGSERVICE]
[] job failed with negative response error: 
 code: repeat job
 description: Service WDBI_PLAIN returned a negative response with response code requestOutOfRange; LinkName: HU_NBT2_63_ETHERNET
 severity: ERROR
 [THROWABLE]
[HU_NBT2 - 63 - cafd_00001ef6-006_040_006] Transaction type: cdDeploy;  Message: TA finished [TRANSACTION]
[HU_NBT2 - 63] -MessageID is used multiple times, so MessageText may be ambiguous-job failed with negative response error: 
 code: repeat job
 description: Service WDBI_PLAIN returned a negative response with response code requestOutOfRange; LinkName: HU_NBT2_63_ETHERNET
 severity: ERROR
 [WARN]
[HU_NBT2 - 63] - [Exception - HU_NBT2 - 63] job failed with negative response error: 
 code: repeat job
 description: Service WDBI_PLAIN returned a negative response with response code requestOutOfRange; LinkName: HU_NBT2_63_ETHERNET
 severity: ERROR

[HU_NBT2 - 63] prepareECUforCoding started [PROGRESS]
MCDDiagService<id=230634, job=com.bmw.psdz.jobs.uds.MCD3_PrepareECUforCoding, service=DSC - DiagnosticSessionControl, description=error: negative response : conditionsNotCorrect, link=HU_NBT2_63_ETHERNET> [DIAGSERVICE]
[HU_NBT2 - 63] prepareECUforCoding finished [PROGRESS]
[HU_NBT2 - 63] authenticateECUforCoding started [PROGRESS]
MCDDiagService<id=16727, job=com.bmw.psdz.jobs.uds.MCD3_AuthenticateECUforCoding, service=SA_SK - SecurityAccessSendKey, description=error: negative response : serviceNotSupportedInActiveSession, link=HU_NBT2_63_ETHERNET> [DIAGSERVICE]
[] job failed with negative response error: 
 code: service returned global negative response
 description: Service SA_SK returned a negative response with response code serviceNotSupportedInActiveSession; LinkName: HU_NBT2_63_ETHERNET
 severity: ERROR
 [THROWABLE]
[HU_NBT2 - 63] There was an error during TAL execution, please check the log files. [WARN]
[HU_NBT2 - 63] There was an error during TAL execution, please check the log files. [WARN]
[HU_NBT2 - 63] - [Exception - HU_NBT2 - 63] job failed with negative response error: 
 code: service returned global negative response
 description: Service SA_SK returned a negative response with response code serviceNotSupportedInActiveSession; LinkName: HU_NBT2_63_ETHERNET
 severity: ERROR

[HU_NBT2 - 63] finalizeECUCoding started [PROGRESS]
[HU_NBT2 - 63] finalizeECUCoding finished [PROGRESS]
[] There was an error, please check the log files. [WARN]
[] - [Exception - HU_NBT2 - 63] job failed with negative response error: 
 code: service returned global negative response
 description: Service SA_SK returned a negative response with response code serviceNotSupportedInActiveSession; LinkName: HU_NBT2_63_ETHERNET
 severity: ERROR

[] finalizeVehicleCoding started [PROGRESS]
[] finalizeVehicleCoding finished [PROGRESS]
[] finalizeTALExecution started [PROGRESS]
[] finalizeTALExecution finished [PROGRESS]
TAL execution finished [TAL_EXECUTION_FINISHED]
TAL-Execution finished with status: "FinishedWithError". [C207]
TAL execution finished. Duration: "12s". [C206]

Read SVT after TAL execution started.
Read SVT after TAL execution finished.
Abarbeitung beendet

Transaktions-Report:       Aktion: Codieren


HU_NBT2 [63]
cdDeploy FinishedWithError
   cafd_00001ef6-006_040_006 NotExecutable

Edited FA

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<faList>
    <id name="">
        <comment/>
        <ns1:fa xmlns:ns1="http://bmw.com/2005/psdz.data.fa">
            <ns1:header createdBy="" date="2026-02-13+01:00" time="20:22:22" vinLong="WBA1B71040J039199"/>
            <ns1:standardFA colourCode="0B45" faVersion="3" fabricCode="HAAT" series="F020" timeCriteria="0318" typeKey="1B71">
                <ns1:eCodes>
                    <ns1:eCode>A080</ns1:eCode>
                </ns1:eCodes>
                <ns1:saCodes>
                    <ns1:saCode>1CA</ns1:saCode>
                    <ns1:saCode>1CB</ns1:saCode>
                    <ns1:saCode>230</ns1:saCode>
                    <ns1:saCode>249</ns1:saCode>
                    <ns1:saCode>2NH</ns1:saCode>
                    <ns1:saCode>2PG</ns1:saCode>
                    <ns1:saCode>2VF</ns1:saCode>
                    <ns1:saCode>2VL</ns1:saCode>
                    <ns1:saCode>320</ns1:saCode>
                    <ns1:saCode>423</ns1:saCode>
                    <ns1:saCode>428</ns1:saCode>
                    <ns1:saCode>481</ns1:saCode>
                    <ns1:saCode>493</ns1:saCode>
                    <ns1:saCode>494</ns1:saCode>
                    <ns1:saCode>4AE</ns1:saCode>
                    <ns1:saCode>4DX</ns1:saCode>
                    <ns1:saCode>4MR</ns1:saCode>
                    <ns1:saCode>4NE</ns1:saCode>
                    <ns1:saCode>502</ns1:saCode>
                    <ns1:saCode>508</ns1:saCode>
                    <ns1:saCode>521</ns1:saCode>
                    <ns1:saCode>522</ns1:saCode>
                    <ns1:saCode>534</ns1:saCode>
                    <ns1:saCode>544</ns1:saCode>
                    <ns1:saCode>548</ns1:saCode>
                    <ns1:saCode>563</ns1:saCode>
                    <ns1:saCode>575</ns1:saCode>
                    <ns1:saCode>609</ns1:saCode>
                    <ns1:saCode>698</ns1:saCode>
                    <ns1:saCode>710</ns1:saCode>
                    <ns1:saCode>715</ns1:saCode>
                    <ns1:saCode>760</ns1:saCode>
                    <ns1:saCode>775</ns1:saCode>
                    <ns1:saCode>7VB</ns1:saCode>
                    <ns1:saCode>7VW</ns1:saCode>
                    <ns1:saCode>801</ns1:saCode>
                    <ns1:saCode>851</ns1:saCode>
                    <ns1:saCode>879</ns1:saCode>
                    <ns1:saCode>8KA</ns1:saCode>
                    <ns1:saCode>8V1</ns1:saCode>
                </ns1:saCodes>
                <ns1:hoCodes/>
            </ns1:standardFA>
        </ns1:fa>
    </id>
</faList>

All help is appreciated

I would add 6NS.

What E-Sys and PSdZData versions are you using?

Are you using any E-Sys Launcher?

[stevenkoiter]

I'm using E-sys 3.30.1 with launcher and Full psdzdata 4.36.22.

Should I try without launcher?

[shawnsheridan]

Originally Posted by stevenkoiter

I'm using E-sys 3.30.1 with launcher and Full psdzdata 4.36.22.

Should I try without launcher?

Yes. Never flash with any Launcher.

[BeamerAR15]

What’s the purpose of a launcher ?
Why use it ?

[stevenkoiter]

Tried again today.

As suggested started E-sys without launcher and set FA with 609, 6CP, 6NS and set zeitkriterium at 0318. Annoyingly got the same error. I'm thinking maybe something could be wrong with my psdzdata 🤷*♂️

[shawnsheridan]

Originally Posted by BeamerAR15

What’s the purpose of a launcher ?
Why use it ?

Today, there is really no purpose, as E-Sys beginning with Version 3.34.0 no longer requires an .est Token, and the CAFD Mapping Database in E-Sys LauncherPRO has not been updated since 2017.

[shawnsheridan]

Originally Posted by stevenkoiter

Tried again today.

As suggested started E-sys without launcher and set FA with 609, 6CP, 6NS and set zeitkriterium at 0318. Annoyingly got the same error. I'm thinking maybe something could be wrong with my psdzdata 🤷*♂️

Try the latest E-Sys and PSdZData. PM sent.