How we research OBD codes
Sources, checks, limitations and corrections: how we distinguish definitions, diagnostics and vehicle-specific cases.
1. Where code definitions come from
Basic definitions are imported from an MIT-licensed community code catalogue. This is a reference for identifying codes, not proof of a cause or a workshop procedure.
Catalogue and licence2. What documented guidance means
Editorially expanded pages distinguish code meaning from possible symptoms, diagnostic hypotheses and confirmatory tests. We identify references and review dates where the guidance was checked. Automated text is not presented as a verified repair.
3. Vehicle and engine applicability
The same code can involve different components or procedures across engine families, model generations and ECU versions. Engine-context pages give hypotheses and scan parameters; where an engine-specific manufacturer bulletin is unavailable we disclose this. OEM procedures and VIN confirmation take priority.
4. Repair costs and safety
Cost figures, where available, describe documented scenarios rather than quotes or predictions. A code does not by itself prove a particular part has failed. For oil pressure, overheating, unsafe braking or severe noise, stop safely and seek assistance.
5. Sources, updates and corrections
A general-code reference does not independently establish a motor-specific failure. Source links are provided for traceability. To report outdated information, share the code, page URL, model year, engine and contradictory documentation. We correct verified errors; we do not publish personal details or VINs in public case studies.
Request a correction
Email info@obdauto.ro with supporting references. Avoid sharing full VINs or personal information.
info@obdauto.ro
