Skip to content

feat(dtc): explain the failure type byte of a trouble code - #242

Merged
tzebrowski merged 1 commit into
masterfrom
feat/dtc-failure-type
Oct 15, 2026
Merged

tzebrowski merged 1 commit into
masterfrom
feat/dtc-failure-type

Conversation

@tzebrowski

Copy link
Copy Markdown
Owner

Show what the -XX suffix of a code means (SAE J2012 / ISO 15031-6), e.g. "Failure type: 14 · Circuit short to ground or open", in the expanded DTC row and in the shared report. ObdMetrics' own table is empty ("Unknown Subtype" for every code), so the app ships the generic table in EN and PL, falling back to the decoder's text and then to the byte's category.

Show what the -XX suffix of a code means (SAE J2012 / ISO 15031-6),
e.g. "Failure type: 14 · Circuit short to ground or open", in the
expanded DTC row and in the shared report. ObdMetrics' own table is
empty ("Unknown Subtype" for every code), so the app ships the generic
table in EN and PL, falling back to the decoder's text and then to the
byte's category.
@tzebrowski
tzebrowski merged commit a252e31 into master Oct 15, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant