Aftermarket ECU support: what GAINS reads, recommends and never writes

On an aftermarket ECU from another maker, GAINS is an advisor, not a tuner with write access. It reads data the ECU maker documents publicly, such as CAN broadcast streams, or logs you export, and recommends exact table changes with reasons. You apply them in the ECU maker's own software. GAINS does not write to or reflash third-party ECUs, because no maker publishes an interface that authorizes it. Every compatibility row is research until bench-verified.354

Key takeaways

  • Support is described in tiers: 1 read-only telemetry, 2 offline calibration files, 3 hand-off to the vendor's tool, 4 authorized parameter write, 5 authorized full deploy.
  • On third-party ECUs, GAINS targets tiers 1-3 only. Tiers 4-5 need a written agreement with the ECU maker; none exists today.
  • Read-only data comes from documented CAN broadcast streams, user-supplied DBC files, exported logs, or standard OBD-II PIDs on factory ECUs.
  • Advisor mode runs the same strategies as on a GAINS ECU and outputs which cells to change, by how much and why. You stay in charge of the write.
  • CAN profiles are built clean-room from vendor-published documents. Competitor software, templates and firmware are never mined.
  • Every vendor row is labelled research until a profile is bench-verified against a real ECU and firmware version.

The short answer

If you already own an aftermarket ECU, GAINS can watch it and advise on it, but it does not write to it.

The ECU maker's own software stays the only tool that changes your calibration.34

That limit is deliberate. No aftermarket ECU maker we researched publishes a calibration-write or flash interface for third parties, and writing without one would mean reverse engineering a product we have no right to modify.52

Integration tiers 0-5

Capability is stated per ECU family and firmware version, using six tiers.

Tier 0UnsupportedSourced8
Tier 1

Read-only live telemetry over a vendor-documented interface (usually CAN broadcast)

Sourced85
Tier 2

Offline calibration files: documented or user-exported formats (CSV, DBC)

Sourced85
Tier 3

Vendor-tool hand-off: GAINS recommends, you apply in the vendor's software

Sourced83
Tier 4

Authorized parameter write to a running ECU (needs vendor agreement)

Sourced83
Tier 5Authorized full calibration deploy (needs vendor agreement)Sourced83

A tier counts only when a vendor document supports it and a bench test confirms it.85

What the public record shows, by ECU family

Tier 1 telemetry documented publiclySeveral familiesresearch, unverifiedSourced · medium56
Third-party write or flash interface publishedNone foundSourced5
GAINS bench-verified profilesNone yetSourced62

Our research found publicly documented read-only CAN broadcast protocols for several major families, including Haltech, ECUMaster, FuelTech and MaxxECU. Others document their streams inside their own tuning software. None is bench-verified by GAINS yet.Medium56

No family we researched publishes a third-party calibration-write or flash interface. The one formal developer route found is MoTeC's licensed M1 Build and partner-package programme, which is a commercial agreement, not a public interface.Medium54

Several makers ship their own phone apps that can edit settings. That is their first-party access; it does not grant any right or route for a third-party app to do the same.Medium5

How read-only data works: CAN broadcast, DBC files and OBD-II

Most aftermarket ECUs can broadcast live values (rpm, MAP, lambda, temperatures) on the CAN bus for dashes and loggers.

A listener reads those frames without sending anything to the ECU, which is why it is the low-risk path.1118

A DBC file describes which CAN IDs carry which signals, with bit position, byte order and scaling. GAINS imports DBC files and also accepts ones you supply for your own setup.132

On factory ECUs, standard OBD-II parameter IDs defined in SAE J1979 give read-only access to common engine data through the diagnostic port.1219

Read-only paths into GAINS

Illustration in production.

Advisor mode: recommendations you apply yourself

Advisor mode runs the same tuning strategies GAINS uses on its own ECUs, with the same steady-state gates and statistics.

The output is a list of cells to change, by how much, and the evidence behind each change.39

Vendor table layouts are mapped to a neutral model through per-vendor adapters, built only from documented or user-exported formats. You open the vendor's software, make the change and save it, then log again.3

Because you apply the write, closed-loop learning on the fly is not available on third-party ECUs. That is a GAINS ECU feature, and the upgrade path from advisor mode.43

Why GAINS does not write to or reflash other makers' ECUs

Calibration file formats and write protocols for aftermarket ECUs are undocumented, and many units carry security information or vendor activation codes. Working around those would mean reverse engineering and defeating protections, which GAINS will not do.52

Direct writes would also bypass the ECU maker's own checks. GAINS's safety model depends on the target ECU re-validating every calibration, and a third-party ECU offers no such contract to an outside app.14

Tier 4 or 5 support will only appear for a family after a written agreement with its maker and bench verification, and the compatibility page will say so explicitly.53

Clean-room rules for CAN profiles

GAINS writes its CAN profiles in its own declarative format: message ID, byte order, bit position, scaling, units and a provenance record per signal. Each signal links to an evidence-register entry for the public document it came from.2

Competitor CAN templates, configuration files and firmware are not used as sources, even when a competitor's product supports many ECUs. Public supported-ECU lists are used only as a demand signal.2

Choosing an aftermarket ECU: what to check

I/O countInjectors, coils, DBW, cam, knock, spare inputs and outputsSourced · medium16
Injector driveSaturated vs peak-and-hold to match injector impedanceSourced · medium2015
Data openness
  • Documented CAN broadcast
  • Exportable logsCSV
Sourced · medium513
Harness path

Plug-in adapter, terminated engine harness, or flying-lead wire-in

Sourced · medium7

Start with the engine

Count injectors, coils, drive-by-wire throttles, cam phasers and knock sensors, then add spare inputs and outputs for what you will add later. Check the injector driver type your injectors need, such as peak-and-hold for low-impedance injectors.Medium1620

Then check the harness path for your car (plug-in adapter, terminated harness or wire-in), whether the CAN broadcast and log export formats are documented, and what the maker says about use on road vehicles.Medium517

Do it with GAINS (separate product module)

GAINS: advisor mode for third-party ECUs and a CAN/BLE adapter are on the roadmap; they are pre-release, and every vendor row on the compatibility page reads "Research, unverified" until a bench test passes.64

The PDM2 (in design) is meant to sit beside an existing ECU, read its documented broadcast in listen-only mode and add switched outputs, inputs, GNSS and logging, without ever writing to that ECU.10

Frequently asked

Can GAINS tune my Haltech, Link, MoTeC or ECUMaster ECU?

It can advise, not write. GAINS reads documented telemetry or your exported logs and recommends exact table changes with reasons; you apply them in the ECU maker's software. Direct writes would need an interface the maker has authorized, and none exists today. Brand names here identify compatibility targets only.35

Can a third-party app write to my ECU?

Only if the ECU maker provides and authorizes an interface for it. Our research found no aftermarket ECU maker that publishes a third-party calibration-write or flash interface; the maker's own app or PC software is the supported way to change a calibration. Be wary of any app that claims otherwise without naming that authorization.54

What is advisor mode?

Advisor mode runs GAINS's tuning strategies on data from an ECU GAINS did not build. It applies steady-state gates and statistics to your logs and outputs a list of cells to change, by how much, and the evidence for each. You make the change in the vendor's software and log again.3

Is reading CAN data from my ECU safe?

Listening is low risk because the listener sends nothing to the ECU, as long as the device is wired correctly and does not disturb bus termination. Problems usually come from wrong bitrate settings or an extra terminating resistor. Never add devices that transmit on an engine bus without knowing the ID plan.Medium1114

Why don't you just reverse engineer the calibration format?

Because it is the ECU maker's work, often protected by security information and licence terms, and because direct writes would bypass the ECU's own checks. GAINS builds profiles clean-room from published documents and will add write support for a family only with the maker's written agreement.25

Related

Sources

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

20 sources
  1. internal GAINS architecture decision record: ADR-0004: Layered real-time adaptation under a signed authority envelope
  2. internal GAINS architecture decision record: ADR-0006: Third-party ECU CAN coverage, clean-room declarative profiles
  3. internal GAINS architecture decision record: ADR-0008: Tuning Knowledge Engine (advisor mode on third-party ECUs)
  4. internal GAINS internal: Architecture Review #1 (docs/architecture/ARCHITECTURE_REVIEW.md), 2026-10-22, §8 third-party ECU snapshot
  5. internal GAINS internal: Third-party ECU integration evidence (docs/research/THIRD_PARTY_ECU_EVIDENCE.md), vendor-published sources retrieved 2026-10-22
  6. internal GAINS internal: Integration capability matrix (docs/research/INTEGRATION_CAPABILITY_MATRIX.csv)
  7. internal GAINS internal: Evidence register rows E-447, E-900..E-904 (harness catalog research)
  8. internal GAINS source code: @aitune/policy CapabilityTier definitions (0-5)
  9. internal GAINS internal: How GAINS tunes an engine (pillar guide)
  10. internal GAINS internal: PDM2 v0 design spec (hardware/mini-pdm/SPEC.md)
  11. ISO 11898-1:2024 Road vehicles, Controller area network (CAN), Part 1: Data link layer and physical coding sublayer · International Organization for Standardization · standard · retrieved 2026-10-27
  12. SAE J1979: E/E Diagnostic Test Modes · SAE International · standard · retrieved 2026-10-27
  13. CAN DBC File Explained: A Simple Intro · CSS Electronics · vendor-doc · retrieved 2026-10-27
  14. Controller Area Network physical layer requirements (SLLA270) · Texas Instruments · vendor-doc · retrieved 2026-10-27
  15. Injection Valve EV 14 data sheet · Bosch Motorsport · vendor-doc · retrieved 2026-10-25
  16. Automotive Handbook, 10th ed. (engine management systems) · Robert Bosch GmbH / Wiley, 2018 · book · retrieved 2026-10-27
  17. Tampering Policy: The EPA's Enforcement Policy on Vehicle and Engine Tampering and Aftermarket Defeat Devices (2020) · U.S. Environmental Protection Agency · standard · retrieved 2026-10-25
  18. CAN bus · Wikipedia · reference · retrieved 2026-10-27
  19. OBD-II PIDs · Wikipedia · reference · retrieved 2026-10-27
  20. Fuel injection · Wikipedia · reference · retrieved 2026-10-25