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.

__________________
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

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.