G. Version Coding and Final Test

G. Version Coding and Final Test

1. Connect StarDiagnosis (DAS) to the vehicle and perform the version coding outlined below:

^ Skip to step 2, if the telephone is NOT installed.

2. Using path: Control units/Information and communication/ICM/Control unit adaptations/Standard version coding/Optional equipment, set CTEL = Present

3. Version code the electronic ignition switch (EIS) to indicate the presence df the VCS module.

D2B Configuration Table:

4. Using path: Control units/Information and communication/D2B/Control unit adaptations/Read coding and change if necessary/Specified configuration of D2B components, set the D2B ring configuration per the table.

5. Return to the Cockpit management and data system menu. Using path: Actual values/Actual configuration of D2B components, verify that the version coding input above (specified value) matches the actual configuration performed during installation (actual values). If a difference exists, the ring has been improperly configured and installation must be disassembled in reverse, diagnosed and the error corrected.

NOTICE! DO NOT alter the configuration in step G4 to match the vehicle configuration. Failure to have the configuration set as specified in the above table will result in erroneous system operation and/or intermittent failure of some or all components.

6. Check the DTC memory of all installed components and the head unit. Any present DTC(s) should be investigated and the source identified. The source of the DTC(s) should be corrected and DTC memory cleared.

Note: Powering up the newly installed system prior to the above described version coding, will set D2B ring configuration errors. These errors may be ignored during the initial DTC check. If, after clearing the DTC(s), they return in the next step, a configuration error is present and must be located and corrected.

7. Confirm that no new DTC(s) have been set in the D2B system group.