The Powertrain Control Module and Engine Control Module in the 2013 Mitsubishi Lancer Evolution manage fuel delivery, ignition timing, boost control, and powertrain coordination for the turbocharged 2.0L engine. Internal failures may cause no-start conditions, stalling, or loss of diagnostic communication, often requiring module replacement rather than external component repair.
Diagnosing engine computer problems in a performance vehicle can be frustrating, especially when symptoms seem to point in multiple directions at once. The 2013 Mitsubishi Lancer Evolution uses a dual-computer architecture with both a Powertrain Control Module and an Engine Control Module working together to manage its turbocharged 2.0L engine. When one of these modules develops an internal fault, the vehicle may refuse to start, stall without warning, or lose communication with diagnostic tools entirely. Understanding how these computers function, what symptoms their failures produce, and what the replacement process involves can help you make informed decisions about the repair path. The factory labor guide provides specific time allowances for module removal, reinstallation, and relearn procedures, which helps clarify what to expect from a service visit and how to budget for the work. This guide walks through the role each module plays in the Evolution, the documented internal trouble code for this vehicle, and how a pre-programmed replacement unit can simplify the repair process by eliminating steps that would otherwise require a dealership scan tool and additional labor time.
The 2013 Mitsubishi Lancer Evolution relies on two closely integrated engine-management computers: the Powertrain Control Module and the Engine Control Module. The PCM oversees the broader powertrain functions, coordinating engine output with transmission behavior, while the ECM focuses specifically on engine operating parameters such as fuel delivery, ignition timing, and emissions control. In a turbocharged 2.0L performance vehicle like the Evolution, these modules manage boost control, air-fuel mapping under high load, and the precise injector pulse widths that keep the engine running safely at elevated performance levels. The PCM also interfaces with the all-wheel-drive system, helping modulate torque distribution based on wheel slip, throttle position, and steering angle inputs. When either module begins to fail, the vehicle may exhibit erratic idle behavior, reluctance to start, or sudden loss of communication with diagnostic equipment. Because the PCM and ECM share data across the controller area network, a fault in one can trigger symptoms that appear to originate from the other. Diagnosing which module has actually failed often requires pinpointing the specific trouble code stored in memory and comparing it against known-good parameters. For owners facing a confirmed module failure, sourcing replacement computers for the Lancer Evolution becomes the next practical step. A properly matched unit ensures the turbocharged 2.0L engine retains its factory calibration, driveability characteristics, and emissions compliance. Installing an incorrect or incompletely programmed module may lead to rough running, illuminated warning lamps, or even refusal to start, making module selection and programming accuracy critical to a successful repair.
The factory labor guide allocates 0.9 hours for removal and reinstallation of either the Powertrain Control Module or the Engine Control Module on the 2013 Mitsubishi Lancer Evolution. That book time covers the physical swap, including accessing the module, disconnecting the wiring harness connectors, transferring or replacing the unit, and reconnecting everything. Because this vehicle uses both a PCM and an ECM, each module carries its own 0.9-hour R&R allowance if both need attention. The relearn operations are tracked separately at 0.5 hours for the PCM relearn and 0.5 hours for the ECM relearn. No torque specifications or detailed access procedures were provided in the labor data for this vehicle, so those figures should be confirmed with the factory service manual before beginning the job. A technician working on one module references the R&R figure and the corresponding relearn figure independently when estimating the service visit.
| Operation | Configuration | Book Time |
|---|---|---|
| Powertrain Control Module R&R | All configurations | 0.9 hr |
| Powertrain Control Module Relearn | All configurations | 0.5 hr |
| Engine Control Module Relearn | All configurations | 0.5 hr |
| Engine Control Module R&R | All configurations | 0.9 hr |
After a new or remanufactured module is installed in the 2013 Mitsubishi Lancer Evolution, the factory procedure requires a relearn operation to synchronize the replacement unit with the vehicle’s immobilizer, throttle body, and learned adaptive data. The labor guide specifies 0.5 hours for a PCM relearn and 0.5 hours for an ECM relearn, reflecting the time a technician needs to complete the synchronization using a compatible scan tool. Without this step, the engine may crank but fail to start, or it may run with noticeably poor drivability. Flagship One addresses this requirement by shipping each unit already programmed to the specific vehicle identification number, meaning the VIN-specific calibration and immobilizer data are written to a pre-programmed replacement module before it leaves the facility. The result is that the relearn procedure listed in the factory labor guide is typically unnecessary when installing one of these units, allowing the vehicle to start and run correctly after the physical swap is completed.
Failure of the PCM or ECM in the 2013 Mitsubishi Lancer Evolution can manifest in several recognizable ways. One of the most common symptoms is a no-start condition where the engine cranks but never fires, often because the module has lost its ability to command fuel injectors or ignition coils. Intermittent stalling while driving is another frequent complaint, particularly when the internal processor encounters a fault mid-operation. Drivers may also notice misfire codes appearing without an obvious mechanical cause, as a failing module can incorrectly calculate timing or fuel delivery. Complete loss of scan-tool communication is a strong indicator of internal module failure rather than a sensor or wiring issue. When the diagnostic connector yields no response from the engine computer, the module itself has likely failed. The Evolution’s turbocharged 2.0L engine is sensitive to even minor calibration errors, so symptoms may include erratic boost behavior, surging at steady throttle, or reduced power output without a clear trigger. Transmission-related concerns such as harsh or delayed shifting can also surface if the PCM portion of the system is compromised. A documented internal processor fault, such as the P0606 internal control module fault, indicates that the computer’s own self-check has detected a problem within its circuitry rather than in an external component. This code typically points toward module replacement rather than sensor or wiring repairs.
The following table lists the module-internal trouble codes documented for the 2013 Mitsubishi Lancer Evolution. These codes originate within the engine or powertrain control module itself rather than from external sensors or actuators. When one of these codes appears, the module’s internal diagnostics have detected a fault in the processor or its supporting circuitry.
| Code | Meaning | Full Guide |
|---|---|---|
| P0606 | Module processor failure | Full P0606 guide → |
P0606 indicates an internal fault detected by the control module’s own self-diagnostic circuitry. This code means the PCM or ECM has found a problem within its internal processor rather than in an external sensor or actuator. Replacement of the affected module is typically the recommended repair path.
The factory labor guide allocates 0.9 hours for removal and reinstallation of either the PCM or the ECM. A separate relearn operation is listed at 0.5 hours for the PCM and 0.5 hours for the ECM. If a pre-programmed unit is used, the relearn step may not be necessary.
Driving with a confirmed internal module fault is not recommended. The vehicle may stall unexpectedly, fail to restart, or exhibit unpredictable behavior under load. A turbocharged engine like the 2.0L in the Evolution depends on precise fuel and timing management to avoid potential damage.
Factory procedure requires the module to be programmed with the vehicle’s identification number and calibration data. Flagship One units arrive already programmed to the specific VIN, which typically eliminates the need for the 0.5-hour relearn operation listed in the labor guide.
The ECM manages engine-specific functions such as fuel injection and ignition timing, while the PCM oversees broader powertrain coordination including transmission interaction. Both modules communicate over the vehicle’s network, and a fault in either can produce overlapping symptoms.
When a module failure is confirmed, vehicle owners generally choose between a dealer-sourced new unit and a refurbished replacement. Dealer parts typically require an additional programming visit, while a pre-programmed unit from Flagship One arrives ready to install with the correct VIN-specific calibration already written. For the 2013 Mitsubishi Lancer Evolution, selecting a module that matches the factory specifications helps preserve the turbocharged engine’s performance and driveability characteristics.
Flagship One stocks a refurbished, VIN-programmed PCM for the 2013 Mitsubishi Lancer Evolution with a lifetime warranty, free shipping and no core charge. The full Mitsubishi Lancer Evolution module lineup covers other engine configurations as well.
The 2013 Mitsubishi Lancer Evolution depends on its PCM and ECM to keep the turbocharged 2.0L engine running at peak performance. When internal faults arise, a correctly programmed replacement module restores the precise fuel, timing, and boost management that this vehicle demands. Flagship One offers VIN-programmed units designed to match the factory calibration, helping get the Evolution back on the road without a separate programming visit.