Driver Profile Not Set Properly (66 12 16)

Publication date: 2016-06-01
Reference number: 66 12 16

DRIVER PROFILE NOT SET PROPERLY

TECHNICAL SERVICE BULLETIN

Reference Number(s): SI B66 12 16, Date of Issue: June 2016

BMW:	G12 (7 Series); Vehicles produced to July 01, 2016
GROUP:	Distance Systems, Cruise Control, Remote Control

SITUATION

Driver settings revert to an alternate driver profile upon entry into vehicle.

CAUSE

Body Domain Controller (BDC) software error

CORRECTION

Program and code vehicle using ISTA/P 3.59.0 or higher

PROCEDURE

NOTE: Parts replacement will not correct this situation.

Run diagnostics with ISTA.

Program and encode the complete vehicle:

ISTA/P version	I-Level	Availability
3.59.0 or higher	S15A-16-07-501	end of June 2016

Until ISTA/P software is available submit a PuMA case for IRAP.

NOTE: that ISTA/P will automatically reprogram and code all programmable control modules that do not have the latest software. For information on programming and coding with ISTA/P, refer to: CenterNet / TIS / Technical Documentation / Programming and Diagnostics / Programming Documentation.

Always connect a BMW approved battery charger / power supply (SI B 04 23 10 ).

WARRANTY INFORMATION

Covered under the terms of the BMW New Vehicle Limited Warranty for Passenger Cars and Light Trucks or the BMW Certified Pre-Owned Program.

Defect Code:

61 38 27 02 00

Labor Operation:	Labor Allowance:	Description:
00 00 006	Refer to KSD2	Performing "vehicle test" (with vehicle diagnosis system - checking faults)
And:
61 21 528	Refer to KSD2	Connect an approved battery charger/power supply (indicated in KSD2 as "Charging battery")
And, as necessary:
61 00 006	Work time (WT)	Performing vehicle diagnosis - test module
And:
61 00 730	Refer to KSD2	Programming / encoding control unit(s)

If you are using a Main labor code for another repair, use the Plus code labor operation 00 00 556 instead.

Refer to KSD2 for the corresponding flat rate unit (FRU) allowances.

Work time labor operation code 61 00 006 is not considered a Main labor operation; however, it does require an individual punch time and an explanation on the repair order and in the claim comments.

Vehicle Programming and Coding

Control module failures that occur during programming:

Please claim these consequential repairs under the defect code listed in this bulletin and use the applicable KSD2 labor operations.

Other Repairs

Control module failures that occur prior to programming and/or additional work is performed as a result of performing the ISTA diagnostics and related test plans:

When covered under an applicable limited warranty, claim these repairs using the applicable defect code and labor operations in KSD2.