Catalog
| Code | Title | Engine family | Steps | Sources | File |
|---|---|---|---|---|---|
| 29CC | Random / multiple cylinder misfire | n55 | 6 | 2 | source |
| 29E0 | Fuel rail pressure / mixture too lean | n55 | 5 | 4 | source |
| 29E1 | Fuel pressure sensor signal | n55 | 5 | 4 | source |
| 29E2 | Fuel injection rail, pressure sensor signal | n55 | 5 | 4 | source |
| 2A82 | VANOS intake solenoid fault | n55 | 5 | 3 | source |
| 2E81 | Electric coolant pump speed deviation | n55 | 3 | 2 | source |
| 2E82 | Electric coolant pump fault | n55 | 3 | 2 | source |
| 30FF | Charge-air pressure too low (underboost) | n55 | 5 | 3 | source |
| P0171 | System too lean (Bank 1) | generic | 7 | 4 | source |
| P0300 | Random / multiple cylinder misfire | generic | 5 | 2 | source |
| P0420 | Catalyst efficiency below threshold (Bank 1) | generic | 5 | 1 | source |
Schema
Each testplan TOML has a dtc field, a [meta] block, and a list of [[step]] entries. The fields per step:
id— unique step ID (s1, s2, ...).instruction— what the operator should do.measurement— the measurement to take (manual question, OBD-II PID, or UDS DID with expected range).on_pass/on_fail— branch to the next step.conclusion— the final diagnosis for terminal steps.source— the in-repo citation (a path to another community file or a research doc).
Contribute
Adding a testplan is a Tier A contribution. Open a PR with a new TOML file in community/testplans/<code>.toml. CI parses the file. The TOML must reference an existing community file (opinion, story, oracle, research) for at least one step.