Prowler V6-3.5L VIN G (1999)
^
Proceed to reflash the module.
On vehicles that have multiple flash updates available, always complete and verify each flash update before attempting the next one.
After all flash reprogramming is completed, read and erase all DTCs in all modules on the vehicle. A variety of DTCs may be set, which are usually
related to a loss of communication with the module(s) being reprogrammed.
Verify the update by reading the new part number using the DRBIII(R). A good double check is to read the part number using DRBIII(R) stand alone.
At times, other modules, wired in parallel, to the DLC connector have prevented flash reprogramming sessions to be successful. After the failed attempt,
review the appropriate wiring diagram for the vehicle you are flash reprogramming and, with the key "OFF"; disconnect the other modules and retry the
flash. Complete the flash, turn the key "OFF" and reconnect any modules that were disconnected. Refer to the "Programmable Modules" section later in
this document for more information.
Error Messages
ERROR MESSAGES
Block Echo/Compare Errors
Block Echo and Block Compare errors are often caused by voltage fluctuations, faulty I/O cables (CH7OOOA, CH7005, CH7010) or faulty
communication connections at the diagnostic connector. Inspect for these conditions and review the sections on Vehicle Battery Voltage and Cable
recommendations.
Checksum Errors
Checksum Errors are generally caused by corrupt flash update files, which can be caused by DRBIII(R) memory problems. If the DRBIII(R) has been
without power for more than 8 hours, the update files and system memory could be in a corrupted state. "Cold Boot" the DRBIII(R). (To "Cold Boot",
press the MORE and YES buttons on the DRBIII(R), at the same time. Then press "F4"). Reload the flash update file(s) from the TechCONNECT
CLIENT. If it fails to complete in the connected mode, first reboot the TechCONNECT Client before re-attempting the flash download to the
DRBIII(R). Then re-attempt the flash reprogramming process.
Enhanced and Original Abort Recovery
ENHANCED ABORT RECOVERY
Interruptions in the flash process are one of the main reasons for failed flash sessions and non-responsive (NR) modules. Interrupting the flash process
after the erase phase has started will leave the control module in a non-functional state.
Generally, but not always, NR modules may be recovered successfully.
Briefly, abort recovery is the process used to get a NR module back to a fully functional state with the latest software update. The technician should be
familiar with the other sections in this document and follow all DRBIII(R) user prompts carefully.
There are two methods for abort-recovery. The newer method is called "Enhanced Abort Recovery". This is the preferred method since the original
method takes several minutes longer and requires the correct selection of module type from a list of possible PCM's or TCM's.
Starting with Release 60.1, a new useful feature was added to the flash reprogramming application for Engine and Transmission control modules. The
DRBIII(R) "writes" the YME and Controller Type information to a "Safe Memory" location. This method allows for rapid recovery of the module part
number and minimizes errors that could otherwise be made by selecting the wrong controller type. It also assumes that the user will attempt abort
recovery for a failed flash attempt before moving to another vehicle with the same DRBIII(R). If you need to move to another vehicle for flash
reprogramming you must erase the saved recovery information in order to successfully perform flash reprogramming. Be careful to match the YME
information displayed on the enhanced abort recovery screen with the vehicle and module that you are attempting to recover. If you use the recovery file
on a different vehicle and module you could damage the module.
The recovery information will be displayed on your DRBIII(R), at the start of a flash session, only if you previously encountered a problem that
prevented a flash session from completing normally. If your prior flash session was successful, the DRBIII(R) automatically erases the recovery file so
that the flash application will not show any recovery information at the start of your next flash session.
Enhanced abort recovery features:
^
Reduces the amount of time for the Module ID process.
^
Lowers the risk of possible user mistakes by presenting the user the Year, Model, Engine, and Controller Type.
^
Currently only applicable to Engine and Transmission flash reprogramming.
^
The enhanced abort recovery file will only be erased upon a successful flash or manually by the user.
