Tuning Wiki

In-car dataloggers record measurements against time or distance so a driver, tuner or engineer can compare runs and investigate vehicle behaviour. Systems range from GPS lap timers and video recorders to sensor-rich standalone loggers and dashboards with integrated recording. A screen, lap timer or ECU connection alone does not prove that a unit records every channel: check the exact model, hardware, firmware, licences and accessories.

Types and examples

  • GPS lap timer: AiM Solo 2 records GPS-based driving data; Solo 2 DL adds an ECU connection. Compare the Solo 2 family and check its ECU protocol and cable.
  • Standalone logger: AiM EVO6 and Race Technology DL1 CLUB record data without an integrated display; optional displays and sensor or ECU interfaces depend on the system. See AiM EVO6 and Race Technology DL1 CLUB.
  • Dash logger: AiM MXG 1.3, ECUMaster ADU and Bosch DDU 11 combine a display with logging. MoTeC C127 has a logging option; an apparently similar display can have different enabled features. See AiM MXG, ECUMaster ADU, Bosch DDU 11 and MoTeC C127.
  • Video and data: RACELOGIC VBOX Video HD1 and HD2 combine video and GNSS data with optional vehicle data. The exact cameras, connections and features vary by system and version. See HD1 and HD2.

Manufacturers and models in this section

Live telemetry and telematics

Local logging stores a recording for later download. Telemetry transmits measurements to a remote receiver, while connected telematics systems may combine vehicle position, status, alerts and remote access. One device can do both. Check which channels are live, transmission delay, mobile or radio coverage, subscriptions, and whether data is buffered and uploaded after a connection is lost. Do not assume a live feed supplies every locally recorded sample.

For example, Race Technology RT LIVE Industrial uses 4G LTE for online data access; CAN data requires the relevant licence. The details and availability depend on the system and service. See In-car live telemetry and telematics for further examples, including RaceCapture and MoTeC T2.

Choosing a system

  1. Define the job: lap and driver comparison, engine calibration, fault finding, chassis development or synchronised video. List the channels needed before choosing hardware.
  2. Check the data source: GNSS for position and speed; inertial sensors for acceleration; direct analogue, frequency or temperature inputs for sensors; and ECU data over a specifically supported CAN, serial, K-Line or OBD protocol. OBD connector compatibility does not guarantee the desired channels or refresh rate.
  3. Confirm the required sample rate for each signal, total channel capacity, memory, download method, GPS antenna placement, sensor conditioning, installation and environmental rating. A device's maximum rate is not automatically available simultaneously for every channel.
  4. Price the whole system: logger, loom, compatible sensors, GPS, display, camera, ECU interface, expansion modules and software or feature licences. Check vehicle, ECU, firmware and wiring against the manufacturer's documentation.
  5. For live reporting, check the receiver, coverage, latency, data plan, account access and offline behaviour. Check analysis software, supported operating systems, export formats and comparison features. Record test conditions and calibration details so that two runs can be compared fairly.

Data-log analysis software by manufacturer

Open a manufacturer page below for its step-by-step guide to retrieving and analysing a session, including model-specific transfer methods and software links.

Choose the analysis application for the device and recorded file, then check supported operating systems, download methods, hardware options and licence terms on the linked manufacturer page. Live telemetry and offline log analysis can be separate services.

ManufacturerAnalysis software or service
AiMRace Studio 3 Analysis
MoTeCi2 Standard and i2 Pro
RACELOGICCircuit Tools; VBOX Test Suite for performance testing
Race TechnologyRace Technology Data Analysis and Live Monitor
ECUMASTERData Master
Bosch MotorsportWinDarab V7
Autosport LabsRaceCapture app and Podium online service
GarminCatalyst device and mobile app review
HP TunersTrackAddict and RaceRender video overlays

Using logged data

Start with a short stationary recording and verify units, sensor calibration and plausible values. Confirm that recording starts and files can be retrieved. On track, compare the same circuit layout and similar conditions; review speed, throttle, braking and engine channels together rather than treating one trace as proof of a fault. A GPS speed trace and ECU wheel speed may differ because they measure different things. Keep the driver focused on driving and use appropriate track rules and a safe mounting arrangement.

For a broader discussion of measurement in engine work, see Data logging for engine preparation and design. Vehicle-specific wiring and ECU protocols must be verified before connection.

Product imagery and references

Manufacturer product pages linked above include marketing photographs. The AiM manufacturer article includes credited photographs used with permission. AiM also publishes a product picture library. Images are credited to their respective manufacturers; availability on those sites does not establish permission to republish them here. Check manufacturer terms and obtain permission where required.