Diagnostic system and programming route
OBD refers both to the regulated diagnostic framework and, in workshop language, access through the vehicle diagnostic connector. A supported programming protocol can be full, partial or virtual depending on ECU and tool.
Preparation still matters
Use stable power, correct vehicle conditions and the current official protocol help. A non-invasive connection is not risk free.
Related terminology
Bench modeDirect connection to a control unit through its external connector, without opening the case on supported protocols. Available read, write and cloning functions vary by ECU and tool.Boot modeA board-level access method that generally requires opening the control unit and placing the processor or memory system into a supported boot state.ChecksumAn integrity calculation used by control-unit software to detect unexpected data changes in defined memory regions. A valid checksum does not prove that the calibration is safe or appropriate.Calibration fileDigital control-unit data containing calibration and, depending on read type, program or configuration regions. File identity and structure must match the target control unit and programming workflow.ECU cloneA controlled transfer of compatible program, calibration, configuration or security-related data from an original unit to a verified replacement. Legitimate ownership and hardware compatibility are essential.Full readA read intended to capture the complete memory scope supported by a protocol, potentially including program, calibration and additional data. 'Full' remains tool- and ECU-specific.Partial readA read containing only selected memory regions, commonly calibration data. It may be suitable for routine work but is not necessarily a complete recovery backup.Recovery fileVerified data retained to restore a control unit after an interrupted or incompatible programming event. Required scope depends on ECU and protocol.