Base maps & remote calibration

Start a specialist engine on a map built around its hardware.

Standalone management gives a project freedom the original ECU may not offer — and makes accurate sensor, trigger, fuel and ignition information essential from the first file.

No production assumptions

With a standalone ECU, every input has to be defined.

Trigger pattern, injector data, fuel pressure, ignition configuration, sensors, boost control and engine geometry all affect whether a base map is safe enough for commissioning.

We build the starting calibration from the information supplied and can support further remote live tuning on compatible platforms and projects. Final dyno or load validation remains an essential professional step.

01

Define the engine

Capacity, compression, camshafts, turbo or supercharger, fuel, target boost and mechanical limits.

02

Define every sensor

Crank and cam triggers, MAP, TPS, temperatures, pressure sensors, lambda and calibration data.

03

Define fuel & ignition

Injector flow and dead time, fuel pressure, coils, firing order and configured outputs.

04

Build the base map

Configure the project for a controlled first start and initial checks — never immediate full-load operation.

05

Log the result

Record the required channels under controlled conditions and return complete logs with clear observations.

06

Refine & validate

Iterate where remote support is agreed, then complete professional dyno or load validation before hard use.

Supported by assessment

Platforms and projects are confirmed before work begins.

Experience may include systems such as MoTeC, OMEX, DTA, MegaSquirt and Link, but support depends on the exact ECU, firmware, software access and project requirements.

MoTeCOMEXDTAMegaSquirtLink ECUOther — ask first

Safety gate

A base map is a commissioning tool, not a finished race calibration.

Before first start

  • Verify timing mechanically with a timing light
  • Confirm fuel and oil pressure independently
  • Calibrate throttle and all temperature/pressure sensors
  • Check trigger synchronisation without fuel where appropriate
  • Use wideband lambda and knock-monitoring procedures
  • Stop immediately if data is inconsistent

Scope the project first

Send the complete build specification before sending the ECU file.

Contact the technical team with the platform, firmware, engine and sensor package.

Discuss compatibility
Submit file