[jbash87]

I'm 99% of the way done with my COMBOX retrofit and everything works properly. I can bluetooth stream music from my phone and make calls just fine. The CIC is all functioning as normal too. BUT...There are still two things I can't seem figure out.

1) The bluetooth device name is still the last 5 digits of the donor VIN and not my VIN. I went through Tool32 to update the COMBOX VIN which took just fine, even flashed it with winkfp so when I read the UIF in INPA my VIN shows up.

2) ISTA now shows an error with CIC communication which wasn't there before. It is a CIC retrofit, but this did not show an error until the COMBOX was installed. This error doesn't seem to cause any negative effects, however.

My searching has turned up nothing so far. Hoping someone here on the best car forum the internet has to offer can help me out!

 

[jbash87]

Nobody??

Can someone who has done this mod at least confirm that the bluetooth device name in the COMBOX is their VIN and not the donor?

 

[james_m]

1.

This is done with NCS Expert. Unfortunately, because the Combox is not available for E6X, you need to load a custom SSD file into NCS Expert first to make it see your car as E9X so it can see the right address for the COMBOX.
Then you should be able to write/update MAN file as normal.

Unfortunately, I've not been able to make this work on mine yet, the SSD file make my copy of NCS Expert crash

2.

Is this the one causing the MOST bus reset during ISTA discovery? I think this is to do with the car expecting the old MULF on the MOST ring. I've not done this myself yet, but suspect only way to remove this is to remove Bluetooth codes from VO - that's what ISTA's using to generate the list of what modules should be there.

 

[jbash87]

Thanks for the reply @james_m. I'm not sure what you mean by my first issue being fixed in NCS Expert though. As far as I know NCS Expert cannot change VIN numbers. I have already used Tool32 and WinKFP to do this. My COMBOX is still saying the old VIN as the bluetooth device name when I connect with my phone.

I never had a MULF, only TCU. But what you're saying has me thinking that maybe I need to switch 639 (Preparation f mobile phone cpl. USA/CDN) which was original to my VO for 644 (Preparation f mobile phone w Bluetooth). I think I've read that before somewhere.

Again, everything works just fine. I've already done the SSD coding. I'm just trying to polish off the install so it is more seamless.

To address your issues though. I'd assume you're SSD is crashing NCS Expert because of formatting. Check out the following thread. Post #21 is very detailed and talks about SSD creation.

E60 CIC Retrofit, USB, Combox - 2006 BMW 530i - 5Series.net - Forums

E60, E61 Parts, Accessories and Mods - E60 CIC Retrofit, USB, Combox - 2006 BMW 530i - BMW CIC ULTIMATE TOOLKIT -Password: Please Send PM for Password. Download Link...

5series.net

I created an excel file where I aligned my VO and the VO from an e90 with a description of all the options. Then created the SSD file by combining them as needed. Note that NCS Expert does not like the "M" codes from an e60 when it's expecting an e90.

 

[Kaane]

I just ignored the vin issue. Error on the bus can be fixed by updating the I-level.

 

[jbash87]

Thanks @Kaane. I hadn't seen anyone talk about the bluetooth name so having someone else chime in that it isn't the same makes me feel much better.

I'll try to work out the I-level and report back.

 

[Kaane]

Here is how I've updated mine. Credit goes to Zimmie.

Used tool 32.
Start Tool32 , Open E60.prg
Choose "i_stufe_lesen" to read your existing I-level config. Save it somewhere.

I_STUFE_WERK = E060-08-03-525
I_STUFE_HO = E060-12-11-500
I_STUFE_HO_BACKUP = E060-08-03-525

Use command "i_stufe_schrieben" to write.
the data write format is: WERK;HO;HO BACKUP
Updated I-level to match my updated VO date of 09/09
So i used this string :

E060-09-09-516;E060-12-11-500;E060-09-09-516

 

[jbash87]

Thanks @Kaane. I haven't tried this yet but I'll get to it at some point. Any idea what the 525 and the 516 represent?

On another note I figured out how to get the bluetooth name to match my VIN. Turns out @james_m was right and I just didn't understand what he was saying. You must set the SSD file to your VIN+checksum and default code the COMBOX. Somehow the bluetooth name is associated to the VIN used in NCS Expert.

 

[Kaane]

Thanks @Kaane. I haven't tried this yet but I'll get to it at some point. Any idea what the 525 and the 516 represent?

On another note I figured out how to get the bluetooth name to match my VIN. Turns out @james_m was right and I just didn't understand what he was saying. You must set the SSD file to your VIN+checksum and default code the COMBOX. Somehow the bluetooth name is associated to the VIN used in NCS Expert.

Those are just build numbers for certain dates. Here is full breakdown of all i-levels availabble.

https://www.e90post.com/forums/attachment.php?attachmentid=1378544&d=1457472882