PullScan

PullScan Learn

Understand automotive telemetry

Engineering articles and practical guides grounded in measured signals, documented relationships, and clearly stated limitations.

BoostData Logging

Why Does the Throttle Close During a Pull?

A falling throttle trace does not explain itself. Learn how pedal position, boost, ECU targets, and surrounding channels help distinguish driver lift from control intervention—and what a log cannot prove.

Read resource
Data LoggingTelemetry Analysis

How to Compare WOT Datalogs: Why Two Pulls Can Look Different

A WOT datalog is one snapshot, not a final verdict. Learn why heat, load, gear, throttle intervention, fueling, boost, and timing can vary between pulls—and how comparing logs helps separate repeatable patterns from normal variation.

Read resource
Data LoggingEngine Management

Timing Correction Explained: How to Read Ignition Retard in a Datalog

Learn what timing correction represents, how knock control changes ignition timing, and why isolated correction values should never be diagnosed without RPM, load, fuel, temperature, and repeatability context. An anonymized Kia Stinger 3.3TT case study demonstrates how a persistent pattern can be identified without claiming an unsupported root cause.

Read resource

Why Does Actual Boost Differ From ECU-Reported Boost?

Actual boost, requested boost, and ECU-reported boost can represent different parts of a load-based control system. Learn how to interpret their relationship using throttle, target, wastegate, fueling, and timing data—with evidence from a real 3.3TT JB4 case.

Read resource
Fueling

What Causes High Fuel Trims?

High fuel trims show that the ECU is adding fuel, but they do not identify the cause by themselves. Learn how air leaks, fuel delivery, ethanol content, sensor inputs, and supplemental fueling affect trim behavior.

Read resource