Getting Started

Learn how the OpenECU Alliance standardizes ECU log data formats across manufacturers.

What is the OpenECU Alliance?

The OpenECU Alliance is an open community dedicated to standardizing ECU log data formats. We maintain:

The OpenECU Spec

A YAML-based specification for describing ECU log file formats and channel mappings.

Adapter Library

Pre-built adapters for popular ECU systems like Haltech, Link, AiM, ECUMaster, and more.

Ecosystem

Spec-compatible applications that work seamlessly with any ECU system.

The Problem We Solve

Every ECU manufacturer exports data differently. The same data point has different names across vendors:

Haltech
"Engine RPM"
Link ECU
"Engine Speed"
AiM
"RPM"
ECUMaster
"Eng RPM"
All mean the same thing
Canonical ID
rpm

Without standardization, every analysis tool needs custom code for each ECU system. Adapters solve this by mapping vendor names to canonical identifiers.

The Solution: Adapters

Adapters are YAML files that map vendor-specific channel names to standardized canonical identifiers:

yaml
channels:
  - id: rpm                    # Canonical ID (standardized)
    name: "Engine RPM"
    source_names:              # Vendor-specific names
      - "Engine RPM"
      - "Engine Speed"
      - "RPM"
      - "Eng RPM"

Applications implementing the OpenECU Spec can use any adapter to parse any supported ECU format - no custom code needed.

How It Works

1

The Spec

OpenECU Spec defines a standard YAML format for describing ECU log formats.

2

Adapters

Community creates adapters that map vendor-specific channels to standard IDs.

3

Applications

Spec-compatible apps use adapters to support any ECU without custom code.

The Ecosystem

OpenECU Spec
  • Adapter file format specification
  • Canonical channel identifiers
  • JSON Schema for validation
  • Official adapter library
Alliance Projects
  • Future donated projects
Spec-Compatible Apps
  • UltraLog
  • Your app here

Next Steps