Evidence-graded diagnostic cases

Cases

A fault code tells you a threshold was crossed. A case shows what someone actually measured, what it did and did not prove, and whether the repair held. Every case is graded by how strong its evidence is — and nothing below the floor moves a published number.

The evidence ladder

Why it exists: a dataset that treats "somebody said so" the same as a before/after dyno becomes folklore with a percentage sign on it.

E0 Claim only. Somebody said so.
E1 A photo or a scan screenshot is attached.
E2 Scans from before and after the repair.
E3 Before log, stated repair, and an after log under comparable conditions.
E4 Instrumented: dyno or bench measurement on both sides of the repair.
OEM Manufacturer source — service data, TSB or recall.

Published cases

No verified real-vehicle cases published yet. We would rather show the gap than pad it. Below is a worked demonstration on synthetic data, so you can see the shape a real one will take — then the method goes live with documented DMS cases, after technical review and consent.

P0299 Demonstration · synthetic

Underboost — worked example

A requested-vs-actual boost trace that confirms an underboost in the data, carries the P0299 check list, and deliberately does not name the wastegate before the test that would. Synthetic samples — no real vehicle was analysed.

Illustrative Requested vs actual boost · not a measurement from any vehicle
0.0 0.4 0.8 1.2 1.6 0s1s2s3s4s5s bar Requested Actual

Example shape: actual builds but plateaus around 0.9 bar and never reaches the 1.40 bar request — the gap is the fault.

Open the worked example →

For workshops & DMS

Have a documented case worth publishing?

DMS Tuned seeds this library with real, instrumented cases (boost control, fuel trims, calibration validation). Pilot workshops can contribute their own — with evidence, consent and a technical review before anything goes live. We never publish a repair we cannot back.

Talk to the engineers →
Ask the engineers