Early access · in active developmentFord EEC-V / Escort ZX2 / GXAG2 + siblings

Ford Escort ZX2
EEC-V PCM disassembly.

An actively-developed tool for the Ford EEC-V PCM in the Ford Escort ZX2 (1998-2003). Our focus is a complete (100%) disassembly of the GXAG2 strategy - the box codes we hold binaries for (CIL2, BAX3, NGP0). We also have working knowledge of the sibling strategies QBAA0 (MGS0, NLX2), QBAB0 (LXQ1), QBAC1 (HBD1) and GRAK6 (MTA5), and are still working their binaries toward full coverage. Upload a 256 KB dump and chat with an assistant grounded in real disassembly work.

Start analyzing How it works

/* target */

cal_id: GXAG2 (CIL2)

cpu: Intel 8065 (MCS-96 family)

reg_file: R00-RFF (256-byte)

banks: 0 / 1 / 8 / 9 = 256 KB (262,144 B)

live: 224 KB + 32 KB 0xFF pad

engine: 2.0L Zetec DOHC 16V, ~130 hp

/* what we've mapped (GXAG2) */

params: 4,270 (3,649 scalar / 486 fn / 135 table)

flags: 10 bit-fields / 7 checksum regions

fixed_pt: Q2 spark / Q7 fuel / Q15 gain

disasm: 57,988 lines 8065 asm

tool: SAD 4.14.3 flow-trace

fleet: 8 ROMs / 5 strategies

xref: byte-level, all 8 bins

/* decoded from your bin */

maf_xfer: 30-pt curve, 0.27-19.6 lb/min

lambda_tgt: RPM x Load, 0.85 WOT / 1.00 cruise

spark_adv: base + ECT/WOT/knock/MBT, 0.25°/cnt

inj_pw_scale: 1.20x (Q15)

vct_cam: exhaust, retard-from-park ~-14.9°

+ idle / fans / fuel-trim / limiters in scope

// compared to GXAG2 reference, byte-exact

// FREE: ask the AI what each does + which byte,

// then hand-edit your bin. you tune it yourself.

// paid makes it easier: compare, datalog, AI edits.

4,270

calibration params mapped

57,988

lines of 8065 disassembly

ROM images analyzed

strategies cross-referenced

Upload

Your PCM dump (256 KB, 262,144 bytes across four banks: 0, 1, 8, 9) is hashed and parsed in your browser. The calibration ID embedded in the image is read first, so the analysis is matched to your exact strategy before anything else.

Chat

We don't guess at your bytes. Our understanding comes from disassembling the PCM's Intel 8065 machine code and tracing how each calibration value is consumed by the running engine strategy. For recognized GXAG2-family tunes, the AI reads decoded engineering values straight from your file and compares them to the reference calibration, down to the individual byte.

Compare

Diff two binaries byte for byte. The AI surfaces exactly which regions changed and discusses the likely calibration intent. Deeper, parameter-aware comparison is rolling out as coverage grows.

Built on a living disassembly

This isn't a generic hex viewer. We reverse-engineer the ZX2 PCM at the byte level, every day, by reading the actual machine code and verifying what each calibration value does against the instructions that use it. Verified results flow into the app on a regular cadence, so the analysis keeps getting deeper.

In the interest of honesty: the chat AI currently exposes a curated, growing set of decoded parameters. Not every value in the 256 KB image is wired into the chat yet, and some capabilities are still being enabled. Coverage and features expand continuously as the disassembly advances, so it's worth checking back.

Upload your tune - help map every ZX2 calibration

The deepest analysis today is GXAG2-specific, but the goal is full coverage of every ZX2 tune. If you have a ZX2 PCM, dump it and upload your 256 KB (262,144-byte) binary with banks 0/1/8/9. Bins from strategies we have not fully mapped - and even more copies of GXAG2, QBAA0, QBAB0, QBAC1 or GRAK6 - directly expand the disassembly and make the AI smarter for everyone. Uploaded calibrations are collected and studied as part of our ongoing research.

Not sure how to read your PCM to a .bin? See what you'll need to get started.