General Programming Rules
WARNING: This page is about a different car, the 2003 BMW 760Li, 2003 BMW 745i, and 2003 BMW 745Li. However, it is still accessible from the selected car via links, so may be relevant.
The procedure for programming control modules on E65/E66 vehicles is controlled by the Coding, Individualization and Programming (CIP) program. The following preconditions must be followed when using the CIP program: first connect the vehicle to an approved BMW battery charger (Deutronic Automotive Power Processor) and never disconnect during programming. This charger must be connected in POWER SUPPLY MODE. The date and time must be set correctly in the DISplus/GT-1 administration button on initial startup screen to check and modify.
Diagnostic head must be hard wired to the network drop to ensure uninterrupted programming (do not use radio connections). If using DISplus, see Fig 1. If using GT-1, see Fig 2.
- Park vehicle where it does not obstruct another vehicle, as programming may take up to 4 hours.
- All control modules must be installed and functional.
- Perform a fault memory deletion with QUICK CLEARING.
- Readout and print individualization settings with the CIP program, as vehicle and key memory will be deleted during programming.
- Read out, and print if applicable, instrument cluster/control display (mileage, condition based service data, radio station settings, etc.).
- Engine must be off and cooled down.
- Transmission oil temperature must be greater than 185°F (85°C).
- Put transmission in P or N position, vehicle must not move.
- Coding/Programming all control modules (with the ignition on), except the CAS.
- Coding/Programming the CAS module with the ignition off and key removed.
- Switch off all electrical accessories.
- Do not move seats, trunk lid, steering wheel, locks, windows, etc.
- Note that wipers can move unexpectedly (make sure path is clear and moisten glass).
- Navigation CD V19.0 must be available when programming with CIP.
- Print as you go for all CIP procedures (measures plan, program abort, multiple attempts).
- Initializing control modules (indicated on screen).
- Re-establishing customer VKM settings overwritten during coding/program (reverts to factory settings).