BMW Forum - BimmerFest BMW Forums banner

HU_NBT2 Coding fails always

35K views 102 replies 29 participants last post by  syncroflash  
#1 ·
Hello, in my new M235i convertible coding the HU_NBT2 head unit always fails. VO coding and FDL coding (even without a change) both fails. All other head units can be coded without any problems, only HU_NBT2 has this problem.

I am using PSDzdata 55.4 and E-Sys 3.24.3

This is the error log:

Code:
Caf's werden gesucht
Tal wird generiert
NCD werden gelesen
FDL CAFD-00001EF6-06.09.34 signieren.
Abarbeitung wird gestartet

TAL-Abarbeitung gestartet.
ExecutionID=2015/05/16-15:30:23.754
[] "prepareTALExecution" wurde gestartet.
[] "prepareTALExecution" wurde beendet.
[] "prepareVehicleForCoding" wurde gestartet.
[] "prepareVehicleForCoding" wurde beendet.
[HU_NBT2 - 63] "prepareECUforCoding" wurde gestartet.
[HU_NBT2 - 63] "prepareECUforCoding" wurde beendet.
[HU_NBT2 - 63] "authenticateECUforCoding" wurde gestartet.
[HU_NBT2 - 63] "authenticateECUforCoding" wurde beendet.
[HU_NBT2 - 63 - cafd_00001ef6-006_009_052] Transaction type: cdDeploy;  Message: Transaktion wurde 

gestartet.
[HU_NBT2 - 63 - cafd_00001ef6-006_009_052] Transaction type: cdDeploy;  Message: Transaktion wurde beendet.
[HU_NBT2 - 63] Während der TAL-Abarbeitung ist ein Fehler aufgetreten, bitte überprüfen Sie die Log-Datei.
[HU_NBT2 - 63] "finalizeECUCoding" wurde gestartet.
[HU_NBT2 - 63] "finalizeECUCoding" wurde beendet.
[] "finalizeVehicleCoding" wurde gestartet.
[] "finalizeVehicleCoding" wurde beendet.
[] "finalizeTALExecution" wurde gestartet.
[] "finalizeTALExecution" wurde beendet.
TAL-Abarbeitung beendet.
TAL-Abarbeitung beendet mit Status: "FinishedWithErrorInTransaction". [C207]
TAL-Abarbeitung beendet. Dauer: "16s". [C206]
Abarbeitung beendet



Report: 

Transaktions-Report:       Aktion: FDL Codieren


HU_NBT2 [63]
cdDeploy ProcessedWithError
   cafd_00001ef6-006_009_052 ProcessedWithError
 
#45 ·
Hi Guys,

Was it just the EVO that had issues FDL coding with the earlier versions of esys launcher?
No, FEM_BODY in cars with 56.x have issues too.
 
#47 ·
Hi shaun

Hope you well buddy!

OK, does the latest launcher solve FEM issues also?
I think so, but I have no way to confirm it with my F10.
 
#48 · (Edited)
I'm using EsysLauncher 2.4.3 with esys 3.27.1 and psdzdata 57.1, but I am still not able to code the HU_NBT2 to activate enhanced bluetooth.

Edit-- Nevermind. I figured it out.
 
#49 ·
I'm using EsysLauncher 2.4.3 with esys 3.27.1 and psdzdata 57.1, but I am still not able to code the HU_NBT2 to activate enhanced bluetooth.

Edit-- Nevermind. I figured it out.
What was the issue and fix?
 
#50 · (Edited)
I'm having the same problem with my F36 (F020). Coding on HU_NBT2 and FEM_BODY gives back errors. I'm running E-sys with Launcher 2.4.2.82 and v.56.5_PSdZData_Lite. I noticed there is a newer Launcher version 2.4.3.85. I will install this one first and give it a go. In the mean time if somebody has some pointers for me, pls let me know.
 

Attachments

#53 ·
Similar issues over here. I recently got 2016 F30 LCI 340. Coding on HU_NBT2 and FEM_BODY gives back errors. Was using this setup and successfully coded 2015 F30 335 and all was good. Is there an updated package that allows coding of [HU_NBT2] + [FEM_BODY] on newer vehicle firmware?

If yes - can someone point me in the write direction?

Current Setup
- E-Sys_Setup_3_24_3_RC_b38445.exe
- ESysLauncherPremiumSetup_2.0.7_Build_54
- v.56.0_PSdZData_Lite

Many Thanks!
 
#54 ·
Try the latest everything.

PM sent,

If afterwards you still have NBT2 Coding error, post exact error.
 
#58 ·
#62 ·
Hello,

I'm also trying to install an NBT2 to my 2016 f22 m235i, when I try to read the coding data I get this msg:

file for "cafd_00001ef6-006_004_004" not found
What PSdZData version do you use?
 
#71 ·
I remember receiving a beta version of launcher and the newest pdzdata back in mid July, I was able to get my hunbt2 coded, but startup emblem never worked. I kept changing to variant 1 to display M logo but it never worked.
Another thing, I have a M235i post 3/15 model, whenever I tried to set the ASD to f80 following exactly what was done with other members who also have hk sound, my asd just turned off and I never heard m4 sound.
Have these issues been fixed?

Can someone help? Ive been trying to get asd to f80 and startup emblem to variant 1 and neither work. Everything else works though somehow
 
#72 ·
I remember receiving a beta version of launcher and the newest pdzdata back in mid July, I was able to get my hunbt2 coded, but startup emblem never worked. I kept changing to variant 1 to display M logo but it never worked.
Another thing, I have a M235i post 3/15 model, whenever I tried to set the ASD to f80 following exactly what was done with other members who also have hk sound, my asd just turned off and I never heard m4 sound.
Have these issues been fixed?

Can someone help? Ive been trying to get asd to f80 and startup emblem to variant 1 and neither work. Everything else works though somehow
Hi Daveslaine,

I have same problem, I am totally unable to change startup emblem. Don't mind what I code, I always get the Connected Drive logo at startup... I have coded many other things like tyre temperature but there are many things that I can't. I have the last everything I think thanks to Shawn but no success yet...
 
#74 ·
Hello, tried to code retrofitted NBT Evo in F30, error appeared(photo attached). After few hours Screen doesn't work at all(no signal), I'm unable to code HU_NBT2 now at all(photo attached). Need help.
SI B65 13 16 - Audio, Navigation, Monitors, Alarms, SRS

SITUATION
If an NBT-EVO head unit is swapped into a different vehicle it will enter a locked mode once it recognizes a different VIN.

This will require REPLACEMENT of the head unit to restore operation.

CAUSE
To prevent easy re-use of stolen Head units additional features are introduced with 11/15 ISTA/P software to bring NBT-EVO to a higher security level.

In NBT-EVO the mechanism is called ***8220;Trusted VIN***8221;