Procedure for Flash Programming a Control Unit.

Fig 1: Identifying Flash Programming Flow Chart (1 Of 3)

Courtesy of BMW OF NORTH AMERICA, INC.

Fig 2: Identifying Flash Programming Flow Chart (2 Of 3)

Courtesy of BMW OF NORTH AMERICA, INC.

Fig 3: Identifying Flash Programming Flow Chart (3 Of 3)

Courtesy of BMW OF NORTH AMERICA, INC.

Additional Steps to be Taken into Consideration: 

Follow the additional information listed below when flash programming an engine or transmission control module.

• Sufficient battery voltage is critical  when flash programming a control module. If the battery voltage drops below a certain level during programming, the session will terminate prior to completion. If the vehicle has been in the workshop for diagnosis with the ignition key on for long periods of time, the battery voltage is most likely deficient.

  Verify the battery voltage prior to programming, if necessary connect a battery charger to the vehicle prior to starting flash programming. Do not connect the charger during the actual procedure. This could cause a voltage spike to occur which will also abort the programming procedure.

  Connect the charger before you start programming! 

• Flash Programmable control modules can be programmed up to 13 times. The remaining programming sessions is displayed during the programming procedure.
• The program will automatically realign the EWS & DME. This function can also be found either in the Engine control module programming software or ZCS coding of the EWS.
• Depending on the level of programming data, the procedure can take between 2 and 15 minutes.
• After programming, clear the control module's adaptation values.  The programming software will automatically provide instructions. Clearing the adaptation values can also be found in the Service Functions menu of the diagnostic software in the DIS. The control module will quickly re-adapt to the system storing new values during a test drive.
• After programming, clear all vehicle control modules that interface with the newly programmed control module.  The programming procedure can cause other interfacing control modules (AGS, ASC, etc) to store erroneous faults. When programming is completed, perform a quick test with the DIS to determine if any faults have been stored. Clear all vehicle control module fault memories to prevent any unnecessary future diagnosis.