Contents Section: Testing & Diagnostics All sections

Coding and Programming - Overview: Overview BMW Z4 E85/E86 рестайлинг

Testing & Diagnostics 6 illustrations ~568 words

Introduction to Coding & Programming

Model: All

Production: All

Coding Plug Identification

Each coding plug features a stored 5-digit numerical code that varies between model/equipment, etc.

The code can be read out through the instrument cluster display by pressing the odometer reset button and turning the ignition switch to KL R. The coding plug number will be display in the instrument cluster matrix.

Scheme 1

Scheme 1: Coding Plug Identification

If this is no longer possible, the coding plug must be removed in order to read the code on the label of the coding plug.

Coding Plug Overview

Since the introduction of the E32 several versions of instrument cluster coding plugs have been introduced, this section will provide an overview of the different versions, plus provide identification and coding information.

Coding Plug Identification - E32/E34

The E32/E34 Instrument cluster coding plugs progressed through three variations of design.

Start of production up to 2/89.

The original E32/E34 instrument cluster coding plug was installed in the wiring harness connector (X16) which plugged into the instrument cluster. This plug contained all of the vehicle specific coding data for the instrument cluster and retained accumulated mileage and service interval information.

In the event that the instrument cluster must be replaced the coding plug is reused with the new cluster. By reusing the old/original plug the mileage in the odometer does not change, since the coding plug is able to retain the information.

Scheme 2

Scheme 2: Coding Plug Identification - E32/E34
  1. If the coding plug must be replaced, the total mileage and Service Interval information will be lost.
  2. Replacement coding plugs pre-coded by part number and are available from the parts department.

Variant Code Identification Display

The variant code for a DME M1.X control module can be accessed in three ways

  1. Electronically via DISplus or GT1: DME Control Module Identification screen Select "Programming" then "DME variant code", installed variant code is displayed.
  2. DME control module variant code label
  3. SI B13 02 90 (3009)

The quickest and most accurate way to access the variant code of the installed DME is by viewing the DME Identification page using the DISplus or GT1.

Scheme 3

Scheme 3

If a control module malfunction is suspected cross reference the BMW and Bosch part numbers in the display with the installed variant code. Problems can occur if

  1. The correct variant code is installed in the wrong control module.
  2. An incorrect variant code is installed in the correct control module

Code Number Identification

Along with the VIN, the Code number for the installed control module(s) is printed on a label, located on the underside of the fuse box cover.

Additional labels are available from the parts department under P/N 01 99 9 784 735

Scheme 4

Scheme 4: Code Number Identification

ZCS Identification/Display

The ZCS information for a specific vehicle can be obtained by

  1. Accessing the control module(s) that electronically stores the information, using the DISplus/GT1 or SSS
  2. Locating the ZCS label affixed in the vehicle

Progman Introduction

With the release of CIP 15.0, BMW released a new software program known as Progman.

Scheme 5

Scheme 5: Progman Introduction

Progman is a software package that operates with Windows XP Embedded to manage

Scheme 6

Scheme 6
  1. Administration & assignment of OPPS/OPS/Diagnostic heads plus network configuration/addressing.
  2. Installation/loading of new data updates via Jetstream.
  3. Activation of a Coding, Individualization or Programming request from a GT1 to an SSS via a multiconsole/multisession feature.
  4. Coding, Individualization or Programming of older vehicles via the SGC/UNIX application.
  5. Coding, Individualization & Programming functions of CIP.