Start with electronic identification
Connect stable power and capture the complete ECU identification using the tool's documented procedure. Compare the result with the housing label and vehicle selection before requesting or reading data.
If the selected ECU and detected identity disagree, stop and investigate. A catalogue entry is a starting point; software updates, replacements and variants can change the correct protocol.
Understand what the read contains
An OBD operation may be a physical calibration read or a virtual file matched by identification. Bench and boot protocols may expose program, calibration, EEPROM or a combined backup.
Label the file with the operation reference and preserve the tool report. File size alone cannot prove that two reads contain equivalent memory regions.
Check patches, unlocks and checksum handling
Some ECUs require an unlock or patch before later OBD writing. Document which file or memory area was changed, the tool version and whether the procedure must be repeated after an update.
Confirm whether checksum is corrected by the tool during writing or expected in the supplied file. Do not apply multiple unknown corrections to the same data.
Plan recovery before the first write
Read the tool's recovery notes, pinout and voltage requirements before programming. Where supported, preserve full backups and determine whether recovery uses OBD, bench or boot.
The vehicle profile pages display imported protocol context, but current tool documentation remains authoritative because support can change with software and subscriptions.