EcuFlash
Used for supported ECU reading and reflashing, with calibration editing available through matching definitions. The exact ECU and interface determine which operations are supported.
Tactrix / EcuFlash source ↗SUBARU / ECUFLASH & ROMRAIDER
Keep the factory ECU. Build the calibration around your car. I offer custom tuning for supported Subaru setups using EcuFlash and RomRaider, with the interface, definitions and logging plan confirmed before work starts.
Already have a cable or a tune file? Send the details first. You do not need to buy equipment to ask a question.
THREE DIFFERENT JOBS
“Open-source tuning” describes a commonly used workflow, not one universal product. RomRaider is open-source software. EcuFlash and the hardware have their own distribution and licensing terms. Installing the software does not establish compatibility with your ECU.
Used for supported ECU reading and reflashing, with calibration editing available through matching definitions. The exact ECU and interface determine which operations are supported.
Tactrix / EcuFlash source ↗A free, open-source editor and datalogger. ECU definitions describe calibration tables; logger definitions describe the channels that can be recorded. Those are separate pieces of the setup.
Official RomRaider project ↗The bridge between the computer and ECU. An OpenPort is an interface, not a replacement ECU. A cable that connects to the diagnostic port is not automatically suitable for reflashing.
Check your equipment →Workflow illustration, not a flashing procedure. I supply the instructions appropriate to your confirmed setup.
KNOW WHAT YOU ARE CONNECTING

A hardware example used in supported EcuFlash workflows. Confirm the exact interface, driver and ECU before purchasing.

Early Subaru applications can require an additional reflash adapter. Color alone is not a fitment check; year, market and ECU matter.
Hardware photos: 43racing / Tactrix European importer. Shown for identification, not as a statement of stock availability or a recommendation to buy before review.
THE ROM MATTERS
Start with the actual ECU, not just the badge on the trunk. This route can suit supported older Subaru factory ECUs, but model year alone cannot establish reading, editing, logging and flashing support. Engine swaps, replacement ECUs and an unknown previous tune need additional review.
Being able to see live data does not prove that the ROM can be safely edited or reflashed. Keep the untouched original read and its identifying information. Never substitute a file from a similar-looking car.
USEFUL DATA / CLEAR FEEDBACK
A log lets me compare the engine’s operating conditions with its response. I choose the channel list and test conditions for your ECU and the current revision. More selected channels are not automatically better: the useful sampling rate and available parameters depend on the setup.
Examples include engine speed, throttle position, calculated load or airflow, manifold pressure, intake-air temperature and coolant temperature.
Depending on support, requested channels may include fuel corrections, injector activity, ignition timing, knock-related corrections and external wideband AFR or lambda.
These are channel categories, not a universal list to select blindly. ECU names and units vary. A dashboard photo or a wideband gauge video does not replace the requested time-based data.
Keep the exported file intact. Include the revision name, fuel, conditions and what you noticed. If the wideband records separately, follow the agreed method for aligning the data. Stop testing when the car behaves abnormally and tell me what happened.
WORK DIRECTLY WITH KEITH
Revision needs depend on the agreed service and the car’s condition. Mechanical faults, inconsistent fuel, unusable logs or changes in hardware can require additional work. We discuss those changes rather than treating repeated flashes as progress.
Prepare your car before a tuning session →No. Software availability and professional calibration are different things. My service covers reviewing your combination, developing the calibration and working through the agreed logging and revision process. Equipment and any applicable licensing are separate unless stated in your quote.
Send the tuning history and ECU information first. An existing file may have unknown changes or protections. I need to establish what is in the car and what is supported before promising a read or revision.
The required tools depend on the ECU and the work. They commonly handle complementary jobs, but I will confirm the actual workflow instead of asking you to install every available program.
For the EJ remote fueling work described here, an external wideband with an approved logging method is required. We need the right measurement at the operating conditions being evaluated, not just a dashboard reading.
Follow the agreed logging plan in appropriate, controlled conditions. Do not operate a laptop while driving. Where the required testing cannot be performed appropriately, arrange a suitable dyno session.
I also offer Atlas tuning for supported FA20 and FA24 WRX setups. Current Atlas software is developed by North American Motorsports Research and is no longer open source. It has its own compatibility, adapter and licensing requirements.
Atlas cannot use an Accessport as its flashing or logging interface, and it does not edit Accessport tune files. Plan any platform change with me first; do not return a modified car to stock calibration without checking that it is appropriate for its hardware.
STI/EJ support is not currently available as a service here. For those cars, ask about the appropriate COBB, EcuFlash/RomRaider or standalone route.
Platform details: NAMR’s Atlas FAQ and current vehicle support matrix.
Tell me about your car, the equipment already installed and what you want to improve. I can review the setup before you order a tune or buy more parts.