PCM - Flash Programming Failure Recovery

NO: 18-32-98

GROUP: Vehicle Performance

DATE: Sep. 25, 1998

SUBJECT:
Flash Programming Failure Recovery

MODELS:
1995           (AA)      Acclaim/Spirit
1995 - 1999    (AB)      Ram Van
1995           (AJ)      Lebaron Convertible
1995 - 1999    (AN)      Dakota
1995           (AS)      Caravan/Voyager/Town & Country
1995 - 1999    (BR/BE)   Ram Truck
1998 - 1999    (DN)      Durango
1995 - 1999    (FJ)      Avenger/Sebring/Talon
1995 - 1999    (JA)      Cirrus/Stratus/Breeze
1996 - 1999    (JX)      Sebring Convertible
1995 - 1999    (LH)      Concorde/Intrepid/Vision/LHS/New Yorker/300M
1996 - 1999    (NS)      Caravan/Voyager/Town & Country
1995 - 1999    (PL)      Neon
1997 - 1999    (PR)      Prowler
1995 - 1999    (SR)      Viper
1997 - 1999    (TJ)      Wrangler
1999           (WJ)      Grand Cherokee
1995 - 1999    (XJ)      Cherokee
1995           (YJ)      Wrangler
1995 - 1998    (ZJ)      Grand Cherokee

DISCUSSION:

Occasionally a flash update procedure may not complete properly and/or the diagnostic equipment may lock up during the procedure. Following are items that may cause this condition along with a process to reinitialize the flash procedure. This information should help prevent the needless replacement of controllers.

Common Causes For Flash Errors

1. Poor/Bad GPIB cable connection between MDS/MDS 2(R) and DRB III(R) (defective cable, broken locking tabs, cable disconnects during procedure, etc.).

2. Poor/Bad J1962 cable connection between DRB III(R) and vehicle (defective cable, broken locking tabs, cable disconnects during procedure, etc.).

3. Loss of power to the diagnostic equipment.

4. Vehicles' ignition switch turned OFF during the programming sequence.

5. Unfamiliarity with procedures (depressing keys randomly or incorrectly).

6. Vehicle's battery voltage too low, but not low enough to display error messages when starting the reprogramming process.

RECOVERY PROCEDURE:

NOTE: THE MDS/DRB III(R) MUST BE OPERATING WITH TIL RELEASE 1169 OR HIGHER AND THE DRB III(R) MUST BE REPROGRAMMED WITH STANDALONE RELEASE 27.0 FOR IT TO WORK WITH THE MDS 2(R).

1. Make sure the GPIB (CH7035) and J1962 (CH7000/7001/7010) cables are properly connected to the DRB III(R), MDS/MDS 2(R) and vehicle. Cables that are in poor condition should be replaced.

2. Using the DRB III(R) reinitialize the flash procedure.

3. Depending on when the flash update was aborted, the diagnostic equipment may require the technician to identity what type of controller was being flash updated. Use the table as a guide:

4. After selecting the correct controller type, follow the prompts listed on the DRB III(R). Once the flash procedure is started, do not disturb the DRB III(R) or the cables connected to it, the vehicle, or the MDS/MDS 2(R).

NOTE: IF AN ERROR MESSAGE IS DISPLAYED AT THIS POINT, THE INCORRECT CONTROLLER TYPE WAS MOST LIKELY SELECTED. IF THIS OCCURS, START THE PROCESS OVER.

5. If the recovery process is unsuccessful, retry the process once again.

6. If error messages continue to be received, even after following the proper procedures and DRB III(R) prompts, contact the STAR center. Be ready to provide all error messages and the procedures used during the recovery process.

POLICY: Information Only