Custom dyno tuning unlocks the true potential of a Subaru BRZ's FA20 engine, transforming its response and power delivery. However, when the tune isn't dialed in perfectly, owners often face frustrating drivability issues ranging from poor throttle response to engine knocking. This guide dives deep into the most common problems encountered after a custom dyno tune and provides actionable, production-ready solutions. We'll cover everything from fuel mapping and ignition timing to data logging and sensor diagnostics, helping you troubleshoot like a professional. Whether you're using an EcuTek, OpenFlash, or Cobb Accessport tuning platform, understanding these pitfalls is the first step toward a reliable, high-performance BRZ.

Understanding Custom Dyno Tunes

A custom dyno tune involves rewriting the engine control unit (ECU) parameters—fuel maps, ignition timing, camshaft timing (if VVT), and throttle response—while the car is strapped to a dynamometer. Unlike off-the-shelf (OTS) maps, a custom tune accounts for your specific modifications, fuel quality, and driving conditions. For the Subaru BRZ, platforms like EcuTek and OpenFlash are popular. A competent tuner will monitor knock correction, air-fuel ratio (AFR), intake air temperature (IAT), and engine load in real time to create safe yet aggressive calibrations. Mistakes at this stage—such as overly aggressive timing or poorly scaled MAF calibrations—lead directly to the issues discussed below.

Common Problems After a Custom Dyno Tune

Below we expand on the five most frequently reported issues, adding deeper diagnostic steps and practical fixes that go beyond surface-level adjustments.

Poor Throttle Response

Post-tune throttle response issues often manifest as a delay between pressing the pedal and engine response, or a sudden surge of power. This can be caused by incorrect throttle mapping in the ECU, overly aggressive tip-in enrichment, or a misconfigured drive-by-wire (DBW) system. In Subaru BRZs, the stock DBW has built-in dampening for smoothness; some tunes remove this too aggressively, creating jerkiness.

Solutions
  • Revisit the throttle pedal mapping: Use tuning software to adjust the percentage request versus actual throttle plate opening. Set a linear curve for predictable response.
  • Check tip-in enrichment tables: Excess fuel on initial throttle opening can cause hesitation. Reduce the enrichment delta for smoother transitions.
  • Inspect for vacuum leaks: Even a small unmetered air leak (e.g., at the intake manifold gasket or PCV line) can confuse the ECU’s airflow calculations and degrade throttle response. A smoke test is recommended.
  • Verify MAF sensor scaling: If the MAF transfer function is miscalibrated after intake modifications, the ECU will misread airflow, leading to delayed or incorrect fuel delivery. Re-scale the MAF curve using logged g/s at known RPM/load points.

Engine Knocking or Pinging

Knocking (detonation) is the most serious issue. It occurs when the air-fuel mixture ignites prematurely due to excessive cylinder pressure or temperature. In FA20 engines, knock often happens at high load, low RPM (lugging) or under part-throttle acceleration. The ECU may pull timing via knock control, but if the base tune is too aggressive, audible pinging persists.

Solutions
  • Retard ignition timing in the affected load cells: Use data logs to identify the knock events; pull 2-3 degrees in those specific cells and re-run.
  • Ensure proper fuel octane: A tune written for 93 octane must not be run on 91. If you have to use lower octane, consider a flex fuel conversion with ethanol to raise effective octane.
  • Check the air-fuel ratio under boost (if turbocharged): Forced induction BRZs require richer mixtures (11.5:1 - 12.0:1) under heavy load to suppress knock. N/A FA20s can run leaner (12.8:1 - 13.2:1) in high load areas.
  • Inspect knock sensor operation: A faulty knock sensor can report false knock, causing the ECU to pull timing unnecessarily. Test sensor resistance and verify OBD-II knock counts in the tuning software.
  • Evaluate cooling system efficiency: Higher intake air temperatures (IAT) promote knock. Ensure the intercooler (if turbo) is adequate and consider a larger radiator for track use.

Increased Fuel Consumption

If your BRZ starts drinking fuel after a dyno tune, the issue is usually an overly rich mixture in the closed-loop or cruise areas. The tuner may have set a target AFR that is too rich (e.g., 12.5:1) for light load, causing the ECU to add fuel unnecessarily. Alternatively, the wideband O2 sensor calibration could be off, leading the ECU to think the mixture is lean when it's actually rich.

Solutions
  • Review fuel maps for cruise load cells: Target AFR for light cruise should be around 14.2:1 to 14.7:1 (stoichiometric for gasoline). If your tune targets 13.0:1 at light throttle, fuel trims will spike rich.
  • Perform wideband O2 sensor check: Log the front oxygen sensor voltage while driving at steady throttle. A healthy sensor should cycle between 0.1V and 0.9V in closed loop. If it's stuck at a high voltage (>0.8V), the sensor is likely faulty or the tune is commanding too much fuel.
  • Inspect fuel trims: Long term fuel trims (LTFT) beyond ±10% indicate a mechanical issue or scaling error. High positive trims (>+15%) suggest an unmetered air leak or MAF miscalibration; high negative trims (<-15%) suggest excess fuel pressure or a clogged air filter.
  • Check injector scaling and dead times: Aftermarket injectors require accurate scaling. If the tuner used incorrect dead times, the ECU will add too much fuel at low pulse widths, worsening fuel economy.

Check Engine Light Activation

Common DTCs after a custom tune include P0171 (system too lean), P0300 (random misfire), P0420 (catalyst efficiency), and P0606 (ECU processor fault). Many of these stem from tuning oversights like disabled oxygen sensor heaters, or from post-ignition hardware changes (e.g., a high-flow cat or catless header).

Solutions
  • Read trouble codes with an OBD-II scanner: Note the freeze frame data. For example, if P0171 occurs at idle, you likely have a vacuum leak. If it occurs at high RPM, check MAF calibration or fuel pressure.
  • Correct tuning errors: If the code is P0606, it often means the tuner corrupted the calibration file. Reflash with a corrected ROM from a reputable source.
  • Disable unneeded emissions monitors: On track-only cars, some tuners disable the rear O2 sensor to prevent P0420 from a catless exhaust. Ensure this is done properly in software.
  • Inspect wiring and sensors: A physically damaged oxygen sensor wire from engine movement can cause intermittent signals. Check the harness near the transmission bellhousing and exhaust manifold.

Overheating Issues

Aggressive dyno tunes, especially those with advanced ignition timing, generate more heat. Combined with a stock cooling system, the engine can quickly exceed safe coolant temperatures (above 215°F). Overheating also increases knock tendency and can warp cylinder heads on FA20 engines.

Solutions
  • Check coolant level and system integrity: Purge all air from the cooling system. Ensure the radiator cap holds pressure (check for 1.3 bar rating).
  • Review tuning parameters that affect engine temp: High idle speeds, retarded timing at low loads, and overly lean mixtures all elevate temperatures. Adjust idle speed to 850-900 RPM and ensure timing at cruise is not excessively retarded.
  • Upgrade the cooling system: For track-driven BRZs, install a larger aluminum radiator (e.g., Koyo or Mishimoto), a high-flow thermostat (160°F-170°F), and an oil cooler. Verify that the electric fans are activating at the correct temperature thresholds (typically 195°F - 200°F via ECU fan control).
  • Monitor IAT and oil temps: With a proper data logger, check that IAT stays within 20°F of ambient under cruise and not more than 50°F higher under boost. High IAT can exacerbate knock and overheating.

Additional Troubleshooting Areas

Idling Issues (Rough Idle, Stalling, Hesitation)

A rough or unstable idle after a dyno tune is common when the idle speed control and fuel trim cells for idle are not properly calibrated. If you’ve added aggressive camshafts (e.g., stage 2 or 3) or a large intake, the MAF transfer function at low flow rates may be inaccurate.

Solutions
  • Re-scale the MAF curve at the idle point (typically 1-4 g/s on FA20). Log the AFR at idle and adjust the scalar until the short term fuel trims stay within -5% to +5%.
  • Check for vacuum leaks: A leak at the throttle body gasket or intake manifold o-rings will cause a lean idle, making the ECU add fuel and oscillate. Use a propane torch (unlit) to search for changes in idle speed.
  • Adjust idle target RPM and idle ignition timing in the ECU. For FA20, aim for 800-850 RPM idle with idle timing around 10°-12° BTDC. If you need a higher idle (e.g., 1000 RPM for a race cam), adjust the base idle air control (IAC) steps.

Data Logging and Analysis

Effective troubleshooting requires logging the correct parameters. Relying on the dyno sheet alone is insufficient for road-driven cars. You need to capture data under real driving conditions: part-throttle cruise, full-throttle pulls, deceleration, and idle. Essential channels for FA20 tuning include:

  • Engine RPM – for load referencing.
  • Manifold Absolute Pressure (MAP) or Mass Air Flow (MAF) g/s – to determine actual engine load.
  • Air Fuel Ratio (AFR) – from the wideband O2 sensor (both factory and aftermarket).
  • Ignition Timing and Knock Retard (KR) – knock retard values above 2° indicate pre-ignition events that need addressing.
  • Long Term Fuel Trim (LTFT) and Short Term Fuel Trim (STFT) – for mixture health.
  • Coolant Temperature (ECT) and Intake Air Temperature (IAT) – thermal monitoring.
  • Throttle Position (TPS) – to correlate driver demand.

Use software like EcuTek ProECU or OpenFlash Tablet to record and analyze logs. Look for patterns: consistent knock at the same RPM load cell, fuel trim drift, or temperature spikes. Many tuners offer remote support if you can provide clean logs.

Tuning Software and Platform Considerations

The choice of tuning platform affects how issues manifest. EcuTek-based tunes offer robust knock control and MAF re-scaling, while Cobb Accessport requires careful base map selection. A common mistake is failing to disable diagnostic trouble codes (DTCs) for sensors that were removed (e.g., rear O2). This can cause intermittent limp modes. Always verify that the tune disables appropriate DTCs and that the base calibration matches the hardware (e.g., injector latency data for ID1000s).

Another pitfall: mixing speed-density and MAF calibrations incorrectly. Some FA20 tunes switch from MAF to speed-density at high loads based on a threshold RPM/load. If the threshold is too low, the engine may oscillate between modes, causing erratic fueling and drivability. Ensure the tuner has properly set the transition table and validated it on the dyno and road.

Mechanical Inspections Before Blaming the Tune

Before spending hours tweaking tables, confirm the mechanical baseline. A failing fuel pump, clogged fuel filter, or dirty injectors can mimic tuning problems. Check:

  • Fuel pressure at the rail (should hold 58 psi idle, 60-65 psi under load for FA20 DI system? Actually FA20 is port injection with ~50-55 psi; verify with a gauge).
  • Compression test – low compression on one cylinder can cause misfires and knock not related to tuning.
  • Spark plugs – used plugs with improper gap can misfire under load, appearing as knock.
  • Intake system – ensure the air filter is clean and the intake tube is not collapsing under high vacuum.

Refer to the FT86 Club tuning guide for a comprehensive pre-tune checklist.

Conclusion

Custom dyno tuning your Subaru BRZ is a powerful way to realize its full potential, but it demands careful attention to detail and a methodical approach to troubleshooting. By understanding the common issues—poor throttle response, engine knock, high fuel consumption, check engine lights, overheating, idling problems, and data logging misinterpretations—you can diagnose and fix problems efficiently. Always verify your hardware baseline before adjusting the tune, and rely on quality logs rather than guesswork. For persistent or complex issues, consulting a professional tuner who specializes in FA20 engines remains the safest path. The FA20 is a forgiving platform when tuned correctly, but it punishes shortcuts. Happy tuning, and keep those logs clean.