What you'll need to get started
This app is free to read, understand, and modify your own raw PCM binary. The single biggest thing you bring is the want to learn. Below is the mindset, the workflow, and the hardware to go from "I have a ZX2" to reading and editing your own tune with confidence.
What you bring to the table
Hardware is the easy part. The thing that actually matters is the curiosity to understand how your engine is controlled and the patience to learn it one parameter at a time. If you want to know why a value does what it does, you already have the most important tool.
- ▸ A genuine want to learn and understand (this is the big one).
- ▸ Patience to read, ask, and verify before you change a byte.
- ▸ A Windows PC to run the reading/flashing tools.
- ▸ Your raw .bin file (and hey, new bins help everyone 😉)
It's free to understand and modify your bin
Ask the AI what each calibration value does, which byte it lives at, and how the running engine uses it, then hand-edit your own binary. That core workflow, learn it and tune it yourself, costs nothing.
The paid tiers do not unlock the knowledge, they just make it easier: decoded parameter reports, two-tune comparison, and AI datalog analysis. Useful accelerators, never a gate on learning.
Reading your PCM to a full bin
To work on your tune you first need to pull the full 256 KB image (262,144 bytes, banks 0 / 1 / 8 / 9) off your PCM. There are two common paths, and the one you pick also decides how you'll run a modified tune.
Moates QuarterHorse
Plugs into the PCM's J3 port and reads your bin. It also lets you live-tune: change the calibration and feel the result while the engine runs. If you want to develop a tune iteratively, this is the path.
Moates BURN2 + FA/FE adapter
With the PCM on the bench, the BURN2 (using the FA/FE adapter) reads the full bin. The same BURN2 setup is also how you program a Moates F3v3 emulator chip for your PCM, which is the route to run a finished custom tune if you are not live-tuning with a QuarterHorse.
Whichever you use, the goal is the same: a complete 256 KB dump. Partial reads will not analyze correctly.
Datalogging your engine
A datalog records what your engine is actually doing on the road, such as RPM, load, fuel trims, knock, AFR, and spark, so you can see how your tune behaves instead of guessing. The easiest option today is an SCT X4.
Good news for logging: you do not need to "marry" the X4 to your PCM to datalog. It can even be married to a different PCM or vehicle and still log yours, as long as you are only using it to record data.
Coming soon
This page is the start. We are building detailed written guides and step-by-step videos covering the hands-on parts:
- ▸ Opening the PCM case safely
- ▸ Cleaning the J3 port for a solid connection
- ▸ Attaching the BURN2/FA/FE or QuarterHorse
- ▸ Reassembly, plus deeper per-parameter explainers
Ready to dig in?
Create your account, upload your 256 KB bin, and start asking the AI what every value does. Bring the curiosity, we'll bring the disassembly.
Support the project
The core, understanding and hand-editing your own bin, is free, and Tier 3 (AI-assisted tune modification) isn't ready yet. If this is useful to you, a contribution of any amount helps fund the AI behind the disassembly research and this app, plus the time behind it. Completely optional.
DonateFree to learn, paid to go faster
Understanding and hand-editing your own bin is free. The paid tiers add tooling that makes it easier: decoded reports, two-tune comparison, datalog analysis, and report exports.
Upload and chat about any tune we know, or your own.
Compare two tunes and get deeper analysis of your own.
Upload datalogs for AI knock, fuel-trim + AFR analysis of your tune.
AI-assisted tune modifications, human-reviewed and returned to you.