09-21-2014, 05:43 PM | #1 |
Lieutenant Colonel
541
Rep 1,894
Posts |
Reading NBT donor VIN & Software level
Hi all,
I'd like to know what is the donor VIN is for my NBT and the current software version? Anyone point me the right direction? Thanks. |
09-21-2014, 11:16 PM | #2 |
General
10411
Rep 40,635
Posts
Drives: 2018 Alpina B6 650ix GC
Join Date: Feb 2010
Location: Houston, TX
|
You can go to Comfort Mode => FSC => Check FSC Status, and at the top of the Log report it will show the Head Unit VIN.
There is no way though to know what I-Level a used ECU is at.
__________________
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
|
09-22-2014, 05:49 PM | #3 |
Lieutenant Colonel
541
Rep 1,894
Posts |
Thanks for that, now I have the donor VIN. Will use your contact to get the latest euro maps, but prob will wait for the 2015 ones to come out first.
Also it looks like my NBT has the FSC codes for 6NR. Tried it but the iOS app just keep on bleeping at me. Bugger that, just removed it. |
Appreciate
0
|
09-22-2014, 06:20 PM | #4 |
General
10411
Rep 40,635
Posts
Drives: 2018 Alpina B6 650ix GC
Join Date: Feb 2010
Location: Houston, TX
|
If NBT has a 9C FSC Code with Status "Accepted", then BMW Apps should work.
__________________
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
|
02-27-2016, 07:19 AM | #5 |
Private
5
Rep 51
Posts |
Error
I'm trying to read my donor vin. Does it have to be done with the emulator unplugged?
I am getting error. Getting SWT Status for ecu null failed C056 Openecuconnection for link FEM BODY 40 Ethernet failed with error MCDError severity 2051, error code 49184, description object with name not found vendor code 3, vendor description provided name FEM BODY 40 Ethernet doesn't map to an item. |
Appreciate
0
|
02-27-2016, 09:08 AM | #6 |
General
10411
Rep 40,635
Posts
Drives: 2018 Alpina B6 650ix GC
Join Date: Feb 2010
Location: Houston, TX
|
You have selected either incorrect E-Sys Launcher Car Series or E-Sys Connection Target.
__________________
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
|
02-27-2016, 12:40 PM | #7 | |
Private
5
Rep 51
Posts |
Quote:
So the donor has: 6AC,6AE,6AK,6AM,6AN,6AP,6NS,6WB,609. I already have the nav working, but issues with the Bluetooth. If I code all the above, it won't break anything? It just won't work if it can't, correct? Last edited by Maroondestroyer; 02-27-2016 at 01:05 PM.. |
|
Appreciate
0
|
02-27-2016, 02:25 PM | #8 |
Private
5
Rep 51
Posts |
Caf's suchen
Tal wird generiert Abarbeitung wird gestartet TAL execution started. ExecutionID=2016/02/27-20:20:55.295 [] prepareTALExecution started [] prepareTALExecution finished [] prepareVehicleForCoding started [] prepareVehicleForCoding finished [HU_NBT - 63] prepareECUforCoding started [HU_NBT - 63] There was an error during TAL execution, please check the log files. [HU_NBT - 63] - [Exception - UNKNOWN] Errors during NCD generation for CAF cafd_00000ded-003_015_013: DataGroup ., Function .: More than one condition parameter is active: [., .] [HU_NBT - 63] finalizeECUCoding started [HU_NBT - 63] finalizeECUCoding finished [] finalizeVehicleCoding started [] finalizeVehicleCoding finished [] finalizeTALExecution started [] finalizeTALExecution finished TAL execution finished TAL-Execution finished with status: "FinishedWithError". [C207] TAL execution finished. Duration: "17s". [C206] Abarbeitung beendet problem after problem. I should maybe take up collecting shells instead. |
Appreciate
0
|
02-27-2016, 02:30 PM | #9 |
General
10411
Rep 40,635
Posts
Drives: 2018 Alpina B6 650ix GC
Join Date: Feb 2010
Location: Houston, TX
|
You have redundant or incompatible Option Codes or FDL 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
|
02-27-2016, 02:35 PM | #10 |
Private
5
Rep 51
Posts |
|
Appreciate
0
|
02-27-2016, 02:45 PM | #11 | |
General
10411
Rep 40,635
Posts
Drives: 2018 Alpina B6 650ix GC
Join Date: Feb 2010
Location: Houston, TX
|
Quote:
Did you remove original Radio / Nav Option Code from FA before adding 609? Do you have only one Bluetooth Option in FA?
__________________
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
|
02-27-2016, 03:12 PM | #12 |
Private
5
Rep 51
Posts |
https://www.flickr.com/photos/140571.../in/datetaken/
That is donor. https://www.flickr.com/photos/140571.../in/datetaken/ That is mine. I will have to see if there is any conflicting in FA once I understand them. I just changed 606 to 609 after install. I will have to research what the different Bluetooth options are first yo see what's listed in FA. I think I just changed 606 to 609. Then, changed 6NK to 6NS. I will check in the morning again. Just when you think you know what you're doing lol. |
Appreciate
0
|
02-27-2016, 03:58 PM | #13 |
Private
5
Rep 51
Posts |
[] There was an error, please check the log files.
MSM update finished with error. [C217] Error in MSM Update: Error during MSM update. [C214] Errors: TSL distribution failed due to an error: The following ECUs are missing from the TSL because they did not respond: 0x36; FsCSM with diagnostic address 0x36 reports error: error code: ERC_MSM_INVALID_TRANSPORT_LIST, specific error code: empty (F30 key exchange) [1352][] - [Exception - MSM - 10] Errors: TSL distribution failed due to an error: The following ECUs are missing from the TSL because they did not respond: 0x36; FsCSM with diagnostic address 0x36 reports error: error code: ERC_MSM_INVALID_TRANSPORT_LIST, specific error code: empty (F30 key exchange) Sorry, now this. there was conflicting bluetooth codes. but now this. |
Appreciate
0
|
02-27-2016, 04:53 PM | #14 |
Private
5
Rep 51
Posts |
Baby steps.
Tried listing as per donor unit to get Bluetooth working. https://www.flickr.com/photos/140571...posted-public/ In Bluetooth options, it only lists telephone 1 as the function. No choices to configure it. Microphone doesn't seem to work either for voice commands. Any one got a spare match?? |
Appreciate
0
|
04-21-2016, 01:24 PM | #16 |
Registered
0
Rep 3
Posts |
retrofittednbt update
hello everyone,
maybe i missed the posts but i want to ask something. i had my donor nbt coded someone else. then there is an update but i think i need to find my donor serial (or i dont know what to find) to update the nbt then code it to myself. are there any guide, anything to follow as a procedure to update a retrofitted nbt ? |
Appreciate
0
|
06-16-2016, 05:03 AM | #18 | |
Captain
93
Rep 713
Posts |
Quote:
Is this also possible when you have NBT reetrofitted in Exx? Is it possible to read it from ECU only? I have connection with HU_NBT unit through ESYS in my E60 but not sure if the way you described will work with Exx car and NBT? Do you have any experience with it? I'm not able to check it now that's why I'm asking, cuse maybe there is some otherw way to read VIN from NBT unit.
__________________
Click "Appreciate" if I helped you.
|
|
Appreciate
0
|
06-16-2016, 05:19 AM | #19 | |
General
10411
Rep 40,635
Posts
Drives: 2018 Alpina B6 650ix GC
Join Date: Feb 2010
Location: Houston, TX
|
Quote:
Are you able to connect but just cant read FSC or you can;t even connect?
__________________
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
|
02-07-2017, 07:38 AM | #20 |
New Member
0
Rep 6
Posts |
Coding headunit with Donor Vin
Hi Shawn, just retrofitted NBT into my BMW. I am using an emulator and Donor VIN however my Sat Nav is not showing the correct location. Just wondering to I need to code the head unit and if so will I lose the Donor VIN?
|
Appreciate
0
|
02-07-2017, 10:24 AM | #21 |
General
10411
Rep 40,635
Posts
Drives: 2018 Alpina B6 650ix GC
Join Date: Feb 2010
Location: Houston, TX
|
Normal Coding should not affect GPS Positioning. This is crappy GPS Aerial or you have newer NBT without Gyro Sensor or Gyro Sensor not coded correctly. To code NBT though, I would use special FA with VIN changed to match Donor VIN of NBT.
__________________
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
|
05-24-2018, 12:36 PM | #22 |
Registered
0
Rep 3
Posts |
I purchased a 2016 HU to replace my pre July 2014 HU, what are the steps to code the head unit? When I installed the HU it worked initially but after restarting car the ECU locked the HU? I'm doing this in order for me to take out the stretched resolution when installing bimmertech vividscreen and apple carplay.
Thanks! |
Appreciate
0
|
Post Reply |
Bookmarks |
Thread Tools | Search this Thread |
|
|