Tuning Wiki
Applies to

Check the hardware and software limits stated in this article.

PSA's 1.6 THP / EP6 turbo petrol engines appear with more than one Bosch MED/MEVD controller and several hardware configurations. Match the engine code, market, gearbox, ECU label, hardware, software, calibration and actual read layout before interpreting a definition or selecting a programming tool. These examples concern Peugeot and Citroën applications; they are not a complete fitment list.

ECU and engine identity

The eTuners THP engine guide associates EP6-DT and EP6-DTS examples with MED17.4, EP6-CDT with MED17.4.2 and EP6-CDTX with MEVD17.4.2. It describes hardware differences including variable valve lift on the latter example. These are tuner application leads, not proof of fitment on every model or market: confirm the installed label and software. Its service intervals and performance assertions are the author's recommendations, not factory schedules or proven limits.

Two commercial MED17.4.2 listings illustrate why both software and calibration matter: a Peugeot 408 1.6 THP 165 identifies hardware 9666319580, software 9663711580, calibration 9679014280; a Peugeot 308 1.6 156 lists the same hardware/software but calibration 9667397780. These are seller identifiers, not independently validated reads, interchangeable files or proof of vehicle fitment. The 408 listing labels torque, spark, injection, turbo and rail groups; its definitions and scaling are unverified and the sold read is not a complete EEPROM/recovery backup.

Definition and read-layout mismatches on the 207 RC and MED17.4.2

A 2017 owner report on a MED17.4 207 RC describes using THP150 material to investigate the file, with a THP175 A2L not matching, and asks how torque and load-related candidate maps work. The exact software and attachments could not be independently checked. A similarly named engine or ECU does not prove a definition fits. File version, read origin and offsets, map dimensions, units, factors, selectors and checksum should be verified for the actual ECU rather than copying forum addresses.

A separate 207 MED17.4.2 owner report compares an OBD read against a definition file and asks about different layouts and filled regions. Suggested explanations were read coverage, tool format and software differences, but the actual cause was not established. The programmer's actual-versus-virtual read mode, memory regions and software identity should be checked before comparing files or treating a read as a full recovery image.

EP6DT sensor locations and logging

A hosted Citroën MED17.4/EP6DT training reproduction describes direct injection, a fixed-geometry twin-scroll turbo, cam timing and a high-pressure fuel rail. It distinguishes a pressure/temperature sensor before the throttle from the manifold-pressure sensor after it. Sensor location and pressure reference should be labelled when comparing boost data, especially across a throttle transient; these details do not establish that every later THP has the same hardware. The document is training material; the vehicle-specific workshop procedure applies to diagnosis and component replacement.

Before and after calibration work, compare equivalent conditions and log available requested and actual load/boost, fuel rail pressure, lambda, ignition timing and knock corrections, temperatures and fault state. Check mechanical timing, fuel supply and turbo plumbing against the applicable service documentation; an apparent calibration problem can also have a hardware cause. No universal numerical ignition, lambda, rail-pressure or boost targets are established here.

Read, write and recovery

Microtronik's HexProg II MED17.4.2 listing advertises OBD, case-closed bench and case-open boot operations for its supported applications. This is one tool's coverage, not proof that every MED17.4.2 or file supports all three. Check the exact controller, tool version, required connections, read coverage, checksum and recovery route. Keep the vehicle-specific original read and configuration and retain functioning diagnostics and emissions equipment.

Not established

  • The cause of the differing memory layouts reported on the 207 MED17.4.2.
  • Validity of any linked commercial map pack or tune; none has been independently validated by this wiki.

See also PSA ECU identification and tuning guide and PSA HDi and BlueHDi diesel tuning guide.

Continue the conversation

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