Mit Navcoder, via one of the drop-down menus.

I am looking at Navcoder and can't see where this is... My best guess is Scan/Single Module which gives me


NavCoder v2.8.350 - Scan Results
File written 5/6/2011 6:16:33 PM

Single Module scan conducted on 5/6/2011 6:16:26 PM

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

TCU Telematics Control Unit
Part number 9 129 850, version HW 50, SW 34, made by Continental on 18/06 (May 2006)
Diagnostic index 21, Bus index 12, Coding index 05
Stored Fault Codes: 1 [--]

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

Module Qty Fault Codes
TCU 1 --
--------------------------------------------------

Code:Save Coding Data

Cheers, got the beta now so that makes sense. Also got a list of things Jochen wants so will run through that too and post it all up here.

Coding data

! NavCoder v2.9.78.Beta - Coding Data File
! File written 5/8/2011 8:31:31 AM
CodingDataFileFormatVersion : 1.0
VehicleVIN :
!
! Device: TCU - Telematics Control Unit
!
! Coding Data Follows:
TCU Adr:CA PN:9129850 HW:50 SW:34 CI:05 DI:21 BI:12 MadeOn:18/06 MadeBy:Continental
ID : 89 12 98 50 50 05 21 12 18 06 23 34
00 : 00 08 21 05 BF 07 8F 0A A5 01 01 06 28 0A 00 00 00 60 3C 00 4C 4E 38 33 30 31 37 04 01 02
01 : 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
02 : 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
03 : 03 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
04 : 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
05 : 05 31 31 32 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

See below, in changing the VIN so it could be seen by INPA it has lost its Bluetooth name and now has a blank, if I try to select Standard name (it works fine) but cannot code it, returns a timeout error.

I turned Transport mode on and off yesterday when I was taking the screenshots. I will try the power off reset and see if that does anything. If it doesn't will try and get the log files of both states. There being no Bluetooth name in the TCU seems like a bigger problem, and suggests that its coded differently than first thought.

You probably need to reset it by pulling the power and waiting a minute or two after each change you are making for the VIN, transport mode etc. I doubt this stuff is supposed to be changed on the fly and for the unit to keep ticking and update all it's working parameters.

I assumed I would need to shut down, wait a minute and restart. But have read elsewhere that these changes can take even longer then that to turn up. Wife about to head off on 3 hr drive so given her the X5 to see if the Bluetooth name has returned when she gets back. I have unplugged the TCU for the last couple of hours also, so will see if that helps too. Full car re-power will have to wait till her return

I'm curious about why you need to change the VIN for INPA? Is there some feature that becomes enabled when the VINs match? I thought the VIN was only for reporting back to BMW in an E-Call.