Technical information

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® “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®. 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®, 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® 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.
• Cold booting (simultaneously pushing MORE & YES, then F4) the DRBIII® will not
erase the enhanced abort recovery file, but cold booting the DRBIII® will still erase
the flash file so it can be reloaded.
• The user has a choice, at the start of a flash session , whether or not to use the
enhanced abort recovery feature. If the user chooses to erase the recovery file, then
the DRBIII® will use the original method of abort recovery.
• Cycling the ignition key, when prompted by the DRBIII®, is still necessary to put the
controller into bootstrap (reprogramming) mode.
ORIGINAL ABORT RECOVERY
If the choice is made to use the original method of abort recovery, a NR module is not
always able to provide the DRBIII with ID information. In this case the technician must
enter this when prompted by the DRBIII®. Be patient when performing this process. If the
module does not respond to standard diagnostic requests, the DRBIII® may take several
minutes before it determines that the engine module is in a NR state. At this point, the
DRBIII® displays the prompt "Could not determine engine controller type. Please select
from list" along with a list of possible controller types (if the DRBIII® is attempting to
identify a TCM, the prompt will say "trans" instead of "engine" and list the possible trans
controller types). Because of module variations, it is important to correctly identify the
PCM/TCM type so that the correct flash procedure is used. Failure to do this will cause
further problems and may damage the module. Tables are provided below to help identify
the proper module type to select. These tables correctly identify the modules that were on
-11- 18-037-05