[DavesZed]

Evening all

Firstly yes mine is an E89, but the systems are basically the same.

OK I've retrofitted a CIC MID unit into my car, yes I'm aware it shouldn't have a MID version but that's not the problem. Everything seems to be working, Radio FM & DAB, CD, NAV (with an emulator), but there are some exceptions.....

NAV only locks onto your current location once you've started driving, from a fresh boot it seems to want to revert to it's last (previous owners) location. Going into Service mode shows GPS as not working with no positioning information, but then how does it pick up my location once I'm driving (still the same in settings after driving!)?
I've plugged a glovebox USB into the back of the headunit and tried updating MAPS but it's not recognising it.

The other problem seems to be the MULF2 unit, I can't get Bluetooth to show up. MOST must be working as it is picking up the AUX and USB ports that are plugged in.

As for coding I've removed $663, that was for my original Professional headunit that had Bluetooth and USB control built in (and both worked perfectly fine). I've left in the coding $6NN, $6FL, +KMP3 and +IPOD.
And I've added in $644, $606 (CIC MID) and $654 (DAB) to the VO and then written these to the CAS, NFRM and MCIC.

So can anyone help, what have I missed? I've done about 24 hours of Google searching and I keep coming up with the same stuff, all of which I've done, I just can't see what I've missed.

Oh I've not codded the CID as I'm running with an Android screen. Sorry if this is a bit of a dumb question but I'm pulling my hair out (and I've not got a lot of it left!!)

[smass]

In the US, most MULF are used for USB only and their BT is disabled. Did you code the MULF to enable/check the Bluetooth? Search for BT or Bluetooth and change to aktiv.

[DavesZed]

Originally Posted by smass

In the US, most MULF are used for USB only and their BT is disabled. Did you code the MULF to enable/check the Bluetooth? Search for BT or Bluetooth and change to aktiv.

Thank you smass, I'll look into it and see if I've missed anything in that part of the coding

[DavesZed]

OK, well I'm still not getting anywhere.
Firstly I've amended my first post, I actually removed $633 and added $644.

Attached are the photos of the MULF2 I've bought.

Now I've tried going through the tcr file and amended it accordingly for Bluetooth etc and written it back to the CIC, I've also changed the VIN in the MULF with WINKFP which was successful. But I must be missing something somewhere as I don't see anything that I can think of as relating to the MULF in the module list. Should I see something like ULF? Like I say I can see MCIC and CID (even though I don't actually have a CID). If I should see it what should it be displayed as and how can I rectify this?

TIA

[smass]

Check INPA UIF for 55 ISPB

[DavesZed]

Originally Posted by smass

Check INPA UIF for 55 ISPB

Now this is a little strange, it is showing the ISPB as there with the Manuf date which matches the sticker on the side (19.08.2010) but it's not showing the VIN. Now I've followed the instructions and set the VIN (and checked it afterward) with Tool32, and I've just done it again just in case and it's still not showing the VIN.
Print outs attached

Thanks for your help, it's appreciated

[DavesZed]

And this is what I'm seeing on the screen...

Now just a thought, my MOST optic cables are going directly from the CIC to the MULF, no other component is included. So I'm assuming this is all OK as the AUX and USB are working. The wires going into the 56 pin plug on the MULF are positive and negative, AUX and microphone, then there's the USB plug and the Bluetooth antenna plug.

[smass]

Most fiber devices sometimes don't display their vin to INPA. That is completely normal. The vin is not really needed to get bluetooth coding to work.

[DavesZed]

Originally Posted by smass

Most fiber devices sometimes don't display their vin to INPA. That is completely normal. The vin is not really needed to get bluetooth coding to work.

I was out checking it again later and the Bluetooth name now appears on the screen when in the service menu, but still no joy in it actually working properly.

As a matter of interest this the list of modules available for coding according to NCS. Unless I'm missing something I do not see any relation to the MULF, should I?

These may seem dumb questions but I've never had problems coding before so assumed, after all the reading I've done on it, that this would work!

[ptpending]

I believe that 6NN option is not compatible with MULF2
haven't seen 606 option in e89, can you show full picture of your monitor in dashboard ?

[DavesZed]

Originally Posted by ptpending

I believe that 6NN option is not compatible with MULF2
haven't seen 606 option in e89, can you show full picture of your monitor in dashboard ?

Thank you for that.
If 6NN is not compatible, then what would be the correct code to use?

606 is specifically for the CIC-MID unit which is Business Nav as opposed to 609 (Professional Nav) which is what the e89 should have. It works but is just a 2/3 on the left of the screen. It's made for the 6.6" screen, but I've got an Android 10.25" screen on mine which I'm using in place of the OEM flip-up screen.
Although it is the smaller headunit it is operating perfectly apart from the Bluetooth issue and that I can't get the glovebox USB to work (tried with a second USB as well). Centre console USB and AUX work perfectly fine through the MULF so the MOST must be working.
I've attached a couple of photos of the screen, not recent ones as I've not taken a full shot of it yet.

[ptpending]

Originally Posted by DavesZed

Thank you for that.
If 6NN is not compatible, then what would be the correct code to use?

606 is specifically for the CIC-MID unit which is Business Nav as opposed to 609 (Professional Nav) which is what the e89 should have. It works but is just a 2/3 on the left of the screen. It's made for the 6.6" screen, but I've got an Android 10.25" screen on mine which I'm using in place of the OEM flip-up screen.
Although it is the smaller headunit it is operating perfectly apart from the Bluetooth issue and that I can't get the glovebox USB to work (tried with a second USB as well). Centre console USB and AUX work perfectly fine through the MULF so the MOST must be working.
I've attached a couple of photos of the screen, not recent ones as I've not taken a full shot of it yet.

nice screen
i think that for MULF2 you have to use only 644 and 6FL. 6NN switches these functions to internal headunit boards, which CIC MID do not have

[DavesZed]

Originally Posted by ptpending

nice screen
i think that for MULF2 you have to use only 644 and 6FL. 6NN switches these functions to internal headunit boards, which CIC MID do not have

I will delete 6NN then and see what happens as 644 has already been coded in (could be a conflict then!). Thanks

[DavesZed]

OK, so it's taken me a week to get back to this project but alas no further along.
6NN was deleted and still didn't achieve anything, still got "please wait" all the time in Bluetooth mode

[smass]

Do you really need bluetooth phone from your MULF when you have an Android screen with the same function? My screen came with it's own mic that was easy to run to the factory location. The newer systems can work better than the factory BMW one in many cases.

[DavesZed]

Originally Posted by smass

Do you really need bluetooth phone from your MULF when you have an Android screen with the same function? My screen came with it's own mic that was easy to run to the factory location. The newer systems can work better than the factory BMW one in many cases.

That's a very good point, and one I have thought about, but I am also considering to change the Android screen for an OEM one (as someone is giving me one for free!!) and then I'd simply use one of the plug-n-play CarPlay/Android Auto boxes instead as TBH I only use Android Auto anyway so this would be a nice OEM option

[ccfj1]

Have a look at the coding in the mid and see if the mulf is selected, you can code the mid up and ignore the VO, as long as the coding in the mid is correct, then it should work.

As others have said, vin coding is not needed, it will work.

if you have an emulator then the usb should allow map updates, you will need the 1b file from the doner mid.

You will need the gps to work to do the update as the mid needs to know its moving for the update to work.

check the GPS antenna and replace if not working.

I'd have a look around and see if you can find an nscexpert dump from a mid with mulf2 and check the coding out.

[DavesZed]

Originally Posted by ccfj1

Have a look at the coding in the mid and see if the mulf is selected, you can code the mid up and ignore the VO, as long as the coding in the mid is correct, then it should work.

As others have said, vin coding is not needed, it will work.

if you have an emulator then the usb should allow map updates, you will need the 1b file from the doner mid.

You will need the gps to work to do the update as the mid needs to know its moving for the update to work.

check the GPS antenna and replace if not working.

I'd have a look around and see if you can find an nscexpert dump from a mid with mulf2 and check the coding out.

Thank you very much for the info

A bit of an update...
Glovebox USB socket.... as it's a cheap aftermarket version I read somewhere that you may need to turn the plug 180 degrees in the back of the USB, so I tried this and hey-presto it's now working perfectly

Although I still own the MID unit I've decided to sell it on and have got hold of a proper Z4 headunit (only headunits for the Z4 will actually fit the Z4!!).

As for getting the MULF to work I'm still working on that one

[ptpending]

the time criteria you are using is 1114
you need to change it to range from 0908 to 0910 temproary and code modules on most bus because after 0910 combox is used for bluetooth functions