Skip to content

Supported ECU Formats

Jump to bottom
Cole Gentry edited this page Feb 23, 2026 · 9 revisions

Supported ECU Formats

UltraLog supports multiple ECU systems. This page details each format's capabilities and requirements.

Quick Compatibility Reference

ECU System Status File Type Export Required
Haltech Full Support .csv Yes (from NSP)
ECUMaster EMU Pro Full Support .csv Yes (from EMU Pro)
RomRaider Full Support .csv Yes (from RomRaider Logger)
Speeduino Full Support .mlg No (native format)
rusEFI Full Support .mlg No (native format)
AiM Full Support .xrk, .drk No (native format)
Link ECU Full Support .llg No (native format)
Emerald Full Support .lg1, .lg2 No (native format)
MegaSquirt Coming Soon - -
AEM Coming Soon - -
MaxxECU Coming Soon - -
MoTeC Coming Soon - -

Haltech

Overview

Full support for Haltech ECU log files exported from NSP (Nexus Software Platform).

Supported File Format

  • Type: CSV text file
  • Extension: .csv
  • Source: Exported from Haltech NSP software
  • Identifier: File begins with %DataLog% header

How to Export from NSP

  1. Open your datalog in Haltech NSP
  2. Go to File → Export → CSV
  3. Select all channels you want to include
  4. Choose save location and filename
  5. Click Export

Supported Channel Types

UltraLog supports 50+ Haltech channel types with automatic unit conversion:

Engine Parameters

  • Engine Speed (RPM)
  • Manifold Pressure (MAP)
  • Throttle Position (TPS)
  • Engine Load

Fuel System

  • Air/Fuel Ratio (AFR)
  • Lambda
  • Fuel Pressure
  • Injector Duty Cycle
  • Fuel Trim (Short-term, Long-term)

Ignition System

  • Ignition Timing
  • Knock Levels
  • Dwell Time

Temperatures

  • Coolant Temperature
  • Intake Air Temperature
  • Oil Temperature
  • Exhaust Gas Temperature (EGT)

Pressures

  • Boost Pressure
  • Oil Pressure
  • Fuel Pressure
  • Barometric Pressure

Vehicle Data

  • Vehicle Speed
  • Gear Position
  • Battery Voltage

And many more...

Unit Handling

Haltech logs store data in specific units based on the CAN protocol. UltraLog:

  • Automatically detects the channel type
  • Applies appropriate conversions
  • Displays in your preferred units via Unit Preferences

Min/Max Values

Haltech logs include min/max metadata for each channel, which UltraLog uses for the legend display.

ECUMaster EMU Pro

Overview

Full support for ECUMaster EMU Pro log files exported as CSV.

Supported File Format

  • Type: CSV text file (semicolon or tab-delimited)
  • Extension: .csv
  • Source: Exported from EMU Pro software
  • Note: Native .emuprolog binary format is NOT supported

How to Export from EMU Pro

  1. Open your log in EMU Pro software
  2. Go to File → Export → CSV
  3. Select channels to export
  4. Choose delimiter (semicolon or tab both work)
  5. Save the file

Channel Path Structure

ECUMaster uses hierarchical channel paths:

engine/rpm
engine/map
engine/coolant_temp
fuel/lambda
fuel/injector_pw
ignition/timing

UltraLog parses these paths and can normalize them to standard names.

Automatic Unit Inference

UltraLog infers units from channel naming patterns:

Pattern Inferred Unit
*temp* °C
*rpm* RPM
*map*, *press* kPa
*lambda* Lambda
*percent*, *duty* %

Supported Channels

Engine

  • RPM
  • MAP
  • TPS
  • Load

Fuel

  • Lambda
  • AFR
  • Injector Pulse Width
  • Fuel Pressure

Ignition

  • Timing
  • Dwell

Temperatures

  • Coolant
  • Intake Air
  • Oil

And more depending on your EMU Pro configuration

Limitations

  • Native .emuprolog binary format is not currently supported
  • Always export to CSV from EMU Pro software

RomRaider

Overview

Full support for RomRaider ECU log files. RomRaider is an open-source tuning suite primarily used for Subaru ECUs, providing comprehensive logging capabilities for OEM and modified ECU parameters.

Supported File Format

  • Type: CSV text file (comma-delimited)
  • Extension: .csv
  • Source: Exported from RomRaider Logger
  • Identifier: File begins with Time column header

How to Export from RomRaider

  1. Open RomRaider Logger
  2. Start logging your parameters
  3. When complete, go to File → Save Log
  4. Choose CSV format and save location
  5. The file is ready to load in UltraLog

CSV Format Details

RomRaider logs use a straightforward CSV format:

Time (msec),Engine Speed (rpm),Engine Load (%),A/F Correction #1 (%)
0,850,15.2,1.5
20,855,15.4,1.6
40,860,15.3,1.5

Key characteristics:

  • First column is always timestamp in milliseconds
  • Column headers include units in parentheses
  • Comma-separated values
  • Timestamps are converted to relative seconds automatically

Automatic Unit Extraction

UltraLog automatically extracts units from column headers:

Header Example Extracted Name Extracted Unit
Engine Speed (rpm) Engine Speed rpm
A/F Correction #1 (%) A/F Correction #1 %
Manifold Relative Pressure (psi) Manifold Relative Pressure psi
Coolant Temperature (C) Coolant Temperature C

For columns without units in parentheses, UltraLog infers units from common patterns.

Supported Channels

Engine Parameters

  • Engine Speed (RPM)
  • Engine Load
  • Manifold Absolute/Relative Pressure
  • Throttle Position
  • Mass Airflow

Fuel System

  • A/F Correction #1 and #2
  • A/F Learning #1 and #2
  • A/F Sensor readings
  • Fuel Injector timing

Ignition System

  • Ignition Timing
  • Knock Correction
  • Fine Knock Learning
  • Feedback Knock Correction

Temperatures

  • Coolant Temperature
  • Intake Air Temperature

Subaru-Specific

  • IAM (Ignition Advance Multiplier)
  • DAM (Dynamic Advance Multiplier)
  • Fine Learning tables
  • Various OEM diagnostic parameters

Timestamp Handling

RomRaider logs time in milliseconds. UltraLog:

  • Converts milliseconds to seconds for display
  • Calculates relative time from the first record
  • Supports precise cursor positioning and playback

Speeduino / rusEFI

Overview

Full support for Speeduino and rusEFI logs in MegaLogViewer (MLG) binary format.

Supported File Format

  • Type: Binary file
  • Extension: .mlg
  • Source: Logged directly by Speeduino/rusEFI
  • Identifier: File begins with MLVLG header

No Export Required

Unlike Haltech and ECUMaster, Speeduino and rusEFI log directly to the MLG format. Simply load the .mlg file directly into UltraLog.

Binary Field Types

UltraLog supports all MLG field types:

Type Description
U08 Unsigned 8-bit integer
S08 Signed 8-bit integer
U16 Unsigned 16-bit integer
S16 Signed 16-bit integer
U32 Unsigned 32-bit integer
S32 Signed 32-bit integer
S64 Signed 64-bit integer
F32 32-bit floating point

Supported Channels

Depends on your Speeduino/rusEFI configuration. Common channels include:

Engine

  • RPM
  • MAP
  • TPS
  • VE (Volumetric Efficiency)

Fuel

  • AFR / Lambda
  • Pulse Width
  • Fuel Pressure

Ignition

  • Advance
  • Dwell

Temperatures

  • Coolant
  • IAT

Sensors

  • O2 Sensor
  • Battery Voltage
  • Various analog inputs

Timestamp Handling

MLG files include precise timestamps for each record, which UltraLog uses for:

  • Time axis display
  • Playback synchronization
  • Cursor position tracking

Format Auto-Detection

UltraLog automatically detects the ECU format based on file contents:

  1. Haltech: Looks for %DataLog% header
  2. ECUMaster: Identifies semicolon/tab-delimited CSV with TIME column
  3. RomRaider: Identifies comma-delimited CSV starting with Time column
  4. Speeduino/rusEFI: Identifies MLVLG binary header
  5. AiM: Identifies <hCNF tag in XRK/DRK files
  6. Link ECU: Identifies lf3 magic bytes in LLG files
  7. Emerald: Identifies .lg1/.lg2 file pair

You don't need to specify the format - just load the file.

AiM

Overview

Full support for AiM motorsport data acquisition systems. AiM devices are widely used in professional racing and track day applications.

Supported File Format

  • Type: XRK/DRK binary format
  • Extension: .xrk, .drk
  • Source: Logged directly by AiM devices
  • Identifier: File begins with <hCNF tag

No Export Required

AiM devices log directly to XRK/DRK format. Simply load the file directly into UltraLog.

Supported Devices

UltraLog works with all AiM data loggers:

  • MXP - Professional dash logger
  • MXG - GPS lap timer with data acquisition
  • MXL2 - Compact GPS lap timer
  • EVO5 - Advanced dash display
  • MyChron5 - Karting data acquisition
  • And other AiM motorsport data loggers

Binary Format Parsing

UltraLog uses a pure Rust implementation to parse the XRK binary format:

  • Automatically extracts all logged channels
  • Parses metadata (vehicle, racer, track, championship, lap count)
  • Handles GPS data and lap timing information
  • Supports all AiM channel types

Supported Data

Depends on your AiM device configuration and sensors. Common channels include:

GPS and Lap Data

  • GPS Speed
  • GPS Position
  • Lap Times
  • Lap Number
  • Split Times

Engine Data

  • RPM
  • Engine Temperature
  • Oil Temperature
  • Oil Pressure

Vehicle Dynamics

  • Lateral G-Force
  • Longitudinal G-Force
  • Vertical G-Force
  • Speed

Sensors

  • Analog inputs
  • Digital inputs
  • CAN bus data (if configured)
  • Lambda/AFR sensors

Metadata

AiM files include rich metadata that UltraLog displays:

  • Vehicle name
  • Racer name
  • Track/venue name
  • Championship
  • Session date and time
  • Lap count

Link ECU

Overview

Full support for Link ECU log files from G4, G4+, and G4X ECUs. Link ECUs are popular in the performance and motorsport community.

Supported File Format

  • Type: Link log format (binary)
  • Extension: .llg
  • Source: Logged directly by Link ECU via PCLink software
  • Identifier: File begins with lf3 magic bytes

No Export Required

Link ECUs log directly to LLG format via PCLink. Simply load the .llg file into UltraLog.

How to Log with PCLink

  1. Connect to your Link ECU with PCLink software
  2. Go to Logging tab
  3. Select channels to log
  4. Click Start Logging
  5. Drive/run the engine
  6. Click Stop Logging
  7. Save the .llg file

Binary Format Details

Link uses a proprietary binary format:

  • Header with ECU model and software version
  • Metadata section with log date/time
  • Channel blocks with name, unit, and time-series data
  • Data stored as f32 (value, time) pairs
  • UTF-16 LE string encoding for metadata

Supported Channels

Depends on your Link ECU model and configuration. Common channels include:

Engine Parameters

  • Engine RPM
  • Manifold Absolute Pressure (MAP)
  • Throttle Position
  • Engine Load

Fuel System

  • Lambda (AFR)
  • Fuel Pressure
  • Injector Pulse Width
  • Fuel Trim

Ignition System

  • Ignition Timing
  • Ignition Coil Dwell
  • Knock levels

Temperatures

  • Coolant Temperature
  • Intake Air Temperature
  • Oil Temperature
  • Exhaust Gas Temperature (EGT)

Pressures

  • Oil Pressure
  • Fuel Pressure
  • Barometric Pressure

Vehicle Sensors

  • Vehicle Speed
  • Gear Position
  • Battery Voltage

Custom Channels

  • Analog Voltage inputs
  • Digital inputs
  • CAN bus data (if configured)

Metadata

Link log files include:

  • ECU model name
  • Log date and time
  • Software version
  • Data source information

Emerald ECU

Overview

Full support for Emerald ECU log files from K6, M3D, and compatible ECU models. Emerald ECUs are popular in the British motorsport and classic car communities.

Supported File Format

  • Type: Binary format (dual-file system)
  • Extensions: .lg1 (data) + .lg2 (channel definitions)
  • Source: Logged directly by Emerald ECU via ECU Manager software
  • Note: Both files must be in the same directory

No Export Required

Emerald ECUs log directly to LG1/LG2 format. Simply load either the .lg1 or .lg2 file into UltraLog - both files are automatically loaded together.

How to Log with Emerald ECU Manager

  1. Connect to your Emerald ECU with ECU Manager software
  2. Go to Logging section
  3. Select channels to log
  4. Click Start Logging
  5. Drive/run the engine
  6. Click Stop Logging
  7. Save the log files (both .lg1 and .lg2 will be created)

Binary Format Details

Emerald uses a dual-file binary format:

  • .lg1 file - Contains the actual time-series data values
  • .lg2 file - Contains channel definitions, names, and metadata
  • Data stored as binary values with timestamps
  • Both files must be present in the same directory for UltraLog to load the log

Supported Channels

Depends on your Emerald ECU model and configuration. Common channels include:

Engine Parameters

  • Engine RPM
  • Throttle Position (TPS)
  • Manifold Absolute Pressure (MAP)
  • Engine Load

Fuel System

  • Lambda (AFR)
  • Fuel Pressure
  • Fuel Temperature
  • Injector Pulse Width

Boost Control

  • Boost Target
  • Boost Duty Cycle
  • Actual Boost Pressure

Ignition System

  • Ignition Advance
  • Dwell Time

Temperatures

  • Coolant Temperature
  • Air Intake Temperature
  • Oil Temperature
  • Exhaust Temperature (if fitted)

Pressures

  • Oil Pressure
  • Fuel Pressure

Electrical

  • Battery Voltage

Custom Channels

  • Analog inputs
  • Digital inputs
  • Calculated channels (if configured in ECU)

Important Notes

  • Both files required: You must keep the .lg1 and .lg2 files together in the same directory
  • Load either file: UltraLog can be pointed at either file - it will automatically find and load the companion file
  • File naming: The files must have matching base names (e.g., mylog.lg1 and mylog.lg2)

MegaSquirt / Honda Tuning Studio - Full Support

  • File type: CSV datalogs exported from TunerStudio
  • Supported devices: MegaSquirt MS1, MS2, MS3, MS3-Pro, MSPNP, MSPNP2, Honda Tuning Studio
  • Features: Automatic channel and unit extraction from column headers, boolean value parsing (MIL lamp ON/OFF), anomalous first-row timestamp handling, UTF-8 BOM support

Supported Data

  • RPM, MAP, TPS, VSS, Gear
  • Injector Duration & Duty Cycle
  • Ignition Table & Final Timing
  • Coolant Temperature (ECT), Intake Air Temperature (IAT)
  • Air-Fuel Ratio, Battery Voltage
  • Boost Pressure, Barometric Pressure
  • Analog inputs (D14, MAP Voltage, ELD Voltage, TPS Voltage)
  • MIL (Malfunction Indicator Lamp) status

Important Notes

  • TunerStudio format: The log file must be exported from TunerStudio (starts with "Tune Datalog export")
  • Channel variability: Available channels depend on your TunerStudio dashboard configuration
  • Compatible software: TunerStudio MS, TunerStudio Lite, Honda Tuning Studio, MegaLogViewer

Coming Soon

The following ECU formats are planned for future releases:

AEM

  • AEM Infinity
  • AEM EMS

MaxxECU

  • MaxxECU log files

MoTeC

  • MoTeC M1 series
  • MoTeC i2 exports

Requesting New Format Support

If your ECU system isn't supported:

  1. Open an issue on GitHub
  2. Include:
    • ECU system name and model
    • Software version used for logging/export
    • A sample log file (if possible)
    • Documentation links (if available)

Trademark Notice

UltraLog is an independent, open-source project created for interoperability purposes. All ECU system names and trademarks mentioned on this page are property of their respective owners.

UltraLog is not affiliated with, endorsed by, or sponsored by any of these companies or projects. Product names are used solely for identification and interoperability purposes.

For full legal information, see Legal.

Next Steps

UltraLog Wiki

Home

Getting Started

User Documentation

Support

Development

Legal

Links

Clone this wiki locally