Both modules test fine. How can they be incompatible?

Because the incompatibility is in their software, not their hardware. The two controllers exchange data continuously — engine load and torque one way, gear state and shift torque requests the other — and that only works if both were written to the same message definitions and the same torque model. Manufacturers therefore release engine and transmission calibrations as matched sets, and each module checks at startup that its counterpart is carrying a partner it recognises. Two individually healthy modules carrying software from different sets will fail that check every time.

Should I just install the newest software available?

No, and this is the most expensive mistake on this code. The target is not the latest calibration, it is the matched pair the manufacturer specifies for your VIN. Flashing the newest engine calibration onto a vehicle whose transmission module still carries an older partner is a standard way to create this code rather than cure it, and doing it in both directions can leave the pair further from a valid combination than it started. Look the specified pairing up and flash to that, even if newer software exists.

Will replacing a module fix it?

Usually not, and the reasoning matters because people often buy two. The mismatch travels with the software, so a replacement module arrives carrying whatever calibration it happens to have — no more likely to match than the one that came off — and a used module brings a donor vehicle's software and configuration as well. What resolves this is programming access: the manufacturer's application with a current subscription, used to write a matched pair to both modules. Without that access, no amount of hardware substitution reaches a valid pairing.

Can I drive it while I arrange the repair?

It is better to have it recovered. With the two controllers unable to coordinate, the transmission is normally held in fail-safe — one fixed gear, no automatic shifting, often no converter lock-up — and the torque reduction the engine should provide during a shift may not arrive at all, so any shift that does happen can be violently harsh in a way that damages clutches and mounts. On some vehicles the engine will not start until a valid pairing exists. Driving it risks converting a programming job into a transmission rebuild.

OBD-II trouble code

P0614: ECM / TCM Incompatible

Two modules that are individually in perfect health are refusing to work together because their software does not match. This is a code you cause rather than one you develop, which is why the repair order is written on the invoice from the last visit and not in a wiring diagram.

High severityPowertrainPCM / ElectronicsDo not drive

Quick facts

System: Powertrain
Category: PCM / Electronics
Severity: High severity
Drivable: No — stop driving until repaired
Repair cost range: $130 – $2,400
DIY difficulty: Shop recommended

What does P0614 mean?

P0614 means the engine controller and the transmission controller have compared notes and concluded that they are not designed to work with each other. Nothing is broken in the ordinary sense. Both modules may power up correctly, communicate normally and pass every electrical test you can put to them. What they cannot do is agree that their software belongs together.

The two controllers exchange data constantly across the vehicle network. The engine module tells the transmission module about load, torque, throttle position and engine speed; the transmission module tells the engine module about gear state, requested torque reduction during shifts and converter status. That exchange only works if both sides were written to the same set of expectations — the same message definitions, the same torque model, the same shift coordination strategy. Manufacturers therefore release engine and transmission calibrations as matched sets, and part of each module's startup routine is to check that its counterpart is carrying a partner it recognises. When it is not, this code is stored.

The most important practical consequence is that this is a code you cause, not one you develop. It does not appear from wear, heat, vibration or age. It appears because a module was replaced, reprogrammed, taken from a donor vehicle, or updated on one side without the other. If the light came on shortly after somebody worked on a controller, the diagnosis is essentially complete before the hood is opened, and the last invoice is more useful than a wiring diagram.

There is one genuine exception, and it is worth knowing because it is not obvious: software that was correct can become incoherent. Reprogramming a module holds the ignition on for an extended period while the module erases and rewrites its own memory, and it is entirely intolerant of a sagging supply. If the battery is weak, or a charger cannot keep up, or something interrupts the process, the module can be left carrying a partially written calibration. It will then report itself as something it is not, and its counterpart will correctly refuse to pair with it. This is the reason a proper battery maintainer during programming is not a nicety — it is the difference between an hour of work and a module that has to be recovered or replaced.

There is also a trap in how people try to fix this, and it costs real money. The instinct when facing a software mismatch is to install the newest software available on the assumption that newer is better. That instinct is wrong here. The target is not the latest calibration, it is the matched pair the manufacturer specifies for this VIN. Flashing the newest engine calibration onto a vehicle whose transmission module is still carrying an older partner is a reliable way to create this code rather than cure it, and doing it twice in different directions can leave both modules further from a valid combination than they started.

The second expensive trap is buying hardware. Because the code names two modules, the temptation is to replace one of them — and then, when that does not help, to replace the other. It does not help because the incompatibility lives in the software, not in the silicon. A replacement module arrives with whatever calibration it happens to carry, which is no more likely to match than the one that came off, and a used module carries a donor vehicle's software and configuration as well. The resolution is programming access, not parts. A shop with the manufacturer's application and a current subscription resolves most of these in an hour; without that access, no amount of hardware substitution will reach a valid pairing.

On driveability, treat this as a do-not-drive situation. With the two controllers unable to coordinate, the transmission will normally be held in a fail-safe strategy — a single fixed gear, no automatic shifting, often no converter lock-up — and the torque reduction the engine is supposed to deliver during shifts may not arrive at all. Shifts that do occur can be violently harsh, which is mechanically damaging. On some vehicles the engine will not start until a valid pairing is established. Recover it rather than drive it; the alternative risks turning a programming job into a transmission repair.

Common causes

Engine or transmission controller reprogrammed without updating its counterpart to the matched calibration
Replacement module fitted carrying software written for a different specification or model year
Used module from a donor vehicle bringing that vehicle's calibration and configuration with it
Reprogramming interrupted by low battery voltage, leaving a partially written calibration
The newest available calibration installed on one module while the other retains an older partner
Aftermarket performance tune applied to one controller only
Manufacturer software campaign performed on one module and not completed on the other
Internal memory failure preventing a module from retaining a correctly written calibration
Vehicle configuration data describing a different transmission or engine specification

Symptoms

Transmission stuck in a single fixed gear with no automatic shifting
Extremely harsh shifts when a shift does occur
Torque converter not locking up, with engine speed high for the road speed
Engine refusing to start on vehicles that require a valid module pairing
Check engine light plus a transmission warning lamp or message
Symptoms beginning immediately after module replacement or a software update
Loss of cruise control and stability control functions
Communication faults stored alongside in one or both modules
Fault returning after a reflash that appeared to succeed

Diagnostic steps

1.Get the exact service history for the last few weeks before running any test, because this code has a cause rather than a symptom. Replacing or reprogramming the engine controller, replacing or reprogramming the transmission controller, fitting either as a used unit, a dealer software campaign, an interrupted update, or a performance tune written for one module and not the other all produce this directly. If the light came on the day after somebody worked on a module, you already know what happened.
2.Read and write down the software and calibration part numbers held by both modules, and note the hardware part numbers too. This is the actual evidence in the case. Manufacturers publish which engine and transmission calibrations are designed to run together for a given vehicle and model year, and comparing what is installed against that set is the whole diagnosis. Do this before touching anything else, because a reflash overwrites the evidence.
3.If nothing has been done to the vehicle, treat the code as a report of software that has become corrupted rather than mismatched, and check for the mechanism. The most common one is an update that ran with insufficient voltage and did not complete. Look for other internal-fault codes in either module, check battery state of health, and check whether a battery went flat or was disconnected around the time the fault appeared.
4.Confirm the network path between the two modules is healthy before assuming the problem is purely software. These two controllers compare data continuously across the vehicle bus, and while a genuine bus fault normally sets its own communication codes, a marginal connection or a poor shared ground can produce inconsistent exchanges. Clearing this cheaply now avoids a reflash that appears to work and then fails again.
5.Identify the correct target calibration pair before flashing anything, and resist the instinct to install the newest software available. The correct target is the matched set the manufacturer specifies for this VIN, and pairing the latest engine calibration with an older transmission calibration is a normal way to create this code rather than to cure it. Look the pairing up rather than working from version numbers.
6.Put a proper maintainer on the battery before any programming begins — not a trickle charger, and not a jump pack. Reprogramming holds the ignition on for a long time with the module writing to its own memory, and a supply that sags part-way through leaves a half-written calibration. That is the single most common way a straightforward reflash becomes a much bigger problem, and it is entirely preventable.
7.Reprogram both modules to the matched pair, then complete the relearn procedures the platform requires. Depending on the vehicle that may include idle and throttle relearns, transmission adaptive resets and a clutch or shift adaptation drive cycle. Verify the fix by reading both calibration part numbers back and confirming they are the specified pair, not merely by checking that the light went out.
8.If the codes persist after both modules carry the correct matched calibrations, stop buying hardware and reconsider the premise. A mismatch that survives correct software on both sides suggests one module cannot retain what was written — an internal memory failure — or that the vehicle's configuration data describes a different specification. That is a different diagnosis, and continuing to swap modules will not resolve it.

Repair cost

$130 – $2,400

Diagnosis is $130 to $250, most of it spent reading both modules' calibration part numbers and checking them against the manufacturer's specified pairing. Where both modules are healthy and simply need reprogramming to a matched set, expect $200 to $600 including the relearn procedures — this is the usual outcome and the one to aim for. Recovering a module left with a partially written calibration is $250 to $700 and does not always succeed. If a module has genuinely failed and needs replacing and programming, $700 to $2,400 depending on which module and which platform. Add cost if a used module has already been fitted and turns out to be VIN-locked or immobilizer-married to its donor. Note that buying additional modules does not resolve a software mismatch and is money spent without effect.

Estimate your repair

Run the numbers for your vehicle

Open the Repair Cost Estimator with control module replacement & programming preselected. Adjust labor rate and vehicle category to fit your situation.

Estimate your repair cost

DIY vs shop

Leave this one to a qualified shop. It typically involves emissions-critical components, refrigerant handling, or other work that requires manufacturer-grade tooling, training, or certification. DIY attempts often produce a more expensive problem than the original code.