Supported Map File Formats
ECU map file types accepted by DigiTune GTS
| Extension | ECU | Tables supported |
|---|---|---|
.mecal |
Motorsport Electronics (ME221, ME442, ME360) | VE, Ignition, IAT Trim (2D/3D), CLT Trim (2D/3D), Knock (2D/3D), Boost duty & target (2×), Injector dead time, Idle duty, Flex VE |
.msq |
MegaSquirt 3, MS3Pro, Speeduino | VE (main 16×16 + 12×12 variants), Ignition, IAT Trim, CLT Trim, Knock thresholds, Boost duty & target, Injector dead time, Idle duty |
.nexmap |
Haltech Elite series | VE, Ignition, IAT Trim (3D), CLT Trim (3D), Knock (3D), Boost duty & target, Idle duty |
.pcl5 / .pclx / .pclr |
Link G4+, G4X | VE, Ignition, IAT Trim, CLT Trim, Warmup enrichment, Injector dwell |
.emu / .emub |
ECUMaster EMU Classic & EMU Black | VE, Ignition, IAT Trim, CLT Trim, Injector dead time |
.emupro |
ECUMaster EMU PRO | VE, Ignition, Warmup (CLT) correction, Knock thresholds (3D), Boost duty & target, Injector dead time (voltage × pressure) |
Notes by ECU type
Motorsport Electronics (ME)
DigiTune GTS automatically detects old (firmware <3.0) and new (firmware ≥3.0) ME file formats, which use different internal table names. Both variants are fully supported. If a table name is not found in the primary location, the parser falls back to alternative names for that firmware version.
If flex fuel is enabled in the map, DigiTune GTS exposes both the Base VE table and the Flex VE table. The active table is selected automatically based on the average ethanol content in the loaded log files.
MegaSquirt / Speeduino
The main VE table is the standard 16×16 grid. If the map contains additional 12×12 sub-tables (veTable1dozen, veTable2dozen), these are updated automatically on save to maintain consistency with the main table.
Haltech
Haltech .nexmap files are WinZip AES-256 encrypted archives. DigiTune GTS handles
decryption transparently — no password is required from you. The inner XML is parsed for all
map data including 3D trim and knock tables.
Haltech ECUs use absolute kPa as the load axis by default. Temperature scaling in Haltech logs applies CAN protocol corrections automatically.
Link ECU
Link .pcl5 / .pclx / .pclr files are XXTEA-encrypted XML.
Decryption and parsing are handled transparently.
ECUMaster
ECUMaster .emu and .emub files are XML-based. VE values are stored as
raw integers (÷10 = %) and ignition values are stored in degrees directly.
CLT and IAT trim values are stored as ratios (÷100). Injector dead time is stored as ÷10 ms.
All scaling is applied automatically on load and reversed on save.
EMU PRO projects (.emupro) use a separate, newer format and are supported
independently of Classic/Black. Warmup correction is shown as a ratio (the ECU stores added
fuel %), boost targets are converted from gauge to absolute kPa to match logged MAP, and the
injector dead time table keeps its battery-voltage × differential-fuel-pressure axes. When the
boost duty table has a third dimension (duty per target pressure), the highest-target surface
is shown for editing and the other surfaces are preserved on save. Saved projects re-open in
the EMU PRO client.
What DigiTune GTS does not change
When you save a map file, DigiTune GTS only updates the specific table cells you have edited. All other ECU parameters — fuelling strategies, sensor calibrations, rev limits, protection settings — are preserved exactly as they were in the original file.