Live values worth checking on a VAG — and what good looks like

About seven live values will tell you most of what you need to know about a VW, Audi, Skoda or SEAT: fuel trims, requested versus actual boost, camshaft timing deviation, DPF soot load and regeneration status, coolant against oil temperature, battery voltage under load, and misfire counters per cylinder. Roughly half of those are part of the generic emissions standard and show up on an inexpensive reader, so if that half is all you want, don't spend more. The rest are manufacturer-defined and need a manufacturer-level tool. This page explains what each one tells you and what a healthy pattern looks like — described in words rather than numbers, because the actual figures vary by engine, model year and market. Treat any figure quoted to you as a universal threshold with suspicion, and check it against a specification for your exact engine before you act on it.

What a measuring block actually is — and what you already get free

A measuring block (you may also see "measured value block", "advanced measuring values", or just "live data") is a labelled reading that a control module publishes about itself while it runs. Every module has them: engine, gearbox, ABS, climate, steering, and so on. A fault code is a conclusion the car reached. A measuring block is the evidence it reached it from — which is why live data is usually the faster route to a repair.

The generic OBD2 / EOBD standard covers emissions-related powertrain data only: things like fuel trims, coolant temperature, manifold pressure, engine load, lambda sensor readings, module supply voltage, readiness monitors, freeze frame and on-board monitor results. That is genuinely useful, it is standardised across manufacturers, and a cheap reader shows it. Everything else — named values in other modules, diagnostic-only readings, adaptation, coding and service functions — is manufacturer-specific.

That standard is not universal in time, either. Broadly, it applies to petrol cars sold in the US from the mid-1990s and in Europe from the early 2000s, with diesels following a few years later; the exact cut-off depends on the market, the model and the year, so check for your car rather than assuming. On an older VAG even the "free" values need a manufacturer-level tool speaking the older protocols, and on genuinely old ones you are looking for a small two-pin connector rather than the familiar 16-pin socket.

One habit is worth more than any single reading: compare two values that ought to agree. Requested against actual. One bank against the other. Coolant against oil. Calculated soot against measured soot. Relationships are honest even when you have no idea what the absolute figure should be.

Fuel trims: the cheapest honest health check

Fuel trims show how far the ECU is having to correct fuelling away from its base map to hit the target mixture, based on what the lambda sensor reports back. Many VAG engines — particularly the older Bosch-era control units — split this into an additive correction (roughly, idle and low airflow) and a multiplicative or percentage correction (part load), and report them separately for each bank on engines that have two. Newer control units may present trims differently or under different labels, so read what your car actually offers rather than hunting for a block number someone quoted on a forum.

A healthy pattern: corrections sitting close to neutral in both directions, similar between banks, and stable while conditions are steady. Small constant movement is normal — the fuelling loop is meant to hunt slightly. What you are looking for is a persistent lean towards adding or removing fuel.

Reading the shape: a large positive (adding fuel) correction at idle that shrinks as airflow rises points at unmetered air getting in downstream of the air meter — a split hose, a leaking gasket, a stuck valve. A correction that stays large across the whole load range points at something proportional: fuel delivery, a lazy or contaminated air-mass meter, low fuel pressure. Large negative corrections mean fuel is being pulled out — a leaking injector, high fuel pressure, or a sensor reading badly. And if one bank is well off while the other is fine, you have just halved the search area.

This one is in the standard set. Almost any reader shows short and long-term trim; a manufacturer-level tool mainly gives you nicer labelling and, on the engines that use it, the additive/multiplicative split.

Requested versus actual boost

On any turbocharged VAG the useful number is the gap between specified/requested charge pressure and actual/measured charge pressure — not either figure alone.

Healthy: actual tracks requested closely through a pull, with at most a brief overshoot when you open the throttle sharply that settles quickly, and the two converge again when you lift.

Unhealthy: actual persistently short of requested under load, which points at a boost leak, a tired wastegate actuator, a vacuum or electrical control fault, a sticking variable-vane mechanism on a diesel, or a restriction somewhere. Actual overshooting request and then collapsing usually means overboost protection intervening — often the same underlying control fault seen from the other side. Actual matching requested on a car that feels flat is a useful negative result: the problem probably is not boost.

Compare like with like. Requested boost is reduced by altitude, high intake temperatures and any active protection, so use the same road, the same gear and a similar temperature each time — and only at speeds and in places where doing so is legal and safe. Manifold pressure is in the standard set on most cars; the requested value usually is not, so this is roughly where a generic reader runs out.

Camshaft timing deviation

This tells you how far actual cam position differs from what the ECU commanded. On chain-driven engines it is one of the earliest honest indications of chain and tensioner wear. It also catches cam adjuster and solenoid faults, and oil supply problems, because the adjusters are hydraulic and depend on clean oil at pressure.

Healthy: deviation small and roughly steady, settling quickly after a cold start once oil pressure comes up, and similar on both banks of an engine that has two.

Worth investigating: deviation that has grown between checks months apart, one bank consistently offset from its partner, deviation that is fine warm but poor cold (or the reverse), or figures that wander while the engine is otherwise steady.

Be honest with yourself about what this is: a symptom, not a diagnosis. Telling a stretched chain from a sticking adjuster from low oil pressure at the head is mechanical work, and it belongs with someone who can get the car in the air and measure. But knowing the deviation before you book the car in changes the conversation entirely — and finding it healthy can save you from an extremely expensive job you were talked into. This value is manufacturer-specific; a generic emissions reader will not show it.

Misfire counters, cylinder by cylinder

Misfire counters tell you which cylinder and how often. The pattern does most of the diagnostic work for you.

Healthy: counters near-static while the engine runs steadily, no single cylinder standing out, and whatever counts do accumulate spread fairly evenly. A few counts picked up over a bumpy road or a gearchange are normal.

One cylinder dominating means something specific to that cylinder: coil, plug, injector, or compression. The classic confirmation is to swap one component with an adjacent cylinder and see whether the counts follow it. Coils and plugs are usually a reasonable home job; injectors on a direct-injection engine are not, because you are working on a high-pressure fuel system and the seals are often single-use — leave those to a workshop. Counts spread across a bank, or across everything, point at something common: fuel pressure, air, cam timing, mixture, or carbon build-up on direct-injection engines.

Standard OBD2 does report misfire monitor data, and many cheap readers show it in some form, though labelling and scaling vary between tools. The named per-cylinder live counter inside the engine module is manufacturer territory and considerably easier to read. One safety point regardless of tool: an engine misfiring badly can destroy a catalytic converter quickly, so it is not something to keep driving on.

DPF soot load and regeneration status (diesels)

Several related values matter here: calculated soot load, measured soot load (derived from differential pressure), ash load, distance or time since the last regeneration, and regeneration status or the reason one is being inhibited.

Healthy: soot climbing gradually with mileage and then dropping sharply once a regeneration completes; regenerations occurring at intervals that make sense for how the car is driven, and running to completion rather than being cut short; calculated and measured soot broadly agreeing; ash creeping up slowly over years rather than months.

Warning shapes: soot high and never dropping, which usually means regenerations start but are interrupted — commonly short journeys rather than a faulty filter. The two soot figures disagreeing badly, which points at the pressure sensor or its pipework rather than a blocked filter. An inhibit reason that is quietly telling you something else is wrong, such as coolant temperature or a fault in another system. Or high ash load on a high-mileage car, which is the filter reaching the end of its life; no amount of driving fixes ash.

Two practical cautions. An active regeneration runs the exhaust extremely hot, so avoid parking over long dry grass or leaf litter during or straight after one, and avoid switching off mid-cycle where you reasonably can. And repeatedly interrupted regenerations can dilute the engine oil with fuel — if the oil level is climbing rather than falling, take that seriously and get it looked at.

This is one of the better arguments for having live data on a diesel, because the difference between "it needs a longer run at sustained legal speeds" and "it needs a new filter" is a data question, and workshops reasonably charge to answer it. Forced or service regenerations are a workshop function for good reason.

A legal note, honestly: the DPF is emissions equipment. Removing or disabling one is unlawful for road use in many countries and affects roadworthiness testing and insurance. Rules vary by country and market and compliance is the owner's responsibility. Reading soot and regeneration data is diagnostics; deleting the filter is not a repair.

The two boring ones: temperature and voltage

Coolant and oil temperature are worth reading together and over time, not as single numbers. Healthy: coolant rising to operating temperature at a sensible rate and then sitting stable, barely moving in normal driving; oil lagging behind during warm-up and settling near or a little above coolant once everything is hot, rising further under sustained hard work. Suspicious: coolant that never quite reaches normal temperature or falls on a motorway run (a thermostat stuck open, which also costs fuel and emissions performance); coolant swinging up and down (air in the system, low level, or pump and fan control problems); or oil still cold long after coolant is hot. This check is nearly free and it changes what you should believe about every other reading, because adaptive systems only behave normally at proper operating temperature. Diagnosing a cold engine mostly wastes your afternoon.

Battery voltage under load is the other one people skip. Read the voltage a module reports, then load the car — headlights, blower, heated screen — at idle and slightly above, somewhere well ventilated. Healthy: a steady charging voltage that holds as loads come on, brief sags that recover promptly, and a short cranking dip. Suspicious: voltage that sags with loads and stays down; a meaningful gap between what a meter reads at the battery terminals and what a module reports, which indicates voltage drop in wiring or earths; or charging voltage that repeatedly collapses. Modern cars with energy management deliberately vary charging voltage, so some variation is normal and expected. A tired battery or a poor earth produces the strangest and most misleading faults across every module in the car, which is why it is worth ruling out before you chase anything else.

How to read these without fooling yourself — and when to spend money

A few rules that save more time than any tool does:

• Change one thing at a time, then re-check under the same conditions. Two changes at once teaches you nothing.
• A snapshot at idle answers very little. Trims, boost and misfires are patterns under load; record a log and look at it afterwards rather than staring at a screen.
• Do not drive and read. Use a passenger, or a tool that records for later.
• Record the freeze frame before clearing any code. Clearing wipes the evidence and also resets readiness monitors, which can leave the car unable to pass an emissions test until they have re-run. Clearing a code, or driving to reset monitors, in order to get a car through a test it would otherwise fail is not diagnosis — the fault is still there, and in many markets it is also an offence.
• Your own history is the best benchmark. The second reading, a few months later, is worth far more than the first.
• If a cheap generic reader covers fuel trims, coolant temperature, manifold pressure, module voltage, freeze frame and misfire monitor data — and that is what you wanted — buy that and stop. You do not need anything else.
• A garage or specialist is genuinely the right answer where the job needs a ramp, a smoke or pressure test, mechanical measurement, or components you cannot safely reach. Chain wear, high-pressure fuel systems and injector work belong there. Live data does not replace that; it makes you a much better-informed customer and stops you paying for diagnosis twice.
• Leaving a dongle plugged into the socket permanently is a habit worth breaking. Some keep modules awake and will flatten a battery over a week of standing.

Before you change anything: coding, adaptation and flashing

Everything above is reading. Writing to a car — coding, adaptation, service functions, and above all flashing engine software — is a different risk category, and it deserves saying plainly rather than in the small print:

• Write down the original value before you change it, exactly as the tool displays it, and change one thing at a time. "I'll remember what it was" is how a five-minute job becomes a recovery job.
• Give the car stable power. A proper battery support unit or charger, engine off and ignition on, and nothing that will interrupt mid-write. A module that loses power part-way through a write is the usual way a working car becomes a non-working one.
• Some coding is safety- or emissions-relevant — lighting, driver assistance, restraint systems, emissions-related engine settings. Changing those can make a car unsafe, non-compliant, or both, and it can invalidate insurance. Being able to change something is not evidence that you should.
• Immobiliser, keys, component protection and airbag/restraint modules are dealer or specialist territory, not a first project. Mistakes there can immobilise the car outright and recovery can need dealer-level access.
• Before flashing, save the original file and verify the backup is complete and readable. Then keep it somewhere that is not the laptop you are flashing from.
• A failed read is a nuisance. A failed write is recoverable far less often, and recovery can mean bench work, boot-mode access, or a replacement and re-coded module. Support also varies enormously by ECU family — do not assume yours is covered because the tool supports "VAG".
• Modified engine software affects emissions compliance, roadworthiness testing and insurance, and the rules differ by country and market. That responsibility sits with the owner, not with any tool. Never "fix" an emissions fault by disabling the equipment or suppressing the code.

If you do want the manufacturer-level side

Everything above the standard's line — named live values in the gearbox, ABS, cluster and other modules, cam deviation, requested boost, DPF soot and regeneration status, plus coding, adaptation and service functions — needs a tool with manufacturer-level access. There are several routes there: independent workshop software, dealer-level equipment, or simply paying a workshop that already owns one. For a single job, that last option is very often the cheapest honest answer, and it comes with someone who reads these values every day.

If you want your own, VAGPULSE — which we make — is Windows software plus a cable in that category, covering module scans, live measuring blocks, coding and adaptation, service functions, and ECU flashing on the engine families it supports. The product page lists which ECU families it covers, which is worth checking against your own car. Whatever you choose, ours included, check coverage for your exact model, engine and model year first: no tool covers every VAG equally, module and protocol support varies with age, and flashing support in particular is engine-family specific rather than universal. And if the honest answer after reading this page is that a cheap generic reader already covers your question, that is the right purchase.

Common questions