See what changed in the tune—and whether the log ever used it.
Load a baseline BIN, a test-tune BIN, the exact TunerPro XDF for that software, and a log. The correlator maps changed bytes back to named XDF tables, then uses decodable RPM/load axes to estimate which cells or regions the log actually exercised. Unsupported or ambiguous XDF definitions are labeled instead of guessed.
Named calibration changes.
Rows are generated from XDF table/constant address ranges. “Exercised” means the log operating points map to changed cells in a table whose RPM/load axes were decoded successfully.
| Calibration | Type | Address | Size | Changed | Axes | Log coverage |
|---|
Changed cells vs. logged operating area.
Orange cells differ between the two BINs. Green outlines mark cells the log visited. A filled changed cell with a green outline is a calibration change that the log actually exercised.
Definition
- Name
- —
Correlation
- Status
- —
Changes outside the XDF still matter.
Not every byte in an ECU binary belongs to a named XDF calibration. This section compares the entire binaries so patch code, checksums, metadata or unsupported calibration regions are not silently ignored.