Reading methods

OBD, Bench and Boot: a workflow overview

The connection method describes how the tool reaches the control unit. It does not, by itself, tell you what data will be returned or which operation is supported.

By Stage1Files Updated

OBD access

OBD work uses the vehicle’s diagnostic connection. For a supported protocol, this can provide identification, reading or writing functions without removing the control unit. The available functions depend on the specific controller and tool protocol. Do not assume that a listed write function implies that a complete original backup can also be read through the same connection.

Bench access

Bench access connects through the control unit’s connector. It is commonly used without opening the enclosure, subject to the exact protocol. Connection diagrams, power requirements and available operations must come from your tool’s current documentation. A generic family name is insufficient grounds for choosing a pinout.

Boot access

Boot methods involve direct access with the control unit open and can require board connections or specific adapters. This adds handling and connection considerations beyond an in-vehicle diagnostic operation. Follow the supported procedure for the exact hardware. This overview deliberately does not substitute a general pinout or wiring sequence for the protocol instructions.

Identify the delivered data

A read may provide selected memory content, a broader backup or a tool-specific format. Record the method and preserve the identification report with the file. Keep an original archive even if the subsequent calibration workflow uses only part of the data. Do not change file extensions to make different formats appear interchangeable.

Connect reading to calibration and writing

Stage1Files receives the eligible file for calibration; it is not the hardware connection to the ECU. After processing, return to the programming tool’s documented workflow for the exact result format, checksum handling and writing operation. Recheck the selected job, original identity and destination before you proceed.

Plan the exception before the write

Know which documented recovery options your tool provides and what information Support will need if communication fails. Preserve identification reports and the original in an accessible location. If access or compatibility remains uncertain, stop at the preparation stage rather than turning the first write into an experiment.

Further reading

Check ECU & TCU coverage or contact Support about a specific file.