Edit tunes, log the car and read datalogs, plus fuel, injector and boost calculators. Your logs and ROMs stay on your device.
Open the toolkit in its own browser tab first (not inside another page), then follow the steps. Once installed it opens in its own window with an icon on your desktop or home screen, and your settings stay saved.
Paste any 2D or 3D table from HP Tuners, EcuFlash, a spreadsheet or anywhere else. Smooth it, interpolate it, edit cells and do math on a selection, then copy it straight back into your software.
Open a .bin, then point the toolkit at a folder of definitions: EcuFlash XML (Subaru, Mitsubishi and others) or TunerPro .xdf (BMW and others). XML definitions a ROM uses are remembered in this browser, so next time that ROM opens on its own. Subaru checksums are corrected when you save; other makes are not, so correct those in your flashing tool before you flash.
You can also click the grid and press Ctrl+V. If the top-left cell is blank, the first row and first column are read as the axis; change that any time with the Axis menu in the toolbar.
Drag to rotate · scroll or pinch to zoom · double-click to reset
Press ? or Hotkeys for keyboard shortcuts.
Checked = enabled. The search on the left narrows this list, and the buttons only change what's shown. Changed switches get a dot.
Pick a sensor, build scaling from your own voltage and pressure points, then true it up against a key-on engine-off reading. Every result comes out as multiplier and offset in psi and bar.
Enter two or more points from a datasheet or a bench test with a gauge. Two points give an exact line. Three or more get a best-fit line with the error shown per point.
| Volts | Pressure | Fit error |
|---|
Key on, engine off, the manifold sits at barometric pressure. Log the absolute MAP parameter (a "relative" parameter subtracts the baro sensor and will read near 0 no matter what). This keeps the multiplier and shifts the offset so the reading lands on true baro.
Working scaling in solid, the selected preset dashed for comparison. The shaded band is the usual 0.5–4.5 V working range.
Highlighted row is closest to sea-level atmosphere. Boost is gauge pressure against 14.696 psia. Faded rows fall outside 0.5–4.5 V.
| Volts | psia | Boost psi | bar abs | Boost bar | kPa abs |
|---|
Sign conventions differ between tools. Everything here is absolute with the offset added. If your editor shows a relative offset, subtract 14.696 psi (1.01325 bar). If it subtracts the offset, flip its sign.
Fill-up mix for a target ethanol content, plus flex sensor voltage to ethanol percent.
Gallons of E85 and pump gas to fill the tank to your target blend.
Ethanol content from sensor voltage, 0–100% linear.
Voltage for each ethanol percentage, for building or checking the ECU sensor scaling table. Highlighted row is your target blend.
| Ethanol | 0.5–4.5 V | 0–5 V |
|---|
Convert lambda to air-fuel ratio for any fuel, read a gas-scale wideband on another fuel, and work out the fuel correction needed to hit a target.
Straight lines: AFR = λ × stoich. The vertical line is the slider's lambda; the highlighted row is the closest step.
Ethanol blends are worked out by mass from the ethanol % by volume (gasoline 14.7:1 at 0.74 g/cc, ethanol 9.0:1 at 0.789 g/cc), so E85 comes out near 9.8:1. Many widebands report gas-scale AFR (14.7 × λ) whatever the fuel; the gas-scale column converts those readings.
Fuel pressure from sensor voltage for common 100 psi and 150 psi linear sensors, on both 0.5–4.5 V and 0–5 V scales.
Voltage for each pressure on every scale, for building or checking the ECU sensor table. Highlighted row is closest to the 0.5–4.5 V · 0–100 psi reading.
| Pressure | 0.5–4.5 V · 100 | 0–5 V · 100 | 0.5–4.5 V · 150 | 0–5 V · 150 |
|---|
Manufacturer injector data. Subaru · EcuFlash converts ID, FIC and DeatschWerks data to EcuFlash units for the factory Subaru ECU. All platforms has every ECU and make the three manufacturers publish, in each platform's own format. Every table copies tab-separated.
EcuFlash cc/min = 2,707,090 ÷ COBB injector scale (µs).
Injector pulse width limit (min), no latency included.
Pasting into EcuFlash: select the table's cells in the same row/column order and paste. Check that your definition shows the same units (cc/min, ms, %) before pasting, then verify with a log. Cells interpolated or extrapolated onto your own axis are marked.
No values or tables found on this sheet. Switch to Original spreadsheet to see it as published.
Laid out automatically from the manufacturer's spreadsheet. If a table looks wrong, check it against Original spreadsheet.
Values are exactly as the manufacturer publishes them for each platform, in that platform's own units. Copies are tab-separated, so they paste cell for cell into most tuning software and spreadsheets.
Read and clear check-engine codes, check emissions readiness, and watch or log live data on any OBD-II car (1996+ US) with an OBDX Pro, an ELM327-type adapter or a Tactrix OpenPort 2.0. Works in Chrome or Edge on a computer, or Chrome on Android.
The Tactrix and other J2534 cables need the small R.Spec bridge app running on this Windows PC (it talks to the cable through its normal driver and adds the older K-line cars). Download the bridge, unzip it, close EcuFlash / RomRaider, double-click Start-RSpec-Bridge.bat once (this sets up the button below), then press Open bridge and Connect. Its window stays open while you scan.
Connect, then press Read all.
—
—
The dashboard is yours: drag a PID from the list onto it (or press its +) and it arrives as a medium square. Drag a gauge anywhere on the dashboard, pull its bottom-right corner to resize it, or drag it back onto the list to remove it; Tidy up lines them all up again. Right-click a gauge or press its ⋮ to make it a gauge, a bar or just the number, small, medium or large, set its colour, set warning limits, change its range or remove it; the gauge turns red outside the limits. Only gauges on the dashboard are polled, so fewer gauges means a faster update rate. The list only shows the PIDs the connected car reports. Hover a PID in the list for its definition (source, request, bytes, scaling, units and range). Misfire counts per cylinder come from mode 06 on CAN cars. Manufacturer PIDs (knock, cam and VVT timing, learned values and more, from the OBDb community database, CC BY-SA 4.0) are found from the VIN on connect: each one the car answers is added, and the result is saved per VIN. On Subarus with a CAN ECU (2008 and newer), SSM is checked too: the ECU ID picks the RAM addresses for FBKC, FLKC, IAM, AVCS and the other RomRaider values; load your RomRaider logger definition to add any parameter it lists for that ECU ID, including MerpMod. Record logs every gauge plus every PID the car reports; when you stop recording the log opens in R-Log (untick the box to stay here), or use Save CSV.
Put each channel name in [brackets] and join them with + - * / ( ). abs(), min() and max() also work. The result is worked out from the latest value of each channel on every update, and it is saved in this browser. It shows a dash until every channel it uses is being read on the current link (CAN or K line). Save adds it to the list, where you can add it to gauges or graphs.
Formula: x is the value (bytes combined, or the float); A, B, C, D are the single bytes. Example: x*0.25-32 or (A*256+B)/1024.
Codes and readiness use the standard OBD-II requests every 1996+ car answers, so they work across makes. Descriptions are the generic SAE meanings; P1xxx and other manufacturer codes link to a search for your make. Clearing codes also resets every readiness monitor, so the car will need a drive cycle before an emissions test. ABS, airbag, transmission and body modules are not read here.
How much power an injector supports at a given duty cycle, or what size you need for a power goal, with duty cycle and pulse width across the rev range.
Estimates from the usual BSFC method: fuel needed = horsepower × BSFC. BSFC starts at 0.60 turbo, 0.55 supercharged, 0.50 naturally aspirated on gasoline and is raised for ethanol (more fuel per horsepower, partly offset by ethanol's efficiency), so E85 turbo lands near 0.84. Fuel pump flow is the total the engine burns at peak, in litres per hour; size the pump with about 20% headroom at your full fuel pressure. The RPM graph uses a typical power curve for the induction type that peaks at your peak power RPM; pulse width is effective (no latency). Real numbers depend on the engine, tune and target AFR, so confirm with a log.
Airflow = displacement × RPM ÷ 2 × VE × charge-air density (boost, altitude and charge temperature). Power ≈ 10 hp per lb/min of air on pump gas, a little more on fuels that allow more timing (E85 about 6% more). Wheel sizes come from the corrected airflow using typical modern wheel flow per inducer area, with the trim chosen for the pressure ratio; turbine wheel and A/R follow the compressor size, exhaust flow and your priority. The curve assumes boost builds to target by the spool RPM, holds until the compressor nears its flow limit, and that VE tapers past peak power. The intake pipe and exhaust diameter can also limit flow and add backpressure, and the cam choice moves where the engine makes its power. These are planning numbers, not a substitute for a compressor map, so check the turbo you pick on its map.
Set the airflow you need from your displacement, power goal and boost. The result is a generic compressor inducer and turbine exducer size, plus a few example turbos. Nothing here is tied to a particular vehicle.
Example turbos from common catalogs that come closest to the suggested sizes. These are generic, not matched to any vehicle. Press Use to pick it and move on to setting boost. Specs are typical catalog numbers; check the exact part you buy.
This map is a typical modern compressor shape scaled to the wheel above: choke flow from the inducer, top pressure ratio from the exducer. The yellow line is your engine at the boost you set, with each 1000 rpm marked. Real maps differ by brand and wheel design, so confirm on the maker's map before you buy.
Open a datalog (RomRaider, EvoScan, EcuTek, Cobb Access Tuner Pro, Haltech NSP CSV or Link .llgx) and chart it. Everything happens in this page — nothing is uploaded anywhere.
The selected preset (graph count, channels, colors, smoothing, scales) is applied to every log you open. Press Save to keep changes in it.