No changes yet. Select DTCs in Patch and apply the OFF pattern.
Pick a family in Patch.
Fault table spans found in this file
—
Known builds for this family
—
The scan re-derives the table for every file. A known-build address is only a sanity check: if the scan lands somewhere else on a file that should match, stop and investigate before patching.
Diff ori vs DTC-off
Load an original and a known-good DTC-off file of the same build. The diff lands on the fault table and shows the struct stride and off-pattern.
Family editor
Edit the selected family (finder range, struct, off-pattern, dtcNames), apply and rescan. Export the JSON and give it to Claude to bake into the next release.
Teach the app a new ECU
- Diff an ori + proven DTC-off pair. Note stride/phase and the bytes the tuner changed.
- New from template → set
struct.size, fields,dtcDecode, finder range,offPattern. - Apply & rescan on the ori. The table must show the expected codes with the right ACTIVE/OFF states.
- Export JSON → give it to Claude with your notes. It goes into families.json, the project notes and the skill.
Finders: · Decoders: . A layout these cannot find needs a new finder (code change).
Diff result
No diff yet.