PREVIEW V9.1 · SC OBD2 Legacy · Not the public website
Skip to content
Smart ControlAutomotive

Observatory · Guide to reading data

P0300 and P0301: why the code is not enough to choose a coil

The qualification and source shown on this page apply to the information below. Suggested reading links do not upgrade its evidence status.

This guide was prepared with AI assistance and has not yet received a final technical review. Its examples are illustrative and do not confirm a cause on your vehicle.

P0300 reports random or multiple misfires; P0301 refers them to cylinder 1. Neither code, on its own, demonstrates that a coil has failed. Volkswagen's misfire diagnostic bulletin requires identifying the cause before replacing components. Source: Volkswagen 2033805/6, pp. 1–4

This is an orientation guide for petrol engines, not a repair procedure. The examples are illustrative and do not come from SCA measurements on a real car.

First observe the dashboard warning light

If the engine warning light flashes or the engine runs very unevenly, stop any optional testing and follow the vehicle manual's instructions. Ford warns that flashing can accompany a misfire and that exhaust temperatures can damage the catalytic converter; it recommends avoiding heavy acceleration and deceleration and having the vehicle checked. Source: Ford manual, Malfunction Indicator Lamp

Describe what you see on the dashboard separately from the code read in the app. A note such as “it was flashing during the problem” is an observation; it must not be added to a report if nobody actually observed it. An OBD reading must not become permission to keep driving.

Three families of checks, without ranking causes

A misfire report may require checks of ignition, fuel supply or mechanical condition. A GM document for specific LGX, LGW and LGZ engines from 2016–2018 describes checks of electrical components and fuel and, within its own scope, further mechanical checks. It does not indicate that this fault is also present in your engine. Source: GM PIP5493E, pp. 1–2

Area to check in the workshopConcrete questionUseful outcome to record
Ignition and connectionsWhich check links the fault to the component or its circuit?Test outcome, conditions and component actually involved.
Cylinder fuel supplyHave the injector and its function been checked using the specified procedure?Outcome of the electrical or functional check appropriate to the system.
Cylinder mechanical conditionIs there evidence of the cylinder's ability to work correctly?Relevant measurement, manufacturer reference and technician's interpretation.

The table is a way to request understandable evidence. It does not invite you to remove coils, disconnect injectors or work on pressurised circuits.

The check must distinguish alternatives

In the cited Volkswagen bulletin, concerning the petrol models from 2008–2023 indicated in the document, diagnosis can check whether the problem follows a component and may require injector or compression checks. These are workshop tasks to perform according to the specific manual. The transferable point is the method: a test distinguishing the hypotheses is needed, not collective replacement suggested by P0300 alone. Source: Volkswagen, pp. 3–4

What to note to make the report useful

Prepare a note with codes and status, symptoms, engine temperature, circumstances when the problem occurred and recent maintenance. Add any freeze frame without confusing it with current values: it represents conditions recorded on an event, not a continuous reading. Source: Bosch OBD1150, §5.8

Illustrative example: P0301 present, engine now idling smoothly, problem reported in an earlier phase. The question to take to the workshop is “which data describe that phase?”, not “which part do I buy today?”. If context is missing, say so; inventing it would make the comparison less reliable.

To organise data with Smart Control OBD2, start with the guide to information actually available in your configuration. A useful report distinguishes what you observed, what the control unit reports and what still needs checking.

Sources and scope

What to observe before drawing conclusions

Keep the exact code and any status shown, the symptoms, and the circumstances in which they appeared. If live readings are available, note their names, values and units. Missing information is not zero and a reading does not by itself confirm a cause.

Use the existing guide to keep the context

Smart Control OBD2 reads available codes and parameters through a compatible adapter. It helps you observe and retain context; it does not automatically identify the cause of a fault. Coverage depends on the vehicle, control unit and adapter.