Cold booting (simultaneously pushing MORE & YES, then F4) the DRBIII(R) will not erase the enhanced abort recovery file, but cold booting theDRBIII(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 therecovery 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 thiscase the technician must enter this when prompted by the DRBIII(R). Be patient when performing this process. If the module does not respond tostandard diagnostic requests, the DRBIII(R) may take several minutes before it determines that the engine module is in a NR state. At this point, theDRBIII(R) displays the prompt "Could not determine engine controller type. Please select from list" along with a list of possible controller types (if theDRBIII(R) is attempting to identify a TCM, the prompt will say "trans" instead of "engine" and list the possible trans controller types). Because ofmodule 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 furtherproblems and may damage the module. Tables are provided below to help identify the proper module type to select. These tables correctly identify themodules that were onthe vehicles when they were built. However, some vehicles will have module types which were superseded to a new type when a replacement part wasinstalled (ie: EATX4 modules replaced with an EATX4A). Correctly identify these modules using DRBIII(R) Standalone prior to attempting flashreprogramming.

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 thepoint 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 steeringcolumn 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 thestarter 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 ProgrammableModules 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 beingflash reprogrammed. Use the PCM/TCM configuration table below as a guide. This step is not necessary if using the enhanced abort recoverymethod.

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 TechCONNECTClient or ISIS DVD.