Which Volvo XC90 Modules Interchange With the S80 and V70
The Volvo XC90 (2002–2012), S80 (1998–2006, second generation 2006–2012) and V70/XC70 (2000–2007, P26 generation) all draw from the same P2 platform architecture, meaning a significant number of electronic control modules share identical hardware. In practice, however, not every module that fits the connector will work correctly — variant coding, software calibration and equipment-level differences mean that fitting the wrong sub-variant can result in anything from a minor fault code to a module that simply refuses to communicate. Understanding exactly where the interchange is clean and where it breaks down is the most important check before ordering a used unit.
What the P2 Platform Actually Shares
Volvo’s P2 platform underpins the XC90 (chassis code 275), the second-generation S80 (AS), the V70/XC70 (SW), and to a lesser degree the S60. The CAN bus architecture, the physical connector families and the ECU suppliers — primarily Bosch, Denso and Siemens VDO — are common across these vehicles. That commonality is real and useful. Where it ends is in software calibration, variant coding stored in the unit’s EEPROM, and options like AWD, DSTC, active bending lights or trailer towing modules that are present on some vehicles and absent on others.
The XC90 is the most distinct of the group because it is the only one with standard all-wheel drive on most variants, a transfer case (the BorgWarner unit on petrol models, the Haldex unit on some diesel variants), and a higher ride height with different suspension geometry. These differences propagate into the ABS/DSTC control module, the STC/DSTC module, and any suspension-related control units. A module calibrated for the S80 two-wheel-drive variant will not correctly handle XC90 wheel-speed and steering inputs without reprogramming. For comparison, see Which Modules the Volvo XC90 Shares With the S80 and V70.
Modules That Interchange Cleanly
Several module families interchange across the XC90, S80 and V70 without restrictions beyond matching the exact part number suffix:
- Climate control panel (CCM): The front climate control unit — the physical panel with buttons and display — interchanges freely between XC90 and V70/XC70 where both are fitted with ECC (Electronic Climate Control). The underlying software is loaded by the unit, not flashed to the panel, so a panel swap is plug-and-play provided the generation matches (pre-facelift to pre-facelift, facelift to facelift).
- Instrument cluster: The cluster interchanges within the same model generation where the engine and options match. However, the cluster holds the mileage in its own memory and requires VIDA/DiCE to perform a legally compliant mileage transfer after replacement. A direct swap without mileage adaptation leaves a discrepancy that will show in a vehicle history check.
- CEM (Central Electronic Module): This is the most commonly interchanged module on P2 vehicles. The CEM controls central locking, interior lighting, wiper timing, horn and a large number of small body functions. A CEM from an S80 of the same generation and similar equipment level will physically seat in a V70 or XC90 and will communicate on the CAN bus. After fitting it must be coded using VIDA for the VIN of the receiving vehicle — without this step, remote locking, alarm arming and various comfort functions will not behave correctly.
- Audio amplifier (HU-xxx, SC-xxx series): The amplifier and head unit modules interchange within the same generation provided the connector configuration matches. The fibre-optic MOST bus is used on higher-specification systems; a non-MOST amplifier will not work in a MOST-equipped vehicle regardless of whether the connector seats.
Modules That Do Not Interchange Without Reprogramming
- ABS/DSTC control module: The XC90 AWD variant requires a module calibrated for four driven wheels and the BorgWarner or Haldex rear axle. An S80 FWD ABS module will physically fit the connector but will immediately throw C-series fault codes and will not release the DSTC correctly. Do not fit an S80 ABS module to an XC90 AWD under any circumstances without verified software compatibility from Volvo VIDA data.
- ECM (Engine Control Module): Engine management units are VIN-coded and immobiliser-linked. An ECM from any P2 vehicle requires VIDA coding and immobiliser synchronisation before it will start the engine in a different vehicle. The physical part number must match exactly — engine variant, emission standard (Euro 3 vs Euro 4), and software generation all produce different part numbers. Fitting an ECM with a matching base number but wrong suffix will cause a no-start with IMMO-related fault codes even after VIDA adaptation attempts.
- TCM (Transmission Control Module) — AW55-50SN and AW55-51SN: The automatic gearbox TCM is partially interchangeable between S80, V70 and XC90 where the same gearbox unit is fitted. However, the XC90’s heavier kerb weight and torque requirements mean some software variants have different shift pressure maps. A used TCM must carry the correct Volvo part number for the receiving vehicle; after fitting, a gearbox adaptation reset using VIDA is mandatory to allow the shift logic to relearn clutch fill times.
- SRS airbag control module: The SRS module is VIN-linked after a deployment event. A module that has previously fired cannot be reflashed to a clean state by standard workshop tools. A non-deployed used unit from the same generation will physically fit and will communicate after VIDA coding, but only if it carries a matching software generation. Fitting an XC90 SRS module to an S80 or V70 is theoretically possible if the number of airbag and pretensioner circuits matches — verify this in VIDA before ordering.
Part Numbers to Know
Exact number matching matters on every P2 module because Volvo uses the last two or three digits of the part number — the so-called design level — to distinguish software generations. Two modules with identical base numbers but different design levels may look identical externally but carry incompatible calibrations.
| Module | Typical Volvo Part Numbers | Notes |
|---|---|---|
| CEM (XC90, 2003–2006) | 30728519, 30728520, 30728521 | Must match equipment level (trailer, sunroof, alarm spec) |
| CEM (V70/XC70, 2004–2007) | 30786066, 30786067, 30786068 | FWD and AWD variants differ; do not cross-fit without VIDA check |
| ABS/DSTC (XC90 AWD) | 30739968, 30739969, 30786325 | AWD-specific; not interchangeable with FWD S80/V70 units |
| Instrument cluster (XC90) | 30773021, 30773022, 30773023 | Mileage transfer required; diesel and petrol variants differ |
| SRS module (XC90, 2003–2006) | 30728458, 30728459 | Circuit count must match vehicle airbag/pretensioner layout |
| TCM AW55-50SN (S80/V70) | 30680771, 30680772 | Adaptation reset required after fitting; shift maps differ by variant |
Affected Vehicles and Years
This interchange guide applies primarily to:
- Volvo XC90 (2002–2012, all engines, both 5-seat and 7-seat layouts)
- Volvo S80 first generation (1998–2006) — partial overlap on CEM and climate only
- Volvo S80 second generation (2006–2012) — shares more with XC90 post-facelift
- Volvo V70 third generation / XC70 (2007–2012) — broadest overlap with XC90
- Volvo S60 (2000–2009) — limited overlap; always verify in VIDA before ordering
Pre-2003 XC90 production (first year) used slightly different CEM and SRS calibrations. Always confirm the build date from the VIN plate, not just the model year.
Coding Requirements After Fitting a Used Module
With very few exceptions, every replaced module on a P2 Volvo requires at minimum a VIDA coding step to write the receiving vehicle’s VIN, configuration data and options into the new unit. The CEM additionally requires a network download that distributes the new module’s address to every other node. Modules that skip this step will partially communicate — enough to crank the engine, for example — but will generate stored fault codes and may suppress functions like DSTC, hill-descent control or trailer stability assist. A related diagnostic guide is Which Volvo S60 and V70 Modules Interchange Across the P2 Platform.
Volvo’s DiCE interface paired with VIDA 2014D remains the most complete tool for P2 coding. Third-party tools such as VCDS (Hex-V2) do not support Volvo, but Dice Clone interfaces with compatible VIDA installations are widely used in independent workshops across Europe. Confirm coding capability with your workshop before fitting, not after.
FAQ
Can I fit an S80 CEM directly into my XC90 without any coding?
The module will seat in the connector and will power up, but it will carry the previous vehicle’s configuration including alarm code, key pairing data and equipment options. Without VIN coding in VIDA, functions including remote locking, alarm arming and correct lighting behaviour will not work properly. Coding is mandatory, not optional.
Does the Volvo XC90 ABS module interchange with the V70 unit?
Only between AWD variants of equal specification. The XC90 AWD ABS module is calibrated for four driven wheels and the BorgWarner rear transfer unit; the standard V70 front-wheel-drive ABS module is incompatible. An XC70 AWD unit is closer but still requires VIDA verification of the part number before fitting. For additional context, read Which Fault Codes the Volvo XC90 ABS Module Sets and Why.
Will a used XC90 instrument cluster work after fitting?
It will display and communicate, but the mileage stored in the cluster will be from the donor vehicle. A VIDA mileage transfer writes the correct reading from the CEM to the new cluster. Without this step the odometer shows the wrong value, which is a legal issue in most European countries and will appear in vehicle history checks.
Is the SRS airbag module from an S80 compatible with the XC90?
Only if the number of airbag and pretensioner circuits is identical in both vehicles and the module has not previously been deployed. The XC90 typically has more side curtain airbag circuits than the equivalent S80. Fitting a module with fewer circuits than the vehicle wiring expects will produce a permanent SRS fault and may prevent the system from arming at all.
What tools are needed to code a replacement P2 Volvo module?
Volvo VIDA software paired with a genuine or compatible DiCE interface is the standard solution for P2 vehicles. Some independent aftermarket tools such as Autel MaxiSys and Launch X431 have limited P2 support for reading and clearing faults, but full module coding and adaptation generally requires VIDA. Confirm support for your specific module type before starting the job.
Find tested OEM electronic parts and modules at:
https://giantparts.eu/
