How to Read Peugeot and Citroen BSI Module Part Numbers Before Buying
The BSI — Body Systems Interface — is the central multiplexing node on most Peugeot and Citroen vehicles built between 1999 and 2012. Two BSI units pulled from the same model year can share the same base number but carry different hardware suffixes that prevent successful coding, and the difference is invisible unless you know where to look on the label. Reading the number correctly before ordering a used unit is the single most effective way to avoid a wasted fitting attempt.
What the BSI Does and Why Part Number Matching Matters
The BSI sits at the centre of the VAN multiplex network used on PSA vehicles of this era. It manages central locking, interior lighting, alarm, windscreen wiper logic, electric windows, the instrument cluster communication bus, and several auxiliary relay outputs. On the Peugeot 307, 407 and Citroen C4 and C5 it also arbitrates between the powertrain CAN and the body VAN, making it the gateway between two separate bus architectures.
Because the BSI holds vehicle-specific calibration data — including the VIN, the key transponder table, and the mileage seed value used by the instrument cluster — a replacement unit must be coded before it operates normally. The coding process, carried out with Lexia-3, PP2000, or DiagBox, writes these values to the new BSI from the diagnostic interface. However, the coding tool can only complete this process if the hardware revision of the replacement unit is compatible with what the car’s software expects. A mismatched hardware suffix will be rejected at the coding stage, sometimes without a clear error message — the tool simply times out or reports a communication failure.
How the Part Number Is Structured
A typical BSI label reads something like 9650794480 or in later hyphenated format 96 508 252 80. PSA part numbers on BSI units follow a consistent pattern worth understanding field by field.
The first eight or nine digits form the base reference. This identifies the physical hardware design — the PCB layout, the main processor family, and the connector configuration. Two units with the same base reference will physically fit the same mounting location and accept the same connector.
The final two digits — in the examples above, 80 — are the hardware and software index suffix. This is the most important field. It encodes the hardware revision level and in many cases the software variant that was fitted at the factory. A unit with suffix 80 is not guaranteed to accept the same coding as one with suffix 00 or 09, even though the base reference matches. On the Peugeot 407 in particular, the jump from suffix 00 to suffix 80 coincided with a processor change that required a different DiagBox configuration file.
Some labels carry an additional production date code in a separate field, typically in WWYY format (week, year), which is useful for confirming the unit’s age but is not part of the compatibility matching process itself.
Common BSI Part Numbers by Platform
The following are genuine OEM references found on BSI units across the most common PSA platforms of the 2001–2010 period. Exact match of all digits including suffix is required before ordering a used unit.
| Vehicle | Years | BSI Part Number | Notes |
|---|---|---|---|
| Peugeot 307 | 2001–2004 | 9650334480 | Early VAN-only architecture |
| Peugeot 307 | 2004–2008 | 9652784780 | Dual CAN/VAN gateway variant |
| Peugeot 407 | 2004–2007 | 9655745280 | Suffix 80 hardware; suffix 00 units not interchangeable |
| Citroen C4 Mk1 | 2004–2008 | 9651840780 | Shared base with some 307 variants; suffix must match |
| Citroen C5 Mk2 | 2004–2008 | 9663962580 | Higher-spec unit with additional CAN nodes |
| Peugeot 206 | 2000–2005 | 9637833380 | Earlier single-bus architecture; simpler coding |
GiantParts lists tested OEM BSI units with the full part number including suffix shown in the product reference. Always confirm your vehicle’s existing number by reading the label on the fitted unit before ordering, not by searching by model year alone — production changes mean the same model year car can carry different BSI variants depending on build month.
Where the Label Is and How to Read It
On the Peugeot 307 and most Citroen C4 variants, the BSI is located behind the glovebox, attached to the lower dashboard crossmember. The label faces inward toward the car’s centre and is usually not visible without removing the glovebox liner. On the 407 and C5 Mk2, the unit is mounted under the dashboard on the driver’s side, often above the steering column shroud.
The label is a white or silver adhesive plate with printed black text. Read the longest numeric sequence — this is your base reference plus suffix. Photograph it before disconnecting anything; power loss to the BSI during removal does not corrupt calibration data, but you want the number recorded before the unit is on the bench.
A second smaller sticker may carry a barcode with the same number encoded. Either format gives the same information. The VIN is not printed on the external label — it is stored internally and can be read through DiagBox under BSI identification.
Fault Codes Associated With BSI Failure or Mismatch
When the BSI fails or when a replacement unit has not been coded, the following codes appear most frequently in the diagnostic log:
- U0100 — Lost communication with ECM/PCM. Appears when the BSI cannot relay CAN messages to the engine management system. Can indicate BSI failure or a wiring fault at the CAN high/low pair.
- U0155 — Lost communication with instrument panel cluster. Common after a BSI replacement before coding is completed.
- B1000 (PSA-specific) — BSI internal fault. Logged when the unit detects its own EEPROM data as corrupted or when the VIN stored internally does not match the value broadcast by the engine ECU.
- B1001 — Configuration mismatch. Logged when options coded into the BSI do not match the physical equipment detected on the network.
- U1213 — VAN bus communication fault. Specific to the older VAN multiplex architecture on the 206 and early 307; indicates the BSI is not receiving responses from body control nodes.
What Cannot Be Confirmed Without Fitting
Even with a perfectly matched part number, two things cannot be verified by visual inspection alone. First, whether the BSI’s internal EEPROM has been partially written with another vehicle’s data from a previous coding attempt — this can cause the new coding session to fail or produce incomplete results, requiring an EEPROM erase at board level before the unit will accept fresh calibration. Second, whether the BSI has suffered thermal damage to the processor from a sustained overvoltage event — a common failure mode on vehicles where the alternator voltage regulator has failed. Visually the unit looks intact, but the processor will not complete its boot sequence.
A reputable used parts supplier should be able to confirm that the unit powers up and communicates on a bench test rig, which eliminates most concealed failures. GiantParts tests OEM units before despatch and ships with part number documentation included.
FAQ
Can I fit a Peugeot 307 BSI into a Citroen C4 if the part numbers are close?
Not reliably. Even where the base reference appears similar, the variant coding stored at the factory differs between Peugeot and Citroen applications. DiagBox treats them as separate vehicle families, and the configuration files for option coding are not identical. Stick to exact part number matches, including marque-specific variants.
Does a replacement BSI need to be programmed with the original mileage?
The BSI does not store the displayed odometer mileage directly — that value is held in the instrument cluster. However, the BSI does store a seed value used to validate the cluster’s mileage during startup. When coding a replacement BSI, DiagBox transfers this seed from the diagnostic interface’s stored vehicle data, not from the old BSI unit, so the cluster continues to display correctly after coding.
What equipment do I need to code a replacement Peugeot or Citroen BSI?
The standard tool is a Lexia-3 interface running DiagBox version 6.01 or later, or the updated Diagbox 9.x software. A genuine PSA dealer interface (Proxia or the current Pass-Thru Diagbox) can do the same job. The coding procedure is called BSI initialisation and takes around 10–15 minutes when everything communicates correctly.
Why does the suffix on the part number matter more than the base reference?
The suffix encodes both the hardware revision of the PCB and the embedded software variant. PSA changed processor families on the BSI at least twice between 2001 and 2010, and each change incremented the suffix group. DiagBox’s configuration files are matched to suffix groups, so a wrong suffix means the coding tool sends commands the hardware processor cannot interpret, and the session fails.
Is it possible to repair a BSI rather than replace it?
Board-level repair is possible for specific known failure modes — cracked solder joints on the main connector pins and failed capacitors on the power supply rail are both repairable with proper equipment. However, EEPROM-level corruption or processor failure is not economically repairable for most workshops. A tested used OEM unit with a matched part number is usually the faster and more reliable path.
Find tested OEM electronic parts and modules at:
https://giantparts.eu/
