Data logger

dataloggerdata acquisition systemDAQCAN loggerdash loggerECU logger

A data logger is a device that records measurements over time, each with a timestamp, so they can be reviewed later. In cars it may be a standalone box, a dash with logging, or memory inside the ECU. It samples sensors, CAN bus messages and often GPS, storing each channel at a set rate.Medium6212

How it works

A data logger does three jobs

Acquire, timestamp and store. It converts analog sensor voltages with an analog-to-digital converter, counts frequency inputs and receives CAN frames. Every sample gets a time so channels line up later, and the result goes to flash memory, often a removable card or key.Medium6712

Resolution sets the smallest change the logger can see. A 12-bit converter splits its range into 4,096 steps, so on a 0-5 V input each step is about 1.2 mV. A 10-bit converter gives about 4.9 mV per step.

Sensor noise and ground offsets often matter more than the last bit.710

Sample rate sets the fastest event it can capture. Sampling must exceed twice the highest frequency of interest to avoid aliasing, and tuners log well above that minimum. Temperatures change slowly and need a few hertz, while pressure pulses and wheel speed need hundreds.86

Loggers come in three forms. ECU-internal logging captures what the ECU calculates. A dash logger adds a screen and its own inputs.

A standalone logger, such as a small CAN-to-SD box, records the bus silently and suits intermittent faults. Many cars run two of these, so time alignment matters.Medium2126

GPS turns a logger into a track tool. Dedicated receivers update at up to 25 Hz, and the u-blox NEO-M9N quotes about 2.0 m CEP position accuracy and 0.05 m/s velocity accuracy. GPS speed then serves as a check on wheel speed, and position gives distance for lap overlays.1413

Typical values

ADC resolution
  • 10-16 bits
  • 12 bits gives about 1.2 mV steps on a 5 V range
Sourced710
Analog sample rateUp to 500 Hz per channelAiM MX-series dash loggerSourced · medium11
GPS update rate1 Hz (some phone internal GPS) to 25 Hz (dedicated receivers)Sourced1514
GPS position accuracy
  • About 2.0 m CEPu-blox NEO-M9N
  • AiM quotes under 0.5 m for GPS091.6 ft
Sourced · medium1413
GPS time pulse accuracy30ns RMSu-blox NEO-M9N; usable to align clocks between devicesSourced14
Internal memory4GBAiM X Log, Solo 2 DL and MX seriesSourced · medium1211
Classical CAN frame
  • Up to 8 data bytes
  • 108 bits before stuffing for an 11-bit ID frame
Sourced1

How an ECU uses it

An ECU logs its own inputs and calculated values: rpm, load, target and measured lambda, injector pulse width, ignition advance, corrections and knock activity. Those internal channels exist nowhere else, which is why an ECU log stays essential even with a separate logger fitted.Medium166

An external logger usually receives ECU data as a CAN broadcast and adds sensors the ECU lacks, such as brake pressure or suspension travel. On stock cars it may poll OBD-II PIDs instead, which shares a limited request rate across every channel.Medium2155

Time alignment matters when two devices record one run. Frames a logger receives from the ECU get the logger's own timestamp, so those channels share a clock. Separate loggers need a common reference, and a GPS time pulse is accurate to tens of nanoseconds.Medium142

How to test it

5 checks, in order.

  1. Check the power feed first. Scope or meter the logger's supply during cranking; a brownout reboots the logger and can truncate or corrupt the file at the worst moment.Low616
  2. Verify each analog channel against a reference. Apply a known voltage from a bench supply, or compare a pressure sensor at key-on with barometric pressure, and confirm the logged value and units.Medium710
  3. For CAN logging, connect in listen-only mode, confirm the bit rate matches the bus and watch the error frame count. Rising errors point to termination or bit rate problems, not to the logger.23
  4. Count samples in the file, not on the settings page. A channel set to 100 Hz that shows 10 Hz steps is limited by its source, such as an OBD-II request rate or a slow CAN message.Medium158
  5. Check alignment between devices. Blip the throttle with the engine running and confirm the event appears at the same time in every log; a constant offset shows a sync error to correct before analysis.Low14

Symptoms and causes

Log file ends early or will not open.

Likely causes Power loss during a write, cranking brownout, or a full or worn memory card.

Check Watch the supply voltage during cranking and check free memory before each session.

Low616

A channel shows stair-steps instead of a smooth curve.

Likely causes The source updates slower than the log rate, such as OBD-II polling or a slow CAN message.

Check Compare the step interval with the message rate seen on a CAN interface.

Medium152

Noisy or offset analog channel.

Likely causes Ground offset between sensor and logger, a sensor ground shared with high-current loads, or wiring run beside ignition leads.

Check Measure voltage between sensor ground and logger ground with the engine running.

Medium910

Two logs disagree on when an event happened.

Likely causes Clocks not synchronized, or buffering delay in a gateway.

Check Align a sharp event, such as a throttle blip, in both files and measure the offset.

Low14

GPS speed and position jump around.

Likely causes Antenna with a blocked sky view, poor placement, or a low satellite count.

Check Log satellite count and move the antenna to an open, high position.

Medium1514

In tuning

Log what explains a decision.

For fueling, log target and measured lambda, fuel pressure, injector duty and trims. For ignition, log advance, knock activity and intake temperature. For boost, log manifold pressure, boost target and wastegate duty.Medium1617

Record protection channels on every run

Oil pressure, fuel pressure, coolant temperature and battery voltage. Many failures show as a falling pressure trend well before an alarm threshold is reached.Low16

Match rate to channel. Knock, lambda and wheel speed need fast rates; temperatures do not. Spending request bandwidth on slow channels starves fast ones when the source is OBD-II or a busy CAN bus.Medium158

Formula and worked example

bytes per second = channels × sample rate × bytes per sample
channels
number of logged channels
sample rate
samples per second per channelHz
bytes per sample
stored size of one value, often 2 for 16-bit databytes
Medium67

Common mistakes

Mistake Logging every channel at the maximum rate and drowning in data.

Do instead Group channels by how fast they change and set a rate per group.Medium8

Mistake Trusting OBD-II polling for transient fueling work.

Do instead Use the ECU's broadcast stream or internal log for transients; OBD-II bandwidth is split across every requested channel.Medium155

Mistake Saving logs without the sensor scaling or DBC version used.

Do instead Store the configuration with each log so old files still decode correctly after changes.Medium4

Myths vs facts

Myth A higher sample rate always gives better data.

Fact Beyond several times the fastest change of interest, extra samples add file size, not insight. A slow source, such as OBD-II polling, cannot be improved by logging it faster.Medium815

Myth More bits of resolution make the measurement more accurate.

Fact Resolution is step size, not accuracy. A 16-bit logger reading a sensor with 1% error still records a 1% error, only in finer steps.710

Myth A phone app is the same as a dedicated data logger.

Fact A phone can log, but some internal GPS updates at only 1 Hz and OBD-II adds request limits. A dedicated logger with 25 Hz GPS and a direct CAN connection captures far more detail.Medium1514

Frequently asked

What does a data logger do in a car?

It records sensor and ECU values over time with timestamps, so you can replay a run and see what happened. A car logger typically captures CAN bus data from the ECU, its own analog and frequency inputs, and often GPS, then stores everything to memory for review in analysis software.Medium6212

What is the difference between a data logger and an ECU log?

An ECU log records what the ECU measures and calculates, such as lambda target, advance and corrections. A separate data logger records what it receives over CAN plus its own sensors and GPS. Tuners use both: the ECU log explains decisions, and the logger adds context the ECU never sees.Medium166

How much memory does a data logger need?

Less than most people expect for channel logging. Forty channels at 100 Hz with 2-byte samples need about 28.8 MB per hour, so 4 GB holds over 100 hours. Raw CAN capture and video use much more, so size memory for those if you record them.Medium612

What resolution does a data logger need?

Twelve bits is common and gives about 1.2 mV steps on a 0-5 V input, finer than most automotive sensors' accuracy. Higher resolution helps with small-signal sensors, but wiring noise and ground offsets usually limit real precision before the converter does.Medium710

How do you sync data from two loggers?

Give them a common time reference. Feeding ECU data into the main logger over CAN puts it on one clock automatically. For separate devices, use GPS time or a shared event such as a throttle blip, then shift one file until the event lines up in both logs.Medium142

Wiring, pinouts and parts

Sources

Numbered as cited above. Hover or tap a citation chip to preview it.

17 sources
  1. CAN bus · Wikipedia · reference · retrieved 2026-10-27
  2. CAN Bus Explained: A Simple Intro · CSS Electronics · vendor-doc · retrieved 2026-10-27
  3. CAN Bus Errors Explained: A Simple Intro · CSS Electronics · vendor-doc · retrieved 2026-10-27
  4. CAN DBC File Explained: A Simple Intro · CSS Electronics · vendor-doc · retrieved 2026-10-27
  5. OBD-II PIDs · Wikipedia · reference · retrieved 2026-10-27
  6. Data logger · Wikipedia · reference · retrieved 2026-10-27
  7. Analog-to-digital converter · Wikipedia · reference · retrieved 2026-10-27
  8. Nyquist-Shannon sampling theorem · Wikipedia · reference · retrieved 2026-10-27
  9. Ground loop (electricity) · Wikipedia · reference · retrieved 2026-10-27
  10. High-speed, analog-to-digital converter basics (SLAA510) · Texas Instruments · vendor-doc · retrieved 2026-10-27
  11. MX series dash logger technical specifications (MXS, MXP, MXG, MXT) · Aim Technologies (AiM UK distributor) · vendor-doc · retrieved 2026-10-27
  12. AiM X Log data logger product page · Aim Technologies (AiM UK distributor) · vendor-doc · retrieved 2026-10-27
  13. AiM GPS09 module product page · Aim Technologies (AiM UK distributor) · vendor-doc · retrieved 2026-10-27
  14. NEO-M9N-00B GNSS module data sheet (UBX-19014285) · u-blox AG · vendor-doc · retrieved 2026-10-27
  15. RaceChrono support and FAQ (GPS receivers, OBD-II adapters, start/finish lines) · RaceChrono · vendor-doc · retrieved 2026-10-27
  16. Automotive Handbook, 10th edition (2018) · Robert Bosch GmbH / Wiley · book · retrieved 2026-10-27
  17. Internal Combustion Engine Fundamentals, 2nd edition (2018) · McGraw-Hill (John B. Heywood) · book · retrieved 2026-10-27