2002 E39 V50 to Bluetooth conversion (TCU)
 

Hi
I am in the process of upgrading my 04/02 E39 M5 to bluetooth.
I have a Motorola V50 in the armrest at the moment.
Thanks to the threads here I have purchased a (Euro) TCU (84.10.6.978.533) from ebay (new), a bluetooth antenna (84506928461) (£15) and a centre armrest oddments tray (51168215943) (£10) from a BMW dealer.
I believe that is all I need (my harness already has a 52pin connector).
Oh, I bought Navcoder and a USB thingy to make it work too.
Anyway today I started dismantling the car. I took lots of pics and will write a how to when it is all finished.
My (first) question is
Which Fakra cable do I use for the bluetooth antenna (I intend to put it under the armrest)
There are four in the trunk area:

One black/purple one marked 'GSM'. I presume that goes to the aerial, as it was plugged into the aerial side of the compensator.
One black/purple one with no markings. This one was connected to the 'phone' side of the compensator, so I presume goes to the centre arm rest.
One cream/purple one marked 'WDCT'. Loose.
One cream/purple marked 'U01464 F MDE'.

Onder the armrest there are two Fakra cables. Both Black & purple.
Any ideas?
Thanks

UPDATE 17th May 2010. See page 4 - http://www.xoutpost.com/741860-post32.html - for an update!

For the Fakras colour code, see this thread.

This TCU teardown may also be of use.

cream WDCT is/was the 2.4GHz antenna. You appear to have two, which is unusual. You need to find out which one goes to the BT antenna.

Check your 54 pin connector wiring, it may not be correct for a TCU, and plugging in the TCU without checking can irepairably damage it. See this thread.

Thanks
the two black fakra cables in the centre console are of the a type. One male and one female.
The two cream fakras in the trunk are identical female b types. I can't find where these cream ones run to. Any idea where they might terminate? One of them has to be the Bluetooth cable but I can't find it (it is not above the trunk)
many thanks for the advice on checking the plug cabling - I will do as soon as it stops raining!

The Cream will terminate in a black connector (yes I know that breaks convention :S) under the console. See these pics.
http://www.mwstewart.co.uk/images/ca...uetooth_33.jpg
http://www.mwstewart.co.uk/images/ca...uetooth_29.jpg

I'd plump for the WDCT cream antenna. It's a 50/50 chance and should be very obvious if you got it wrong.

You could plug the cables into the TCU one by one and see if the resistance reading at the console on a multimeter changes from Open Circuit to xMOhms.

Well, Fakras identified.
The black/purple (unmarked) Fakra in the trunk goes to the centre console black/purple male connector.
The other black/purple fakra in the trunk (marked 'GSM') does exactly what it says on the label and goes to the external GSM antenna.
The Cream/purple fakra in the trunk (marked 'U01464/F MDE') goes to the centre console black/purple female connector (unconventionally, as bob states above).
I have no idea where the second cream/purple connector (marked 'WDCT') in the trunk terminates - could not find it anywhere!

Now to the wiring of the 54pin plug....

My 54pin plug is not a BIT II plug.

From what I have read in the links above and the sticky retrofit guide, I think it is compatible without mods, although I'm not 100% as it doesn't exactly match some of the other posts.

Here are the pins
1 yellow
3 yellow
5 black
6 yellow
9 red
10 brown/white
11 white
15 white/grey/yellow
17 red/yellow
18 red/yellow

19 black
21 black
22 blue/brown
29 green
30 black
32 red/yellow
33 white/green
34 red
35 violet/white
36 black/brown

37 black/white
38 black/brown
39 brown
46 white
47 black/brown
48 black/white
51 white/brown
52 grey/red
54 brown/black

Is that ok?
Many thanks

You are going to have to check the WDS for your car [Search for Telematics]. The TCU really only needs PWR, GND, ibus and audio.

This is my car, an E46
http://i88.photobucket.com/albums/k1...MW/TCU/tcu.jpg
RT Red
SW Black
GN Green
BR Brown
GE Yellow
WS White
VI Violet
GR Grey
BL Blue

Great table, thanks - all looks good apart from pin 51, which is a different colour again in the pictures of the plugs on the link above. (black).

I'll plug in as it is and try it - don't think I can do any harm. I'll let you know if it works!

Thank you again

I dunno, your wires, (the big hitters like TELON, mute, speaker out) all look differnt colours. Check your WDS that they are the correct [different] colours for your vehicle. You only need to follow a few wires through, and the WDS is hyperlinked throughout.

Edit:

Click here, search for I01157 Telematics control module (TCU-Everest) (without USA LHD)

3 is GE
5 is SW
6 is GE
52 is GR/RT
37 is SW/BR
38 is SW/WS etc which matches your wiring

51 is GE which doesn't match

I'd say it'll be fine to plug in the TCU.

Well, all plugged in and seems ok.
However, bluetooth is off and I can't turn it on with navcoder.
It correctly identifies the TCU, but when I tick the bluetooth box,the option to 'code TCU' remains greyed out. I've emailed Jochen to see if he knows why.
http://i833.photobucket.com/albums/z...s/IMG_0698.jpg

You need to read the TCU first, otherwise you are trying to blank the BT name, BT passkey and emergency number for example. :wow:

I did. Several times. The bluetooth boxes all remain blank.

You need to solve that step first. Are you seeing iBus traffic from TEL?

Yes, lots! The nav display recognises it too and the telephone option has appeared.
Read ID fills the ID and control type boxes.
Read TCU doesn't seem to do anything!

IF you have a registered copy of Navcoder (I think you said that you did) then I don't know. For me, I hit Read ID, then Read TCU, and that populates all the boxes. I'm sure the resident iBus expert will be along shortly to help you out.

Thanks!
Yes I bought the registered copy.

Just for info, here is the full scan of the audio system, and below that is the ibus TEL-NAV only traffic from switch on for a couple of minutes.

NavCoder v2.8.162 - Scan Results
File written 26/03/2010 11:15:21

Audio / Nav System scan conducted on 26/03/2010 11:14:11

--------------------------------------------------
Following devices were found and are communicating:

BMBT On-board monitor control panel
Part number 6 916 610, version HW 46, SW 46, made by Alpine on 02/02 (January 2002)
Diagnostic index 31, Bus index 10, Coding index 00
Stored Fault Codes: No Fault Codes stored.

MFL Multi-function steering wheel
Part number 0 000 000, version HW 01, SW 09, made by 2 on 00/00
Diagnostic index 03, Bus index 78, Coding index 00
Stored Fault Codes: No Fault Code data available.

GT Graphics driver
Part number 6 922 720, version HW 12, SW 63, made by Philips on 12/02 (March 2002)
Diagnostic index 04, Bus index 09, Coding index 04
Stored Fault Codes: No Fault Code data available.

NAV Navigation (Europe)
Part number 6 922 720, version HW 12, SW 63, made by Philips on 12/02 (March 2002)
Diagnostic index 04, Bus index 09, Coding index 04
Stored Fault Codes: No Fault Codes stored.

RAD Radio
Part number 6 919 078, version HW 02, SW 70, made by Becker on 13/02 (March 2002)
Diagnostic index 39, Bus index 12, Coding index 02
Stored Fault Codes: 1 [0x0081]

VID Video module
Part number 6 924 749, version HW 06, SW 15, made by Loewe on 13/02 (March 2002)
Diagnostic index 02, Bus index 13, Coding index 02
Stored Fault Codes: No Fault Codes stored.

TEL Telephone
Part number 6 946 011, version HW 30, SW 31, made by Continental on 20/03 (May 2003)
Diagnostic index 20, Bus index 12, Coding index 03
Stored Fault Codes: 1 [0x6D21]

--------------------------------------------------
Summary of stored Fault Codes:

Module Qty Fault Codes
RAD 1 0x0081
TEL 1 0x6D21
--------------------------------------------------

The following devices did not respond:
They are either not fitted, not turned on, or not communicating on the I-bus.

FMBT Rear monitor controls
MID Multi-information display
FID Multi-information display, rear
IRIS Integrated radio information system
DSP Digital sound processor amplifier
DSPC Digital signal processor controller
CDC CD changer
CDCD CD changer DIN

Tips for devices that do not communicate:
--> Check device is fitted to vehicle
--> Check ignition is turned on
--> Check device is switched on


26/03/2010 11:20:46.312: C8 04 BF 02 01 70
26/03/2010 11:20:46.312: TEL --> GLO : Device status ready after Reset
26/03/2010 11:20:46.328: C8 04 BF 02 30 41
26/03/2010 11:20:46.328: TEL --> GLO : Device status ready
26/03/2010 11:20:46.390: 68 04 7F 02 01 10
26/03/2010 11:20:46.390: RAD --> NAV : Device status ready after Reset
26/03/2010 11:20:46.421: C8 04 E7 2B 03 03
26/03/2010 11:20:46.421: TEL --> ANZV: Telephone indicators: Red_blink
26/03/2010 11:20:46.468: C8 04 E7 2B 03 03
26/03/2010 11:20:46.468: TEL --> ANZV: Telephone indicators: Red_blink
26/03/2010 11:20:46.484: C8 04 E7 2C D0 D7
26/03/2010 11:20:46.484: TEL --> ANZV: Telephone status: Phone_On Phone_Adapter_Fitted
26/03/2010 11:20:46.531: C8 05 E7 A6 00 00 8C
26/03/2010 11:20:46.531: TEL --> ANZV: Special indicators: Request
26/03/2010 11:20:46.562: C8 03 50 01 9A
26/03/2010 11:20:46.562: TEL --> MFL : Device status request
26/03/2010 11:20:46.593: C8 03 80 01 4A
26/03/2010 11:20:46.593: TEL --> IKE : Device status request
26/03/2010 11:20:46.609: C8 03 C0 01 0A
26/03/2010 11:20:46.609: TEL --> MID : Device status request
26/03/2010 11:20:46.656: C8 03 3B 01 F1
26/03/2010 11:20:46.656: TEL --> GT : Device status request
26/03/2010 11:20:46.671: C8 03 68 01 A2
26/03/2010 11:20:46.671: TEL --> RAD : Device status request
26/03/2010 11:20:53.500: 68 0B 7F A8 32 0A 33 CA 8A 06 C8 A1 90
26/03/2010 11:20:53.500: RAD --> NAV : TMC data: Type32: Data="0A" Type33: User_Msg, Loc=51361 Evnt=518 Dir=Pos,Extnt=1 Dur=2 Diversion_recommended
26/03/2010 11:20:56.343: 68 05 7F A8 37 13 9E
26/03/2010 11:20:56.343: RAD --> NAV : TMC data: Type37: Data="13"
26/03/2010 11:20:56.406: 68 05 7F A8 37 13 9E
26/03/2010 11:20:56.406: RAD --> NAV : TMC data: Type37: Data="13"
26/03/2010 11:20:56.421: 68 05 7F A8 3F 00 85
26/03/2010 11:20:56.421: RAD --> NAV : TMC data: Type3F: Data="00"
26/03/2010 11:20:56.468: 68 05 7F A8 32 08 80
26/03/2010 11:20:56.468: RAD --> NAV : TMC data: Type32: Data="08"
26/03/2010 11:21:08.218: C8 04 3B 02 30 C5
26/03/2010 11:21:08.218: TEL --> GT : Device status ready
26/03/2010 11:21:14.421: 68 0B 7F A8 32 0A 33 CA 8A 06 C8 A1 90
26/03/2010 11:21:14.421: RAD --> NAV : TMC data: Type32: Data="0A" Type33: User_Msg, Loc=51361 Evnt=518 Dir=Pos,Extnt=1 Dur=2 Diversion_recommended
26/03/2010 11:21:15.781: 68 0B 7F A8 32 0A 33 CA 8A 06 C8 A1 90
26/03/2010 11:21:15.781: RAD --> NAV : TMC data: Type32: Data="0A" Type33: User_Msg, Loc=51361 Evnt=518 Dir=Pos,Extnt=1 Dur=2 Diversion_recommended
26/03/2010 11:21:48.250: C8 04 3B 02 30 C5
26/03/2010 11:21:48.250: TEL --> GT : Device status ready
26/03/2010 11:22:08.468: C8 07 7F A9 0B 00 00 03 11
26/03/2010 11:22:08.468: TEL --> NAV : Telephone data, Data="0B 00 00 03"
26/03/2010 11:22:08.578: C8 0B 7F A9 04 00 00 00 00 00 00 00 11
26/03/2010 11:22:08.578: TEL --> NAV : Telephone data: Current_network_ID: 26/03/2010 11:22:18.578: C8 0B 7F A9 04 00 00 00 00 00 00 00 11
26/03/2010 11:22:18.578: TEL --> NAV : Telephone data: Current_network_ID: 26/03/2010 11:22:28.296: C8 04 3B 02 30 C5
26/03/2010 11:22:28.296: TEL --> GT : Device status ready
26/03/2010 11:22:28.687: C8 0B 7F A9 04 00 00 00 00 00 00 00 11
26/03/2010 11:22:28.687: TEL --> NAV : Telephone data: Current_network_ID: 26/03/2010 11:22:33.437: 68 0B 7F A8 32 0A 33 CA 8A 06 C8 A1 90
26/03/2010 11:22:33.437: RAD --> NAV : TMC data: Type32: Data="0A" Type33: User_Msg, Loc=51361 Evnt=518 Dir=Pos,Extnt=1 Dur=2 Diversion_recommended
26/03/2010 11:22:38.781: C8 0B 7F A9 04 00 00 00 00 00 00 00 11
26/03/2010 11:22:38.781: TEL --> NAV : Telephone data: Current_network_ID: 26/03/2010 11:22:48.875: C8 0B 7F A9 04 00 00 00 00 00 00 00 11
26/03/2010 11:22:48.875: TEL --> NAV : Telephone data: Current_network_ID: 26/03/2010 11:23:08.328: C8 04 3B 02 30 C5
26/03/2010 11:23:08.328: TEL --> GT : Device status ready
26/03/2010 11:23:48.343: C8 04 3B 02 30 C5
26/03/2010 11:23:48.343: TEL --> GT : Device status ready
26/03/2010 11:24:24.515: 68 0B 7F A8 32 0A 33 CA 8A 06 C8 A1 90
26/03/2010 11:24:24.515: RAD --> NAV : TMC data: Type32: Data="0A" Type33: User_Msg, Loc=51361 Evnt=518 Dir=Pos,Extnt=1 Dur=2 Diversion_recommended
26/03/2010 11:24:24.687: 68 0B 7F A8 32 0A 33 CA 8A 06 C8 A1 90
26/03/2010 11:24:24.687: RAD --> NAV : TMC data: Type32: Data="0A" Type33: User_Msg, Loc=51361 Evnt=518 Dir=Pos,Extnt=1 Dur=2 Diversion_recommended
26/03/2010 11:24:28.390: C8 04 3B 02 30 C5
26/03/2010 11:24:28.390: TEL --> GT : Device status ready
26/03/2010 11:24:28.796: 68 0B 7F A8 32 0A 33 CA 8A 06 C8 A1 90
26/03/2010 11:24:28.796: RAD --> NAV : TMC data: Type32: Data="0A" Type33: User_Msg, Loc=51361 Evnt=518 Dir=Pos,Extnt=1 Dur=2 Diversion_recommended
26/03/2010 11:24:28.812: 68 0B 7F A8 32 0A 33 CA 8A 06 C8 A1 90
26/03/2010 11:24:28.812: RAD --> NAV : TMC data: Type32: Data="0A" Type33: User_Msg, Loc=51361 Evnt=518 Dir=Pos,Extnt=1 Dur=2 Diversion_recommended

If I am reading the scan correctly, it appears that NavCoder found a TCU part number 84.11-6 946 011 with a May 2003 date of manufacture. That part number is different from the part you list in your original post (PN 84.10-6 978 533). That might be a problem. Or, it could be that the -533 part is just the remanufactured version of the -011 TCU, and BMW does not change the internal PN designation during the "remanufacturing" process.

Next, the TCU has a fault stored, so that could be part of the issue. However, without knowing the meaning of the fault, it is impossible to guess.

This is a different type of TCU from the US CDMA version that kiwijochen figured out for NavCoder coding. Therefore, this may require totally different coding instructions to read and activate Bluetooth. In other words, Jochen might have to dump memory contents and write an enhancement to NavCoder for this type of module.

Finally, it is possible that this TCU is not capable of Bluetooth. The U.S.-spec CDMA TCU modules did not receive bluetooth until 2004, for the 2005 model year. This module appears to be dated 2003, which precedes the arrival of Bluetooth in other similar modules by two model years. This particular module does not have any date information in the parts catalog, so it is difficult to determine when it was actually used in cars. (The presence of a Bluetooth logo on the part sticker is also meaningless-- BMW had BT logos on the parts stickers long before the modules actually had BT ability.)

I hate to be the bearer of bad news, but it is very possible that the last point above is your problem-- that this module does not have Bluetooth capability.

Ok. On the sticker on the front it says 84116978533-01
16921111
27.05.2007
BMW everest ibus ece
sw31 hw30
bt 00e00c5246a3
pk8084
imei 352etc
ejas001085. Sveibs22b4

It is possible the unit is so new that Navcoder doesn't yet support it. This could be fixed by checking you have the latest version of Navcoder.

Just checked - it is the latest.

Tried doing a battery off reset, remembering to power down the nav by waiting 1 minute after IGN off [LED goes out after flashing]?

Nope. The Beta version is always the latest.

Tools - Options and use your eyes

Brian:
TCU coding for ECE or CDMA model is almost identical
And NavCoder regonises all TCUs correctly - so far...:D

Cool. I will note this.

This takes me back to my possible worst-case scenario for Stringbag... that this TCU may not have BT capability.

Brian, I'm starting to think the same!
Jochen, thanks for your help!
Okay, downloaded the latest (beta) navcoder.
select Code/Telephone
Click on 'Read ID'
Populates the data on top 2 lines, everything else blank.
click on 'Read TCU'
The bluetooth box is Ticked.
Everything else in the bluetoth section is blank.
VR section remains greyed out.
SDV section is active, but blank unless I click on SDV defaults
'code TCU' remains greyed out.
Even if I populate all the blank fields on the page, the 'code TCU' remains blank.

Jochen, how do I get a log of the TCU coding?

Many thanks for all your help everyone!
Stringbag

Tick Tools - Log Ibus Messages to make a log
Then read TCU again

You have coding index 03, which has no VR support.

But I'd like to see a log of your reading your TCU, because name, passkey, SDV settings should work.

Thanks, I'll do it tomorrow morning.

Log file sent.

Well, with a new beta by Jochen (massive thank you) I can now code my TCU.
However, I can't initiate pairing!
It displays 'telephone' on the nav screen, but when I select it, all it says is 'insert card!' or 'emergency'.
Only one of the leds on the nav screen flashes and that is red.
I have tried holding down the R/T button on the steering wheel, the sneezing man and a combination of the two. No change at all.
There is a slot on the TCU but it is far too big for a sim card.
I have an 18 pin connector in the armrest - from WDS it is X4545. I have searched this forum and some have suggested that if the TCU doesn't go into pairing nmode when the ign is first switched on, that you need to press the paining button. I don't have one, but can connect the pins in the X4545 connector.
I have not tried this yet because all the suggestions I have read only have 4 pins going to the armrest x4545 - mine has all 18!
How do I work out which of these pins is the right one? Pin 32 isn't it on the 54pin adaptor in the trunk.
Any ideas?
Thanks.
Oh, and happy Easter!

TCU pairing requires no button presses.

The TCU goes into pairing mode for the first few minutes after ign is switched on.

So:
Put your phone into BT search mode
Then turn on vehicle ign
See what happens

I have head from some people that an eject box may need to be fitted to allow the TCU to go into pairing mode, although this is unconfirmed.

However, no button presses are required for pairing mode.

For some reason Bluetooth is not transmitting. Two phones -a new and an old one can't see any blootooth signal from the car.
The only eject box I have is the old v50 one without a pairing button. Putting it back makes no difference.
All I get when I select telephone on the nav screen is 'emergency' , a phone symbol and the words 'insert card'.
No 'activate phone' or similar.

I'm confused!

I may be wrong, but I think you cannot use such a telephone unit as a bluetooth phone in your car... that's NOT a ULF.

I have one of those in my car (see this thread) and I'm seeking advice as it doesn't work anymore, so I already investigated several options.

Hope my experience will help you...

BMW TCU can ONLY communicate with its handset, NOT with other phones.
You got this ...and you need these other pieces to get it to work..!

I don't know if you can mix pieces (TCU from a car and handset from another one)... but you CANNOT make it pair with other phones.

BTW, I had the same problem when using Navcoder (cannot write on TCU, just read from it) and I thought it was because there was no need to activate bluetooth not there is a way to change its name and PK.
Correct me if I'm wrong (I was about to pm Jochen about this matter myself, then I thought that was the reason).

Hope this helps.

UPDATE
 

Well, despite Jochen's best efforts I can't get the TCU that I bought to pair via bluetooth. If you want to use this method, then I suggest that you avoid the WCDT TCUs - avoid these part numbers:
TcuGSM(9) = 6938763 ' till 03/2004 ENDED SA638 Professional car phone
TcuGSM(10) = 6946011 ' ENDED SA638 Professional car phone
TcuGSM(11) = 6978533 ' RMFD SA638 Professional car phone
TcuGSM(12) = 9187926 ' RMFD SA638 Professional car phone

and try one of these instead:
TcuGSM(0) = 6946991 ' till 01/2005 ENDED SA633 Business mobile phone preparation
TcuGSM(1) = 6965055 ' till 03/2005 ENDED SA633 Business mobile phone preparation
TcuGSM(2) = 6964113 ' till 09/2005 ENDED SA633 Business mobile phone preparation
TcuGSM(3) = 6963758 ' till 07/2006 ENDED SA633 Business mobile phone preparation
TcuGSM(4) = 9129850 ' till 11/2006 ENDED SA633 Business mobile phone preparation
TcuGSM(5) = 9127894 ' till 03/2007 ENDED SA633 Business mobile phone preparation
TcuGSM(6) = 9132712 ' ENDED SA633 Business mobile phone preparation
TcuGSM(7) = 9195454 ' RMFD SA633 Business mobile phone preparation
TcuGSM(8) = 9207075 ' RMFD SA633 Business mobile phone preparation

The good news is that it should be plug and play with a >02/02 E39. There are no wiring or pinout changes required.
I bit the bullet and bought a ULF. It was plug and play with no modifications.
I would advise buying Navcoder as you can then change the ID to your car and enable VR.
Here are some pics:

Before (with the CD player and nav unit removed)

http://i833.photobucket.com/albums/z...s/IMG_0664.jpg

So, remove the traffic master (useless) and old motorola bits (including the 54pin to 25pin adaptor.
Plug in your ULF/TCU.
Remove all of this from the centre console.

http://i833.photobucket.com/albums/z...s/IMG_0674.jpg

You will be left with one x4545 18pin connector and two fakras - both go to the trunk - one to the compensator for the gsm signal and one goes to the ULF/TCU which we will use for bluetooth.

Attach a bluetooth antenna to the Fakra connector, stick it down to stop it rattling, and replace the old eject box with either a blank or an eject box of your choice. (if you have fitted a ULF, you can pair using navcoder, so don't need a bluetooth eject box).

http://i833.photobucket.com/albums/z...s/IMG_0697.jpg

That is it.

Finally, here are the instructions from BMW.
I can't work out how to upload a copy here - the file is just a bit bigger than the max allowed on the forum, so here is a link.
http://homepage.mac.com/vladimir/bmw...lBluetooth.pdf

TCU works on 2001 530i
 

Hi - I have a TCU pn 84106964114 (2nd generation, if my documents are correct) in my E39. I fabricated the DB-25 to 54 pin connector, installed the SES jumper and installed the later version of the microphone.

It works well, with voice recognition as well as MID and steering wheel control. I have been able to pair my Droid, plus my wife's Motorola (don't know model) and the address books transfer.

NavCoder works with it, too.

Perhaps I'm lucky, but a TCU does work in an older E39.

Bob