[steddyman]

Thanks Shawn. That makes a lot of sense.

I have tried to VO code the HBT twice and has mentioned above it fails. I don't know if this is because the VIN doesn't match because I don't have the emulator yet.?

[shawnsheridan]

Originally Posted by steddyman

Thanks Shawn. That makes a lot of sense.

I have tried to VO code the HBT twice and has mentioned above it fails. I don't know if this is because the VIN doesn't match because I don't have the emulator yet.?

Ahh, ok. I forgot.

[steddyman]

Do you think it will work with the emulator (bimmertech)?

Does that work two way? Ie fools the NBT into thinking the car is the same VIN and the other way around?

[shawnsheridan]

People code with Emulators, so I know that will work. What I don;t know right now for sure is if your coding issue is due to the lack of the emulator. Again, no point in speculating on any of this stuff.

[steve@codemybimmer]

Originally Posted by steddyman

Thanks Shawn. That makes a lot of sense.

I have tried to VO code the HBT twice and has mentioned above it fails. I don't know if this is because the VIN doesn't match because I don't have the emulator yet.?

Have you tried VO coding it with a different build date? It didn't work for me when I used 07/12 but when I used 11/12 it changed the language from German to English, and it change the vehicle profile from F31 back to F30.

[steddyman]

Originally Posted by Aritaurus

Have you tried VO coding it with a different build date? It didn't work for me when I used 07/12 but when I used 11/12 it changed the language from German to English, and it change the vehicle profile from F31 back to F30.

I haven but my build date is 12/2013 already.

We're you using and Emulator when it worked or were the Vins different?

[steve@codemybimmer]

Originally Posted by steddyman

I haven but my build date is 12/2013 already.

We're you using and Emulator when it worked or were the Vins different?

When I VO coded the car, I was still able to do it even without the emulator in there.

I think you might have to go with an older build date since that head unit is older than your car. Try 11/12 because that's when NBT was first rolled out in Europe for the F30.

It could be that the software on that NBT is not new enough for you to VO code with the 12/13 build date.

[steddyman]

That worries me as there may be other options on the car that rely upon my later build date that I would screw up by setting it backwards. Also, if it was an incompatibility between the deployed NBT and the build date, wouldn't the calculate FP throw an error?

How do I go about updating the software on the NBT to a later version. That may work better.

[steddyman]

Just looking at the list of options on my existing VIN and the one on the donor VIN. Could a mismatch here cause problems for me?

For example I haven't added the following options which show on the VIN for the NBT: 612, 614, 615, 616, 6AA, 6AB, 6NL
I have the following options set on my FA: 609 (added), 654, 6NS (changed from 6NL)

654 is the DAB tuner, which of course this model of NBT does not have.

Should I be adding all the above options to my FA and removing 654?

[shawnsheridan]

Originally Posted by steddyman

Just looking at the list of options on my existing VIN and the one on the donor VIN. Could a mismatch here cause problems for me?

For example I haven't added the following options which show on the VIN for the NBT: 612, 614, 615, 616, 6AA, 6AB, 6NL
I have the following options set on my FA: 609 (added), 654, 6NS (changed from 6NL)

654 is the DAB tuner, which of course this model of NBT does not have.

Should I be adding all the above options to my FA and removing 654?

You wrote your Head Unit was currently incapable of being VO Coded, which means it doesn't matter what is currently in your VO, as that has not been applied to NBT.

It does matter though what was in the Donor's VO as that is what is currently applied to NBT. If their exists an incompatibility with its current coding and your car's hardware and other ECU's coding, there will be issues.

You really need to let it rest for now until your emulator arrives, and you can apply the proper coding, and then assess what you have and what if anything isn't working as it should be.

[steve@codemybimmer]

Originally Posted by steddyman

That worries me as there may be other options on the car that rely upon my later build date that I would screw up by setting it backwards. Also, if it was an incompatibility between the deployed NBT and the build date, wouldn't the calculate FP throw an error?

How do I go about updating the software on the NBT to a later version. That may work better.

I wouldn't recommend flashing your NBT.

Is your vehicle really a 12/13 production? It could also be that your version of the psdzdata files are not new enough to VO code that far.

I'm currently using 51.1 and it still won't let me VO code my HU_NBT with 09/13 which was the donor vehicle's build date. The furthest I can go is 07/13.

[steddyman]

Originally Posted by shawnsheridan

You wrote your Head Unit was currently incapable of being VO Coded, which means it doesn't matter what is currently in your VO, as that has not been applied to NBT.

It does matter though what was in the Donor's VO as that is what is currently applied to NBT. If their exists an incompatibility with its current coding and your car's hardware and other ECU's coding, there will be issues.

You really need to let it rest for now until your emulator arrives, and you can apply the proper coding, and then assess what you have and what if anything isn't working as it should be.

Thanks Shawn

Aritaurus has stated that he could VO code his head unit with out the emulator installed even though it had a different VIN so I don't think that is the problem.

The fact my VO has DAB specified will surely be trying to enable that on the NBT when I VO code it. If that is the case then won't it fail as the manufacturing date and region of the done NBT means it doesn't have the necessary hardware to take it.

[steddyman]

Originally Posted by Aritaurus

I wouldn't recommend flashing your NBT.

Is your vehicle really a 12/13 production? It could also be that your version of the psdzdata files are not new enough to VO code that far.

I'm currently using 51.1 and it still won't let me VO code my HU_NBT with 09/13 which was the donor vehicle's build date. The furthest I can go is 07/13.

Looking at the values in the shows the build date for my car is 11/13. That will be right since I ordered it at the start of November but i was told it was built the first week of December.

I can VO code other options on the car, which makes me think the data is compatible. The build date of the NBT is late 2012.

[steve@codemybimmer]

Originally Posted by steddyman

Looking at the values in the shows the build date for my car is 11/13. That will be right since I ordered it at the start of November but i was told it was built the first week of December.

I can VO code other options on the car, which makes me think the data is compatible. The build date of the NBT is late 2012.

There's really no harm in using the older build date worse case scenario is that you will get an error and the settings won't propagate.

Just make sure you go to options and uncheck "Write to VCM after TAL execution" if you don't, this will write the modified VO to your car which you do not want.

You're really only using the modified VO as a reference point to program the head unit only. If you don't write the VO to the car, it won't affect any of your other ECU's.

At first, I tried 07/12 and that did not work, then went with 11/12 and and the settings propagated. Later on, I changed it to 07/13 so I could get the latest idrive features.

I also added 614, 615, 6AL, 6NK to my VO and it all coded fine enough though I should be using 6AM, 6AK, 6AC, 6NS since the head unit is from a 2014 model.

In your case, I would VO code HU_NBT with the 11/12 build date and use 6AL, 614,615, 6NK since the head unit is from a early 2013 build. Try not to use the new option codes as those are usually specific to 2014 models.

[steddyman]

YES!

I cracked it. My theory was right, option code 654 was preventing the NBT from VO coding. I removed it from the FA, updated the car, then the VO coding of both the KOMBI and NBT completed without errors.

I now have everything working, including sound, except for Navigation. My Emulator should arrive tomorrow and I'll fit it in the next couple of days.

Thanks for all your help Shawn and Aritaurus.

[shawnsheridan]

Originally Posted by steddyman

YES!

I cracked it. My theory was right, option code 654 was preventing the NBT from VO coding. I removed it from the FA, updated the car, then the VO coding of both the KOMBI and NBT completed without errors.

I now have everything working, including sound, except for Navigation. My Emulator should arrive tomorrow and I'll fit it in the next couple of days.

Thanks for all your help Shawn and Aritaurus.

[nordberg]

Well done Steddyman! This thread has been compulsive viewing over the last few days following your trials and tribulations! I take my hat off to you, excellent work.

Also great to see all the help you've been getting from shawnsheridan and Aritaurus. What a fantastic community...

[steddyman]

Thanks man

I can't get my head around how fantastic and supportive this community is. You guys are the best.

[steddyman]

Well. I still have one odd problem that perhaps somebody who has gone from Entry to NBT can help with.

For some reason when I swap to the Nav iDrive controller (not touch) it is no longer recognised. I have tried VO coding it previously but it always failed with a timeout like the controller wasn't there.

I put it down to a faulty controller so got a replacement one today from the original reseller (still have the old one). This one is exactly the same, still won't work so I doubt it is a second faulty iDrive controller.

Anybody got any ideas on what I could do to make this work?

Thanks

[steddyman]

I noticed this entry on the options list, that is not on my car. But it does not appear to be on the options list of the donor car either. Does anyone have this code on their FA?

S8S8A COUNTRY-SPECIFIC NAVIGATION CONTROL

Also, I checked the VIN of a car within five of mine, which is another UK 330d but with Pro Nav with all the standard UK services. This is of course the NBT with touch in the UK, but should I be coding my car with these codes?

S609A - Navigation system Professional
S654A - DAB-Tuner (I know this one won't work)
S698A - Area-Code 2 for DVD
S6ACA - Intelligent emergency call
S6AEA - TeleServices
S6AKA - ConnectedDrive Services
S6AMA - Real Time Traffic Information
S6ANA - Concierge service
S6APA - Remote Services
S6NHA - Hands-free with USB interface (I changed this to 6NS)
S6NRA - Apps (this isn't standard so I would need an FSC code for this)

[shawnsheridan]

First, make sure all of these NBT FDL's are set to nicht_aktiv:

ZBE_TOUCH
ZBE_TOUCH_BROWSER
ZBE_TOUCH_INTERACTIVE_MAP
ZBE_TOUCH_SPELLER

If it sill does not work, disconnect the emulator, and see if it works then. And yes, I know the old controller works fine with the emulator.

[steddyman]

Ok Shaun thanks. I guess I expected the VO coding of the NBT to do that. I'll try setting those and see what happens.