ScanCar guides
Generic vs Manufacturer OBD2 Codes: Find the Right Definition
ScanCar editorial team · Updated 19 November 2026
Look up a diagnostic trouble code only after you have copied the whole code and noted where it came from. Some definitions are standardised, while others need the maker's information for the exact car or controller. A search result for the wrong engine can point you towards a different system.
Keep the full result
- Copy the characters and any sub-code or failure type as shown, with the tool's wording. Do not reduce a longer manufacturer result to whichever five characters look familiar.
- Name the module or menu you read, such as generic OBD engine data or a named controller. Add model year, engine and market. Record pending or stored status separately from the code definition.
- Check a reputable generic code reference first for a standardised code. For a manufacturer code, an unfamiliar suffix or conflicting definitions, look up official service data for the exact vehicle or give the complete record to a technician who can do it.
Two examples of what a definition can tell you
Standardised example: P0300 is commonly described as random or multiple cylinder misfire detected. It describes an observed pattern and does not identify a coil, plug or injector that must be replaced. Add symptoms and any available freeze frame before testing.
Vehicle-specific example: if a tool displays a manufacturer-controlled powertrain code with no description, leave the cause unknown. The same search phrase on a different make's forum is not reliable proof of the definition. If the scanner cannot access the module you need at all, a better definition for some other module will not resolve it.
Use the definition to choose the next check
SAE J2012 is the DTC definitions standard; the RAC guide gives UK drivers a practical introduction to code interpretation. Use the freeze-frame checklist to attach context to an engine DTC. Treat the lookup as a test priority, not an instruction to buy a component.