FixVault

Release Notes CIP 18.0 (09 04 05)

Publication date: 2005-07-01
Reference number: 09 04 05

RELEASE NOTES CIP 18.0

RELEASE NOTES CIP 18.0

TECHNICAL SERVICE BULLETIN

Reference Number(s): SI B 09 04 05, Date of Issue:  July 2005
BMW: All Models
GROUP: 09 - Programming/Coding Explanations

SUBJECT

Release Notes CIP 18.0 

SITUATION

CIP 18.0 has been released. Certain errors may occur during installation or usage.

CAUSE

Software error

COMPLAINT

The following problems with Progman/CIP 18.0 are currently known:

  1. E65: ASK programming aborts with Error 2084 - Flash download error. This also causes coding to fail.
  2. E60/E63/E64: With older integration levels, the "Control unit data incorrect" message is displayed in the status report for individual control units.
  3. E65: The CAR settings cannot be coded when attempting to reset the CKM values to the default values.
  4. E83 / E85: A "Code" button appears for DME variants that are not codeable. The attempt to code the control unit fails with the message "No further measures".
  5. The incorrect CIP version may be displayed on the "Online update" screen following a JET Stream update.
  6. E60/E63/E64, E90: Reading and writing of individual data (navigation destinations, phonebooks, etc.) does not work when programming the CCC and MASK.
  7. E90: The programming of RAD2 Professional is shown in the final report with error 2020 (control unit not responding). Coding has error 1000 (general error).

PROCEDURE

  1. The second flash attempt must be carried out by Special Measure.
  2. The error can be ignored because a Measures Plan containing all control units to be programmed is generated at a later stage and the vehicle is programmed correctly.
  3. The CKM values can be set correctly before coding by selecting individual CKM settings.
  4. Ignore the button or message in the case of DME variants that cannot be coded.
  5. Ignore the incorrect CIP version displayed.
  6. The vehicle data (navigation destinations, phonebooks, etc.) must be backed up manually.
  7. Start a new session after a battery reset and repeat programming/coding.