[Mmouse]

Hello everyone I have 2008 e90. I have Tcu/mulf2 factory installed. I upgraded from ccc to 2013 cic unit but my usb and aux in the armrest is not working, on the radio it say aux active but you can’t change the volume also Bluetooth is not working also. Any help would be greatly appreciated. Thanks

[Captain Confused]

Did you do any coding to the new cic? It may not have come from a car that had usb so the cic doesn't know it's there? You'll have code the Bluetooth to activate it in the cic.

I just did a retrofit on my non idrive car with a cic that had Bluetooth but since my car wasn't coded for it originally I had to tell my car it was one and reflash the cic. Once that was done everything worked again

[Mmouse]

Originally Posted by Captain Confused

Did you do any coding to the new cic? It may not have come from a car that had usb so the cic doesn't know it's there? You'll have code the Bluetooth to activate it in the cic.

I just did a retrofit on my non idrive car with a cic that had Bluetooth but since my car wasn't coded for it originally I had to tell my car it was one and reflash the cic. Once that was done everything worked again

Yes I coded the #0909 and $6va

[Captain Confused]

Did you do an ecu read the trace file for the cic and then write it with the options?

I also think Bluetooth is $644

[Mmouse]

Originally Posted by Captain Confused

Did you do an ecu read the trace file for the cic and then write it with the options?

I also think Bluetooth is $644

Yeah I read the trace file I tried changing some of the options but nothing changed as I really don’t know if I am changing the right ones.
Do I still need to add $644 as the Bluetooth is in the mulf2

[Captain Confused]

If your car doesn't have a VO of showing Bluetooth being active then yea you'll need to add $644.

I had mulf2 before my cic retrofit but Bluetooth wasn't active. It only became active when I added $644 and changed the cic to say it was active. Basically anything with the keyword Bluetooth or BT I changed to activ. It's what worked for me

[ctuna]

http://www.e90post.com/forums/forumdisplay.php?f=122

http://www.e90post.com/forums/forumdisplay.php?f=368

Did you change the vin in the new cic to match your car?
the newer Nav's are usually paired with a combox .

Better go to the idrive and coding subforums for more detailed
answers.

[FaxData]

If you're only doing ccc->cic, you only need to add #0909 and $6VA. Your vehicle order should already have $639 and $6FL. Did you 1. use a non-manipulation profile, 2. change the FA/VO, 3. execute FA_WRITE to CAS and FRM/NFRM, then 4. change the ECU to CIC and finally 5. execute SG_CODIEREN? The final step is where the new configuration is written to the CIC. FA_WRITE only changes the vehicle order, it doesn't actually write the settings to the CIC.

(I wrote a tutorial btw)

[PichaDis11]

Originally Posted by FaxData

If you're only doing ccc->cic, you only need to add #0909 and $6VA. Your vehicle order should already have $639 and $6FL. Did you 1. use a non-manipulation profile, 2. change the FA/VO, 3. execute FA_WRITE to CAS and FRM/NFRM, then 4. change the ECU to CIC and finally 5. execute SG_CODIEREN? The final step is where the new configuration is written to the CIC. FA_WRITE only changes the vehicle order, it doesn't actually write the settings to the CIC.

(I wrote a tutorial btw)

After doing those.. reset both mulf2 and tcu with job SG_reset.

You can double check CIC trace file if it was coded correctly. Should see MULF_high or so.

[Mmouse]

Originally Posted by FaxData

If you're only doing ccc->cic, you only need to add #0909 and $6VA. Your vehicle order should already have $639 and $6FL. Did you 1. use a non-manipulation profile, 2. change the FA/VO, 3. execute FA_WRITE to CAS and FRM/NFRM, then 4. change the ECU to CIC and finally 5. execute SG_CODIEREN? The final step is where the new configuration is written to the CIC. FA_WRITE only changes the vehicle order, it doesn't actually write the settings to the CIC.

(I wrote a tutorial btw)

Thanks for all the responses
Yes I did the above only thing is how do I know I was using a non manipulation profile.

I tried doing a sg_reset I got error

[FaxData]

Originally Posted by Mmouse

Thanks for all the responses
Yes I did the above only thing is how do I know I was using a non manipulation profile.

I tried doing a sg_reset I got error

To turn off manipulation, go to Datei menu -> Profil editieren -> FSW/PSW, and uncheck "FSW-/PSW-Manipulate with FSW_PSW.MAN"

See the screenshot below.

Also, to my knowledge you cannot code the TCU or the MULF2 without an ICOM. But you shouldn't need to if you aren't replacing your TCU/MULF2; I did not do SG_RESET when I did a CIC retrofit. Coding the CIC with manipulation off was enough.

[ptpending]

you can code mulf or combox without icom(MOST) on e9x, headunit is acting as a gateway from K-CAN to MOST
you cannot code MOST modules on some early e60 and some e65 cars

[Mmouse]

Originally Posted by FaxData

To turn off manipulation, go to Datei menu -> Profil editieren -> FSW/PSW, and uncheck "FSW-/PSW-Manipulate with FSW_PSW.MAN"

See the screenshot below.

Also, to my knowledge you cannot code the TCU or the MULF2 without an ICOM. But you shouldn't need to if you aren't replacing your TCU/MULF2; I did not do SG_RESET when I did a CIC retrofit. Coding the CIC with manipulation off was enough.

Ok gonna recode the CIC
also I am using a plug n play harness with emulator i don’t think that should be the issue but just some more info

[Mmouse]

Originally Posted by FaxData

To turn off manipulation, go to Datei menu -> Profil editieren -> FSW/PSW, and uncheck "FSW-/PSW-Manipulate with FSW_PSW.MAN"

See the screenshot below.

Also, to my knowledge you cannot code the TCU or the MULF2 without an ICOM. But you shouldn't need to if you aren't replacing your TCU/MULF2; I did not do SG_RESET when I did a CIC retrofit. Coding the CIC with manipulation off was enough.

Do you know what is causing the error above

[FaxData]

I got errors coding the TCU as well. (I originally attempted to retrofit a MULF2 and eventually gave up, and moved on to a combox.) I don’t think you can code the TCU or MULF2 without an ICOM, but again I don’t think you need to. Just code the CIC.

Also, since your emulator is plug and play, try removing it temporarily to code your CIC. You can put it back on after your trunk modules are working, or script activate the CIC.

[ctuna]

Up to 3/07 build you can code most modules with and
K/D can but after that its not firmly known is K/D can
is enough.

The two profiles currently supplied with the Bimmergeeks downloads
are Factory and Manipulate.
Factory reads the VO files back into the selected module.
This is called blank file programming but its not its VO coding.
Man reads the Man files you have modified back into the module.

Profiles select which options the files are read from or whatever
option you want when you make a new profile.

[Mmouse]

Originally Posted by FaxData

I got errors coding the TCU as well. (I originally attempted to retrofit a MULF2 and eventually gave up, and moved on to a combox.) I don’t think you can code the TCU or MULF2 without an ICOM, but again I don’t think you need to. Just code the CIC.

Also, since your emulator is plug and play, try removing it temporarily to code your CIC. You can put it back on after your trunk modules are working, or script activate the CIC.

So I can plug a CCC harness right in the back of the CIC without any re pinning?

[FaxData]

Originally Posted by Mmouse

So I can plug a CCC harness right in the back of the CIC without any re pinning?

Yes. The emulator only disrupts the VIN check between the CIC and the CAS. The pin-outs for the CCC and CIC are the same.

[Mmouse]

Originally Posted by FaxData

Yes. The emulator only disrupts the VIN check between the CIC and the CAS. The pin-outs for the CCC and CIC are the same.

Ok I removed the plug n play with emulator and connect with original ccc plug and everything works aux & Bluetooth except usb (greyed saying not supported instead of not connected)
This is the one I have
http://www.ebay.com/itm/Plug-and-Pla...ss!11735!US!-1

[FaxData]

Originally Posted by Mmouse

Ok I removed the plug n play with emulator and connect with original ccc plug and everything works aux & Bluetooth except usb (greyed saying not supported instead of not connected)

Ok, since Bluetooth is working, your TCU is active and working. And since AUX is working, your MULF2 is [at least partially] working and your CIC is properly coded. First, I would try a variety of different USB drives, maybe there's an issue with the USB drive you've been testing? And make sure that the drives are formatted as FAT32 and not NTFS or HFS or anything like that. The car only supports FAT/FAT32, as far as I know.

[ctuna]

Can't you change the Vin in the Head Unit using Tool32.
Thus avoiding an emulator.
Also might be worth looking in the Head Unit Files so
see whats enabled.
Do a search for USB in same.

[FaxData]

Originally Posted by ctuna

Can't you change the Vin in the Head Unit using Tool32.
Thus avoiding an emulator.
Also might be worth looking in the Head Unit Files so
see whats enabled.
Do a search for USB in same.

Changing the VIN in the head unit would resolve the VIN mismatch but then the root security certificate would be rejected. Script activation would resolve this, or using CIC patcher if the CIC is running C1A firmware and is from US or ECE region.

But... it's worth seeing if the USB/Aux issues can be resolved first. If it's truly the emulator that's the problem, I would ask for a refund from the eBay seller. mmouse, in case you don't see my post above, please try the different USB drives as I suggested.