| 
 | ||||||||
| Xoutpost server transfer and maintenance is occurring.... | 
| Xoutpost is currently undergoing a planned server migration.... stay tuned for new developments.... sincerely, the management | 
|  | 
|  | LinkBack | Thread Tools | Display Modes | 
| 
			 
			#111  
			
			
			
			
			
		 | |||
| 
 | |||
| 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? | 
| Sponsored Links | |
| 
 | |
| 
			 
			#112  
			
			
			
			
			
		 | ||||
| 
 | ||||
| 
			
			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. 
				__________________ SOLD 2000 E38 750iL Highline Edition, Upgraded with the lastest 2006 X5 Electronics MKIV Navigation, 16:9 Display, Bluetooth, TV/Video with Backup Camera, Sirius, and Aux Input | 
| 
			 
			#113  
			
			
			
			
			
		 | |||
| 
 | |||
| 
			
			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 | 
| 
			 
			#114  
			
			
			
			
			
		 | |||
| 
 | |||
| Quote: 
 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  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) Last edited by neiloakley; 02-11-2010 at 09:54 AM. | 
| 
			 
			#115  
			
			
			
			
			
		 | |||
| 
 | |||
| Quote: 
 Just click the connector number for a full table. Quote: 
 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. | 
| 
			 
			#116  
			
			
			
			
			
		 | |||
| 
 | |||
| 
			
			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. Quote: 
 (see diagrams below) Quote: 
 Quote: 
 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? | 
| 
			 
			#117  
			
			
			
			
			
		 | |||
| 
 | |||
| Quote: 
 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 | 
| 
			 
			#118  
			
			
			
			
			
		 | |||
| 
 | |||
| 
			
			OK i'll leave the eject box off   But it still doesn't pair  Going to start from scratch and see if i made any mistakes. | 
| 
			 
			#119  
			
			
			
			
			
		 | |||
| 
 | |||
| 
			
			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... | 
| 
			 
			#120  
			
			
			
			
			
		 | |||
| 
 | |||
| 
			
			Bluetooth antenna is connected (brand new one)   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 | 
|  | 
| Bookmarks | 
| 
 |  | 
|  |