Enhanced and Original Abort Recovery
ENHANCED ABORT RECOVERYInterruptions 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.
^ Cold booting (simultaneously pushing MORE & YES, then F4) the DRBIII(R) will not erase the enhanced abort recovery file, but cold booting the DRBIII(R) 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(R) will use the original method of abort recovery.
^ Cycling the ignition key, when prompted by the DRBIII(R), 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(R). Be patient when performing this process. If the module does not respond to standard diagnostic requests, the DRBIII(R) may take several minutes before it determines that the engine module is in a NR state. At this point, the DRBIII(R) displays the prompt "Could not determine engine controller type. Please select from list" along with a list of possible controller types (if the DRBIII(R) 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
the vehicles when they were built. However, some vehicles will have module types which were superseded to a new type when a replacement part was installed (ie: EATX4 modules replaced with an EATX4A). Correctly identify these modules using DRBIII(R) Standalone prior to attempting flash reprogramming.
NOTE:
When instructed to turn the key to the LOCKED position, be sure that the key is not just turned to the OFF position. The key must be rotated to the point at which it can be removed from the ignition switch. On most vehicles the switch is on the steering column and at this position the steering column is LOCKED. When instructed to turn the key to the RUN position, be careful not to turn the key past this position which may engage the starter motor. This creates electrical noise which interferes with the flash process.
General Steps for Abort Recovery
1. Review all Tips and Techniques before continuing. Pay special attention to the section on Preparing to Flash a controller and to the Programmable Modules section.
2. Cycle the vehicle's ignition key to the LOCKED position and back to the RUN position.
3. Reset the DRBIII(R) by disconnecting the vehicle cable from the DRBIII(R) for 4 seconds and then reconnecting the cable.
4. Depending on where the flash session was aborted, the DRBIII(R) may require that the technician identify the control module type that was being flash reprogrammed. Use the PCM/TCM configuration table below as a guide. This step is not necessary if using the enhanced abort recovery method.
5. After selecting the proper control module type or choosing enhanced abort recovery, follow the prompts that are displayed on the DRBIII(R).
NOTE:
If an error message is displayed at this point, an incorrect module type was most likely selected. If this occurs, start the process over.
6. If the recovery process is unsuccessful, perform the following:
a. Review the TSB/Recall notice (authorizing the flash update) and all Tips and Techniques in this document.
b. Reboot/Restart the TechCONNECT Client.
c. "Cold Boot" the DRBIII(R). (Press the MORE and YES buttons on the DRBIII(R) at the same time, then press F4).
d. Start this process over from item # 1. If using Disconnected Mode, the flash update will have to be reloaded from the TechCONNECT Client or ISIS DVD.