View Single Post
      06-05-2017, 09:35 AM   #27
v3n0m
Lieutenant
57
Rep
451
Posts

Drives: 2013 MCB M5
Join Date: Apr 2013
Location: Vancouver, BC

iTrader: (0)

Quote:
Originally Posted by Dracon View Post
Ok, so here's what I learned as part of my little project.

Apparently, there's two major variants of the NBT hardware itself in respect to the ports on the back for North America.

One of them has an additional 12pin connector above the quad lock and a Bright Orange ethernet port (direct ethernet connection to the RSE). These are for connecting to the RSE system if the vehicle is so equipped (like mine). The 12 pin connector carries video signal to the RSE module and the Bright Orange ethernet port connects the NBT to the RSE for communications.

Here's the back of the first unit I purchased which was from a 2014 M6

[IMG]http://i1301.photobucket.com/albums/...pswo7efgne.jpg[/IMG]

And the unit I purchased which was from a 2014 328i (which didn't have Rear Seat Entertainment). Note the additional connector and USB port.

[IMG]http://i1301.photobucket.com/albums/...psnfavdkyj.jpg[/IMG]

So after I got the right unit, the swap out was pretty simple in terms of hardware. Amazingly, it's very quick and easy to access the NBT on the 5-series. It only requires removal of the main dash trim and the front control panel.

Once the new NBT was installed, I had to change the VIN to my VIN, clear out all the previous vehicle's FSC codes and load in the FSC codes for my VIN in order to get all the features re-activated (Navigation, SiriusXM, BMW Apps, etc, etc).

Surprisingly enough, ISTA/P didn't seem to care that the 2014+ NBT was installed in the vehicle as even the 2014+ models are valid part numbers for the 2013 model of the 5-series. ISTA/P only complained about the fact I retrofitted the Touchbox module and the Touch iDrive controller, which was easily fixed in Expert Mode to reflash and recode the NBT to my VO.

After that, it was a matter to comparing the coding between a 2014 model and a 2013 model to see what the differences are. If I changed my VO to 2014 and VO coded the module, mostly everything worked except for a new screens which didn't apply to 2013 model vehicles (like 2013 model vehicles can't control their ambient lighting brightness and style via the iDrive). So I weeded out the parameters I needed and left out the ones that didn't apply to me and recoded the new NBT with my new custom parameters and everything worked just fine.

So now I have Sirius station art on my navigation display. Also making a couple adjustments to my coding on the Rear Seat Entertainment allows it to display the album art on the rear screens as well. I don't know if the newer hardware revisions have any other advantages except an updated SiriusXM tuner with displays the channel art. Something like this probably wouldn't make sense for anyone outside North America since SiriusXM isn't offered elsewhere.

Here's after everything was swapped out and installed and coded:

Main display in the front

[IMG]http://i1301.photobucket.com/albums/...psgljsy9em.jpg[/IMG]

and SiriusXM channel art on the rear screens

[IMG]http://i1301.photobucket.com/albums/...ps60mnn7wr.jpg[/IMG]
Hi Dracon. Few questions for you if you could help me out. I'm familiar with coding and flashing firmware using esys, but less familiar with ista/p.

1. How did you change the new nbt vin to yours/how did you virginize the existing unit.
2. How did you read the original fsc code from your old nbt and put it on the new one?
3. How did you override the touch controller issue (I run into this when trying to code sometimes too)?

Is that all you needed to do aside from VO coding it to activate the new nbt? Would you be able to share the coded values you deactivated?

Thanks!
Appreciate 0