Service Procedure

The MDS2 (Mopar Diagnostic System) with the DRB Ill� (Diagnostic Readout Box scan tool) operating at CIS CD2092 or higher is required to perform this repair.

NOTE:
The MDS2 refers to the mechanical instrument cluster as a MIC.

1. Log onto the MDS2 system.

2. Connect the MDS2 (Mopar Diagnostic System) and DRB III (Scan Tool) to the vehicle and switch the IGNITION KEY TO "ON".

NOTE:
The MDS2 and DRB III should begin to "Auto Connect" within a few seconds after all connections have been made.

3. If the "Auto Connect" does not initialize, use the arrow keys and select # 2 CONNECT TO MDS2 on the DRB III MAIN MENU SCREEN.

NOTE:
Once MDS2, DRB III and vehicle communication have been established, the CANNOT READ VIN FROM DRB III message will be replaced by the VEHICLE VIN. Press the "OK" button to request a MDS2 SESSION FOR THE VEHICLE VIN INDICATED. Press the "OK" button when asked to begin the session.

4. Push the FLASH TAB on the MDS2.

5. Select READ PART NUMBERS FROM VEHICLE and click SHOW UPDATES on the MDS2. Press the "OK" button.

NOTE:
If the Mechanical Instrument Cluster (MIC) software on the vehicle has already been updated or reprogrammed, a Flash Update Information Box will appear that says "Part number (updated part number is displayed) is up to date and does not require any new updates." Continue with Step 7.

6. Select the NEW SOFTWARE PART NUMBER with the light pen and click UPDATE CONTROLLER SOFTWARE.

7. The MDS2 and DRB III will prompt for any operator action needed during the remainder of the reprogramming process.

NOTE:
Due to the MIC flash procedure, diagnostic trouble codes (DTC's) may be set in other modules (PCM, ETAX, SKIM, ABS) within the vehicle (if so equipped). Some DTC's may cause the Malfunction Indicator Light (MIL) to illuminate. All of the DTC's relate to a loss of communications with the module that is being flashed. Check all modules, record the trouble codes, and erase the trouble codes prior to returning the vehicle to the customer. Erase any trouble codes in the PCM only after all other modules have had their trouble codes erased.