Retrofit Bluetooth with a TCU instead of a ULF in any I-Bus Car
 

For a long time, we had a collective assumption that a Bluetooth-Assist TCU would not work in cars made prior to 2004. However, a few recent installations proved this false. A BimmerBoard member named crds recently installed a TCU in his 2003 M5, a person over on E46Fanatics installed a TCU in a 2001 E46, a few others on M3Forum installed TCUs, and I installed a TCU in my Dad's 2002 M3 (see the reference posts below). The advantage to the TCU is that it costs 1/2 as much as a ULF. My Dad got his new TCU for $345, compared to over $600 for a new ULF (if you can even find one).

Schizophrenic behavior of '03 M5 with both SES and Bluetooth TCU?
OEM Bluetooth kit I put together for $419 pre 03/02 - E46Fanatics
HUGE news regarding the newest oem bluetooth tcu - BMW M3 Forum.com (E30 M3 | E36 M3 | E46 M3 | E92 M3)

The TCU part number we installed is 84.10-9 195 455. It is the newest available, though others will work.

My Dad has a 3G iPhone with the latest OS, and the TCU works perfectly with the iPhone, so this appears to be an optimum Bluetooth solution for a much lower cost. Another advantage, both cost and cosmetic, is that the TCU does not require an eject box. The TCU goes into pairing mode for a couple minutes when you first start the car, so it does not need a pairing button. The only real downside to the TCU is that its voice recognition instructions only control the phone. There are no navigation control instructions like in the ULF and SES modules.

The only challenge is that the factory default coding for a TCU has voice recognition turned off. If you have a SES module, then this is not a problem. Or, if you are buying a used TCU with VR already turned on, this is not a problem. Otherwise, you will need to get VR turned on. I tried every option I could find in Progman/SSS, GT-1, and NCS Expert with no luck. It does not have the options we need for an early year car. Maybe someone who is a true stud with these tools could do it, but it was beyond my ability and desire to experiment. Fortunately kiwijochen, the author of NavCoder and international BMW I-Bus expert programmer, came through.

This weekend, Jochen, my Dad (with his 2002 M3 and new TCU), and I had a Skype call going between Georgia, USA at my house and Jochen in Switzerland. We were using NavCoder to download information from the TCU and send it to Jochen so that Jochen could analyze it and send update instructions back to us. It worked like a champ. My Dad now has voice recognition in his M3. And, if Jochen can incorporate this into NavCoder, we have a way cheaper option for Bluetooth in all I-Bus cars.

This is great news! As a Navcoder owner, I anxiously await this... ;)

BTW, if a TCU came out of an existing car (say for example, i pulled the TCU out of my mother's 2006 X3), would VR already be active? i.e. are only new units uncoded for VR?

Good work Brian

I do not know. It seems like voice recognition should be turned on in most models. But, my next door neighbor has a 2005 E46 with a BMW Assist Bluetooth TCU, and he does not have voice recognition. So, either the option is turned off, or he got a TCU before BMW incorporated built-in VR. (He is a little too nervous about electronic experimentation to ask me to try to upgrade his car.)

I have access to the 06 X3... Ive never used voice commands though... How do I test it? (my BlackBerry is paired now and working --address book transfers etc)

Push and hold the "sneezing man" button on your steering wheel for a few seconds. That invokes voice recognition. If you push and hold, and it does nothing or it only redials your most recently called number, then VR is turned off.

OK just tried it--seems to work just like it does with my 6th gen ULF in my e46...

Pressed and held button, then "Dial Number 555-555-1234...."

Guy starts talking to me, then dials the number, so I'm assuming its programmed...

Enabling this functionality is all the dealer programming will do?

and if it is turned off how do you turn it back on? i have a 2006 bmw x5 3.0, with navi, thanks

It is possible that your TCU does not have the voice recognition capability. However, you have a 2006, so that is unlikely. I suspect that it is merely disabled in the coding. I have not seen the options available to a dealer for coding a TCU, so it may be as simple as a setting change in the dealer's programming system. Or, the VR option could be something they are required to charge a large sum of money to enable (like BMW does in some European markets) or is hidden from them in the US coding software.

If Jochen can incorporate this into NavCoder, they you would be able to turn it on yourself.

Does Jochen feel confident that he can incorporate into NavCoder?

Yes he does :-)

But not this week, huge workload in my day job :-(

I hear you there... ;)

That's great news!

Does this allow you to keep assist? I wonder if the newer module will work with the X5. There was a specific issue with the X5 wiring. I know a few people on the forum tried the TCU in the early days with no luck what so ever.

Thanks for the update though. It may be worth looking into.

Yes, the newer TCU has Assist - but I'm not fully aware of all the Assist coding, and don't want to mess with Assist too much, as it's too hard to test
eg: there's settings for Auto-Emergency call when airbag goes off, etc

Contrary to my previous comment, I got curious and started writing code.

Reading ID, determining telephone type (ULR or Everest), Reading emergency phone number, reading and coding VR on new TCU now work.

I'll add the SDV and then see if I can squeeze in the other phone numbers... and then I need testers to verify for me

Jochen

You have my services with a 2006 X3 with BT/Assist module until Thursday AM...

Hey - any luck with this? I have posted in another thread that i retrofitted nav and got a harness from what i believe is an older X5 (03 or 04). I didn't go the retrofit harness route.

So when i plug in the module (not knowing i didnt have ulf or what tcu was ) everything goes blank. Is this likely if there are issues with older models using the TCU? Essentially if this is an older harness it goes back to older model in terms of wiring correct?

So OP - how did you get TCU working with an "older model"?

This TCU has been installed in several E38, E39, and E46 cars from 2000 to 2006. The wiring became standardized across all models in 2002. So, any US-spec harness 2002 or newer would work fine.

I read through your other thread, and I think that I would buy that you have a harness for the BIT-II system, but that is a possibility. Something is severely wrong if the telephone module effectively crashes the entire audio/nav system. If I were you, I would look up the assist wiring harness on the BMW wiring diagram software, and carefully compare it to the 54-pin plug in your harness. Then, I would go one step further and us a multimeter to test the wires to confirm that they are what they should be. Like ccfj suggested, you probably have a fault on the I-Bus wire. That is where I would look first.

ok thanks. The wiring actually came from europe car since i bought it from ebay. I'm very close to just paying for my mistakes and buying a new harness.

you mean to say that you doubt its a bit II system harness? I have the wiring diagram software - not sure how to run it though LOL. Will take a look.

Yup, that was a typo in my note. I meant say that I did not think you had BIT-II wiring... However, that was before I knew that you got it from Europe. So, given that you have no idea the source of the wiring, all bets are off. Plus, the harness is a mismatch for your DSP. You are 0 for 2. It is a tough decision, but I would consider starting over with a proper harness. You can probably get your harness working, but it will take some effort and a lot of very careful wire tracing against the wiring diagram for your car.

Yup I hear you. All bets are off for sure. I had the harness installed by an indie mechanic so i dont know if i want to get the new one and incur the cost for another install. DSP i'm not concerned about - I want to put in replacement amp and sub anyway.

I opened up the wiring diagram DVD I have and i'm not an electrician. Can't understand it.

try this... the WDS is online now:
WDS BMW Wiring Diagram System - Model Selection

The easy way to resolve the issue is to write down the wire colours and corresponding pin numbers of the suspect TCU connection, then compare to the Euro and USA-phone wiring in the WDS.

Determine what you have based on hard cold facts.

Correct any wiring that is different, so that the TCU is then cabled the same as a USA-TCU.

If this is too technical for you, go to an autoelectrician and ask him to do it.

If plugging in the TCU is causing the nav screen to shut down, then it can only be affecting the power supply, and must be blowing a fuse.

Check what fuse blew, that will tell you which wire on what pin is the issue at the moment, compare with WDS and correct the wiring. If the wiring is correct and the TCU blows a fuse, the TCU must be faulty.

If your description of "shut down" means something else, then please be more descriptive so we can understand what is happening.

Maybe the databus is being blocked by the TCU, and that would mean you would have no control or display of any data.

Thanks Jochen.

To clarify - when i plug in the TCU, I can't turn on the nav monitor. No radio etc.

I'll check out the pins and compare as you suggested as well.

The TCU isn't faulty because with the previous harness I had bluetooth working fine.

Chances are if there is a difference with the US and EU specs TCU harness then I've got the EURO version harness and US version TCU (since it was in the car when i purchased it and working)

thanks again for the responses.

Time to compare TCU wiring:

USA TCU Everest
54p black connector.
Key pins:
15=ibus
17=Term30 (permanent power)
18=Term30 (permanent power)
35=TermR (ignition switch power)
36=Ground
52=Illumination
54=Ground

Euro ULF
54p black connector.
Key pins:
15=ibus
17=Term30 (permanent power)
18=not used
35=TermR (ignition switch power)
36=Ground
52=Illumination
54=not used
== same as US TCU

BIT interface with Siemens phone
54p black connector.
Key pins:
13=ibus !!!!!
17=Loudspeaker !!!
24=Ground
25=Term30 (permanent power)
31, 32=Term 30
33,34 = Ground
42=Ground
43=Term30
== MAJOR wiring differences between BIT wiring and ULF/TCU

CONCLUSION: Your loom is wired for a different Telephone module.
Because you don't know what your loom was made for the ONLY solution to your problem is to pull the connector housing off the loom's telephone connector and document all fitted pins and wire colours.

THEN re-pin the connector to match your telephone unit that you are fitting
(Re-pin = remove wire from existing connector pin number, and insert to new pin number. Use small jewellers scredrivew to push down the locking tab to remove the wire.)

Refer to the WDS for your correct pin numbers and wire colours.

After an hours or so of repinning you'll have the problem fixed.

You guys are the best. Thanks Jochen. This definitely makes sense and thanks for the above research. NOW i think I can handle this. LOL. I just have to figure out where pin 1 is :bustingup

Once it stop's raining here I'll pop the trunk and take a look at this.

So here's a thought - it's most likely that I have BIT right? Since it looks like power and ground are on different wires it could possibly cause my issue of absolutely no power to anything else. Just a thought - could be completely off and you can feel free to say "stop assuming.. just go check the pins.." :thumbup:

Written on the connector. It's small, use a good light and a magnifying glass if your eyes are no longer so young :-)

NO NO NO - you cannot leap to conclusions just because I found 1 out of many different TEL types that is different to the USA TCU.

The WDS shows around 20 different TEL types and I did not check them all.

You MUST document the wire colours and pin numbers, that is the ONLY way to find out what you loom is cabled for.

Understood. No quick and easy way. LOL. I'll report back with findings as i'm sure i'll need help finding the right one in WDS.

Ignore WDS for now.
Document the wire colors and pin numbers.
We can tell you what to do once you have provided the documented wire colors and pin numbers.

sounds like a plan.

OK - got the info. Here is the PIN info.

the connector has this info on it, not sure if it matters just thought i'd add it.
White 'lever': seimens A1000-Y454
Black connector- seimens B1054-Y10 PBT GF20

1 red
2 white
9 clear
10 white
11 gray
12 purple white striped
13 white gray striped yellow rings
17 blk brown striped
18 blk white stripe
19 red
20 blk
24 brown blk stripe
25 red yellow
28 black
29 white brown or orange
31 red yellow
32 red yellow
33 brown black
34 brown black
37 yellow
38 green
39 crlear
42 brown blk
43 red yel
46 red
47 green white
48 blue white
52 brown white
53 clear
54 white

The 'clear' wires look like audio type wires. let me know if it makes sense. Let me know if this helps.

OK, Looks like the BIT for the Siemens Handset. Info follows...

Hard to make a table here.
List shows your pin + wire colour, then Function, then where to connect this wire on USA TCU (TCU pX), and the USA TCU function

You'll be able to make the phone functions work, and connect a Bluetooth phone.
You won't have Emergency Buttons Assist because the Euro loom doesn't support it.
If you use a USA Eject Box, you must change the Eject Box connector from Euro type to USA Type

Here we go:

BITII Siemens Cordless Handset Euro Function USA TCU-Everest Pin, USA Function
1 red TELON, Telephone On, to Euro Eject Box X4039 p11 TCU p9, RXCAUDIO, to USA Eject Box X4545 p15
2 white DIN, to Euro Eject Box X4039 p6 TCU p11, TXAUDIO; to USA Eject Box X4545 p11
9 clear Shield, diagnostic conn to nav Not used, insulate and tie back
10 white RXD, diagnostic conn to nav Not used, insulate and tie back
11 gray TXD, diagnostic conn to nav Not used, insulate and tie back
12 purple white striped Voltage supply terminal R, to X400 p2 TCU p35, TermR (ign power), to X400 p2
13 white gray striped yellow rings* I-bus databus, to X400 p4 TCU p15, Ibus, to X400 p4
17 blk brown striped TELNF-, telephone audio out, -ve, to X400 p9 TCU p38, TELNF-, to X400p9
18 blk white stripe TELNF+, telephone audio out, +ve, to X400 p10 TCU p37, TELNF+, to X400 p10
19 red 12V, to Euro Eject Box X4039 p5 TCU p32, Charger, to USA Eject Box X4545 p1
20 blk RES, to Euro Eject box X4039 p10 TCU p4, AUDIOGND, to USA Eject Box X4545 p4
24 brown blk stripe Ground (main ground connection), to X400 p7 Not used, Insulate and tie back
25 red yellow Permanent power fm F74 10A, to X400 p1 TCU p17, Permanent power vm F74, to X400p1
28 black CTS, diagnostic conn to nav Not used, insulate and tie back
29 white brown or orange TELM, Telephone mute, to X400 p8 TCU p51, TELM, to X400 p8
31 red yellow Permanent power fm F74 10A, to X400 p1 TCU p18, Permanent power vm F74, to X400 p1
32 red yellow Permanent power fm F74 10A, to X400 p1 Warning! Permanent +12V! Not used, Insulate and tie back
33 brown black Ground (main ground connection), to X400 p7 TCU p36, Ground, to X400 p7
34 brown black Ground (main ground connection), to X400 p7 TCU p54, Ground, to X400 p7
37 yellow IN, to Euro Eject Box X4039 p12 TCU p30, RXD, to USA Eject box X4545 p18
38 green DOUT, to Euro Eject Box X4039 p14 TCU p29, TXD, to USA Eject box X4545 p9
39 clear Shield of Euro Eject Box cable, to Eject Box X4039 p7 TCU p39, Eject Box Ground, to USA Eject Box X4545 p7
42 brown blk Ground (main ground connection), to X400 p7 Not used, Insulate and tie back
43 red yel Permanent power fm F74 10A, to X400 p1 Warning! Permanent +12V! Not used, Insulate and tie back
46 red RTS, diagnostic conn to nav Not used, insulate and tie back
47 green white TELON, Telephone On, to X400 p11 TCU p33, TELON
48 blue white WDCT_OFF, to Euro Eject Box X4039 p4 Not used in USA Eject Box, insulate and tie back
52 brown white FS_MIC-, microphone -ve, to mic plug p3 TCU p19, FS_MIC-
53 clear Microphone cable shield, to mic plug p2 TCU p21, Mic shield
54 white FS_MIC+, microphone +ve, to mic plug p1 TCU p1, FS_MIC+

NOTE:
Power p25, 31, 32, 43 are all joined together in the loom
Ground p24, 33, 34, 42 are all joined together in the loom

There is no cabling for ASSIST.
The Emergency button + LED cannot be used.

If you have the Telephone Compensator installed, then you need to connect it's TELON to X400 p11, as there is no extra TELON wire in the Euro loom

The Euro loom has no cabling for illumination (58g from X400 p5), so if fitting the USA Eject box, the illumination will not work
I have described the Eject box wiring in a way that will be compatible, but you will need to change the Eject Box plug as well from Euro to USA standard
The Eject Box plug may be different in the US.


If you PM me your email address, I'll email the above as a spreadsheet

thanks to all - the converter was the fix!! :D :D :D

got the converter today and it worked!! I now have bluetoooth! weirdest thing though - the range on the bluetooth sucks. When i'm standing near trunk it works fine - when i'm in the front of the car it's terrible that shouldn't be the case right? Before my bluetooth would turn on while i was standing 10 ft away from the car. Nothing in the harness and wiring should reduce signal right? That's all antenna - but all of that is the same. when i'm sitting in drivers seat it fails to connect.

BT range is purely the antenna and should not be affected by anything else. Verify your BT antenna and antenna cable connections. If you have a TCU, make sure the antenna cable is connected to the "cream" color coded plug.

ok i'll give that a try - but my TCU is bluetooth and assist - and its the same TCU i had great range on before.. i'll give it a try regardless..

oh and sorry for thread hijack LOL... this may go down as the worst hijack in history..

Can anyone advise me on this?
I have a 2000 M5 that had a phone system in it, have the SES module still in car. If I do the 25 to 54 pin adapter should this unit be a simple plug and play (with BT antenna of course)?
Are the newer (E90, etc) modules compatible? Have seen a few listed on ebay but when I do a search on the part number on realoem or BMW parts sites I get nothing, any idea why that is?
Any reason not to mount the BT antenna in the arm rest area? For better reception...
Any difference between the CDMA and GSM units in regards to BlueTooth useage (dont care about plugging phone in, no snap-in modules for my phones).

I have tried searching, but find little about what makes the early 2000's different. I know with the ULF setup they charge an extra $100, but haven't seen WHY...
I dont use the phone often in car so I can't justify spending $500-800 on a BT setup, but $300ish for a used TCU is closer to justifiable for me (and wife unit)...
Thanks all..
Matt

Yes, this would be plug-and-play in your car. I helped a friend of mine do this installation in his 2001 750iL with SES. Your in-car wiring is essentially identical to his. All you need is the 25-pin to 54-pin adapter and the TCU part number listed above. That is it.

Do not use an E90 TCU; that would be incompatible with your car. This TCU, part number 84.10-9 195 455 is described as a "CDMA" TCU. Other units described as "GSM" are for European-markets, I think, and would not be compatible with your car.

Guys, Noob here, and not to hijack the thread and your all awesome, but can you tell me in my 04 X5, I have assist and it has a bluetooth antenna attached to it...do I need all the other parts besides the TCU, like the new gen mic, the BT antenna and BT antenna bracket? Thank you! P.S. I think this thread should go sticky..!

If you have Assist in your 04 X5, then you only need to swap the TCU modules. Your car should have the new gen mic. You will have to look for the BT antenna and bracket-- it may already have those too.

You will need to get the new TCU coded in your car to make it perfect.

Brian, Hi, Thank you, It has a BT antenna mounted, but is it for the assist, if so then I would need a second antenna? I would need coding to get the VR to work?
What is it that Jochen is working on with navcoder, will that allow us all to have VR, or will we have to use the GT1 softwae?

The car only needs one BT antenna. So, if it is there, then it is all the newer BT TCU needs. However, you will probably have to visually confirm the presence of the BT antenna to be sure.

The dealer's Progman (GT1, etc.) software is what you probably want to use to code it. It will fully configure the Assist and other settings for your car. However, if you do not care about Assist, then all you really need is Jochen's NavCoder to enable voice recognition.

Well I wonder why there is a BT antenna, it is even mounted where the BT antenna goes and it says bluetooth antenna...I better check the part number on the TCU, something is up...oh and Brian I am 750il96erbill over on the BB!!

Very cool-- good to make the connection. Your X5 is stunning, by the way. I love that color. It is not Imola, right? It looks like it has a little more blue than Imola in the pictures.

Anyway, you probably do have the BT antenna. BMW installed a lot of BT antennas in cars that did not come with BT-capable TCU modules. So, you could be in that lucky crew. My hunch is that all you need is a TCU swap and coding.

Thank you! and it is Imola, I was using my cellphone for the pic and that is when it was still on the lot.
I will check the TCU tonight for a P/N.

Thanks Brian.
I am guessing you have a ULF setup in your E38? Did you notice a difference between the ULF in yours and TCU in his, as far as features of BT or Voice Recognition?
BTW, Any pics of your car? I love the Highline Interior on those... Was planning to get an E38 before I test drove an M5 and fell in love with the power...
Also, any pictures of the BT Antenna connector, or anyone know what kind of connector is used?
Matt

Thanks for the interior compliments. I love it-- it is the reason I bought the car, actually. I had a 1998 740iL for 6 years, and I developed a serious Jones for the Highline. So, I sold it and bought the 2000 750iL a couple years ago. Unfortunately, I do not have any good pictures handy. Also, the Bluetooth antenna plug is called a "Fakra" plug, but I do not have any handy pictures of that either.

Yes, I have a ULF, and I have installed a TCU in my Dad's 2002 E46 and helped my friend install a TCU in his 2001 750iL.

Here is a list of the major differences we have identified so far between the two:

• ULF has voice recognition enabled in the factory default coding
• TCU has voice recognition disabled in the factory default coding
• NavCoder can enable and disable voice recognition in both TCU and ULF modules

• ULF has the complete VR instruction set that includes navigation commands
• TCU only has the telephone-related Vr instruction set

• ULF requires a pairing button (typically with an eject box and and adapter wiring)
• TCU does not require a pairing button

• ULF 13th generation discounted "official" retail price is $455 (Tischer BMW as of June 2009), but unavailable through US dealers
• ULF 13th gen typically costs >$600 from eBay and other non-BMW sellers
• TCU costs $328 + $50 core (Tischer as of June 2009), and is easily available through all US dealers

• ULF 13th prices used on eBay are typically around $500
• TCU used prices on ebay are typically arond $250 for the newest version

• TCU seems to have better in-car volume than the ULF (my own personal experience comparing my ULF to two other TCU installations).

• TCU shows signal strength on the navigation screen telephone menu.

• TCU has a slightly cooler ring sound (my own personal preference)

Thanks for the feedback Brian, too bad GA is so far from San Diego...
With the stock SES module I dont need the VR (TCU) enabled right? SES will take care of nav and phone?

What should I search for on Ebay? I only found a non BT TCU, and a few E90 units (which are MOST right?)
Wish I could try it out before kicking down the $, not sure if its something I really need or not...
Thanks again.
Matt

Right, since you have VR covered with your SES, the TCU is perfect. If you buy a used TCU, it could have VR turned on. In that case, you could use NavCoder to disable VR. Here is a great TCU part number reference. This will help guide you to the TCUs that have Bluetooth (and VR). In your case, you could live with a slightly older TCU that has BT but not VR.

http://www.bimmerboard.com/members/p...artNumbers.pdf

Has any one actually tried to swap a TCU in a pre March 2004 build of the X5? Any one done the swap of TCU in an X5 and actually gotten it to work? I was considering trying it but I can't return the module if it does not work. All the anecdotal evidence seems to be in other cars and not the X5. I know there was a specific wiring issue with the X5 that prevented the early adopters that thought they had bluetooth from actually installing a TCU. The only known option is still a ULF. Anyone have any feedback?
Thanks!

I have a 2002 X5, no dsp, no navi. I got a TCU from my friends X5, with help from Brian-bmw and others, I managed to get it to work including voice recognition. I have not tried to upload the phone book yet, but everything else works great.

+1 to SLX5.

I have studied the wiring diagrams for the X5 and compared them to other models, and I have not discovered any differences. Furthermore, I have not found any documented issues that point to unique wiring in the X5 that prevents a Bluetooth TCU from working in the early model year cars. So, I would chalk-up the X5 TCU incompatibility wiring issue to urban legend unless we can get some confirmation (and with confirmation will come remediation).

Brian and SlX5,
Thanks for the update. The wiring issue is actually from BMW itself. This is part of the SIB for the later models that can have the TCU replaced. I am really considering going with this option. The TCU is about $350 which is a lot cheaper than the ULF. I am nervous that if I can't get it to work in my car, I will be taking a loss in reselling the TCU and still have to end up with a ULF. None of the vendors will accept a return on the TCU. There are also previous threads on this forum where people have attempted to do this retrofit with the earlier 2004 X5 that came with the TCU that had a bluetooth passcode but no bluetooth

Good news is you can easily sell the TCU to someone if it doesn't work... Maybe it you lose $50 on it or so, but its decent risk I'd say... Plus then others can benefit from hearing your results. ;)

BTW SLX5: Doesn't the phone book transfer automatically? Just hit the guy speaking on the steering wheel--the phone book should pop up on the radio display (if you have Nav go into the Phone Book directory)

Do you know the SIB number?

The only significant TCU SIB I know about is SI B84 13 04. This SIB discusses the upgrade and explains the production breakpoints for cars that had TCUs without Bluetooth and then TCUs with Bluetooth but not voice recognition. There is a statement about wiring compatibility, but it is not exclusive to the X5, and it does not preclude the TCU from being installed in an earlier car in general. This is the quote...

"For E46 and E83 vehicles up to 3/05 production and E85 and E53 vehicles up to 4/05 production, voice activation functions are not part of the TCU. A separate SES module can be installed. Refer to the EPC.

• E46, E83, E85 and E53 vehicles produced between 3/2004 and 8/2004 are equipped with a TCU that does not support Bluetooth. On these vehicles, the TCU can be replaced at the customer's expense with a 2005 MY TCU. Cradles may not be added to these vehicles because of wiring incompatibility."

This is referring to the handset cradle, but you would simply remove the cradle, if you have it. If you have any idea what the SIB was that talked about X5 wiring compatibility, maybe we can take a look and figure it out.

sna77, I tried to upload the phone book by pressing the "guy speaking" it didn't do it.

I have a Palm Treo 650, with the TCU 84 10 6963798 and I have a 2002 no navi or DSP, anyone know how to (or what buttons I need to press) to upload the phonebook?

I came across this on the BMW bluetooth

http://www.e38.org/BMW-03_00-Voice-Control-en.pdf

(pg 10)

The names and telephone numbers
entered in your voice control
phonebook are independent of the
telephone or SIM card memory of your
BMW car telephone or BMW mobile
phone.
In other words, it is not possible to call
up the numbers stored in the telephone
itself or on the SIM card by voice input,
nor is it possible to store numbers there
by voice input.


But people in here have being able to do it.

Cool, thanks for posting that info. That answered my question regarding having to retrofit a cradle with the BT button. Looks like I'm having bad luck with the TCU's I've bought so far. Will try having the bluetooth programming turned on as Killcrap has suggested.

You may have a bad TCU moule. It is possible to turn BT on and off with coding. However, if it was turned on previously, it should remain turned on when installed in your car. Check out NavCoder. Jochen as recently enhanced it to directly enable and disable a number of features. That is a lot easier than taking the car to a dealer.

Hey Brian. I did install (update) my mk4 with a ver that had the ///M logo that I dl'd from the M5 boards. I wonder if that has anything to do with it. Unfortunately, navcoder is pc based and I'm a Mac user. Do you think if I just reinstalled he most recent mk4 software update it may fix my issue? Currently with the tcu I bought, it says "phone connected?" when you go to the telephone screen. Does that mean something? Any help is appreciated! TIA!

The updated nav OS has nothing to do with the Bluetooth function on the TCU. They are independent of one another.

I am not as familiar with the TCU messages, so I can only think of three potential causes of a "phone connected" message.

1) Bluetooth is disabled
2) A Bluetoth phone is not paired with the car
3) The TCU does not support Bluetooth, and the wired handset is not connected

Just to go back and double-check, what is the part number of your TCU module? I looked back through one of your other threads, and you mentioned a part number 84.10-9 120 844 that you were helping install in a friend's car. I originally said that was a good PN, but I must have misread the number. Part number 84.10-9 120 844 does not support Bluetooth.

I updated my TCU with the latest model and no luck. I have to do some more research. I had installed a pairing button with the intent of getting a ULF before all this new info about the TCU. I will remove the pairing button and see if I can even get it to recognize. I purchased a re manufactured unit from Tischer. Any ideas of what I should check for? I will verify that there is a bluetooth antenna. That is the only other thing I can think of that may be missing. I have a 04X5 made in August of 03.

Thanks!

As soon as you start your car it, it goes into pairing mode. I would suggest to put the phone into pairing mode, start the car and take the phone to the trunk where you have installed the TCU. Even if you don't have an Antenna, it should pick up. Remember you will need the pass key once it pairs. Also check for the mic.

SL,
Thanks for the tips. I also replaced the mic with the newer model. I will try it from the trunk area though that is a good point.

Abster

Definitely remove the pairing button and eject box if you have that too. These are incompatible with the TCU.

Next, your car most likely does not have a Bluetooth antenn. It might have the BT antenna cable, though. So, if you have not installed a BT antenna and have not visually verified that one is in the car, then you will need to add that.

Finally +1 to everything SLX5 suggested. The TCU goes into pairing mode for a couple minutes every time you start the car. So, just be ready to pair your phone as soon as you switch the ignition on.

Brian,
Thanks for the feedback. I have one question about verifying that there is an antenna, where is the antenna usually located? I remember something about the pillar of the drivers side door? Also, do you have part number for the antenna? I need to return the core to Tischer and I will use the refund to purchase an antenna if required.

Thanks!

I am not sure where the BT antenna is officially located in the X5. I think that it is on a bracket above the nav computer/CD changer.

Here is the BT antenna part number, and a BT antenna cable if you need that too.
84.50-6 928 461 Bluetooth antenna
61.12-0 137 616 Bluetooth antenna cable

what TCU is needed to add Bluetooth to an 04 4.4i MY 8/04, thanks

The newer, the better.
Units below have bluetooth and Assist

TELEMATICS CONTROL UNIT CDMA Sep-04 to Feb-05 84116946993 1st release of integrated BT/Assist TCU (personally confirmed BT). No voice
input but can be added by separate SES voice module.

TELEMATICS CONTROL UNIT CDMA Mar-05 to May-05 84106964114 Added support for voice input (phone only, not nav). Added support for
Siemens S66 phone

TELEMATICS CONTROL UNIT CDMA Jun-05 to Aug-05 84106965056 Improved performance of Address book transfer on some phones reported.

TELEMATICS CONTROL UNIT CDMA Sep-05 to Feb-06 84106963798 Fixed problem of NAV defaulting to Telephone menu on startup. Has voice
support; works better than 993


TELEMATICS CONTROL UNIT CDMA Sep-05 to May-06 84109120843

RMFD TELEMATICS CONTROL UNIT CDMA Sep-05 to Jul-06 84109122529 RMFD = remanufactured.

RMFD TELEMATICS CONTROL UNIT CDMA Sep-05 to Sep-06 84109132711


RMFD TELEMATICS CONTROL UNIT CDMA Mar-05 to Sep-06 84109171721

TELEMATICS CONTROL UNIT CDMA Sep-06 84109115729 Continental TCU

TELEMATICS CONTROL UNIT CDMA Dec-06 84109129851 part no not in realoem database

TELEMATICS CONTROL UNIT CDMA Sep-06 to Sep-07 84109166534 ENDED

TELEMATICS CONTROL UNIT CDMA 84109195455 Newest iBus TCU currently being sold by Tischer 09/2008

thanks for the help ended up getting the 933 first edition BT module and works great. now i wanted to add the cradle and iphone snap in adapter? this is my nex hurdle, thanks again any advice on part numbers for the proper cradle and iphone aapter.
? thanks

Re: Retrofit Bluetooth with a TCU instead of a ULF in any I-Bus Car
 

Anyone?


Sent from my iPhone using Tapatalk

OK, I've just been to the BMW dealer in the UK and they say the UK has never delivered a TCU although it is on the pricelist. I have a few questions with this, is the TCU 84.50.6.928.461 only a BMW assist unit for the US? Will it work as a bluetooth unit in the UK, (Obviously, I'm not interested in assist), and finaly do I need the adapter harness 84.11.0.302.181 as they don't show this as a valid part.

Cheers,

- Douglas

The USA gets a TDMA TCU.
For Europe you need the GSM TCU

However, the phone part is only for the assist function - so therefore if you ignore Assist you probably can use the TDMA one in Europe. I only say probably as I am not 100% sure...

what is the difference between TCU and ULF?

The ULF and TCU modules are two different components that can provide Bluetooth capabilities. The ULF is solely dedicated to Bluetooth. The TCU does a lot more, but only the newer modules have Bluetooth and Voice Recognition. Ironically, the TCU is about ½ the cost of a ULF.

Here is a high-level summary of the two. There may be more differences, because this is largely based on observation from the BMW community.

* All ULF modules provide Bluetooth
* Only the newer TCU modules have the Bluetooth feature

* Most ULF modules have built-in voice recognition
* ULF has voice recognition enabled in the factory default coding
* Only the newest TCU modules have the voice recognition feature.
* TCU has voice recognition disabled in the factory default coding
* NavCoder can enable and disable voice recognition in both TCU and ULF modules

* ULF has the complete VR instruction set that includes navigation commands
* TCU only has the telephone-related VR instruction set

* ULF requires a pairing button (typically with an eject box and and adapter wiring)
* TCU does not require a pairing button

* ULF 13th generation discounted "official" retail price is $455 (Tischer BMW as of June 2009), but unavailable through US dealers
* ULF 13th gen typically costs >$600 from eBay and other non-BMW sellers
* TCU costs $328 + $50 core (Tischer as of June 2009), and is easily available through all US dealers

* ULF 13th prices used on eBay are typically around $500
* TCU used prices on ebay are typically arond $250 for the newest version

* TCU seems to have better in-car volume than the ULF (my own personal experience comparing my ULF to two other TCU installations).

* TCU shows signal strength on the navigation screen telephone menu.

Thx for your very clear informations, BTW I wonder if it is possible to mount (after market) a TCU unit on my european X3 with steering control.
Where can I find (if any available) a step-by-step procedure to do it yourself?
I know that the retrofitting with a ULF is relatively simple, is the same way with the TCU

I have not seen a step-by-step retrofit guide to install a TCU in a European X3. However, if you found instructions to install a ULF, you can follow those for the TCU. The installation is essentially identical, except you do not need to install the eject box for the TCU.

well fact is that we have in the italian BMWpassion forum a guide to install the TCU and it is pretty simple. You need some cable, connectors and a TCU..off course. The you add some pins to the radio module connector and hopefully it will work... But I am not sure if the connection schematic is the same as for the TCU.

The late model Euro TCUs have different P/Ns from the US ones. Quite a few numbers in the ETK list.

Hope you guys can help me, I have been hunting around for hours trying to find a definite answer! I have an E46 2003 330d with sat nav, tv, cd changer, harmon Kardon and bluetooth. I have an N97 mini which refuses totally to pair with the cars bluetooth. It connects and then immediatley disconnects.

I understand that I will have an older generation ULF module which is present in the boot area above the CD changer. This is probably why my phone won't pair with it due to the age differences in the technology. I have done a bit of research and found out that Telephone TCU's are a cheaper alternaive to replacing the costly latest gen ULF.

If I remove my ULF and replace it with the latest TCU is it a simply plug and play swap over?

I have already removed the phone eject box from the console and replaced it with cup holders.

Thanks in advance.

Paul.

Yes, the TCU is plug-and-play replacement for the ULF in your car, especially since you already removed the eject box.

Many thanks for your quick reply, that's good news then! I have checked the latest TCU available in the USA which is part number 84109195455. Will this be compatable in the UK or will I have some problems with it. There is a part number for the UK one but I don't think it is as late a build as the US one!

I think that the US TCU would work OK in the UK, but I do not know for absolute certain. The main difference is the cellular band that the BMW Assist and wired telephone operation on. However, that is not involved at all with the Bluetooth, so I doubt that it matters.

I've had a similiar problem since my wife changed her phone.
Car 04 325 cI C with ULF. Phone is a Verizon Env3. Prior phone was a RAZR V3.
Even had my dealer try to pair it with the Verizon Env3 .. no luck..
It WILL pair with my son's BT ear piece, and I have not tried it with my 06 X5, which pairs fine with my LG 8300.
I don't know how to tell which ULF or TCU ( I do have Voice Reco in my X5), I have, but if I am able to successfully pair her phone to my X, can I assume that upon discovering what type of device is in the X and version ie, TCU vs ULF and Gen #, if I replicate it in an E46 will her phone work?

Thank you
ED

Try disabling the phonebook pairing and see if that helps. The Env3 phones seem to have mixed experience with people.

Power down issues on TCU
 

My two year old BMW battery is dead on a 02/2004 build X5...
Performing SIB 61 08 00 "Closed Circuit Current Measurement " shows 286 milliamps being drawn once the 16 minutes have elapsed and the vehicle goes into sleep mode. It should be less than 40 milliamps. While still measuring current, pulling Fuse 74 immediately drops the current to 21 milliamps. This tells me my Everest TCU is not powering down.

Looking at the 45+ SIB's on Telecommunications I only found SIB 84 01 04 which states the following:

SUBJECT
Service Action: Check and Replace TCU
MODEL
E46 (3 Series), E85 (Z4), E53 (X5), E83 (X3)
SITUATION
Low ambient temperatures (below 32°F) may cause the TCU (Telematics Control Unit) to go into reset mode.
The result is that calls to BMW Assist or "SOS" calls will not be completed.
Once in reset mode, the TCU will remain in this condition even with the ignition turned off. This could result in a discharged battery.
This Service Action will check the TCU and replace it if necessary.
...
AFFECTED VEHICLES
This Service Action involves E46 (3 Series), E85 (Z4), E53 (X5) and E83 (X3) vehicles which were produced from 8/2003 to 11/2003.


Has anyone found any SIB which indicates more recent TCU's have issues powering down? If the The Non-Volatile Memory (NVM) within the TCU has been corrupted (see SIB 84 07 07) can this cause it to not powerdown?

This is a TCU retrofit thread. Your issue is totally unrelated. You might have better luck if you start a brand new thread with this question.

I posted the question here as those who are adding a TCU need to be aware of all the issues BMW has had with the past parts... hence my comment about the 45+ SIB's which exist since 2003. Perhaps a list of these bulletins would be more value for the thread.

I was actually hoping you or kiwijochen would have an answer!

Ok here is a new challenge for everyone (looking at Brian and Jochen ;) )

I have a 2003 Range Rover with MKIV Sat Nav, DSP and built in telephone module (the kind you put a sim card in) with an eject box in the arm rest.

It has voice recognition now, and i can control the nav and phone by voice.

I want to upgrade to bluetooth (either by TCU or ULF but prefer TCU because of price, and the fact i wont require a pairing button).

Obviously I already have the microphone, but i doubt there will be an antenna so i will purchase one of those.

My question is will the TCU or ULF module work? and would i remove the current phone module (whereever it may be) and replace with the TCU or ULF module?

I'm willing to experiment, and use navcoder/post results so everyone can share the info.

Cheers

This is quite straightforward:

1. Determine exactly what type phone you have now, as per WDS
2. Remove old telephone control unit
3. Adapt wiring of telephone connector (if necessary) to suit TCU
4. Connect TCU and code as required.

You are not the first to do this...

NOTE: you will currently have a separate SES module for voice recognition (VR), you can choose to retain this or replace the VR with the TCU VR (TCU = phone VR only)

But Range Rover aren't listed, do i have to keep looking at different ones on WDS until i find one with matching wiring?

No Problems

What coding options are there other than enabling VR? And if i enable VR on the TCU and keep the existing VR SES module will it get confused when i use the VR button?

A Range Rover is an X5 in a different skin
Look at the X5 phones.

Yes, 2 x VR will be confusing!!

Other options:
VIN
Speed dependent volume
Assist functions
GPS dead reckoning adjustment for Assist
Bluetooth on/off
Change Bluetooth name
Change Bluetooth passkey
And more.... but the rest are not so interesting...

So i can disable VR on TCU (i dont care about not dialing using VR)

Can these all be done with NavCoder?

Yes, disable VR on TCU

NavCoder can set all TCU options - some are in beta test right now but all looks good
Most people don't use Assist so I didn't bother making the Assist options visible...

Great - everything is a lot clearer now.

One last thing thought. What types of telephone module are there?

Obviously there is the ULF module, and the TCU module i need to fit (with bluetooth), but what other ones are there?

I'm assuming my car doesn't have bluetooth, because it has a slot to put a sim card in. But could it be a case of removing the eject box and adding a bluetooth antenna?

I'll have time tonight to try and finde the telephone module in my range rover (in the boot maybe) but i think it will only have Land Rover part number on it

Well there's the Siemens fixed unit, the Siemens cordless phone, around 2 or 3 variants of that
Plus Motorola, around 10 variants

In all there's around 15 or so different phone types for the BMW.

Depends on vehicle, age, country, system...

Nothing is ever easy it is hahaha.

Well had a quick look at WDS, and i have the cordless type, and it's a 2003 Range rover so my money is on the highlighted one in the pic, but i will take out the telephone module tonight and compare wiring colours/pin locations on the module.

Neil, I've been working on preciciely the same conversion. Bimmernav sells a kit to do exactly what we want using original parts but it's pricey. A couple of smart guys like us can certaintly figure it out. So I got a UTF to try but when I plug it into the factory plug it freezes the satnav etc. I have heard that the Range Rover and X5 use slightly diferent pinouts although the same conector. I have downloaded teh pinout for the x5 but haven't found it for the RR so am hoping the colours are for the same components... that's as far as I have gotten.

- D

UTF???

And what connector did you look at? I'll be taking my phone module out the range rover tonight, so will happily share pin outs on the connector that plugs into the module.

Is the telephone module in the boot in the rangie?

Well it is quite straightforward, change the pinout from the old phone to what the ULF needs.

You'll have some wires left over, and you'll need to add a couple, but it's pretty easy.

I helped a guy in the Middle East do it last week.

Jochen

Yes, in the boot, around where the video module is.

If you have the Siemens phone then the pinout is shown in the WDS.
But confirm the phone type first

OK this is what i have, I really got confused when i saw the antenna (part number 8540 8387422) ontop of my nav drive, i thought it was bluetooth but not sure now. Also, should there be two antennas? I could see two antenna cable plugged into the bottom of the siemens unit.

Now how do i find the correct one in WDS? And more importantly, if i buy a TCU, how will i know which wires go to which pins if i cant check the pin configuration of the car the TCU came from?

Read this:

BIT 2 with CKPH (GSM and WDCT networks)

The Siemens CKPH (cordless keypad handset) is connected via a WDCT antenna to the BIT 2. Data communication with the vehicle electrical system takes place via the I/K-bus interface. This enables operation via the on-board monitor, MID and multifunction steering wheel. Hands-free operation is effected by means of a microphone and the existing audio system, radio, DSP or double-coil speakers. Other audio sources are deactivated by the control unit during hands-free operation.

Reception and relaying of SMS messages is possible. These text displays can be read off in the CKPH1 and CKPH2 and in the on-board monitor and MID. A personal telephone directory can be stored on the SIM card.

Long-distance data or fax transmissions can also be effected with a separate connection.

Brief description of components
The Siemens telephone with CKPH (fixed mounting) consists of the following components:

•CKPH (cordless keypad handset)

•Eject box with card reader

•Basic Interface Telephone

•Hands-free microphone

•Double-coil speakers

•Antennas

CKPH (cordless keypad handset)
The cordless keypad handset replaces the handset previously supplied with a coiled cable. The cable connection to the eject box is omitted. Communication is conducted by radio and enables more freedom of movement. Calls can thus also be made and received in closer proximity to the vehicle (approx. 10 m).

The eject box is the basic and reception station for the CKPH. In the case of the tandem system option, the second CKPH is accommodated in a second eject box in the centre armrest at the rear. The handset can be stowed with the keypad facing upwards or downwards.

Data is transmitted between CKPH and BIT 2 via a WDCT antenna (Worldwide Digital Cordless Telephone antenna (2.46 GHz).

The cordless keypad handset is supplied by a storage battery. The battery is recharged by integrated charging electronics when its capacity drops below 1/3. However, the CKPH must be engaged in the eject box for this purpose. Charging starts only when terminal R is activated.

Important: A charging procedure lasting approx. 10 hours is initiated when the storage-battery compartment is opened. This formatting procedure results in an increased closed-circuit current.

Caution: Do not charge storage batteries externally!!

Eject box with card reader
The eject box serves to accommodate the telephone handset. It contains a voltage regulator and an SIM card reader and is located in the centre armrest.

The ISM band (Industrial Science Medical 2.46 GHz) is not authorised in all countries. WDCT operation can be deactivated and activated with a switch in the eject box. With one switch-off operation, the BIT2 control unit and the SBDH on the ISM band are deactivated (the WDCT switch is at ”0”).

With the WDCT switch at ”0”, the radio link to SBDH is not set up when terminal R is switched on again. The SBDH no longer functions. The telephone unit can only be used without the handset.

The power supply is provided by terminals 30 (+6V) and 31. Terminal 58g supplies the signal for illuminating the CKPH.

Basic Interface Telephone 2
The BIT 2 control unit contains the following components:

•I/K-bus interface

•Motor-vehicle interface (audio)

•Microprocessor, program and data memories

•GSM module

•WDCT basic station

•Voltage supply

Data communication with the vehicle electrical system is facilitated by the I/K-bus interface. It is thus possible to operate the phone using the multifunction steering wheel, on-board monitor or MID.

The WDCT basic station has a transmitter power of max. 10 mW and establishes the connection to the CKPH via the WDCT antenna. The transmitter power is modulated as required.

The BIT 2 control unit is located in the luggage compartment on the left.

If terminal R or 15 switches to ignition-lock position ”0”, the phone remains active for a certain run-on time. The run-on time (timer) can be set between 0 and 120 minutes in the phone menu on the handset (refer to Owner's Manual). 0 minutes is set as the standard value.

Hands-free microphone
Hands-free operation is effected by means of a microphone and the existing audio system, radio, DSP or double-coil speakers. Other audio sources are deactivated by the BIT 2 control unit during hands-free operation.

Communication is conducted in digital full-duplex transmission, i.e. NF is enabled for both call participants. It is possible to speak and listen simultaneously.

Double-coil speakers
Double-coil speakers are only fitted in conjunction with the hands-free facility. The audio coil is muted during an incoming/outgoing call. The second coil is used for conducting communication.

On cars without DSP , the BIT 2 control unit is connected directly to the double-coil speakers. On cars with DSP, the speakers are connected directly to the devices. The double-coil speakers are installed at front right and left.

Antennas
The BIT 2 control unit transmits and receives calls from the mobile-telephone network via the GSM antenna. The wideband antenna is designed for a frequency of 900 MHz and consists of two emitters.

Depending on the model, the GSM antenna is fitted at the following locations:

Model
Location

E38
Group antenna on outer skin of roof

E39
Window antenna

E39/2
Antenna on outer skin of roof

E46
Antenna on outer skin of roof

E46C
Antenna rod

E53
Antenna underneath rear spoiler




The WDCT antenna transmits the communication by radio to the CKPH. The installation location depends on the model and is set out as follows:

Model
Installation location

E38
underneath rear parcel shelf

E39
underneath rear parcel shelf

E39/2 (touring)
under left side trim panel

The antenna is the WDCT antenna (worldwide Dect)

[QUOTE=neiloakley;702894]Now how do i find the correct one in WDS?

It is printed in black and white on your phone module what it is. And looking in th WDS, there are only TWO matching options - and the only differences are with or without voice recognition.

So there you go. The phone type is non-ambiguous.

Again, look at the WDS. You will see there are only 2 x TCU entries. And the only difference is with or without voice recognition.

So once more the solution is very clear.

Refer to the WDS, and compare the wiring differences between TCU and your Siemens BIT-II phone.

Then simply change the BIT-II wiring to the TCU wiring.
The WDS tells the whole story.

Can you send me a screenshot of the TCU you are seeing in WDS? I dont even have a TCU yet so i'm unsure how you have found the correct one.


I do have voice reconitiong at the moment (I will use navcoder to disable VR on the TCU to avoid conflict)

Really simple.

When the list of phones is on the screen, you go through them until you see the one that says "TCU"

Honestly, it's as easy as looking up words in a dictionary!

You don't need a screenshot for that....

argh i think it's just clicked. The Wiring is not specific to the unit, but the car.

SO all TCU units need the pins in the same configuration, and it need to swap the wires in my car about to match the configuration required by the TCU

So my car currently has
Telephone (BM On-Board monitor with Fixed mounting, Siemens (cordless handset) with SES Language-input system up to 2002_3)


And I want to fit a TCU unit so i need to swap the wiring to match the following:
Telematcis control unit (TCU-Everest) (SES Language-input system with TCU Telematic Control Unit without USA_LHD)

Which TCU i get doesn't matter, as long as i have rewired my connect for a TCU moduel correct?

Well, thats the same isn't it?

The only difference in TCUs is whether they are ECE or US models.
ECE = Assist over GSM, and optional Bluetooth cordless handset in the car.
US = Assist over CDMA, and no optional Bluetooth cordless handset in the car.
But the wiring (power, ground, ibus, microphone, audio) is identical.

As I said earlier: "simply change the BIT-II wiring to the TCU wiring."

Of course, always refer to the right wiring diagram.
Do not read USA diagrams if you have a Non-US market car.

The WDS shows all, very clearly.

No - a TCU module in a x5 could have the power on pin 1 and ground on pin 2

a tcu module on an x3 could have ground on pin 1 and power on pin 2

If you are saying the wiring for TCU modules are identical then i understand what i need to do, and as long as i look at ECE diagram in WDS and rewire to match that, i can get any ECE TCU module and plug it straight in.

I'm now looking for one of these (sourced form here http://www.bimmerboard.com/members/p...artNumbers.pdf)

European GSM based TCUs - won't work in US

TELEMATICS CONTROL UNIT GSM Jan-05 84116946991
TELEMATICS CONTROL UNIT GSM Mar-05 84106965055
TELEMATICS CONTROL UNIT GSM Sep-05 84106964113
TELEMATICS CONTROL UNIT GSM Jul-06 84106963758
TELEMATICS CONTROL UNIT GSM Nov-06 84109129850
TELEMATICS CONTROL UNIT GSM Mar-07 84109127894
TELEMATICS CONTROL UNIT GSM 84116946011
TELEMATICS CONTROL UNIT RFMD GSM 84106978533
TELEMATICS CONTROL UNIT GSM Jul-06 84106963758

TELEMATICS CONTROL UNIT GSM Nov-06 84109129850

WDS shows very clearly:

X5 TCU = power term30 pin 17 & pin 18, power termR pin 35, ground pin 36 & 54

X3 TCU = power term30 pin 17 & pin 18, power termR pin 35, ground pin 36 & 54

You may care to note that the WDS contains all the info you need.....

Hi

I am hoping to add bluetooth to an E46 that has not got it, nor has the cabling for it, by making up some cabling for power, ibus and audio via a mute box. I have an aftermarket Alpine media station head unit fitted.

I am in possesion of a 2005 TCU +SES module. It has a 54 pin connector. Does anyone know the BMW part number of the barebones connector so I can buy one and make up a loom? Else is a cheap loom with the 54pin connector available? I saw mention of a 25pin to 54pin adaptor, is there a BMW part number for it?

Also is the audio signal on pins 37/38 the caller's voice, and is it an amplified signal or line-level?

The 54-pin adapter plug is part number 84.12-0 308 375. I would build your custom wiring based on this.

I think that the caller voice output is line-level, because that would normally route through either the radio or AMP, depending on year and options of the car. I don't think that ever drives speakers directly.

Also appears to be available loose, but from Audi

4E0 972 144 54 pin multilock (Audi) £1.47
000-979-010 Pins for the connector £0.97 each

Jochen

Please feel free to call me an idiot but i still cant figure out WDS. Hopefully you will see i have tried . . .

I've selected E53, then selected Communication>Telecommunication>Basic Interface Telephone (Bit II) (SES Language-input system with BIT Basis Interface Telephone from 2003_03)

That shows a diagram with component U407

So i look up U407 and get Component and signal information>Components>U)Radio/interferance supression equipment>U407 Basic Interface, telephone>U407 Basic Interface Telephone (Fixed Mounting, siemens (cordless handset) from 2002_03)

But i cant find the pin out list for this.

When i search for the TCU (I01157) it comes up with Components>I_Components of outside manufacturer>I01157 Telematcis Control Unit (TCU_Everest) (without USA_LHD)

and then i can see a table of all the Pin assignments at plug connector X18500

Where can i go from here? The only pin out i can find for BIT2 is X4038

but that doesn't show "Basic Interface Telephone (Fixed Mounting, siemens (cordless handset) from 2002_03)" only "up to 2002_3

So shich plugs should i be comparing? X18500 and X4038 seem so different :dunno:

X4038 - Siemens Internal (Eject Box) at pins 1,2, 5, 19, 20, 37, 38, 48
X18500 - Telephone, Internal (Eject Box) at pins 3, 5, 6, 32
I can work these back using the wiring diagram for A117 Eject Box, but that only shows the pins for BIT, and not diagram for TCU. BIT has 8, TCU has 4, happy to leave 4 disconnected but without colours for the TCU wires i dont know which wire from the TCU goes to which pins on the eject box

X4038 - Comunication Link TXD RXD and Sheild at 9, 10, 11
X18500 - NO SUCH CONNECTIONS
See attached picture, it doesn't go anywhere? Can i leave it off?

X4038 - Data Cable (Navigation Unit) at pin 28 and 46
X18500 - NO SUCH CONNECTIONS
See attached picture, it doesn't go anywhere? Can i leave it off?

X18500 - Night Light Signal pin 52
X4038 - no such connection
I can get this from the eject box, pin 3 (X4545)

The circuit diagram shows connector numbers, and also shows the connector pins, wire colour, wire size and wire function.
Just click the connector number for a full table.

Thats all the info you need.
You see the wiring and signals of the existing BIT2
You see the wiring and signals of the wanted new TCU

Simply transfer the relevant wires from the old to the new

Of course, some will be no longer required, and you may need to reassign some wires running from phone to the eject box.

But it is pretty straight forward.

Work in this order:
Ground
Ibus
Power
Microphone
Audio Out
Eject Box
SOS switch (if fitted)

That's all you need.

Hi Jochen - thanks for taking the time to reply. I've done all the wires i thought i needed, and now it comes up 'Activate Phone' on the nav screen correctly, but i'm unable to get the TCU to go into pairing mode.

Not for me it doesn't! When i look at the TCU wiring diagram it doesn't give me wire colours. So i have no idea how to give the TCU the 4 wires from the eject box it needs, when the BIT2 had EIGHT wires.

(see diagrams below)

Its only simple if you know how to do it.

Ground - done
Ibus - done
Power - done
Microphone - done
Audio Out - done
Eject Box - NOT DONE/CANT DO


Why do i need to connect the eject box anyway? I want to use bluetooth, i have no interest in pluggin in my phone?

If you don't want the eject box then don't wire it. Just ignore it.

The only functions the eject box provide are:
1. phone charging
2. passive antenna coupling
3. physical holding of the phone

Pairing mode of the TCU is initiated automatically when you turn the ignition from off to acc/on, but only for first 15s or so

Jochen

OK i'll leave the eject box off :D

But it still doesn't pair :(

Going to start from scratch and see if i made any mistakes.

if Telephone appears in the nav menu then you have done sufficient wiring to make the TCU pair.

Of course, you must have the Bluetooth antenna connected!

Note that
1. The Bluetooth may be turned off in the TCU - what is the history of the TCU? Where did it come from? Has it ever been coded?

2. Not all phones see the BMW TCU via Bluetooth. Try another phone...

Bluetooth antenna is connected (brand new one) :thumbup:

Not sure of the history. Guess i'll be ordering navcoder and interface to find out.

I thought Bluetooth always came coded on, but VR needed turning on.

Cheers

Neil

Depends - if you have the TCU-ECE model, and it came from a car which previously had the cordless DECT handset then some settings may need to be changed.

NavCoder is your friend :-)

Neil, Can you post the changes you needed to make to the connector? As in what colour goes to what pin?

Cheers,

- D

Ha good sales pitch :) I'll be buying it shortly as it definately wont pair :(

Not that easy mate. Depends what your starting with and what your going too. Plus cant get mine to pair yet so not gunna tell other people how i've done it as may be wrong

Well, give us a chance, I'm doing exactly as you, going from a cordless Siemens in a RR to a BMW TCU. I'll give it a try and see if mine pairs.

- D

Ok at the moment its 15 pages of scribbles, and diagrams. Let me get it typed up so it's understandable and you can have a go.

can you help me...?? i buy yesterday a used 10/ 2004 x3 2.0d with nav.i checked that i have a tcu 84.109129850-01. but i can not pair the phone.on the screen of the radio-nav i only have options like computer-sat nav-set and monitor off (if i remember right) .i can not find any option about telephone.what i have to do??

If the "Telephone" option is not displayed on the main navigation menu, then the TCU is either not connected or it has failed. Based on the date of manufacture, that TCU should have the Bluetooth feature, but I am not as familiar with the European TCU modules.

yes on the top of the tcu has the logo of the bluetouth and a 4 digit pk.it is like this one http://filer.case.edu/jxw115/BMW/BTO.../img_1131a.jpg

Check its plugged in firmly and that the fuse isn't blown. If the unit doeasn't have power, the car wont know its there.

Jochen - Another puzzle for you - why is the BT Pairing button greyed out? I cant get my phone to pair (TCU doesn't appear in list of available devices) and i thought navcode could be used to force pairing

In the latest Beta version your TCU gets identified as a TCU-GSM

I do not know of a way to initiate bluetooth pairing mode programmatically on the TCU-GSM, hence the BT Pairing button is disabled.

But talk to me via email for some fun things to test with your TCU :-)

Do you have any idea why i cant pair? My phone doesn't find the car, i try just after i switch ignition on, i've enabled bluetooth, but nothing. This is the TCU i have retrofitted into a Range Rover

hello,
i have the same issue here,trying to upgrade my bit-II to bluetooth using
84109115729 Continental TCU 2007 X3 date 14.03.2007 SW 03.25 and no need for the eject box

my car is 330i 2003 with mkiv upgraded to v32 with bit-ii wireless telephone

i was reading your post waining for a success job but i cannt get it, did it work with you? and what must i get and replace beside the TCU?

i have the navcoder and the serial to ibus interface for the programing step

Did anyone have probles getting a TCU into pairing mode? Some people in this thread report the need to plug in the eject box temporarily to get pairing to start.

It is possible that a European TCU uses the pairing button in gibbo_ireland's situation. Or, it is just as likely that gibbo_ireland had a ULF and not a TCU. I vote for the latter. Every BMW document I have read and everyone else's documented experience I have read states that the TCU goes into pairing mode every time you start the car.

Can't say I recall where I found this file last year... but for those who have an account on BMW TIS EPA, here's a decent list of Group 84 (Communication) SIBs. Perhaps this could help in some troubleshooting. Most issues have to do with Assist, but there are a few on Bluetooth pairing.

http://www.bimmerboard.com/members/r...to%20Jun08.pdf

Maybe this extra step is required?

Link

Jochen> What is the navcoder command for R/T and seatbelt-in and I can try this on my bench?!

Press the "R/T" button on the steering wheel emulator in NavCoder

I logged
20/03/2010 11:58:23.881: 50 04 68 3B A0 A7
20/03/2010 11:58:23.881: MFL --> RAD : Radio/Telephone control: Send/End_released

I think I need to try it in the car, if it ever comes back from the mechanic...

R/T =
20/03/2010 1:50:33 p.m..282: 50 04 68 3B 02 05
20/03/2010 1:50:33 p.m..282: MFL --> RAD : Radio/Telephone control: R/T_pressed
20/03/2010 1:50:33 p.m..463: 50 04 68 3B 22 25
20/03/2010 1:50:33 p.m..463: MFL --> RAD : Radio/Telephone control: R/T_released

the sneezing man = Send/End =
20/03/2010 1:50:37 p.m..476: 50 04 C8 3B 80 27
20/03/2010 1:50:37 p.m..476: MFL --> TEL : Radio/Telephone control: Send/End_pressed
20/03/2010 1:50:37 p.m..563: 50 04 C8 3B A0 07
20/03/2010 1:50:37 p.m..563: MFL --> TEL : Radio/Telephone control: Send/End_released

I think I'm missing a RAD -->TEL initiate link to handset.

I have a radio here but it won't power up unless connected to a car.

BTW Kiwi: I found the problem we hit the other day with the TCU, and it's my fault.

Nope.

Yes it will, when you know how :-)

Skype or email me

I apologize if this has already been answered here or in another thread. I am currently in the market for either a ULF module or and TCU/SES combination. There are several on eBay, but most ads market them as being specific to certain models/series.

Up until this point, my understanding was that a particular ULF, TCU, or SES module would work in any car, with the limitations being age of the module relative to the car. Are these modules also model/series specific?

Also, is there any difference between a ULF Module and a ULF Module, High?

E46, E39,first X5, X3 are all iBus. 1er, current X5, E60, E90 are all optical (MOST). iBus TCUs and cars are not compatible with MOST TCUs and cars. More important though is the hardware version. All but the very last TCUs and ULFs were very poor at pairing with phones not on the supported phone list. If you have an iPhone, Blackbery or Android, or something else new, you may find most TCUs won't work properly with it.

Thanks, that is good to know. I have an iPhone 3G. I am getting the impression that I will need to buy these new or find something built within the past two years. I get the impression that this is critical for a TCU or ULF, but not so much for the SES. Is that true?

The iPhone works great with a 5th Generation ULF (which is very old), and probably older modules as well. The TCUs with Bluetooth all work with the iPhone.

The SES contains no bluetooth functionality, so the phone you have matters not.

They are model specific

A ULF won't work in a 1500, 1600, 1800 or 2002
Neither will it work in an E24, E31, E34 or E36
It also won't work in an M1

But it will in many other ibus-cars....

Good to know. I understand from your's and Big Bob's message that the ULF is model specific and that the SES has no phone compatibility issues, but do the older SESs (e.g., pre-2003) have any kind of compatibility issues with respect to the car itself? In other words, if I bought a 2001 SES that was taken out of a 7-series, would it work in my 2003 M3 coupe?

The ULF works in any ibus car, which means it is limited to the following:

BMW 3-series E46 (1998-2007)
BMW 5-series E39 (1995-2004)
BMW 7-series E38 (1994-2001)
BMW X3 E83 (2004-current [expected to be produced until 2010])
BMW X5 E53 (1999-2006)
BMW Z4 E85 E86 (2002-2008)
BMW New Mini One and Cooper R50 (2001-2006)
BMW New Mini Convertible R52 (2005-2008)
BMW New Mini Cooper S R53 (2001-2006)
BMW Range Rover L30 (1999-2003)
BMW Rover 75 R40 (1999-2005)
BMW MG ZT X10 / ZT-T X11 (2001-2005)
BMW Rolls Royce Phantom RR1 (2003-??)

Thanks, but my question is about the older SES modules, not the ULF. I'm looking at two options: Either the latest ULF, or the latest TCU with any SES that will work.

I've never seen a post that gives the full details of all SES modules and the improvements made in between. Do you really really need Nav VR? What the hell do you want to shout at your car like a loon for, before giving up and using your fingers? You can be sure VR will be a novelty that wears off in 2 weeks.

I do not know of any incompatibility between the various SES part numbers and the model year of your car. To be specific, an SES from a 2001 7 Series would work perfectly well in your car. This part is generally considered to be interchangeable between all applicable cars (E38 7 Series, E39 5 Series, E46 3 Series, E53 X5, E83 X3, and E85 Z4).

Well, to the extent that I will be doing VR with the phone, I would also like to do it with the nav. Different strokes, and all that. Interesting that there has been no breakdown of the SES modules similar to what I have found with the ULF and TCU modules.

Thanks, Brian. That is very good to know. I'm still comparing the ULF vs. TCU/SES. With the TCU/SES, I like the fact that the car automatically goes into pairing mode when turned on. Conversely, it seems that the ULF option is practical only to the extent that I can (or want to) either--

a) Retrofit my 2003 M3 with an Eject Box; or

b) Somehow acquire a pairing button, which seem very difficult to find; or

c) Make my own pairing button.


Of course, the ULF has the advantage of being an all-in-one unit. Fewer parts to go bad.

I've had VR on most of my BT car kits. It's useless with any road noise present. Just a friendly warning that it's a novelty ;)

Point well taken. I guess BMW just couldn't make it simple, huh?

Ok, I read the following statement on another site that was posted Feb. 2008: "A small momentary switch is perfectly fine since the button does not need to be accessed on a continuous basis - only when new phones are paired to the system."

I take it from this statement that I would only have to go through ULF pairing procedure the first time I pair the phone with the car. After that, the phone automatically pairs with the car. Am I understanding this correctly?

I found the answer:

"Pairing button is used to pair the phone to the car the first time. After that, the phone will pair up once you start the car. Some folks just leave the button under the cup holders so as to not cut a hole into car."

Don't forget about the "notepad" function in the SES module... you can record your voice (and all the background noise) for up to a couple minutes.

As for car specific TCU, there are several settings which can be coded to the TCU if you don't like error codes being logged. Though after 31 occurences, the TCU stops counting. The settings vary by hardware version, but I few I recall:
GPS: on/off
SOS Button: active / not-active
Display: Professional / Business
Voice Recognition: on/off

NavCoder can change some of this.

Were you able to pair this TCU (84.10 6963758 - 03) with your car? I have an exact same issue, ECE TCU (European), Bluetooth gets identified in NavCoder and other systems, but I can't find it with my iPhones, and screen always read ACTIVATE PHONE on on-board monitor and instrument cluster.

Car is USA but this TCU is european, does it mean that I have to re-code the FA / VO to match the TCU? I can't add TCU through progman in standard way I was thinking if I need to overwrite the vehicle order directly and try it then?

thank you.

Don't mean to hijack this post, but someone also look into this post, I got a lot of screenshots in there too with all relevant software:
http://www.xoutpost.com/electronics/...us-x5-e53.html

Can someone share their VO coding code and the TCU part number, I want to try to enter the same one into my car to see if I can get it to work. Thank you.

Here are some of the ZCS (Central Coding Key containing GM / SA / VN) bits for the various telephone options.

0639 00000000 0000800000000000 0000000000 1 TEL_PROF_US //Preparation for car phone US //Autotelefonvorbereitung US
0640 00000000 0000000000000000 0000000000 0 //Preparation for car phone //Autotelefonvorbereitung
0641 00000000 0000000000100000 0000000000 1 TELEFON //Telephone preparation AMPS net //Autotelefonvorbereitung AMPS-Netz
0644 00000000 0000200000000000 0000000000 1 TEL_VORB //Preparation for car phone bluetooth //Autotelefonvorbereitung Bluetooth

"Decode BMW Order v0.3" should be using this info though...

What about 0633 and which one of the options is most likely to be relevant to Ibus everest ece gsm module?

Thanks.

I GOT IT TO WORK, FINALLY but not 100% fully!!!





see details here:
http://www.xoutpost.com/electronics/bluetooth/81491-retrofit-bluetoth-using-tcu-ece-european-us-x5-e53.html

I have a 4/04 build TCU in my car. (its the one month part). I have a PK and my phone has seen the BT before, but I cannot pair. Cant seem to get any of the steeringwheel buttons to work for this either. Will navcoder 'release' the BT here or work for this at all or am I really SOL and need to buy a newer TCU? I have the BT antenna, and I have SOS.

What is the part number of your TCU? Check it against this list... if it is not one of the modules confirmed with BT, then you do not have it.

http://www.bimmerboard.com/members/p...artNumbers.pdf

If that is the original TCU, it should not have Bluetooth according to SIB 841304:

"E46, E83, E85 and E53 vehicles produced
between 3/2004 and 8/2004 are equipped with a
TCU that does not support Bluetooth. On these
vehicles, the TCU can be replaced at the
customer's expense with a 2005 MY TCU.
Cradles may not be added to these vehicles
because of wiring incompatibility.

Please disregard the Owner's Manual insert,
shown to the left, indicating Bluetooth
functionality. The hardware in these vehicles
will not work correctly."

The SIB indicates the seat belt needs to be fastened on E53 X5 in order to initiate the pairing procedure. I didn't find this necessary on the TCU that I retrofitted.

Remove the TCU and see if you . have a pass code on it. If it does try to pair it with the phone

I have this Visteon ULF Module end of life Mar-04 84216934961 3rd generation that says it has Bluetooth only; no Assist; direct replacement for TCU; requires pairing button; ULF modules have voice control of phone and nav.
I also saw a passkey on the module .
http://farm9.staticflickr.com/8065/8...17ba71df7d.jpg
IMG-20121117-00681 by JoyCaluma, on Flickr

Should this function properly?
the car was produced 04/04.

I tried to initiate the pairing but to no avail :dunno:

cheers!

Yes, you have a ULF, not a TCU. I had one of those a while ago too. You must have the eject box cradle with the pairing button to initiate pairing.

How did you try to initiate pairing? For a ULF, you must push and hold the button with the car off. Then continue to hold while your turn the car on and continue holding for another 10 seconds or so. Make sure to fasten your seat belt, because the seat belt warning can interrupt the pairing on some cars.

exactly what I did. 60secs max :D but still no response

The fuse (F74) of the ULF is good.

do i have to turn the engine ON or just the acc ?

It will pair with the key in either ACC or on position.

Just to confirm... you are definitely using the pairing button on the center console eject box and not the button on the steering wheel, correct?

Also, are you getting the "TELEPHONE" option on the main navigation menu?

Yep. Affirmative.

And yes I have that option on my nav.
If I select it, it says ACTIVATE PHONE.

Could the ULF be damaged?

Can I just easily swap it with another ULF?

Yes, swapping to a new ULF is very easy.

I would try a test with NavCoder before you wrote it off. You can make it enter pairing mode with NavCoder. The problem could be the button or wiring.

Yes, swapping to a new ULF is very easy.

I would try a test with NavCoder before you wrote it off. You can make it enter pairing mode with NavCoder. The problem could be the button or wiring.

Thanks for the advice

Now NavCoder would be another issue for me.

for anyone checking, I just swapped in an 06 vintage TCU into my 04 which had a TCU/Assist but no BT. No coding, no issues, straight plug and play. The only thing I dont know is which mic I have in the headliner, so I still need to look and see.

Hi Brian
Whila I am still waiting for my navcoder cable, I checked the eject box switch and it is working up to a small pcb in the eject box.
If I press the button, does it just simply pull a pin of the ULF to the GND?

Yes, all the pairing button on the eject box does is pull ULF pin 32 (I think) to ground. Verify the correct pin on the 54-pin ULF plug, but that is all it does.

Cool Thanks!

hello guys,

i would like to have bluetooth at my 06/2002 Euro E46 and was searching for information.

what i found out is: i should have the second generation phone wiring as my car is produced later than 03/2002 and i have BIT2 phone.

so it should be plug&play to buy a ULF and use it instead of the BIT2 hardware.

but, i came across that i already have a bluetooth antenna under the ash tray as my car also has bmw assist.

doesn´t this mean that my car already has a TCU? :confused:

galaxy s2 couldn´t find it, should it?

am i right, that i could buy a GSM TCU with bluetooth support (which p/n is the first with bluetooth?) and just change the tcu? do i have to unmount the BIT2 completely?

just to be more precise, i will add the options list from my car:

any advice is highly appreciated :thumbup:

Just chuck in a late model TCU and you are good to go. I think they stopped making them in 2007 and the e83 and e85 shipped the last. Actually they were early hardware with new software (remanufactured)

I'm not very familiar with the BIT2 system, but doesn't it use bluetooth to talk to your cordless headset?
If that's the case, hopefully your bluetooth antenna cable (FAKRA style) will plug into the bluetooth connection on the new TCU. If not, you may need to remove the plastic casing around the FAKRA connector in order for it to plug into the TCU.

Well, it turns out to be a little bit more complicated then i thought...

plugged the tcu instead of the bit2 and blowed fuse #7 :stickpoke

i unplugged the SES and the BIT2 phone and tried a new fuse: didn´t blow #7, but unfortunally the tcu won´t be shown in inpa and dissapeared in the widescreen.

i don´t know if the tcu is blown or the wiring is still faulty :stickpoke

Fuse no. 7 actualy for the MKiv system. I mean without it u wil turn off every thing related to the mkiv. I had it burned a couple of times while i was installing my tcu. Just make sure to disconnect the eject box totaly. And 4 the piaring button i didnt install also.

Check out my post http://www.xoutpost.com/electronics/...-new-post.html

Even with the new wiring the tcu won´t be recognized by the car and even not by navcoder :rant:

If you re-pin the ULF/TCU plug, then it will work. Many people have made BITII to TCU/ULF conversion adapter harnesses.

I did re-wire the BIT2 connector to TCU, but its still not recognized.

Try this: BIT-II to TCU/ULF Adapter Harness

I made the re-wiring according to the following graphs:

http://www.abload.de/img/wds_stock9bu7f.jpg


http://www.abload.de/img/wds_tcul9up3.jpg

The first one is BIT2 and the second is TCU. I double-checked the wiring and even measured if ground and 12v are active at the 54pin connector, but the TCU doesn´t start up.

I´ve been told, that TCUs in euro e46 were used from 2005 on and earlier cars couldn´t be retrofitted. instead i should buy a ULF and would be ready

Did you also make an adapter for the eject box plug? Try to copy the pin routing in that reference post. It worked for that person. It is possible that you have a bad TCU, but I would bet first on the wiring adapter.

The pinout in the mentioned thread is for an ULF, not for a TCU. I checked the wiring for ULF, its slightly different to TCU but only minor changes.

I did not change the eject box wiring, as I changed the eject-box wiring at the TCU. Even though i don´t think an eject-box is necessary to start the TCU. I think, and i could be false here, that the TCU should be recognized by the vehicle just with 12V, ground and Ibus?!

Can anyone confirm this point?

TCU and ULF are the same at the 54-pin plug. The differences are not material. The essential pins are I-Bus, power, and ground. I-Bus in some cars routes through the center console eject box plug, so that is why that adapter is important.

Did you validate with a multi-meter that you are getting the three critical sources at the 54-pin plug?

So this is

http://www.abload.de/img/versorgung_tcuk0xgy.jpg

exactly the same as this one?

http://www.abload.de/img/versorgung_ulfo4xll.jpg

they ARE different, even the differencies are minor.

I did not try to multi-meter the ibus, i guess bus system is not intended to be measured this way, but yes, i measured both ground contacts and both 12v supply on their own and against each other. they are ok.

ibus must be ok, as the adapter routes the bus signal to the SES system and SES is still working.

Mulitmeter the I-Bus. You will get a positive voltage in the 5V - 7V range if it is connected.

OT:
Where do you still get those wiring diagrams? Wds spaghetticoder removed BMW.. Also the wds here in xoutpost is not functioning properly.