BMW ICOM software ISTA 4.19.2x ISTA/P 3.66.2 new features:
I levels newly added or updated in this ISTA version are marked in BOLD.
F, G, I series (ISTA 4)
Series group — I level
F001 (F0x, RR4, RR5, RR6) — F001-19-07-520
F010 (F06, F1x) — F010-19-03-530
F020 (F2x, F3x, F80, F82, F83, F87) — F020-19-07-539
F025 (F15, F16, F25, F26, F85, F86) — F025-19-03-550
F056 (F39, F4x, F5x, F6x) — F056-19-07-554
S15A (G01, G02, G1x, G3x, RR1x, RR31, F90, F97, F98) — S15A-19-07-553
S15C (G08, G38) — S15C-19-07-553
S18A (G05, G07, G14, G15, G20, G28, G29) — S18A-19-07-553
I001 (I01, I12, I15) — I001-19-07-539
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-18-03-510
Note: 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
- is contained in the current ISTA release,
- was already contained in a previous ISTA release or
- will be provided in a future ISTA release.
Series group e.g. F020 – year 2017 – 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
Currently no innovations.
New models can be dealt with
Benefit: The new vehicles F40, G06, G16, G21, F91, F92 can be dealt with.
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 HUB2 (formerly Entry Evo) and also in the HU-H3 MGU since 7/2018.
The process is identical for both control units and is documented in the ISTA user guide.
The user guide can be opened in ISTA using the “?” button.
New protection against tampering – control unit encoding
In G05, G15 and subsequent vehicles, 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.
Note: The automatic control unit validation works as of ISTA 4.16.1x. As a prerequisite, the necessary settings must be made in the ISPI Admin Client. These are described in the following.
This process can take place automatically with ISTA 4.16.1x once the affected workshop systems (ISPI Admin Client) are correctly configured and there is an online connection to the BMW backend.
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 manual process is described below:
1.Select the exchanged control unit in the “After Replacement” tab and then calculate the measures plan.
Then ISTA will automatically include the control unit validation in the measures plan.
2.If ISTA cannot carry out automatic validation, a warning about the absence of control unit validation is displayed.
3.By clicking on the “Next” button, ISTA generates the required ValidationRequest_VIN_xxx.json.zip file and opens a file dialogue to save it. The file must be sent to technical support later via PuMA
4.ISTA displays a note confirming that the file was successfully saved. At this point, you can exit the process using the “Cancel” button. After processing the measures plan, the session can be closed.
Note: The vehicle must not be handed over to the customer without successful control unit validation. Various vehicle functions are not available without control unit validation, corresponding fault memories are set.
5.Please send the saved json.zip file to technical support attached to a PuMA message.
6.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.
Start a new ISTA session
7.In order to import the json file, select “ECU Validation” in the “Additional Software” tab.
8.In order to import the validated file, select “Import control unit validation file manually” and confirm with OK
9.Select the ValidationRequest_VIN_xxx_response.json file in the file dialogue and confirm with “Continue”
Note: Unzip the ZIP file and import the json file into ISTA.
10.The file is written into the vehicle and checked.
11.After confirming the note, ISTA displays the tab for control unit exchange. Select the exchanged control unit and calculate and work through the measures plan.
UOBDII Official Blog All rights reserved How to use ISTA/D 4.19 ISTA/P 3.66 for manual ECU validation