logo elektroda
logo elektroda
X
logo elektroda
Advanced Search
logo elektroda

Citroën CAN Bus Wiring, Pinout, and Diagnostic Guide for C4, Berlingo, Jumper, DS3

Ask a question on the Forum

User question

Schemat canbus citroen

Artificial Intelligence Response

Direct answer to the question

  • There is no single, universal “Citroën CAN bus schematic.” Citroën/PSA/Stellantis vehicles use several CAN networks and the exact topology, pinouts, wire colors, and splice points depend on the model, year, engine, and options.
  • To provide the correct schematic, please share: model, model year (or VIN), and which network/function you need (powertrain CAN, body/comfort CAN, ABS/ESP, infotainment, etc.).

Key points

  • Typical networks: HS‑CAN ≈ 500 kbit/s (powertrain/brakes), MS/LS‑CAN ≈ 125 kbit/s (body/comfort), plus LIN sub‑buses.
  • Gateway: the BSI (Built‑in Systems Interface) routes traffic between networks.
  • Diagnostic access: OBD‑II pin 6 = CAN‑H, pin 14 = CAN‑L, pin 4 = chassis ground, pin 16 = +12 V.
  • Health checks: ≈60 Ω between pins 6–14 with battery disconnected; CAN‑H ≈ 2.6–3.5 V and CAN‑L ≈ 1.5–2.4 V with ignition on.

Detailed problem analysis

  • Network architecture
    • HS‑CAN (500 kbit/s): Engine ECU (ECM), gearbox/TCU, ABS/ESP, electric power steering, sometimes airbag and instrument cluster (varies by platform).
    • MS/LS‑CAN (≈125 kbit/s): BSI, body controller functions (lighting, wipers), HVAC, infotainment, parking aid, door/seat modules, instrument cluster on some models.
    • LIN: Single‑wire sub‑nets for actuators and sensors (mirrors, window switches, rain/light sensor), usually mastered by a door module, HVAC, or steering column module.
    • Legacy note: Older PSA models (pre‑mid‑2000s) used VAN (a different multiplex bus). Do not mix VAN and CAN diagrams.
  • Topology and terminations
    • Twisted pair for CAN‑H/CAN‑L with 120 Ω terminations at both ends of each segment (≈60 Ω measured across a healthy, connected bus).
    • Star points are uncommon on HS‑CAN; instead, harness splices (PSA-labeled “Sxxx”) form branches. MS‑CAN often uses more branching via the BSI.
    • The BSI is the logical gateway between domains; it is not normally a termination for the HS‑CAN powertrain segment.
  • Typical measurement values and what they mean
    • Resistance (battery disconnected): ≈60 Ω good; ≈120 Ω indicates one missing terminator; very low Ω suggests H–L short; open circuit indicates a severed pair or both terminators missing.
    • Bias/voltage (ignition on): quiescent around 2.5 V mid‑rail; during traffic CAN‑H rises toward ~3.5 V, CAN‑L drops toward ~1.5 V (mirror image). Use an oscilloscope for confirmation; DMM only shows averages.
  • Wire identification
    • Wire colors and numbering vary by platform and year. Many PSA looms label CAN pairs with harness “cable numbers” (e.g., 9001/9000) rather than relying solely on color. Do not rely on color alone; confirm by diagram and continuity.
  • Common physical access points
    • OBD‑II DLC under dash (HS‑CAN on pins 6/14).
    • BSI/fusebox area (often under dash or behind glovebox, depending on model).
    • ABS hydraulic unit, ECM in engine bay, instrument cluster connector, and behind the head unit for body/infotainment CAN.
  • Quick isolation workflow without the OEM diagram
    1. Verify power/ground quality at BSI and main ECUs (low system voltage or poor grounds can mimic CAN faults).
    2. Measure 6–14 resistance at DLC with battery disconnected.
    3. If not ≈60 Ω, unplug major endpoints (ECM, ABS, BSI connectors one at a time) to see when 60 Ω returns, identifying the missing terminator or shorted branch.
    4. With ignition on, check CAN‑H/CAN‑L voltages versus ground at multiple nodes to locate where the bias collapses.
    5. Use an oscilloscope to view differential signaling and identify a dormant or dominant node (stuck‑at‑dominant fault).
    6. For intermittent faults, gently flex harness sections and inspect common chafe points (front subframe pass‑throughs, behind battery tray, A‑pillar looms, tailgate gaiters).

Current information and trends

  • Around 2010, PSA introduced notable protocol and network changes across platforms. This matters for retrofits (e.g., head units, instrument clusters) and cross‑year swaps—confirm the exact CAN variant and gateway coding before mixing components.
  • Newer Stellantis platforms increasingly use UDS diagnostics and, on some domains, CAN‑FD. Certain late‑model vehicles may enforce security access for enhanced diagnostics and coding. Always verify tool capability (e.g., Diagbox versions) for the specific MY.
  • Infotainment/telematics modules in recent models often sit on a separate body/infotainment CAN with the BSI acting as a firewall/gateway; coding is required when replacing these parts.

Supporting explanations and details

  • Why ≈60 Ω: Two 120 Ω terminators in parallel at the physical ends of a given CAN segment; a missing terminator doubles measured resistance, while a third unintended terminator or short lowers it.
  • Why the BSI matters: It translates and filters traffic between HS‑CAN and MS‑CAN and hosts configuration data (“BSI coding”). Replacing or mis‑coding the BSI can break inter‑domain communications without any physical wiring fault.
  • Typical module allocation example (varies by model):
    • HS‑CAN: ECM, ABS/ESP, EPS, TCU.
    • MS‑CAN: BSI, HVAC, parking ECU, head unit, telematics, door modules.
    • LIN branches: window lifters, mirror controls, climate flap motors.

Ethical and legal aspects

  • OEM wiring diagrams are copyrighted; obtain them via legal sources (manufacturer service portals or licensed databases). Sharing full OEM diagrams publicly may violate IP.
  • When tapping CAN for telematics/aftermarket, inform the vehicle owner about data privacy. Avoid interfering with safety systems (SRS, ABS/ESP). Disconnect the battery and observe airbag de‑powering wait times before working near SRS harnesses/connectors.

Practical guidelines

  • To get the exact schematic you need
    • Provide model, year (or VIN). With that, you can be directed to the precise connector, pin, splice, and harness references (e.g., “BSI connector 16V‑GREY, pins A4/A5, splice S320”).
    • Use official Stellantis Service documentation or professional databases (ALLDATA/Mitchell/HaynesPro) that return VIN‑filtered diagrams, connector views, and splice locations.
  • Diagnostic best practices
    • Always verify powers/grounds at the module before suspecting CAN.
    • Use back‑probe pins or breakout leads; avoid piercing insulation where possible.
    • Keep stubs short when attaching analyzers; long stubs can degrade signal integrity on HS‑CAN.
    • If the bus is down, disconnect add‑ons (aftermarket alarm, tracker, head unit) first—these are frequent fault sources.
  • Installation tips for aftermarket devices
    • Use a CAN interface matched to your Citroën platform/year. Many PSA changes around 2010+ mean older interfaces may not parse messages.
    • Take CAN from a body bus behind the head unit for comfort functions; never load the powertrain HS‑CAN with unnecessary devices.

Possible disclaimers or additional notes

  • Wire colors vary even within a model year due to option packs and supplier changes; trust VIN‑specific diagrams over color heuristics.
  • Some models place the instrument cluster on HS‑CAN; others on MS‑CAN. Do not assume location by function alone.
  • Fault‑tolerant single‑wire CAN is not used on PSA HS‑CAN; if you see single‑wire multiplexing on older cars, it is likely VAN or LIN.

Suggestions for further research

  • Standards: ISO 11898 (CAN physical/data link), ISO 15765‑4 (OBD on CAN), ISO 14229 (UDS).
  • Tooling: PSA Diagbox for diagnostics/coding; a mid‑bandwidth oscilloscope (≥20 MHz) and a CAN analyzer that supports PSA/UDS for deeper traces.
  • Platform specifics: For accurate splice and connector IDs, consult the VIN‑filtered wiring section of the official service portal or a licensed database.

Brief summary

  • Citroën vehicles use multiple CAN networks bridged by the BSI; there is no all‑models schematic. The correct diagram is model/VIN‑specific. You can quickly assess bus health at the OBD‑II port (≈60 Ω; CAN‑H higher than CAN‑L). For an exact CAN schematic and connector/splice IDs, please provide your model and year (or VIN) and the system of interest, and I will guide you to the precise wiring and test points.

User question

I have a Citroën C-Elysée 1.2 VTi (2014). I tried to connect an OBD2 diagnostic scanner (ICAR Pro 2S ELM Bluetooth). The Bluetooth connection works, but it cannot communicate with the ECU. What should I check, and how can I solve this issue? Note that this OBD scanner works normally with my Peugeot 407 (2007 HDi).

Artificial Intelligence Response

Direct answer to the question

Your Bluetooth link is not the problem. If the iCar Pro 2S pairs with the phone in the Citroën, the adapter is powered; the failure is almost certainly on the OBD/CAN communication side between the dongle and the car. On the 2014 C‑Elysée, the first things I would check are:

  1. Ignition / engine state: try connecting with ignition ON, and if that fails, with the engine running, because the C‑Elysée uses an energy-saving mode after engine stop. The handbook states that after the engine is stopped, the car can enter “mode économie d’énergie” and put functions into standby. (service.citroen.com)
  2. Fuse F02 in the dashboard fuse box: the Citroën handbook explicitly lists F02 (5 A) for the diagnostic socket. If F02 is open, power may still appear at the dongle but communication can fail. (service.citroen.com)
  3. OBD port pins 6 and 14: inspect for bent, spread, dirty, or pushed-back terminals; those are the HS‑CAN data pins.
  4. App/protocol settings: force the app to ISO 15765‑4 CAN, 11‑bit, 500 kbit/s. In ELM terminology this is protocol 6. (elmelectronics.com)
  5. Adapter/app compatibility: the Vgate device officially claims support for all OBD‑II protocols, but Car Scanner also notes that some adapters initialize poorly and may be flagged as a “bad adapter” during ECU initialization. (vgatemall.com)

If those checks pass and it still will not talk to the ECU, the practical solution is often to use a PSA-specific interface such as Lexia/Diagbox, because generic ELM adapters are reliable for standard OBD but are less consistent on PSA cars for initialization and deeper module access.

Detailed problem analysis

The important diagnostic fact is this:

  • Bluetooth connected only proves the phone can talk to the dongle.
  • It does not prove the dongle can talk to the vehicle ECU.
  • Since the same dongle works on your Peugeot 407, the dongle is probably not dead, but that does not guarantee the same initialization behavior on the Citroën. ELM327 devices support several protocols, including ISO 15765‑4 CAN, and protocol selection matters. (elmelectronics.com)

A correction to some common online claims: the issue is not necessarily that the C‑Elysée has some hard security gateway blocking all generic scanners. On a 2014 Euro-market petrol car, standard emissions OBD should normally still be reachable through the 16‑pin socket. In practice, the failure is more often one of these:

  • vehicle not in the right wake/ignition state,
  • blown diagnostic fuse,
  • bad contact on OBD pins,
  • CAN wiring fault,
  • app selecting the wrong device/protocol,
  • marginal ELM initialization timing.

1) Check the car state first

The Citroën handbook says the car enters energy economy mode after engine stop and puts functions into standby after a limited time. That is why PSA cars often connect more reliably with the engine running or immediately after switching ignition on. (service.citroen.com)

Do this test sequence:

  • Plug in the iCar Pro 2S.
  • Turn ignition ON, wait 15–30 seconds, then connect.
  • If it still fails, start the engine and try again.
  • If the battery is weak, charge it first; low system voltage can destabilize CAN communication.

2) Check the fuse that actually feeds the diagnostic socket

This is one of the most useful vehicle-specific facts for your car: in the C‑Elysée handbook, the dashboard fuse box lists:

So even if the dongle lights up, check F02 physically with a meter, not only visually. A partially oxidized fuse, loose fuse contact, or cracked element can create intermittent operation.

3) Inspect the DLC/OBD connector itself

Look closely at the 16‑pin socket in the car:

  • Pin 16 = battery +
  • Pins 4 and 5 = grounds
  • Pin 6 = CAN‑H
  • Pin 14 = CAN‑L

The most common mechanical fault is that pins 6 and 14 have been spread or pushed back by previous workshop tools. With some dongles, the power pins make contact but the CAN pins do not.

Use a flashlight and compare all terminals:

  • Are 6 and 14 recessed deeper?
  • Are they widened?
  • Is there corrosion or dirt?

If needed, with ignition off, carefully retension the female contacts.

4) Measure the CAN bus electrically

If you have a multimeter, this is the fastest way to separate a vehicle wiring problem from an adapter/software problem.

Test Condition Expected result Interpretation
Pin 16 to pin 4/5 key on ~12 to 14 V Power present
Pin 4 to chassis key off ~0 Ω / good continuity Ground OK
Pin 5 to chassis key off near 0 Ω Signal ground OK
Pin 6 to pin 14 battery disconnected, network asleep ~60 Ω Bus termination normal
Pin 6 to ground key on about 2.5 to 3.5 V CAN‑H bias/traffic
Pin 14 to ground key on about 1.5 to 2.5 V CAN‑L bias/traffic

For high-speed CAN, the recessive state is biased around 2.5 V, and in dominant state CAN‑H rises to about 3.5 V while CAN‑L falls to about 1.5 V. Standard CAN termination is two 120 Ω resistors in parallel, so the bus measures about 60 Ω across CAN‑H and CAN‑L. (nxp.com)

Interpretation of the 6–14 resistance test:

  • ~60 Ω: bus wiring is probably healthy.
  • ~120 Ω: one terminator missing / one bus branch open.
  • Very low Ω: CAN‑H and CAN‑L shorted together.
  • Open / OL: broken line to the diagnostic connector or severe network fault.

If you measure ~60 Ω and reasonable CAN bias voltages, then the vehicle wiring is likely fine and the problem moves toward protocol/app/adapter compatibility.

5) Force the correct protocol in the app

The ELM327 command set defines:

That is the setting I would force for this car if “Automatic” fails.

Recommended app-side actions:

  • Create a new vehicle profile for the Citroën.
  • Make sure the app is connected to the correct Bluetooth device. Car Scanner explicitly warns that many users select the wrong device in the app settings. (carscanner.info)
  • Close all other OBD apps.
  • Try:
    • Automatic (Fast) first,
    • then manually ISO 15765‑4 CAN 11‑bit 500 kbit/s.

If you use a terminal app, try this sequence:

ATZ
ATI
ATE0
ATL0
ATSP6
ATDP
0100

Meaning:

  • ATI = identify the ELM firmware/device string,
  • ATSP6 = force protocol 6,
  • ATDP = display the current protocol,
  • 0100 = ask for supported OBD Mode 01 PIDs. (elmelectronics.com)

If 0100 still returns NO DATA or UNABLE TO CONNECT, and your CAN measurements are good, then the remaining suspects are:

  • adapter timing/firmware behavior,
  • app initialization behavior,
  • or a vehicle-side ECU/BSI issue.

6) Do not over-trust “works on another car”

Your Peugeot 407 proving the dongle works is useful, but only partially. The ELM327 family supports multiple protocols, and a device can behave perfectly on one car yet fail on another if initialization timing or protocol negotiation differs. Elm Electronics documents the protocol families supported and notes version differences in ELM firmware. (elmelectronics.com)

Also, the Vgate iCar Pro 2S product page claims:

  • support for all OBD2 protocols,
  • higher baud rate,
  • broad third-party app compatibility. (vgatemall.com)

That means your adapter is supposed to work, but Car Scanner’s official FAQ also notes that some adapters still behave poorly during ECU initialization and may trigger a “Bad adapter” warning. (carscanner.info)

So, in engineering terms: the adapter may be functional but still marginal for this specific car/app combination.

7) Most likely outcomes, ranked

For your symptom set, my probability ranking would be:

  1. Wrong vehicle state / economy mode / weak battery
  2. Fuse F02 fault
  3. Bad contact at pins 6 and 14
  4. App protocol selection / wrong device selection
  5. ELM compatibility/timing issue with this PSA vehicle
  6. Actual CAN wiring or ECU problem

Current information and trends

Current generic Bluetooth OBD adapters such as the Vgate iCar Pro 2S advertise broad protocol support and faster wireless links, but the practical weak point is still ECU initialization quality, not Bluetooth bandwidth. Car Scanner’s own documentation separates “Bluetooth connected” problems from “vehicle ECU communication” problems, which matches exactly your symptom. (vgatemall.com)

In current aftermarket diagnostics, the general trend is:

  • generic ELM adapters for basic OBD data and emissions DTCs,
  • brand-specific tools for reliable access to all modules and functions.

For PSA vehicles, that usually means Diagbox/Lexia if you want dependable communication beyond the simplest generic OBD layer.

Supporting explanations and details

Think of the path as three separate layers:

  1. Phone ↔ Bluetooth adapter
  2. Adapter ↔ OBD socket electrical pins
  3. OBD socket ↔ vehicle CAN network / ECU

Your first layer is working. The fault is in layer 2 or 3.

A very common false assumption is:

“The adapter powers up, so the OBD port is fine.”

Not necessarily. The adapter only needs pin 16 and ground to power up. It still needs:

  • good mechanical contact on pins 6 and 14,
  • a live HS‑CAN network,
  • correct protocol initialization.

That is why the power LED and Bluetooth pairing can be perfect while ECU communication is dead.

Ethical and legal aspects

Citroën’s own handbook warns that access to the diagnostic socket associated with the vehicle’s embedded electronic systems is intended for the Citroën network or qualified workshops with suitable tools, due to the risk of causing malfunctions in electronic systems. (service.citroen.com)

From a safety standpoint:

  • never probe pins carelessly with large meter probes,
  • never short adjacent OBD pins,
  • disconnect the battery before resistance testing,
  • wait for the vehicle network to go to sleep before measuring bus resistance.

Practical guidelines

Recommended troubleshooting order

  1. Try with engine running
  2. Check F02 (5 A)
  3. Inspect OBD pins 6 and 14
  4. Force protocol 6 / ISO 15765‑4 CAN 11‑bit 500k
  5. Run the multimeter tests
  6. Test with Car Scanner or another app
  7. If still no communication, use Diagbox/Lexia

Best practices

  • Use only one OBD app at a time.
  • Delete old paired OBD devices if several have the same name.
  • Make a fresh vehicle profile in the app.
  • Avoid cheap extension cables between the car and the dongle.

If you want one quick practical test

If you want the fastest answer with minimal tools:

  • start the engine,
  • check F02,
  • manually set ISO 15765‑4 CAN 11/500,
  • try a second app,
  • then borrow or use a PSA Diagbox/Lexia interface.

If Diagbox talks to the car immediately, your car wiring is likely fine and the problem is simply the generic ELM/app combination.

Possible disclaimers or additional notes

  • I would not strongly endorse the claim that the 2014 C‑Elysée is generically “blocked” to ELM scanners. That is too absolute.
  • I would also not rely on the idea that because the Peugeot 407 works, the Citroën must work identically.
  • If your goal is only engine fault codes and basic live data, the iCar Pro 2S should have a fair chance once fuse, pins, and protocol are correct. (vgatemall.com)
  • If your goal is BSI, ABS, airbag, coding, service functions, a generic ELM tool is the wrong class of tool; use PSA-specific equipment.

Suggestions for further research

If the above does not solve it, the next useful data would be:

  • voltage at pin 16 to pin 4,
  • resistance pin 6 to pin 14 with battery disconnected,
  • voltage pin 6 to ground and pin 14 to ground with ignition on,
  • exact app used,
  • result of ATI, ATDP, and 0100.

With those four measurements plus the AT command results, it becomes possible to tell whether you have:

  • a fuse/pin problem,
  • a dead CAN branch,
  • or simply an adapter compatibility issue.

Brief summary

The most likely fix path for your Citroën C‑Elysée 1.2 VTi (2014) is:

  • connect with engine running, not just Bluetooth paired,
  • check fuse F02 (5 A) because the Citroën handbook assigns it to the diagnostic socket,
  • inspect OBD pins 6 and 14,
  • force ISO 15765‑4 CAN 11‑bit 500 kbit/s in the app,
  • if necessary, verify the CAN bus electrically (~60 Ω across pins 6 and 14 when powered down). (service.citroen.com)

If all of that checks out and the iCar still cannot talk, the practical answer is: use a PSA-specific diagnostic tool such as Diagbox/Lexia, because the generic ELM adapter/app combination is then the most likely limitation.

If you want, I can give you a pin-by-pin test procedure with photos/diagram style, or interpret your multimeter readings step by step.

Ask additional question

Wait...(2min)
Disclaimer: The responses provided by artificial intelligence (language model) may be inaccurate and misleading. Elektroda is not responsible for the accuracy, reliability, or completeness of the presented information. All responses should be verified by the user.
Report illegal content (Article 16 DSA)