1.8T misfires in VCDS: groups 014, 015 and 016

Updated:

Does your 1.8T shake at idle, hesitate during acceleration or illuminate the check engine light? One possible cause is an engine misfire. On many older Motronic ECUs, you can view misfire information in VCDS groups 014, 015 and 016. These readings can help determine whether the problem affects one cylinder or the entire engine.

This guide applies to four-cylinder 1.8T engines where these groups are available for misfire diagnosis. Group numbers and counting methods differ between ECUs, so always check the field labels. For VCDS basics, see How to record a VCDS log.

At a glance: what a healthy reading looks like

How the ECU detects misfires

The ECU monitors irregularities in crankshaft speed between combustion events. If the crankshaft accelerates differently from what is expected, the ECU may register a misfire. The underlying cause may be missing spark, too much or too little fuel, a mechanical issue or unstable engine operation.

Importantly, a misfire fault code does not automatically mean an ignition coil has failed. An intake leak, low compression, injector problem or fuel-delivery fault may produce similar symptoms.

What groups 014, 015 and 016 show

According to the procedure for a particular Audi A3 8L system:

Group Fields Purpose
014 Includes engine speed, load, total misfires and detection status General misfire monitoring
015 Counters for cylinders 1, 2 and 3, plus status Identify which of the first three cylinders is affected
016 Counter for cylinder 4, plus status Monitor cylinder 4

The status field may show activated / blocked. These indicate whether misfire detection is active or inhibited. Audi says recognition is blocked when misfires are expected anyway, e.g. while the engine warms up or during the fuel cut on overrun. In that case, a zero counter should not be taken as firm evidence that there are no misfires.

Audi's procedure, run at idle, specifies 0 in the counters while misfire detection is active. Group 014 also gives an engine load of 10–25% as the specified value. Audi does not say over what period the counters count. Owners report that they reset to zero after about a minute, so do not read them as a total of every misfire the car has ever had.

How to check misfires while stationary

  1. Read DTCs in 01-Engine before clearing anything. Save any available freeze-frame data or fault conditions.
  2. Warm up the engine if it is safe to do so and there are no symptoms suggesting imminent damage.
  3. Select Select → 01-Engine → Meas. Blocks - 08.
  4. Open 014, 015 and 016 if your ECU supports them.
  5. Watch the counters for several dozen seconds while the engine is running roughly. Note whether a particular cylinder's count rises.
  6. If the symptom appears only when driving, do not attempt aggressive testing with a badly misfiring engine. Continue only if further testing is safe and diagnostically justified.

A flashing check engine light or severe misfiring can indicate a condition capable of overheating the catalytic converter. Stop loading the engine and address the fault before further tests.

One cylinder or several? How to interpret the readings

What you see Where to start
Only cylinder 2's counter rises Cylinder 2 spark plug and coil, injector, compression, wiring and connectors
Counters for two cylinders increase Shared components, intake, fuel system and potential mechanical issues
Counters rise on all cylinders Fuel pressure, fuel quality, intake leaks, MAF, general engine instability
Counters do not rise but the car still jerks Check detection status, other parameters and other causes of hesitation
Misfires occur only when warm Coils, plugs, fuel system and temperature-sensitive components

Start by identifying when the symptom occurs. If only one cylinder is affected, and safe service procedures permit it, you can compare its spark plug and coil with another cylinder and check whether the problem follows the part. Observe ignition-system safety requirements and inspect wiring and connectors for damage.

Example reading

The values below are a hypothetical example, not an actual workshop case:

Time Cylinder 1 Cylinder 2 Cylinder 3 Cylinder 4
Start 0 0 0 0
After 20 seconds 0 6 0 0
After 40 seconds 0 13 0 0

The increasing counter on cylinder 2 justifies focusing further tests on that cylinder. It does not prove that you need to buy a new coil. Check DTCs, the spark plug, injector, fuel pressure and compression as appropriate.

Typical DTCs

OBD code VAG code Meaning
P0300 16684 Random / multiple-cylinder misfire detected
P0301 16685 Cylinder 1 misfire detected
P0302 16686 Cylinder 2 misfire detected
P0303 16687 Cylinder 3 misfire detected
P0304 16688 Cylinder 4 misfire detected

Also save related codes, for example those concerning the MAF, oxygen sensor, air/fuel mixture and crankshaft/camshaft sensors. They may point to a shared root cause.

Groups 020 and 032: important connections

Group 020 on selected 1.8T ECUs reports ignition retard applied by knock control, not the number of misfires. See Ignition timing retard — group 020.

Group 032 can help identify a mixture issue contributing to misfires. See Fuel trims — group 032.

Common mistakes

Frequently asked questions

Does P0302 mean cylinder 2's ignition coil is bad?

No. It means a misfire has been detected on cylinder 2. The cause could also be the spark plug, injector, an air leak or a mechanical fault.

Is a single occasional misfire always a serious problem?

It depends on the conditions, frequency and symptoms. One reading is not necessarily evidence of a persistent fault, but recurring misfires should be investigated.

Why does the counter stay at zero even though the car hesitates?

Misfire detection may be inactive, the ECU may not recognise that kind of uneven running, or the hesitation may come from a different system.

Can vaglogs help?

If you have a CSV log containing these values, upload it to vaglogs and see on the chart when and on which cylinder the counters rise. The diagnostics do not judge misfire counters yet, and finding the cause still requires the fault codes and further checks.

Sources