[vithy]

I'm on v.51 if i'm not mistaken.

Originally Posted by Terabyte

Hey Vithy

On what Version is the rest of the car? 54.0 too?

[mikessc]

Originally Posted by vithy

My F30 build date is 03/12, didn't come with Navi, but after NBT install worked fine. No issue with ICM Gyro data.

Hi vithy,

May I know the HWEL id and CAFD id of your ICM module ?

Thanks

[vithy]

Here you go..

Originally Posted by mikessc

Hi vithy,

May I know the HWEL id and CAFD id of your ICM module ?

Thanks

[mikessc]

I study the CAFD file of both NBT and ICM

GYRO_INTERN
if condition parameter of your car series is something like:
boolean(//cat[@val < "128"][crit[@val=2374]])

Your NBT will have internal GYRO if your FA E-Wort has item with value=GYIN

Followings are ICM functions that might affects HU_NBT or HU_CIC.
ie. bdt means car build date , Zeitkriterium (Time Criteria)

C_NVC_aktiv_1
aktiv if bdt >= 1307 and has(sa609 or sa606)

C_NVC_Exit_no_dyn_aktiv_l
aktiv if bdt >= 1307 and has(sa609 or sa606)

C_NVC_Navi_Dynamik_aktiv_l
aktiv if bdt >= 1307 and has(sa609 or sa606)

C_VZA_Funktion
ein (value=01) if bdt >= 1307 and has sa609

C_2DR_Rekonstruktion_Navigationsbaum
ein (value=01) if has sa609

Verbau609_NaviHigh
verbaut ie. installed (value=01) if has sa609

BMW changed ICM CAFD conditions for above functions near feb-2012.
So I presume, car built >= 1203 with have ICM with GYRO.

It is not advisable to VO code ICM module with modified Zeitkriterium.
This is because there are other non-Navi related functions with condition
parameter that is set base on Zeitkriterium when you VO code the module.

Regards,
Michael

[mikessc]

Hi vithy,

Did you flash your ICM or VO code it with modified Zeitkriterium
after retrofiting your NBT ?

Regards,

Michael

[mikessc]

Another way to determine if NBT has internal GYRO using tool32.

Prg file = nbt.prg
job name = status_lesen
Argument = ARG;STATUS_GYRO

[vithy]

I have never touched any functions in ICM. It was just plug and play of the NBT. My build date is 1203.

Originally Posted by mikessc

Hi vithy,

Did you flash your ICM or VO code it with modified Zeitkriterium
after retrofiting your NBT ?

Regards,

Michael

[vithy]

When I get a chance, I will try to read the ICM and see whats on the CAFD. Maybe you can check and see on my CAFD it there's anything different.

Originally Posted by mikessc

I study the CAFD file of both NBT and ICM

GYRO_INTERN
if condition parameter of your car series is something like:
boolean(//cat[@val < "128"][crit[@val=2374]])

Your NBT will have internal GYRO if your FA E-Wort has item with value=GYIN

Followings are ICM functions that might affects HU_NBT or HU_CIC.
ie. bdt means car build date , Zeitkriterium (Time Criteria)

C_NVC_aktiv_1
aktiv if bdt >= 1307 and has(sa609 or sa606)

C_NVC_Exit_no_dyn_aktiv_l
aktiv if bdt >= 1307 and has(sa609 or sa606)

C_NVC_Navi_Dynamik_aktiv_l
aktiv if bdt >= 1307 and has(sa609 or sa606)

C_VZA_Funktion
ein (value=01) if bdt >= 1307 and has sa609

C_2DR_Rekonstruktion_Navigationsbaum
ein (value=01) if has sa609

Verbau609_NaviHigh
verbaut ie. installed (value=01) if has sa609

BMW changed ICM CAFD conditions for above functions near feb-2012.
So I presume, car built >= 1203 with have ICM with GYRO.

It is not advisable to VO code ICM module with modified Zeitkriterium.
This is because there are other non-Navi related functions with condition
parameter that is set base on Zeitkriterium when you VO code the module.

Regards,
Michael

[mikessc]

Originally Posted by vithy

When I get a chance, I will try to read the ICM and see whats on the CAFD. Maybe you can check and see on my CAFD it there's anything different.

I am more than happy to investigate.

Send me your ICM ncd and original FA (without VIN).

What was your original HU option ?
What's your car built date ?

My car is F10 build date may 2012.
I intend to retrofit NBT and 2 hurdles that I see are the requirement
of new ZGW and using older version of NBT (HW <= 7).

I am trying to find ways to reuse old ZGW (with most)
and using newer version of NBT (without GYRO).

[vithy]

Here you go with both FA and CAFD.

I don't think that matters for F30. Since first production date the ICM has been the same. Now if you calculate SVT with different ISTEP shipment even as early as 11/11, no changes in ICM hardware. At least on my tests.

However hardware changed as of 07/13 build

If you look at my ICM hardware ID (00000D95_002_003_005) , this has been the case for builds from 11/11 to 03/13. This is the case for cars with or without CIC.

Starting 07/13 ICM changed to 00000D96_002_003_008 and remain the same till current date.

If you can. Send me your SVT and FA.

I think, Fist thing you should do is, upgrade all your ECU's to the latest ISTEP. At least to a version that had and when NBT came into production. Then tap into your CAN2 and bring into NBT. Then get a MOST cable to run from NBT to your KOMBI (6WA or 6WB). And do your testing. My guess is it will work.

I'm not sure about F10 ICM. But it still shouldn't be an issue with GYRO. Gyro is only used when you don't have GPS data. At lest in the case of NBT/CIC. But again this is just my guess.

Let me know.

Originally Posted by mikessc

I am more than happy to investigate.

Send me your ICM ncd and original FA (without VIN).

What was your original HU option ?
What's your car built date ?

My car is F10 build date may 2012.
I intend to retrofit NBT and 2 hurdles that I see are the requirement
of new ZGW and using older version of NBT (HW <= 7).

I am trying to find ways to reuse old ZGW (with most)
and using newer version of NBT (without GYRO).

[VitaminXX]

I flashed a NBT on bench and put it in a F10. Eerything works well, except music setting and some of mileage setting which returned to default value every time I start up the car. I then deleted the setting files in the setting menu. Now, only setting in music returnes to default. Has anyone encountered this issue?

[BeatB]

Hey guys.

Yesterday I went to a BMW dealership for an issue with sport mode (I have rarely a little jerking when switching from the 1st gear into the 2nd). They could not find the problem, but they said in february there is coming a new update from Munich for the software and maybe this will fix the issue.

My fear is if they are going to update the software (maybe it's the entire car software for all ECUs - I dont know) that I will have issues when coding the NBT unit with HW21.

I have the whole equipment at home for the retrofit, will start the retrofit in march - cant wait

[Terabyte]

Hey

When you change your car´s FA, there should not be a problem with flashing by the Dealer.

If you are unsure, you can flash your ecu´s by yourself.

[Coolala]

Hi all,

I found this is really an excellent thread. All guys contribute a lot of knowledge and advice here, and sharing their experience. I’m now going to retrofit NBT to my car. I still have some questions need to be solved before starting.

Questions about NBT retrofit WITH emulator installed:

My car build date: Oct 2012
NBT production date: Week26 of 2014

1. After hardware connection and NBT head unit in place. I need first to update the master VO by adding back relevant option codes like 609, 6NS, 6NR. Correct?
2. Then after step 1, do I need to VO code all ECU units one by one, or just VO code the ECU’s HU_NBT and ZBE2 is enough?
3. After step 2, FDL code related parameter like KOMBI_CIC = kombi_low and BASIC_KOMBI_MMI_LIST = aktiv …correct?
4. Will there any problem to VO code the HU_NBT ECU if there is an emulator ALREADY CONNECTED? I’m just worrying about this action will overwrite the donor vin in NBT unit by my own car vin , then FSC code will be mismatched and navigation will not work again. Is it true?
5. Just in case it is necessary, vin can be changed after installing emulator by just changing vin in FA and then coding NBT and FSC-vin and FSC-codes will stay intact?
6. Is there any action that I MUST NOT do in order to prevent overwriting the donor vin in NBT unit? I mean is there any risky coding action?
7. According to the above dates mentioned, do I need to change the build date when VO coding the NBT?
8. If it is necessary to change the build date of my car when VO coding, where to change it in Esys?
9. If it is necessary to change the build date when VO coding, what is the logic? Is that because NBT first release on 7/12, then the build date of car should be >= 7/12 ?
10. About hardware connection, my car is F20 M-Sport with combox in the boot. I have new USB HUD cable, MIC cable ordered, to avoid rewiring the existing USB cable and MIC cable back to the front. To prevent the conflict between NBT and combox unit in the boot, I need also to detach the canbus and MOST cable from combox unit and then connect the MOST cable with a close loop fibre connector. Is it a correct way to do so for car with combox in boot?

Any help gratefully appreciated.

[DavidV]

Originally Posted by Terabyte

Hey

When you change your car´s FA, there should not be a problem with flashing by the Dealer.

If you are unsure, you can flash your ecu´s by yourself.

sorry but there would be an issue, and the ISTA won't flash the car when you have a retrofitted NBT with an emulator, that's been tested.

Any other operation at the dealer (service, reading/deleting fault codes) is possible, but not flashing.

options: either flashing it at home (with a power stabilizer) either mounting up again the stock navi/radio.

This is my car being flashed "home-made-style"

[DavidV]

Originally Posted by BeatB

Hey guys.

Yesterday I went to a BMW dealership for an issue with sport mode (I have rarely a little jerking when switching from the 1st gear into the 2nd). They could not find the problem, but they said in february there is coming a new update from Munich for the software and maybe this will fix the issue.

My fear is if they are going to update the software (maybe it's the entire car software for all ECUs - I dont know) that I will have issues when coding the NBT unit with HW21.

I have the whole equipment at home for the retrofit, will start the retrofit in march - cant wait

The dealer answer is the standard answer.... a new update will solve.... blah blah blah....

let's not start a sideways conversation, but it seems that your issue (several others have suffered it, including myself) is due to the transmission auto adaptation.

Just have your adaptation values reset and it'll smooth all over again. Using ECO pro mode with my driving pattern ends up with that behaviour in my case

[BeatB]

ok thanks for your suggestion.

But this transmission auto adaption is only for automatic transmission I guess?

I have the manual transmission , so there should not be the automatic adaption option I think.

[DavidV]

Originally Posted by BeatB

ok thanks for your suggestion.

But this transmission auto adaption is only for automatic transmission I guess?

I have the manual transmission , so there should not be the automatic adaption option I think.

As in here 90% of us have the auto tranny, I was making a wrong assumption!

[Terabyte]

I red out the error memory of NBT today.

There is one error. (MOST Bus error). I think it is because there is no Most cable connected to NBT right?

Anyone else have this error in the error memory?

[vithy]

I have never seen this error on mine.

Are you seeing the error on rheingold? I'm assuming after flashing NBT?

Originally Posted by Terabyte

I red out the error memory of NBT today.

There is one error. (MOST Bus error). I think it is because there is no Most cable connected to NBT right?

Anyone else have this error in the error memory?

[Terabyte]

I have seen it with tool32

But i deleted the error memory today with Rheingold. I will check again if the error comes back.

[thehobbit]

Since a lot of people here went with NBT retrofit, may I ask you where have you buyed your parts? E-Bay? On-line shops? Refurbished parts?
How much were you quoted for NBT and screen? Do you have any reccommended source?
I'm interested too , and maybe in the next months I will start working on.
Thanks!