H. Version Coding and Diagnostic Testing

H. Version Coding and Diagnostic Testing

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

^ Skip to step 4 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 to Exists

D2B Configuration Table:

3. Using path: Control units/Information and communication/D2B/Control unit adaptations/D2B Nominal configuration, set the D2B ring configuration per the table.

4. Return to the D2B functions menu. Using path: Actual values/D2B Actual Configuration, verify 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 you MUST disassemble in reverse, diagnose and correct the error.

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

5. Check the DTC memory of all installed components and the head unit. Any present DTC(s) should be investigated and the source identified. Once identified, the source of the DTC(s) should be corrected and the 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.

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