Tuning Wiki
Applies to

Check the hardware and software limits stated in this article.

PSA diesel models use several Bosch, Siemens/Continental and Delphi ECUs across HDi and BlueHDi engines. This guide separates examples by engine, ECU and evidence; the badge or displacement alone does not establish injector type, turbo control, calibration or programming access. Record vehicle, market, engine code, transmission, ECU label, manufacturer and Bosch numbers, software and calibration before research or programming.

Early 2.0 HDi: mechanical wastegate example

HDI Tuning's EDC15C2 file comparison discusses a Peugeot 306 2.0 HDi 90 and explains its pedal request, torque/fuelling and smoke-related controls. The author identifies this particular engine's boost control as a pressure-actuated mechanical wastegate, not an electronically commanded boost valve. This is a specific example, not a rule for all 2.0 HDi engines. Inspect the actual turbo, actuator, hoses and control system before expecting a software boost target to move it. The document's interpretations and remap comparison are the author's, not independently validated file definitions.

1.6 HDi EDC16C34: maps and diagnostics

A 2026 map-identification discussion for a Citroën Berlingo 1.6 HDi identifies the ECU as Bosch 0281013872, PSA 9664843780 and software 1039398221. Candidate groups for driver demand, torque, injected quantity, injection timing, rail and boost are proposed there, but selectors, factors and map roles remain unresolved. The attachment and claims are unverified, so the proposed names and addresses are hypotheses to examine in that exact read.

A separate Peugeot 207 1.6 HDi seller listing uses the same displayed Bosch hardware number but software 1039398203. It illustrates why a hardware number alone is insufficient to select the Berlingo definitions. Seller labels and stock status have not been verified; the underlying reads may differ in software, calibration and coverage.

Citroën's 2007 training reproduction covers DV6TED4 with EDC16C34 and DW10BTED4 with SID803/803A in separate sections. It uses absolute manifold pressure in air-system checks and distinguishes requested and measured values. Interpret units, ambient pressure and measurement location correctly; check sensor data, vacuum and actuators and intake/charge leaks against the applicable service procedure before changing boost controls. It is training material and explicitly not an after-sales procedure; it does not establish identical hardware on every variant.

HDI Tuning's 16-valve 1.6 HDi/TDCi hardware guide describes different turbo arrangements for its 90 and 110 examples. A VNT command is not automatically a measured vane position; confirm the actual hardware and feedback. Compare requested and measured boost and rail pressure, airflow, fuel demand, fault state, coolant temperature and regeneration state at comparable loads. Do not apply the 306's mechanical-wastegate model to this engine by analogy.

An owner's Peugeot 207 EDC16C34 tuning thread documents several file revisions on a modified car, with heavy smoke reported on an early test before the file was revised. The shared settings and outcomes are not validated calibration guidance. Keep identifiable original and revised files, record hardware changes, and investigate smoke and measured air/fuel behaviour rather than treating a perceived power gain as validation. A separate modified 207 guide illustrates the relationship between pedal torque request, injection quantity, rail pressure and injection duration; its hardware and assumptions are specific to that build, and its values should not be transferred as generic limits.

2.0 HDi SID803/803A: feedback and calibration examples

The Citroën SID803/803A training describes requested and measured turbo pressure as absolute pressure; atmospheric pressure corresponds approximately to zero gauge boost. For the documented DW10BTED4 system, compare those values with turbo solenoid control and requested position, plus measured position where fitted. Its position feedback sensor is equipment-dependent; a command alone does not prove actual actuator travel. Follow the current vehicle-specific diagnostic procedure when checking vacuum supply, linkage, actuator and feedback.

A DW10BTED4 SID803 forum discussion reports P2562 and jerking with suspected position feedback trouble; the replies address vacuum integrity, movement and sensor response, and one describes a different EGR-related experience. These are anecdotal observations, not a confirmed diagnosis for every P2562 or a calibration target.

A seller's Peugeot 807 2.0 136 hp SID803A example identifies hardware 9661642180 and software 9664807480. It labels a 16 × 16 table as fuel quantity versus engine speed and torque. That role, axes, scaling and applicability are seller claims, not independently validated definitions; confirm them in the exact read before using them.

1.6 HDi and BlueHDi: EDC17 turbo hardware

A reproduced DV6DTED EDC17C10 technical document describes a fixed-geometry Mitsubishi turbo whose vacuum-operated pressure regulator has a position sensor. Consequently, the presence of feedback does not by itself identify a variable-geometry turbo. Identify the actuator and valve on the actual car, and interpret position, solenoid control and boost readings accordingly. The reproduction contains mixed DV6 headings; verify applicability against the vehicle's current service information.

For a particular conversion from a TD02 wastegate turbo to a GTD1244VZ 819872 / 9804119380 VNT, HDI Tuning's 8-valve retrofit guide says its 1.6 HDi 75/95 EDC17C10 examples require position-sensor wiring changes, while its 1.6 BlueHDi 75/100 EDC17C60 examples normally do not. The author also reports vehicle-to-vehicle wiring variation. This is a conversion-specific guide, not a universal pinout: document the original wiring and verify the correct sensor connections and diagnostic response for the particular vehicle and replacement turbo.

In an EDC17C60 1.6 BlueHDi 120 tuning overview, HDI Tuning describes some boost and rail maps stored as 8-bit data requiring a factor and offset. Raw bytes are therefore not necessarily engineering units: verify data width, scaling, axes and the conditions selecting each table in the exact file. The article does not identify a specific software version or publish independently validated definitions; its map counts and suggested settings are not universal.

1.5 BlueHDi MD1CS003: torque modelling

HDI Tuning's 1.5 BlueHDi MD1CS003 overview describes pedal request, an internal torque model including friction, torque monitoring and multiple boost maps. Its map counts and numerical modifications are the tuner's examples, not universal definitions or safe targets. Understand torque request, limits, fuel conversion, airflow, boost, rail and monitoring together for the exact file; investigate monitoring faults and retain functioning diagnostics rather than simply suppressing them.

A Peugeot 308 1.5 130 hp listing labels a Bosch MD1CS003 file with hardware 9818703480 and software upgrade 9693382980; it lists torque monitoring, torque/fuel conversion candidates, rail and VGT among its groups. The seller displays a table it calls a torque limiter against rpm and fuel per stroke. Its actual function, axes and selector are unverified; do not treat its label or numerical entries as confirmed limits. The listing says its file does not include a full backup or EEPROM.

The same MD1CS003 tuner describes torque-to-injection conversions that taper outside the original torque range, and corresponding reverse calculations. It recommends considering the axes and both conversion directions together, alongside airflow-based fuelling and monitoring. This is the tuner's description, without a published exact calibration to independently verify; it is a lead for analysing a matched file, not a general instruction to alter conversion or monitoring maps.

Another 1.5 BlueHDi 130 MD1CS003 vendor example lists Bosch 10SW070417, hardware 9826975080 and software upgrade 9694717280. The seller notes that OTP regions can differ between files. Matching numbers or file size alone does not prove full read coverage or make vehicle-specific regions interchangeable; confirm exact tool support, areas read and recovery provisions.

2.0 BlueHDi Delphi examples and pre-tune checks

For a Peugeot 308 T9 2.0 BlueHDi 174 hp DCM7.1A, ETP's listing associates hardware 9818035080 with several software upgrades, including 9692968980 and 9693993380; another vendor separately lists the first upgrade for a 308. These are catalogue claims, not proof that files are interchangeable. Record the actual hardware, software and upgrade from the vehicle.

A Peugeot 308 2.0 DCM6.2A seller listing labels one displayed table as maximum torque against coolant temperature and engine speed, along with separate injection, boost and rail groups. Its public page does not establish the matching hardware/software and the labels and axes are unverified. It illustrates why operating conditions and protective derates matter when interpreting a candidate map; its values are not measured engine output or tuning targets.

Diagnose existing aftertreatment faults before interpreting a tune. One workshop report records a 2015 Peugeot Partner 1.6 BlueHDi BHZ logging P20E8, where pressure testing and electrical checks led to contamination and corrosion at the tank-pump connector. That is one case, not a universal cause of the code. Use the correct diagnostic procedure and preserve operational aftertreatment and fault monitoring.

2.2 HDi: EDC15C2 and EDC16CP39

A Peugeot 406 2.2 HDi EDC15C2 map discussion identifies hardware 0281010877 and software 1037353776. The author flags some graph labels as mistakenly using mg where mm³ was intended; images and files require forum access and have not been independently checked. It is a useful lead on the importance of confirming fuel-quantity units and axes, not a verified definition for another read. Mass and volume units are not interchangeable without accounting for fuel density.

A reproduced DW12BTED4 EDC16CP39 training document describes its 170 hp engine as having two fixed-geometry turbos operating sequentially in parallel, four turbo-control valves, position feedback on the VT2 valve, and two boost-pressure sensors. The document distinguishes single-turbo operation, transition and twin-turbo operation. For that arrangement, identify which pressure sensor and actuator each logged parameter represents and compare behaviour across the transition; two turbos do not automatically imply two variable-geometry turbos. Do not transfer the arrangement to other 2.2 variants.

For a different application, HDI Tuning's 4007/C-Crosser 2.2 156 EDC16CP39 guide describes a 2 MB performance-map flash and discusses both OBD and board-level access. A calibration flash read does not establish complete recovery coverage; check the actual ECU, tool protocol and all memory areas required for that vehicle.

2.7 and 3.0 V6 HDi: separate systems

A 2006 Peugeot 407 2.7 HDi discussion identifies SID201 and reports low power and P0243 after a component replacement, with replies debating the correct actuator and wiring checks. The discussion does not establish a confirmed universal cause. Resolve baseline faults using the specific vehicle's diagrams, tests and actual turbo hardware before calibration work.

A separate Peugeot 407 3.0 V6 HDi vendor guide identifies EDC17CP11 and describes tool-specific OBD and bench routes. It is a different engine/ECU example from the 2.7 SID201; quoted performance figures are vendor claims, not calibration targets or proof of gearbox compatibility.

Rail pressure and programming discussions

In one tuner's 2.0 HDi/TDCi DCM3.5 repair example, measured rail pressure fell below request under load and one injector had excessive return flow; the author reports pressure recovered after replacement. The article also lists fuel supply, regulator and pump problems as possibilities. Model and software are not specified, and the case does not establish the cause of every low-pressure fault. Diagnose against the exact vehicle procedure before changing fuel limits.

A 2020–2022 MD1CS003 community thread contains differing accounts of PSA BlueHDi read/write and starting behaviour, without full ECU and software identification. Historical forum experiences are leads rather than current tool coverage: verify exact-unit unlock, read and write method, checksum and recovery using the tool provider's current instructions.

Programming and other PSA diesel families

For selected MD1CS003 units, Magicmotorsport Flex 8.23 advertises a Korhex boot-glitch unlock followed by bench, and lists internal flash and EEPROM operations for that protocol. AutoTuner describes bench normal read after its mail-in unlock on supported MD1CS003 units. These are different vendor-specific workflows, not proof that all MD1CS003s are locked or that every unit is supported. Record exact hardware, software, read areas, checksum and proven recovery method; check the current tool documentation and the MD1CS003 hub.

As a distinct 2.0 BlueHDi example, Alientech's historical K-TAG release (Russian) lists Delphi DCM7.1A on selected PSA DW10 applications with its boot protocol. Do not transfer Bosch MD1 definitions, pinouts or access to Delphi. Siemens SID is another distinct family. Keep aftertreatment and diagnostic functions operational, and consult exact-vehicle service information.

For older rotary-pump diesels see the Peugeot and Citroën rotary-pump guide; for commercial vans see the Boxer and Relay diesel guide. For related engine/ECU examples see the PSA ECU identification and tuning guide and PSA 1.6 THP petrol guide.

For which high-pressure pump and injector family is fitted to each engine code see Peugeot and Citroën diesel injection pumps and injectors by engine code; for rail-pressure limits, injector upgrades and coding see the Peugeot HDi injector and high-pressure pump tuning guide.

Continue the conversation

If this topic interests you, consider joining the following forums. They host material referenced in this article.