kirvedx

I wrote a big write-up about it, then tried to edit it with obvious corrections and additions; and the whole post disappeared. So I'll try this again. Let's start with the straight forward answer:

To code a combox in an E60 you'll have to use an SSD file.

This is because our E60 cars never had a combox from factory, and therefore BMW never shipped a module file for the combox for E60's. Even if another chassis (like E90) has the same or a similar module (i.e. CIC) and said chassis did have a module file for the combox because it was shipped from factory at any point (yes, combox module data exists for E90), the same module in our car won't be identifiable through factory software such as NCS or INPA - our modules won't ever see the combox either, or at least ever be default coded to work with it, and we can never code the combox itself by default (to the VO of) our E60 car. This is due to the fact that what our chassis (E60) car's modules are allowed to know about is all dictated by the module files (the SP-Datens). Version matters to an extent, but if E60 modules never included a combox, then even with a CIC (a module that is paired with a combox in a E90), our E60 SP-Datens will never see it or know how to work with it.

NCS Expert gives us a solution for this, known as a virtual VO by means of a SSD file. First, let's cover typical NCS Expert usage whereby we default a module's coding by our chassis' VO:

1. File->Load Profile->Factory Coding (Expert)
2. F1 (Start).
3. F3 (Chassis).
4. Select E60 (in pop-up).
5. Select CAS (in pop-up). You can select LMA but the CAS selection gets us all the settings for all modules in a single TRC file by default with this method.
6. Wait a few seconds for CHASSIS/FG/FA/NRCL-NO to load.
7. F6 (Back)
8. F4 (Process ECU)
9. Select module (in pop-up)
10. F2 (Change Job) though SG_CODIEREN is selected by default.
11. Select SG_CODIEREN (in pop-up)
12. F3 (Execute Job)
13. Wait for Coding Active to change to Coding Ended

...and that is how you can default code any module that has ever been known to be installed by the factory in your chassis by your VO. This will never work on modules that have never been installed by the factory. To do so, you need a virtual VO.

A virtual VO is provided by a SSD file. Let's take a look at the one I used for my retrofit (a bn-2000 in my 2006 530xi):

Now, I borrowed an SSD from Vortex over at bmwcoding forums. His SSD blindly enabled all features, and was missing a lot of features that my car has and/or didn't have features that closely resembled mine. It was a very inefficient SSD to use for me to say the least. So what I did was clean it up by removing $612, $616, $6AL, $6NR, and by adding many of the features from my car that were possible for the E90 in question. Where needed, I made sure the options chosen for the E90 at least were the E90's equivalent for the E60's. This takes time to do, and I highly recommend it be done. There are options lists out there, use one. There are VIN decoders out there, use them to see the possible features.

The reason is, because there are a ton of settings that you'll need to review in the codings for the combox and CIC, and as long as you had the SSD tuned as closely to your car as possible, you can get away with simply making the few changes we know have to be made, and hope that the rest match for your car appropriately. It's not truly just as simple as defaulting the combox to the E90 Virtual VO, and then doing the same for the CIC and making necessary changes in a subsequent true VO default of the CIC. At the least, with a tuned SSD file you will likely only discover minor discrepencies.

The other issue I ran into with Vortex's SSD is that the VIN provided is from a European car (so I obviously made feature changes there as well where I could - but the default codings for the combox and CIC were still EURO style - such as anything that could be "left-handed drive" was set to "right-handed drive"). You'll have to change those.

So here's how you use the SSD file (which by the way, you should only have 2 lines in your SSD file...the first the line that starts with "M", and the second the line that starts with "A". The second line is huge, and ends with "0000000"):

1. File->Load Profile->Factory Coding (Expert)
2. F1 (Start).
3. F5 (Open file).
4. Select SSD FILE (in pop-up).
5. The file obviously loads immediately and populates CHASSIS/FG/FA/NRCL-NO.
6. F6 (Back)
7. F4 (Process ECU)
8. Select module (in pop-up)
9. F2 (Change Job) though SG_CODIEREN is selected by default.
10. Select SG_CODIEREN (in pop-up)
11. F3 (Execute Job)
12. Wait for Coding Active to change to Coding Ended

It's really that simple.

Do this first for the combox, then do a READ and back-up the ~5kb TRC file. Then do it again for the CIC, and follow up by reading the CIC and back-up the ~18KB TRC file.

PLEASE NOTE:



You can then, using the true VO default coding method, immediately go ahead and default your CIC again back to an E60 - as this is what it needs to be anyways.

Now you have your work cut out for you:

1. Open Notepad++
2. Load all relavent TRC files:
   1. The CIC E60 VO default coding
   2. The CIC E90 SSD default coding
   3. The combox E90 SSD default coding
3. For items 2.1 and 2.2, perform the following steps to sort the codings alphabetically for an easier time:
   1. Press CTRL + F
   2. Select the Replace tab
   3. Make sure "wrap around" is selected on the left
   4. Make sure in Search Mode, you select Extended (\n\r\t\0\x...)
   5. For Find what enter \r\n\t
   6. For Replace with enter *
   7. Select Replace All
   8. Select Edit->Line Operations->Sort lines lexicographically ascending
   9. For Find what enter *
   10. For Replace with enter \r\n\t
   11. Select Replace All
4. Now scroll through both files evenly and for instances of combox in the E90 SSD default coding file, ensure the same coding key is updated to reflect the combox value in the E60 VO default coding file.

When you have finished, there are still other settings that you'll need to update in the E60 file with the values from the E90 file in order for it to work right, such as BT_INSTANCE_ID (needs to be 02 instead of 01). The combox coding file will be coded for a european car, but should be ready to go regardless. You could update the codings, but it should just work. I'll reference the commit in my repository that will show a perfect diff that will show you exactly what changes I made, you can find the link at the bottom of this post once its updated. If you can't wait, there are posts all over that list all the codings settings. Once done, save a copy of your updated E60 codings file and change the .TRC part to .MAN.

Now there are stll 2 more important steps to do once you have the settings made properly:

1. Code the CIC using the MAN file in manipulation mode with NCS Expert.
2. Update the VIN on the combox (this assumes you are using the patcher method).

The reason for number 1, is because we've already default coded the CIC, now we need to make modifications to the settings that our module data won't provide by default. The reason for number 2, is because the combox just took the VIN of the VO provided in the SSD file (as modules do when they are coded). We want/need our VINs to match (with the VIN that is authorized) for certain features. If you do end up wanting to update the combox settings, you'll need to do that first - then update the VIN after (as even coding the combox settings by use of SSD will revert the combox back to the VIN of the SSD).

To perform step 1, you can follow the NCS_DIY.pdf method provided on the bmwcoding forums as part of the Beginner's Lounge for coders:

1. File->Load Profile->Manipulation (Expert)
2. F1 (Start).
3. F3 (Chassis).
4. Select E60 (in pop-up).
5. Select CAS (in pop-up). You can select LMA but the CAS selection gets us all the settings for all modules in a single TRC file by default with this method.
6. Wait a few seconds for CHASSIS/FG/FA/NRCL-NO to load.
7. F6 (Back)
8. F4 (Process ECU)
9. Select CIC (in pop-up)
10. F4 (Read ECU)
11. Close the NETTODAT.TRC file
12. F5 (Basic Functions)
13. Select coapiReadSgGetFswPsw
14. Select OK (in pop-up)
15. Select OK (in pop-up)
16. F2 (Change Job)
17. Select SG_CODIEREN (in pop-up)
18. F3 (Execute Job)

To perform step 2, you need to use Tool32:

1. Open Tool32
2. Press F3
3. Select CMEDIAR.png
4. Find c_fg_schreiben and select it
5. Enter your 18 digit (with checksum letter) VIN in the data input to the right
6. Press the run-once button (the 1_x) button in the top menu.
7. Perform the same steps (5 and 6) with the c_fg_auftrag job
8. Test with c_fg_lesen or aif_lesen (looking for fg_number to match the last 7 of the vin you entered)

The alternative method is to just use aif_schreiben, but I wouldn't use that considering many of the arguments are just empty and I've never written that job with altogether missing arguments (just when there are 0's).

PLEASE NOTE:




I'm working on a detailed 2021 write up for the whole retrofit (CIC and Combox) that includes all the stuff I had to dig for - including this portion. When I'm done I'll link it, and it'll include all the specific changes I made to the codings which will be tuned for a US E60 530XI that came with a CCC-Mask, Telematics, TCU (no mulf), and Smart Phone Prep, that's had a CIC/Combox retrofit with $614, $615, $644, $6VA, $6FL, $6NF, and $7SP, Patched, and all features working. The changes I'll have committed to the repository I'm keeping for my car/retrofits - and with it there will be the commit diffs which show very neatly what to change (you could even cherry pick the commits yourself if you really know what you're doing!). It'll also show you, again by commit diffs, how I updated the SSD and the VO, for both my car and the SSD, as I tracked changes in everything (I'm an engineer - it's second nature to me).

Until then, here's the codings for the combox as an M5 user had them (the settings are updated to be for left-handed drive, and probably include some assist/telematics settings we don't want, but nevertheless):


And here's the CHANGES ONLY needed for the CIC after you've re-defaulted it back to E60:


Hope that helps!

iNvaderZiM

Bro I'm going to contact you what's the best way for me to reach you so that I can have you remotely access my car and code and program a few things I want to get the wireless internet on my car and also do the aux can we add a Bluetooth feature for music because I can only get Bluetooth for a calls also would like to have you code my index 12 injectors my Instagram is HellboyFame

neilv

So I just swapped a Combox to my CIC retrofitted car. It was fairly simple and I managed to do it without an SSD. You gotta get the CIC in and working first then go to the combox.

MOST connector plugs right in and online there are tons of references for repinning the combox connector from TCU or mulf or TCU + MULF. Some of the coax cables may also need adapters or trimming the tabs.

Coding is easy; I used an 03/10 date and added -TELD to the VO to delete the SOS error. Beyond that I saved the CIC FSW/PSW file (from NCSexpert) and loaded it in NCS dummy. You can see 3 specific areas where the combox can be selected so just change to those. This forum post #7 here (https://cartechnology.co.uk/showthread.php?tid=43440) also has a list of the other options that you can change(including the 3 combox ones) to use to get connected drive, bluetooth streaming and all the other stuff going. I also have an E90 with a combox, so I'm able to switch it over and code it in the order car if I need anything changed. Tool32 change the VIN to match the new car (I also changed the Bluetooth name) and all the FSC codes will now work.

kirvedx

If you have an e90 car just make an SSD file out of that VIN and VO and you dont have to swap anything. You can use the SSD file with NCSExpert to code the combox when you need to change something. Using an SSD file is actually very convenient and easy to do - explaining it tends to make it seem overly complex and complicated.

Also, if you had HiFi, or even Logic7, in the retrofitted car - you probably will notice that there is no bass (the bass tuner works, but it seems to cap out and the audio is tinny/treble-full and not so great). This is because the CIC changes how the wires were utilized and it interfaces with an upgraded HiFi amp so as to power all the speakers through the amp, not just the subs. There's a temporary work around where you pull one block out of the main CIC connector, pull its pins, and splice them into another block.

Work around for woofer with CIC retrofit

However, the real fix is to either upgrade to the newer HiFi amplifier and reconfigure the speaker wiring or buy a digitial audio processor and custom wire the speakers.

OEM HiFi amplifier retrofit

HiFi to MS-8 upgrade

neilv

For me I only needed to code the Combox to change the setting for Bluetooth calling. Otherwise everything worked right away (though I think I still need to change the Aux setting). Its 30 seconds in and out of the car to remove but I am lucky to have that option.

Stereo worked for me just fine (I'm logic7) and I didn't need to touch any sound options. Even the defrost/heater controls stayed the same since I didn't change any of the settings to E90 versions.

kirvedx

Well that was certainly a convenient swap for you then, options must have been just right between the car you took it from and the car you put it in. You'd typically use the SSD file on the CIC and Combox only to get the right settings between the two devices, and as well when crafting the SSD file to get all the other settings for your car that can apply tweaked right by default. Not many would be able to go about doing it the way you have and have everything working right - even if it did "play music" and "just work".

Though that's not to say that if someone knows what options they have in their car that they couldn't simply code those options to the right value and avoid default coding whatsoever - though without a car that can see the Combox they'd need an SSD file.

I've seen a lot of posts simply providing the MAN file in full, but paying attention to when they're made and what options they are enabling I tend to prefer to just default code (than spend hours upon hours from their versions). I use android, not apple - and wouldn't want options enabled that I don't use. I'm OCD Also, connected drive and other services - if not shut down and deprecated, like teleservices - don't actually work properly on cars that didn't support it (and there's a fee for the subscription even when it does, like when you're retrofitting a car that could have come with it). Though, there's plenty of others that have posted more modern versions that do forgoe those deprecated things and quickly explain what you can change according to your setup.

All those long guides are just teaching people how to do the things that one would need to do not knowing much about the options they're touching and let alone how they relate to the infotainment center or their car - beyond how to access the combox from a car that can't see one using NCSExpert. From there they want to know how to enable features that their VO wouldn't indicate they have - but if you already know, that's time saved for you.

As long as you have fun and its working for you though, job well done. The Combox itself is a pretty easy job, its settings list is far shorter than the CIC - if you don't mind swapping between cars and changing over your setup to that car to code - and then back again. I didn't have that option, for instance, and it was super convenient putting my laptop in my trunk, a charger on the car, and sitting inside my home simply swapping between my true VO and an SSD file as I tweaked my system through team viewer.

kirvedx

I will say though, that from your picture it does seem you have a far easier time accessing the combox than I do Looks so audio oriented in that compartment of yours

neilv

For me I coded the CIC to my car and all my options first; made sure that worked. Then after that went in and changed the settings needed for the combox (that site I posted had a list of all the different parts needed) and voila it all worked. Those were the only different settings when he compared a CIC to a CIC + combox in an E90. If you run it in NCS dummy it gives you an english read out of what the settings mean so its real easy to tell if its needed or not.

My way may not work for some but I found it simpler so I just thought I'd share (Im not a good electronics person either)

kirvedx

I see you did 03/10 - like me. Doesn't it just irk you that with just a one month newer build date that $6VC would have stuck in your VO?

Anyway - yea, no doubt I get that. I guess I wanted to iterate over that with you just in case, because I did something similar in just making the direct changes someone else offered to make it work (though I did default the CIC so I didn't have to spend hours learning my VO and features, discovering just how much the CIC settings pertain to). I ended up putting in the work anyways to tweak everything and add the features I wanted after doing the SWPatcher, etc. However, seems you already went through the CIC settings and have everythign working properly, and you already commented that your Logic7 setup didn't have the bass-drop issues that HiFi systems do.

That's awesome it worked for you in such a straight forward way, and that you had the car to swap with. It's definitely understandable that you went the route you did.

black_rain

I am happy to find that a thread with CIC retrofitting in the title isn't dead. I am waiting for a few parts to come in to start this full install including the updated CIC controller. First, i sourced all the parts from ebay and ppl parting out vehciles on FB marketplace so nothing is coded to my VIN. I have also purchased the CAN emulator which should be here soon. As for the CAN emulator i read that i may not need it but only if i can get my CIC HU updated. Is there anyone that is willing to help with coding and i am willing to compensate. Please reply here or send a PM. Thanks in advance.