This guide uses a 2019 US-market WRX STI and a separate 2008 STI training example to illustrate HP Tuners support, MAF-based logging and the limits of forum advice. The ordinary WRX, STI and different markets can use different engines and ECUs; identify the exact vehicle and calibration before making changes.
Vehicle, gearbox and HP Tuners support
Subaru's 2019 US brochure describes the WRX STI as a 2.5-litre turbocharged, intercooled horizontally opposed four-cylinder with dual active valve control and a six-speed manual. It separately describes the ordinary WRX's 2.0-litre direct-injection turbo engine. Specifications and equipment depend on market and year; gearbox type and engine family should be verified on the actual car. Subaru: 2019 WRX and WRX STI brochure; Subaru: 2018 US WRX and STI specifications.
HP Tuners' published Subaru vehicle table lists 2008–20 STI separately from 2008–14 WRX, and identifies MPVI2 or newer interface generations for those entries. The list is not evidence that every market, ECU, calibration or gearbox is supported. Confirm the installed ECU, model year and current software and device requirements with HP Tuners, particularly on an imported or swapped car. A 2019 STI listing should not be read as proof of support for a 2019 non-STI WRX. HP Tuners Subaru vehicle list. Some regions may redirect the manufacturer page to a regional homepage; contact the manufacturer if the list is not accessible.
2019 STI owner discussion
In a 2024 discussion, a 2019 STI owner described using HP Tuners with a MAF-based setup, a replacement intake, intercooler, adjustable fuel-pressure regulator, three-port boost solenoid and wideband. The owner reported using the three SI-DRIVE modes and their own calibration. These are self-reported modifications and observations, not validated maps, evidence of safe boost targets or a guarantee that any feature is available on another ECU.
The same owner reported an ECU failure when applying custom features and said the supplier subsequently addressed their case. The report does not independently establish the cause, which versions were affected or a current product defect. Before applying any custom operating-system feature, confirm support and current instructions for the exact ECU and software version, maintain the manufacturer's specified stable supply, and have a suitable recovery plan. Do not flash someone else's tune or assume an unsupported controller can be recovered by repeated writes.
Airflow and mixture: a separate STI teaching example
High Performance Academy's EcuFlash/RomRaider STI worked example discusses how a local fuel-trim or mixture error may vary with rpm and manifold pressure and describes fuel-pressure pulsation as a possible contributor in that example. It also discusses learned trims potentially carrying into open-loop operation. Treat these as explanations for that documented ECU and test, not a diagnosis for every EJ engine. Its map labels, values, reset procedure and channels belong to EcuFlash/RomRaider and must not be presented as HP Tuners definitions or copied into a VCM Editor file.
For an actual vehicle, establish injector and MAF hardware, fuel type and fuel-pressure condition first. At stable temperature and load, compare MAF signal, engine speed, manifold pressure and short- and long-term fuel corrections where available. Check operating state and whether learned correction is applied before interpreting a trim. During higher-load operation, compare commanded lambda to a correctly configured independent wideband on the same timeline; closed-loop trim alone cannot establish mixture in every condition. Avoid correcting a pressure-related or mechanical fault by blindly reshaping the MAF curve.
Wideband and boost logging
HP Tuners describes Pro Link and Pro Link+ external analogue inputs for appropriate interface generations and VCM Scanner; the separate cable and feature requirements vary with device. Configure the correct input channel and wideband controller transfer function, check sensor ground and scaling, and verify the reading before using it. A signal appearing in Scanner is not proof the ECU uses it for closed-loop control. HP Tuners: Pro Feature Set and external inputs; HP Tuners: testing analogue inputs.
For boost investigation, log requested and measured manifold pressure, barometric pressure, rpm, throttle, intake temperature and wastegate-solenoid command if the actual calibration exposes meaningful channels. Determine whether pressure is absolute or gauge; a duty command does not show actual wastegate position. Record the SI-DRIVE mode, gear, fuel and operating conditions for each comparison. Investigate hoses, actuator, solenoid, sensors and fuel supply as well as calibration, and retain the vehicle's protective functions. A modified 2019 owner's settings are not a starting calibration for another car.
Read and log are different capabilities
In an HP Academy forum discussion, a participant described a 2007/2008 WRX that they could log but could not read or write with their HP Tuners setup. The precise vehicle and cause were not established. A successful diagnostic connection does not prove calibration support: check ECU identity, market, device, software and licensing with HP Tuners before purchase or flashing. This old report does not establish a current general limitation.
Record diagnostic trouble codes before a read; HP Tuners warns that the read can clear them. Save the car's own initial supported read and baseline log, then make and validate changes in a controlled sequence. HP Tuners: getting started with VCM Editor. See also VCM Scanner and MPVI4.