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 | Location / ownership | Size | Changed | Axes | Log coverage |
|---|
Calibration definition quality + safe cleanup.
Checks exact 032HS identity, canonicalizes symbol names, removes true duplicates, measures XDF coverage and excludes unresolved conflicts. Proprietary 5120, map-switch and Rolling ALS locations/signatures are intentionally not exposed by the public tool.
Strict mode is fail-closed for firmware/patch identity. Dictionary-proven definitions are labeled verified; unique definitions without exact dictionary proof are retained but marked UNVERIFIED; conflicting unproven definitions are excluded and recorded in the audit.
Is the tune at the turbo, fuel or calibration limit?
Combines the BIN/XDF with optional ME7 log data. Static calibration can show requested load and protection ceilings; a physical headroom verdict needs confirmed hardware plus live airflow, boost, WGDC, injector duty, knock and thermal evidence.
Static BIN/XDF limits
| Check | Result | Meaning |
|---|
Live headroom evidence
| Check | Result | Evidence |
|---|
This is a screening tool, not a dyno, compressor map or engine durability guarantee. It never recommends automatically raising LDRXN, KFLDHBN, WGDC or ignition. A clean static result is never called a good/safe tune. Positive headroom requires complete real logs plus confirmed hardware; missing channels return UNKNOWN. Partial 5120, unresolved sensor scaling and development files fail closed.
Scalars, tables, axes and definition conflicts.
The detector inventories every resolved XDF scalar/table, includes table axes in coverage, checks duplicate/overlapping definitions, then scans changed bytes outside those ranges for conservative scalar/table candidates.
XDF definition conflicts
| Issue | Range | Overlap | Why it matters |
|---|
Unknown scalar/table candidates
| Candidate | Range | Length | Reason |
|---|
Binary-only auto-detection cannot prove a Bosch symbol name or map purpose. Treat unknown candidates as leads for disassembly/DAMOS/XDF validation, not safe editing targets.
Things worth reviewing before you trust the revision.
Heuristic checks compare the stock and test calibration through the supplied XDF. A flag is a reason to inspect the tune or logs—not proof that the calibration is unsafe.
Thresholds are intentionally conservative and generic. Hardware, fuel, sensor scaling, 5120 state, ECU software version and operating conditions can change what is acceptable.
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.