Technical information

instructions were followed, perform the following:
• Cold boot the DRBIII®. This resets memory and removes all update files from the
DRBIII®. (Push MORE and YES buttons at the same time, then press F4).
• Reload the flash update file 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®.
• 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®. A good double check
is to read the part number using DRBIII® 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
Block Echo/Compare Errors
Block Echo and Block Compare errors are often caused by voltage fluctuations, faulty I/O
cables (CH7000A, 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® memory problems. If the DRBIII® 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®. (To "Cold Boot", press the MORE and YES buttons on the DRBIII®, 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®. Then re-attempt the flash reprogramming
process.
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® user prompts carefully.
18-037-05 -10-