halis duraki/
- 0xduraki
A coding plug is a mechanically keyed or electronically coded device/plug, that can open or bridge circuits in a particular component, therefore allowing it to operate differently dependent on the type of plug installed.
BMW used a mechanical coding plug which simply opened or bridged circuits to assign market specific data to the instrument cluster of the E23, E24, E28 and E30 vehicles. With the introduction of the E32 in 1988 and the E34 in 1989, electronic coding plugs were utilized in the instrument cluster.
The change to an electronic coding plug which allowed market specific data to be assigned to the instrument cluster also contained Non-Volatile Random Access Memory (NV-RAM), which provided an ability to retain vehicle specific data in the plug such as:
By using a plug that is able to store data, the instrument cluster can be replaced without loosing vehicle mileage, unless the coding plug is damaged.
With the introduction of vehicles like the E31 and E38 the instrument cluster no longer utilizes a coding plug since it receives most of its input signals directly from a control module, EKM (E31) or IKE (E38), this allows vehicle data to be directly stored in the con- trol module and the instrument cluster is no longer coded. For these vehicles and newer models, market specific data is stored in the control module (EKM or IKE). By coding these modules by way of ZCS coding (refer to ZCS coding) market specific data is assigned/released to the control module.
Coding Plug: Intergrated Circuit (IC) Details
The user @kfister posted in 2007 on bimmerboard.com forum with all the messages he manage to dump from the BMW E34 Coding Plug ROM // EEPROM. He also noted that the Code Plug has copies of frame number, ZCS key for storage, mileage, and bitmapped options (shown below).
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.
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.
The E32/E34 Instrument cluster coding plugs progressed through three variations of design.
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.
The E32/E34 instrument cluster and coding plug were redesigned in Feb. ‘89. As a result of this redesign the coding plug became an external component and plugged directly into the back of the instrument cluster, no longer part of the X16 connector.
In 9/90 the cluster was slightly redesigned again to address changes in the fuel gauge and some minor physical changes. The electronics of the cluster as well as the coding plug were upgraded considerably.
The coding plug and the instrument cluster are not compatible with the earlier redesign. The printed circuit board and the coding plug are colored blue for distinction over the components of the earlier redesigned cluster.
The new blue coding plug is also keyed differently to prevent unintentional exchange with the earlier coding plug.
After 9/91 production, the instrument cluster coding plug can be coded using the ZCS function within CIP by selecting the specific module via the DISplus/GT1/SSS . The physical characteristics of the coding plug did not change.
A replacement uncoded coding plug must be coded after installa- tion into the instrument cluster, refer to ZCS coding section in this manual.
References