03-27-2020, 04:45 PM | #1 |
Lieutenant
170
Rep 468
Posts |
Flashed NBT but got errors!
Hi, I flashed my evo today which pretty much went successful but I got an error at the end.
I'll post the screenshot below. The NBT is working fine, the nav, etc. The main thing is I can't access Connected drive and It will not connected to BMW servers, therefore I dont have any if the apps nor my Carplay is working. I went from J to S. Can someone please help? log: HU_NBT2 - 63 - ibad_00002710-007_005_013] Transaction type: ibaDeploy; Message: 100% progress on ECUId:HU_NBT2_0x63 [100% of ibad_00002710-007_005_013] [TRANSACTION] [HU_NBT2 - 63 - ibad_00002710-007_005_013] Transaction type: ibaDeploy; Message: TA finished [TRANSACTION] [HU_NBT2 - 63] finalizeECUFlash started [PROGRESS] [HU_NBT2 - 63] finalizeECUFlash finished [PROGRESS] [] finalizeVehicleFlash started [PROGRESS] [] finalizeVehicleFlash finished [PROGRESS] [] prepareVehicleForCoding started [PROGRESS] [] prepareVehicleForCoding finished [PROGRESS] [HU_NBT2 - 63] prepareECUforCoding started [PROGRESS] [] Errors during NCD generation for CAF cafd_00001ef6-006_048_013: 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_048_013: 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: "52min 18s". [C206] Read SVT after TAL execution started. Read SVT after TAL execution finished. |
03-27-2020, 04:56 PM | #2 |
New BMW owner
139
Rep 621
Posts
Drives: BMW 316d, BMW F40 116d
Join Date: Jan 2012
Location: Belgium
|
What Esys version are you running?
|
Appreciate
0
|
03-27-2020, 04:59 PM | #4 |
New BMW owner
139
Rep 621
Posts
Drives: BMW 316d, BMW F40 116d
Join Date: Jan 2012
Location: Belgium
|
Use 3.27.1
Use 3.30 to make your Tal execution but use 3.27.1 to start the flashing. Don't know why but 3.27.1 is the best Esys version to flash NBT. |
Appreciate
0
|
03-27-2020, 05:09 PM | #5 | |
Lieutenant
170
Rep 468
Posts |
Quote:
I will try tomorrow again with the 3.27 and see what happens |
|
Appreciate
0
|
03-27-2020, 08:05 PM | #6 |
Lieutenant
170
Rep 468
Posts |
Also could someone pls tell me why do I have hardware difference sign at the ATM module?
All parts are OE and nothing has been retrofitted at all. The only retrofit was via VO coding 6CP, 6NS and 6NR Would this be the problem? shawnsheridan could you please take a look? Many Thanks |
Appreciate
0
|
03-27-2020, 08:22 PM | #7 | |
General
10445
Rep 40,765
Posts
Drives: 2018 Alpina B6 650ix GC
Join Date: Feb 2010
Location: Houston, TX
|
Quote:
Do you have for example both 6NH and 6NS in FA at same time?
__________________
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
|
03-27-2020, 08:27 PM | #8 | |
Lieutenant
170
Rep 468
Posts |
Quote:
Would this also cause the hardware difference symbol at the ATM module because of it? So I guess, remove the 6NS, and the flash again? Thanks so much! |
|
Appreciate
0
|
03-27-2020, 08:35 PM | #9 | |
General
10445
Rep 40,765
Posts
Drives: 2018 Alpina B6 650ix GC
Join Date: Feb 2010
Location: Houston, TX
|
Quote:
Do not worry about the Red/Blue folders. This is not hardware differences. |
|
Appreciate
0
|
03-27-2020, 08:39 PM | #10 | ||
Lieutenant
170
Rep 468
Posts |
Quote:
The ATM module had the green recycle symbol beside, which I presume was also due to wrong VO. Thanks again Click on the photo to enlarge, the ATM is above |
||
Appreciate
0
|
03-28-2020, 01:45 PM | #11 |
Lieutenant
170
Rep 468
Posts |
Just in the process of the NBT flash and also FEM_GW as it was listed dependency.
I wanted the flash the ATM module aswell, but after VO coding the car back to stock the little hardware difference symbol was still there. So when selecting the ATM module for flashing, the window popped up about HWdeinstall?? How is it possible that esys is thinking there is hardware difference when this is the original part? Also what does the HWdeinstall option mean? Thank you |
Appreciate
0
|
03-28-2020, 04:23 PM | #12 | |
Lieutenant
170
Rep 468
Posts |
Quote:
I did that today. 2nd flash and still the same error. So I checked the FA again from VCM Read FA, and the old data is still there?? I once again edited the FA back to stock, calculate fa, save, load to VCM, Write FA, and its not taking it on?? What Im I doing wrong! Thanks |
|
Appreciate
0
|
03-28-2020, 04:26 PM | #13 | |
General
10445
Rep 40,765
Posts
Drives: 2018 Alpina B6 650ix GC
Join Date: Feb 2010
Location: Houston, TX
|
Quote:
__________________
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
1
xpro170.00 |
03-29-2020, 06:25 AM | #14 |
New BMW owner
139
Rep 621
Posts
Drives: BMW 316d, BMW F40 116d
Join Date: Jan 2012
Location: Belgium
|
Just a question.
Did you press SAVE FA to car in the VCM tab? |
Appreciate
0
|
03-29-2020, 08:25 AM | #15 |
Lieutenant
170
Rep 468
Posts |
Yes I did. The problem was as I VO coded the 6NS, while I already had 6NH and they conflicted during the flash.
However, as Im trying to follow Shawns instruction in the post above, unfortunately I cannot VO NBT ecu as the code button is greyed out after loading SVT ECU. First of all, the NBT doesn have cafd file aswell.. Any other steps I can try? Thanks |
Appreciate
0
|
03-29-2020, 08:28 AM | #16 | |
General
10445
Rep 40,765
Posts
Drives: 2018 Alpina B6 650ix GC
Join Date: Feb 2010
Location: Houston, TX
|
Quote:
__________________
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
|
03-29-2020, 08:30 AM | #17 | ||
Lieutenant
170
Rep 468
Posts |
Quote:
Other modules allow to VO code ecu, except NBT where is greyed out |
||
Appreciate
0
|
03-29-2020, 08:46 AM | #18 |
Colonel
588
Rep 2,302
Posts |
Assign a new CAFD and you can code the NBT.
|
Appreciate
0
|
03-29-2020, 08:56 AM | #19 | |
Lieutenant
170
Rep 468
Posts |
Quote:
Process repeated and this time code successful. I will flash the NBT again. 3rd time lucky they say! |
|
Appreciate
0
|
03-29-2020, 09:00 AM | #20 |
Lieutenant
170
Rep 468
Posts |
One question before I proceed.
I VO coded the car to factory option now. VCM loaded and write FA FP. When I try again to read from VCM im still getting the old VO codes?? How is this possible? |
Appreciate
0
|
03-29-2020, 09:05 AM | #21 |
Colonel
588
Rep 2,302
Posts |
The hook for updating the VCM in the settings isn't set.
|
Appreciate
0
|
03-29-2020, 09:07 AM | #22 | |
Lieutenant
170
Rep 468
Posts |
Quote:
So don't understand how VCM is giving old VO still? Thanks so much |
|
Appreciate
0
|
Post Reply |
Bookmarks |
|
|