Remote ECU Calibration

Remote calibration is a straightforward concept: you run the car, log data, send it to me. I review the data, make changes to the calibration file, and send the file back. You flash it and run again. That cycle repeats until the calibration is where it needs to be.

It works because Syvecs, MoTeC, and Life Racing are built for it. High sample rate logging, precise sensor inputs, and direct file transfer mean I can do thorough work without being in the same location as the car or the dyno.

What I need from you is good data and honest communication about what the car is doing. What you get back is a calibration file built from that data, with documentation on what changed and why. I write about the underlying theory on the blog.

What platforms does Optimum Engine Mapping support?

• ▸Syvecs — all current standalone and plug-in ECUs
• ▸MoTeC — full M1 platform
• ▸Life Racing — F88 and F90 series
• ▸EcuTek — GT-R R35 only

Authorized dealer for Syvecs, MoTeC, and Life Racing.

For MoTeC display configuration, see the dedicated service page.

For CAN bus integration alongside calibration work, see the dedicated page.

For platform documentation, the knowledge base covers Syvecs and Life Racing references.

What does a remote calibration project involve?

Projects vary significantly depending on platform, application, and where the car is in the build process. Some clients are buying an ECU from me and starting from a base map with a car that isn't running yet. Others have a car that's been calibrated before and need it revisited after a hardware change. Others have an existing calibration that something isn't right with and need a second set of eyes.

The process in all cases is iterative — file revision, you run the car and capture data, I review, we go again. I won't push through calibration work if something in the data indicates a mechanical or electrical issue that needs to be addressed first.

What determines the cost of a calibration project?

Projects are quoted individually. What affects the scope and the quote:

• ▸Platform and ECU model
• ▸Engine configuration and number of fuel types used
• ▸Whether this is a first calibration from a base map or a revision to existing work
• ▸Feature scope — traction control, launch control, flex fuel, GDI integration, sequential gearbox control, flatfoot shifting, rev-match, torque control
• ▸Troubleshooting support on issues that fall outside the calibration scope

Contact me through the form with your platform, engine configuration, and what you're trying to accomplish.