Release Notes Programming

Passenger Cars

ISTA 4.27.2x
ISTA Service Data 4.27.20
ISTA/P 3.68.0
BMW Group Page 2
Release Notes Programming Passenger Cars, ISTA 4.27.2x of 26

Table of contents
Table of contents ............................................................................................................................................... 2
1 General notes ............................................................................................................................................. 3
2 Overview of the I levels contained.............................................................................................................. 4
3 Innovations ................................................................................................................................................. 7
3.1 Innovations – Locking Configuration Switch ....................................................................................... 7
3.2 New features - automatic deblocking of the component protection .................................................. 11
4 Known faults F, G, I Series ....................................................................................................................... 13
4.1 F4x, F6x PHEV cannot be started after programming ...................................................................... 13
4.2 Top View (360) is encoded several times by ISTA ........................................................................... 14
4.3 Camera-based driver assistance system cannot be programmed ................................................... 15
4.4 KAFAS does not respond any more after programming ................................................................... 16
4.5 Head Unit HU-H3 (MGU) control unit - No navigation after programming to 20-07-5xx ................... 17
4.6 Notes on individual campaigns ......................................................................................................... 18
4.7 RAM - activation code campaign when programming to 20-03 or more recent ............................... 19
4.8 G05, G06, G07 - activation code campaign when programming to 19-11 or more recent ............... 20
4.9 High-beam Assistant - activation code campaign when programming to 19-07 or later .................. 21
4.10 HU-HU3 (MGU)/RSE control unit cannot be encoded .................................................................. 22
4.11 F0x - programming not possible, control units are requested for installation ................................ 23
4.12 ISTA 4 - Information on BDC exchange or programming cancellation gateway control units ...... 24
4.13 Invalid IP address for BN2020Ethernet control units ..................................................................... 25
5 Known faults E Series (ISTA/P) ............................................................................................................... 26
5.1 Vehicle order import fails due to antivirus software and firewall ....................................................... 26
BMW Group Page 3
Release Notes Programming Passenger Cars, ISTA 4.27.2x of 26

1 General notes
With the launch of ISTA 4, the functionality for programming has been integrated in ISTA.

The following series can be dealt with using ISTA/P:

• E Series

The following series can be dealt with using ISTA 4:

• F, G and I Series

These Release Notes contain information for both programming systems.

The Release Notes list all known faults and faults that are currently still unresolved, with possible
workarounds which are important for the Retailer Organisation. Please contact Technical Support if
additional faults occur on the vehicle. In particular in the following cases:

• vehicle-related programming faults / encoding faults and activation faults

• functional faults on the vehicle

With ISTA 4, it is now also possible to send feedback relating to programming directly to BMW AG. Selecting
the "Feedback" symbol (envelope symbol) displays the feedback screen with input boxes.

If a new fault pattern is included in a release, this is indicated in the heading with *NEW*. This is
no longer indicated in the follow-up release.
BMW Group Page 4
Release Notes Programming Passenger Cars, ISTA 4.27.2x of 26

2 Overview of the I levels contained

I levels newly added or updated in this ISTA version are BOLDhighlighted.

F, G, I series (ISTA 4)

Series group I level

F001 (F0x, RR4, RR5, RR6) F001-20-11-540

F010 (F06, F1x) F010-20-11-540

F020 (F2x, F3x, F80, F82, F83, F87) F020-20-11-540

F025 (F15, F16, F25, F26, F85, F86) F025-20-11-540

F056 (F39, F4x, F5x, F6x) F056-20-11-545

S15A (G01, G02, G1x, G3x, RR1x, RR31, F90, F97, F98) S15A-20-11-542

S15C (G08, G38) S15C-20-11-542

S18A (G05, G06, G07, G14, G15, G16, G20, G21, G22, S18A-20-11-545

G28, G29, F40, F44, F91, F92, F93, F95, F96)

I001 (I01, I12, I15) I001-20-11-540

RR21 (RR21, RR22) RR21-20-11-540

I levels correspond to the ISTA Service Data version on the front page.

E Series (ISTA/P)

Series group I level

E065 (E65, E66) E065-17-11-545

E060 (E60, E61, E63, E64) E060-16-11-500

E070 (E70, E71, E72) E070-16-11-500

E89x (E81, E82, E84, E87, E88, E89, E90, E91, E92, E93) E89x-18-07-520

R056 (R55, R56, R57, R58, R59, R60, R61) R056-17-03-504

RR01 (RR1, RR2, RR3) RR01-20-11-500

BMW Group Page 5
Release Notes Programming Passenger Cars, ISTA 4.27.2x of 26
BMW Group Page 6
Release Notes Programming Passenger Cars, ISTA 4.27.2x of 26

Info on the integration levels

PuMA measures or similar documents sometimes refer to an I level for the solution to a problem.
In this case it is important to know which ISTA release contains the I level.

The name of the I level indicates, if it

1. is contained in the current ISTA release,

2. was already contained in a previous ISTA release or

3. will be provided in a future ISTA release.

Series group e.g. F020 - Year2017 -Month (3, 7 or 11)-Version (>= 500)

Assuming the current release contains: S15A-17-03-506

Then the following I level is not available yet: S15A-17-07$-501)

Then this I level was already contained in an older ISTA release: S15A-16-11$-503)

Then this I level was already contained in an older ISTA release: S15A-17-03$-505)
BMW Group Page 7
Release Notes Programming Passenger Cars, ISTA 4.27.2x of 26

3 Innovations
The following interesting innovations are included, amongst others.

ISTA 4

New models can be dealt with

Benefit: The new vehicles G23, G80, G82 are treatable.

New protection against tampering - control unit encoding

In and subsequent vehicles G05, G15, the HU-H3 (formerly MGU), TCB, RSE and instrument cluster control
units are linked together. This should prevent tampering with vehicles.

If one or more of the components are exchanged, the connection must then be re-established.

In order to re-establish the connection, an electronic certificate must be created in a BMW backend and
imported into the vehicle.

The control unit validation can only be performed after the component protection has been
deblocked.

This process can run with ISTA 4.16.1x automatically, once the affected workshop systems (ISPI Admin
Client) are correctly configured and there is an online connection to the BMW back end.

The required settings for the ISPI Admin Client are described in the ISPI Administrator Manual (Application:
ISPI Admin Client (administration area) / ISPI Admin Client: Functions / ISPI Admin Client: Certification
management).

If the prerequisites for the automatic process do not exist, technical support can help to manually validate the
control units.

The process is documented in the ISTA user guide.

The user guide can be opened in ISTA using the “?” button.

3.1 Innovations – Locking Configuration Switch

With the launch of the BMW iX3 (G08 Battery Electric Vehicle), control units are introduced that meet
increased security requirements with regard to manipulation (SME, EME, CCU).
BMW Group Page 8
Release Notes Programming Passenger Cars, ISTA 4.27.2x of 26

With the following vehicle models in 2021, the number of control units will increase further.

The Locking Configuration Switch (LCS) will become relevant when an affected control unit is replaced. As in
the past, the software functions of a new part control unit will be adjusted to the vehicle, national-market
version and existing optional equipment, etc. by means of the encoding. In future, some of the software
functions will be protected by the Locking Configuration Switch.

To adapt the new part control unit in case of Locking Configuration Switch, a kind of activation code, the so-
called Secure Token, is required. This token is requested by a BMW back end and written into the control
unit by ISTA.

Automatic process

This process is executed by ISTA automatically , once the affected workshop systems (ISPI Admin Client)
are correctly configured and there is an online connection to the BMW back end.

To do so, select the corresponding control unit in the "After Replacement" tab and then execute the
measures plan.
BMW Group Page 9
Release Notes Programming Passenger Cars, ISTA 4.27.2x of 26

To retrieve Secure Token, ISTA must be enabled for the application of vehicle certificates.

The required settings for the ISPI Admin Client are described in the ISPI Administrator Manual
(Application: ISPI Admin Client (administration area) / ISPI Admin Client: Functions / ISPI Admin
Client: Certification management).

Manual process

If the prerequisites for the automatic process do not exist, the secure token must be inserted with the
assistance of technical support.

The process is similar to the control unit validation.

If ISTA could not automatically import the LCS, a warning message will be displayed.

By clicking on the "OK" button, ISTA generates the required TokenRequest_VIN_xxx.json file and opens a
file dialogue to save it. The file must be sent to technical support later via PuMA or TSARA.
BMW Group Page 10
Release Notes Programming Passenger Cars, ISTA 4.27.2x of 26

The session can be terminated if necessary.

PuMA/TSARA

Please send the saved json file to Technical Support attached to a PuMA/TSARA message.

Technical Support will send you back a validated version of the file as file type json for the affected vehicle.
This is subsequently required by ISTA.

For transmission via PuMA, the json file must be archived in a ZIP file.

The validated file from Technical Support must be unpacked again before importing it into ISTA.

Establish connection to the vehicle. To import the json file, select "Import secure token" in the Immediate
actions tab.
BMW Group Page 11
Release Notes Programming Passenger Cars, ISTA 4.27.2x of 26

Select the TokenRequest_VIN_xxx_response.json file in the file dialogue and confirm.

If the TokenRequest_VIN_xxx_response.json file has been read successfully, ISTA automatically switches to
the control unit exchange / after exchange tab.

There, mark the affected control unit as exchanged. Calculate and execute the measures plan.

3.2 New features - automatic deblocking of the component protection

Automatic deblocking of the component protection when replacing the BDC

BMW Group Page 12
Release Notes Programming Passenger Cars, ISTA 4.27.2x of 26

The activation code required to unlock the component protection is generated when a replacement part BDC
is ordered. After installation of the new part BDC and its instruction "after exchange" in ISTA, the activation
code is downloaded and activated.

The support of the Technical Support is no longer required.

The automatic process only works for replacement parts BDC ordered via ATLAS (Advanced ParTs Logistics
in AfterSales).

This includes the following countries/markets as of 2020:

Austria Luxembourg

Belgium Malaysia (end of 2020)

Denmark Netherlands

Germany Norway

Finland Portugal

France Switzerland

Italy Spain

Japan Sweden

Canada USA

In all other countries, the activation code for deblocking must still be provided by Technical Support.

Process for deblocking component protection

The component protection is extended to the vehicles G11, G12 version as of 07/2015 and F15, F16, F85,
F86 with version as of 07/2016.

As well as the HU-H2 (formerly NBT Evo), the component protection is also active since 3/2018 for the HU-
H2 (formerly Entry Evo) and also in the HU-H3 MGU since 7/2018.

The manual process is identical for the control units and is documented in the ISTA user guide.

The user guide can be opened in ISTA using the “?” button.
BMW Group Page 13
Release Notes Programming Passenger Cars, ISTA 4.27.2x of 26

4 Known faults F, G, I Series

4.1 F4x, F6x PHEV cannot be started after programming

Fault description:

After programming, various fault memories are saved in the DME and EME.

Among others 0x03168A, 0x0316AA, 0x0316BA, 0x0316BD, 0x0316C6, 0x0316E5, 0x0317D1, 0x222834,
0x2228FE, 0x22331F, 0x223323.

Model series affected:

Vehicles F45, F49, F49, F60 Plug-in Hybrid Electric Vehicle.

Measure / Workaround:

Program the EME again with ISTA.

Fault corrected by:

Expected for 4.27.3x.

Affected application:

ISTA 4
BMW Group Page 14
Release Notes Programming Passenger Cars, ISTA 4.27.2x of 26

4.2 Top View (360) is encoded several times by ISTA

Fault description:

Due to a software problem, the views in the parking view can be mixed up after programming the TRSVC
control unit.

Model series affected:

Vehicles G01, G02, G08, G1x, G3x, RR1x, RR31, F90, F97, F98 before life cycle impulse with control unit
TRSVC.

Measure / Workaround:

ISTA schedules the control unit encoding several times.

Carry out the measures plans.

Then ISTA schedules a service function to check the parking view display in the CID.

Carry out service function to check that the display is correct.

Fault corrected by:

With programming to I level 20-11-540 or higher.

Affected application:

ISTA 4
BMW Group Page 15
Release Notes Programming Passenger Cars, ISTA 4.27.2x of 26

4.3 Camera-based driver assistance system cannot be programmed

Fault description:

The KAFAS control unit cannot be programmed with ISTA.

Final report crashes with status not executable.

Model series affected:

Vehicles G11, G12, G14, G15, G16, G29, G30, G31, G32 with build level 07/2020.

Measure / Workaround:

Contact technical support re IRAP.

Exchanging the KAFAS does not provide a solution.

Also see PuMA measure 65505525.

Fault corrected by:

With programming to I level 20-11-540 or higher.

Affected application:

ISTA 4
BMW Group Page 16
Release Notes Programming Passenger Cars, ISTA 4.27.2x of 26

4.4 KAFAS does not respond any more after programming

Fault description:

After programming, the KAFAS control unit no longer responds.

Model series affected:

Vehicles G05, G07, G14, G15, G20, G29 with I level 18-11-5xx.

Measure / Workaround:

1) Let vehicle go to sleep. KAFAS then responds again.

2) Start new ISTA session, calculate and carry out measures plan.

Fault corrected by:

Currently open

Affected application:

ISTA 4
BMW Group Page 17
Release Notes Programming Passenger Cars, ISTA 4.27.2x of 26

4.5 Head Unit HU-H3 (MGU) control unit - No navigation after programming to 20-07-5xx

Fault description:

After programming the HU-H3 MGU-01, the navigation does not function

Model series affected:

Vehicles G0x, G1x, G2x, F4x, F9x with control unit MGU-01 which are programmed from an I level 19-03-5xx
or older to an I level 20-07-5xx.

Measure / Workaround:

For ISTA 4.25.3x, the service function - Execute automatic enabling – is automatically included in the
measures plan.

The service function is scheduled to be repeated if necessary.

It can be ignored, if the enabling of the navigation map was successfully executed.

Fault corrected by:

With programming to I level 20-11-540 or higher.

Affected application:

ISTA 4
BMW Group Page 18
Release Notes Programming Passenger Cars, ISTA 4.27.2x of 26

4.6 Notes on individual campaigns

Fault description:

If necessary, after vehicle programming, actions to restore individual data are completed with the result
Warning, and ISTA reschedules them in the final work.

This behaviour can also occur if no control unit has been replaced.

The background is the update of the programming functions contained in ISTA for future derivatives.

Model series affected:

All series

Measure / Workaround:

The operations relating to the individual data can be ignored.

Fault corrected by:

Currently open

Affected application:

ISTA 4
BMW Group Page 19
Release Notes Programming Passenger Cars, ISTA 4.27.2x of 26

4.7 RAM - activation code campaign when programming to 20-03 or more recent

Fault description:

When programming to S18A-20-03-5xx or more recent, an activation code campaign for the RAM control unit
is scheduled.

Model series affected:

Vehicles G0x, G1x, G2x, F40, F44, F9x.

Measure / Workaround:

Import the activation code into the vehicle

Fault corrected by:

Affects vehicles with build level before March 2020.

Affected application:

ISTA 4
BMW Group Page 20
Release Notes Programming Passenger Cars, ISTA 4.27.2x of 26

4.8 G05, G06, G07 - activation code campaign when programming to 19-11 or more
recent

Fault description:

When programming to S18A-19-11-5xx or more recent, an activation code campaign for the VIP control unit
is scheduled.

Model series affected:

Vehicles G07 and G05, G06 with optional equipment 2VR, 2VW, 2VF.

Measure / Workaround:

Import the activation code into the vehicle

Fault corrected by:

Affects vehicles with version before November 2019.

Affected application:

ISTA 4
BMW Group Page 21
Release Notes Programming Passenger Cars, ISTA 4.27.2x of 26

4.9 High-beam Assistant - activation code campaign when programming to 19-07 or later

Fault description:

When programming to S18A-19-07-5xx or S15A-19-07-5xx or later, an activation code campaign for the
KAFAS control unit is scheduled.

The reason is that the function is activated retrospectively for the customer.

Model series affected:

Vehicles G05, G07, G14, G15, G20, G29 and G11, G12 from life cycle impulse with optional equipment 5AC.

Measure / Workaround:

Import the activation code into the vehicle

Fault corrected by:

Affects vehicles with version before July 2019.

Affected application:

ISTA 4
BMW Group Page 22
Release Notes Programming Passenger Cars, ISTA 4.27.2x of 26

4.10 HU-HU3 (MGU)/RSE control unit cannot be encoded

Fault description:

Encoding the HU-H3 MGU-01 or RSE fails repeatedly.

Model series affected:

Vehicles G0x, G1x, G2x, F4x, F9x with control unit MGU-01

Measure / Workaround:

Assign HU-H3 control unit manually for programming in ISTA.

Fault corrected by:

Currently open

Affected application:

ISTA 4
BMW Group Page 23
Release Notes Programming Passenger Cars, ISTA 4.27.2x of 26

4.11 F0x - programming not possible, control units are requested for installation

Fault description:

ISTA 4 instructs one or several of the specified control units for installation, although they are already fitted in
the vehicle.

Model series affected:

Vehicles F01, F02, F03, F04, F07 with production data until March 2011 and the following control units:

• TEL-ULF260, TEL-ULF2HI, TEL-E15GSM

• MMC-01, MMC-01-FIRMWARE

• AMP-HIFI01, AMP-TOP70

• SDARS-01

• LRR-01

Measure / Workaround:

The vehicle can be dealt with using ISTA/P.

AN IBAC activate code is required for this. This can be requested from technical support.

Fault corrected by:

Currently open

Affected application:

ISTA 4
BMW Group Page 24
Release Notes Programming Passenger Cars, ISTA 4.27.2x of 26

4.12 ISTA 4 - Information on BDC exchange or programming cancellation gateway

control units

The exchange of the BDC is again supported with ISTA 4.09.1x.

Fault description:

When carrying out the special measures plan in the event of a BDC exchange, or due to a programming
abort of the gateway control unit, the following pop-ups appear repeatedly:

• Requesting that the ignition be switched on

• {$SYS-0012 Identification Error$}

• Connection to control unit Unknown interrupted

Model series affected:

Vehicles with the control units FEM or BDC.

Measure / Workaround:

Confirm pop-ups until the special measures plan has been carried out.

Fault corrected by:

Currently still open.

Affected application:

ISTA 4
BMW Group Page 25
Release Notes Programming Passenger Cars, ISTA 4.27.2x of 26

4.13 Invalid IP address for BN2020Ethernet control units

Fault description:

During vehicle management, one of the following Ethernet-capable control units should be programmed: HU-
H, RSE, ATM, KOMBI, ACC, ICAM, KAFAS

At the start of the session, a note appears indicating that the IP address is invalid. The Ethernet
programming can fail if the following steps are not followed:

Model series affected:

All F, G, I Series

Measure / Workaround:

1. End ISTA session

2. Carry out a battery reset

3. Restart the session

4. If fault message still appears: Check the Ethernet wiring in the vehicle using the wiring diagram in ISTA

5. If fault message still appears: Contact Technical Support

Fault corrected by:

Currently still open

Affected application:

ISTA 4
BMW Group Page 26
Release Notes Programming Passenger Cars, ISTA 4.27.2x of 26

5 Known faults E Series (ISTA/P)

5.1 Vehicle order import fails due to antivirus software and firewall

IMPORTANT!

In individual cases, the vehicle order-import fails because of installed security software (antivirus
software or firewall). After the session starts, the vehicle identification with ISTA/P fails. (BMW-
internal locations are not affected by the fault)

Measure / Workaround:

For more details, see ISPI Dealer Self Support entry 51219.

Affected application:

ISTA/P