Telematics Control Unit (TCU) - Swapping For Testing
SI B 84 11 06Communication Systems
March 2010
Technical Service
This Service Information bulletin supersedes SI B84 11 06 dated June 2006.
[NEW] designates changes to this revision
SUBJECT
Swapping TCUs for Testing
[NEW] MODEL
SITUATION
Installing a Telematics Control Unit (TCU) from a known good vehicle into a problem vehicle is acceptable for testing purposes only.
[NEW] Precautions:
^ The vehicles must have same production range, e.g., do not install a pre-3/08 TCU into a post-3/08 production vehicle.
^ The vehicle must have the same TCU type, e.g., Code Division Multiple Access (CDMA), Global System for Mobile (GSM), I/K-Bus, etc.
^ The vehicles must be similarly equipped, e.g., if the problem vehicle is equipped with a navigation system, the known good vehicle must be equipped with a navigation system.
^ Do NOT code the TCU to the vehicle.
The TCU from the known good vehicle must be reinstalled in the original vehicle after testing has been completed.
[NEW] The appropriate relationship between the Electronic Serial Number (ESN) or the International Mobile Equipment Identity (IMEI) in the TCU and the Vehicle Identification Number (VIN) must always be maintained, since BMW of North America, LLC deactivates the cellular services for the Network Access Device (NAD) within the TCU when the BMW Assist subscriber agreement expires.
[NEW] If a TCU is swapped from one vehicle to another vehicle and BMW of North America, LLC is unaware of the change, the incorrect NAD may be inadvertently deactivated at the end of the BMW Assist term. To prevent data corruption, a short test using BMW diagnostic tools must be performed on both vehicles once the TCUs are reinstalled or replaced, if the TCU was determined to be defective.
WARRANTY
[NEW] Refer to SI B01 10 06 (Part Swapping for Diagnostic or Programming Purposes Only).