Bosch EDC16C34 Immo Off and Original Files: Peugeot, Citroen, Ford, Volvo 1.6 HDi/TDCi
A Citroen Berlingo 1.6 HDi comes in on the back of a recovery truck. It cranks, it won’t fire, and the owner eventually admits the engine ECU came from a breaker after the original one died during a remap that someone started over OBD and never finished. You pull the unit and the Bosch label says 0281013872. That hardware number appears on 37 of the files in our catalogue, more than any other EDC16C34 part, and the story attached to it is typical of this family: huge numbers of vans and family cars, plenty of used ECUs moving between them, and a lot of flashes that stopped halfway.
This guide covers the Bosch EDC16C34 as fitted to the PSA 1.6 HDi and the same engine family in Ford, Volvo, Mazda and Fiat vehicles, where it’s badged 1.6 TDCi, 1.6D and so on. It’s written from the 307 EDC16C34 products currently published in our shop, so the part numbers, software numbers and counts below come from real reads rather than from a parts catalogue. Two jobs dominate the EDC16C34 requests we see: getting a car back onto a clean original file, and getting an ECU to accept a car it wasn’t built for (immo off, virgin or clone). Both get proper space below, next to the EGR, DPF and tuning files that make up the rest of the catalogue.
How to recognise an EDC16C34 on the car and on the bench
Don’t identify this ECU from the model year alone. The 1.6 HDi and its Ford and Volvo twins ran on EDC16C34 for several years, but later versions of the same engines moved to other controllers (EDC17 or Continental SID807, depending on version and market). Two cars that look identical in the car park can have different ECUs, so the label and the read decide, not the registration document.
The Bosch label is the first thing to check. On the EDC16C34 units we see, it carries:
- Bosch hardware number: ten digits starting with 0281. Every hardware number in our EDC16C34 data follows that pattern, for example 0281011629, 0281012982 or 0281014444.
- Bosch software number: ten digits starting with 1037 on most units, with a smaller group starting 1039 (for example 1039398221, which appears on five files in our catalogue). This is the number that decides whether a file fits.
- Type designation: most labels print EDC16C34 itself, which saves a lot of guesswork compared with families where you have to work it out from the hardware number.
- Vehicle maker part number: Ford and Volvo units add their own reference. In our titles you’ll see Ford numbers built on the 12A650 base, such as 6S61-12A650-UA, 5S61-12A650-AF and 4N51-12A650-BB, and Volvo numbers such as 31211076. PSA units carry a PSA reference as well.
If the label is damaged, most flashing tools will show the numbers from the ECU itself, and the software number inside the file is the one that matters anyway. Our guide on reading ECU label numbers goes through the fields in more detail if you’re training someone new on the bench.
Hardware numbers that come up most often
These are the most frequent EDC16C34 hardware numbers in our catalogue, with the number of published files for each. Clicking a number shows every file we hold for it.
- 0281013872: 37 files. The samples we hold with it include a Citroen Berlingo, a Citroen C5 and a Peugeot 207.
- 0281011775: 17 files. In our samples this is the Volvo number, on the S40, C30 and V50.
- 0281012486: 12 files, including Ford C-Max reads.
- 0281013332: 11 files, seen on the Peugeot 308 and Citroen C4.
- 0281011629: 10 files, on the Peugeot 307 and Citroen C4.
- 0281014444: 10 files, the Peugeot Bipper number in our samples, including a virgin file.
Other numbers further down the list include 0281011863 (10 files), 0281013871 (9), 0281014729 (7), 0281012982 (6) and 0281012619 (6). Notice that one hardware number regularly covers several vehicles: 0281012982 turns up on a Citroen Jumpy, a Peugeot Expert and a Peugeot 308 in our data. Hardware alone never tells you which file to buy.
Two software numbers in one title
Some of our EDC16C34 titles list two software numbers. A Volvo S40 file is titled with 1037375523 and 1037397449, and a Volvo C30 file with 1037375523 and 1037505785. In cases like this the first number is usually what was printed on the label when the ECU left Bosch, and the second is what the ECU actually contained when it was read, after one or more dealer updates. On the Volvo files, 1037375523 looks like the label number while the flash itself has moved on. Always match the software number from your read. If you only have the label, say so when you ask for a file, because we’ll need to allow for updates.
Vehicles and engines in our EDC16C34 catalogue
The 1.6 HDi was a shared PSA and Ford engine, which is why a single ECU family spreads across so many badges. The table below shows how the 307 published EDC16C34 products break down by brand and model in our catalogue. Counts are published products today, not a list of every car that ever used this ECU. Our product data doesn’t carry engine codes for this family, so engines are described by badge and displacement rather than by code.
| Brand | Models in our catalogue (files) | Engine | Files in our catalogue |
|---|---|---|---|
| Peugeot | Partner (27), 207 (24), 407 (23), 206 (19), 307 (19), 308 (10), Bipper (9), 3008 (3), Expert (2), 5008 (1) | 1.6 HDi | 137 |
| Citroen | C4 (37), C5 (15), C3 (10), Berlingo (9), C4 Picasso (9), Nemo (5), Jumpy (3), Xsara (2), Xsara Picasso (1) | 1.6 HDi | 91 |
| Ford | Focus (37), C-Max (4), Fusion (4), Fiesta (3) | 1.6 TDCi | 48 |
| Volvo | S40 (14), C30 (3), V50 (1) | 1.6D | 18 |
| PSA (generic) | Not tied to one model, virgin files among them | 1.6 HDi | 5 |
| Fiat | Scudo (3) | 1.6 diesel | 3 |
| Mazda | Mazda 3 (3) | 1.6 diesel | 3 |
The Citroen C4 and the Ford Focus tie at the top with 37 files each, which says a lot about how many of these cars are still being kept on the road. The light commercials are strong too: Partner, Berlingo, Bipper, Nemo, Jumpy, Expert and Scudo make up a big share of the PSA list, and those vans tend to arrive with high mileage, EGR trouble and a history of cheap repairs.
Where a product’s title and its tags disagree, trust the title and the numbers in it. There are also two VW products that sometimes show up next to EDC16C34 in searches. They’re titled EDC16U34 and EDC16CP34, which are different ECUs for VAG engines, and they aren’t interchangeable with anything in this guide.
Example EDC16C34 files you can compare with your read
These are real products from the catalogue, picked to show the spread of vehicles and file types. Where the title carries no hardware number, the column says n/a and you match on the software number.
A few pairs in that table deserve a second look. The Peugeot 407 original on 1037375958 and the EGR off file for the same software sit side by side, so a workshop can keep the stock file on record, write the modified one, and still go back later. The Citroen Jumpy file on 1037386162 shares its hardware and software with a Peugeot Expert file, which is what you’d expect from those twin vans. The Fiat Scudo belongs to the same van family, and its original file (0281013869, 1037393467) uses a software number that also appears on a Citroen Jumpy EGR off file. Badges change. Calibrations often don’t.
File types for EDC16C34 and when each one is the right call
Here’s how the EDC16C34 catalogue splits by file type. One product can sit in two categories (a combined DPF and EGR file, for example), so these counts overlap and shouldn’t be added together.
- Original File: 177 files
- EGR Off: 75 files
- Chip Tuning: 53 files
- DPF Off: 13 files
- Immo Off: 8 files
- Virgin: 3 files
Original files: the job most EDC16C34 buyers actually have
More than half of the EDC16C34 catalogue is original (stock) files, and that matches what comes through the door. The usual reasons are dull but real. A remap started over OBD failed and the ECU no longer talks. A previous tuner didn’t keep the stock read and the owner now wants the car back to standard before selling it or before an inspection. The car has a modified file of unknown origin and you want a clean reference to compare against. Or the flash is corrupted after a voltage problem and you need a known-good file for the same software to write back.
Matching an original file properly on EDC16C34 comes down to three checks. First, the hardware number should match, or at least be one that’s known to run the same software. Second, the software number from your read must match the file exactly; a neighbouring number from the same year is a different calibration, even if the car seems to run on it. Third, look at what you actually need to write. An original flash file restores the calibration, but if the problem is in the EEPROM (immobiliser data, adaptations) the flash won’t touch it.
An original file is also the honest answer when a customer blames the ECU for a mechanical fault. Writing stock software to a 1.6 HDi with a sticking turbo actuator, a leaking injector seal or a blocked EGR valve won’t fix any of those. What it does do is take the software off the list of suspects, which is often worth the money on its own.
EGR off and DPF off
EGR files are the second largest group, 75 in our catalogue, and it isn’t hard to see why. The EGR valve on these engines fails often, and on the vans in particular it tends to be heavily coked by the time anyone looks at it. An EGR off file stops the ECU running EGR control and logging the related faults. DPF off files (13 here) do the same for the particulate filter side, and several products, such as the Peugeot 3008 and Mazda 3 files, combine the two.
Be straight with customers about this. Removing or disabling EGR or DPF is not road-legal in the EU, the UK and many other countries, and a car with the DPF removed will fail an emissions inspection in most places that check for it. These files are for off-road use, motorsport, or export to markets where the rules allow it. On PSA-based cars with a DPF additive system, parts of the DPF strategy and its warnings can involve modules other than the engine ECU, so don’t promise that one engine file will clear every light on the dash. And a blocked filter or a sticking valve is still a mechanical fault: if the root cause is oil getting past the turbo seals or an injector washer leaking, the next problem arrives a few thousand miles later.
Chip tuning
There are 53 tuning files for this family, such as the Citroen C5 stage 1 file on 1037393452, and a tuned file for the Citroen Nemo on 1037391748 that sits next to the matching original in the catalogue. Tuning a small diesel that’s done 200,000 km without checking its condition first is how you end up with a boost-deviation limp mode and an unhappy customer. Check boost, rail pressure and smoke on a road test before writing anything, and keep the original read somewhere safe, in two places.
EDC16C34 immo off, virgin files and swapped ECUs
The immobiliser questions are why this page exists, so here’s the practical version. On the PSA cars in this family the engine ECU is paired with the BSI (the body control unit), and the keys are paired with the BSI. Fit an ECU from another car and the BSI and ECU don’t recognise each other: the engine won’t run, or it catches and dies straight away. Ford, Volvo and Mazda use their own immobiliser logic around the same Bosch hardware, with the pairing held by other modules on those cars, but the result on the bench is the same. A second-hand ECU won’t start the car until you deal with the immobiliser data.
There are three ways to deal with it, and they aren’t equal. For background on the method itself, see our immo off explainer. The notes below are specific to EDC16C34.
1. Clone the old ECU into the replacement
If the customer’s original ECU still reads, even if it’s dead in the car, cloning is almost always the best route. Read the flash and the EEPROM from the old unit, write both to the replacement (same hardware, ideally same software), and the car sees its own ECU again. No coding, no disabled security. That’s why the first rule on this family is to read the EEPROM as well as the flash, every time, before you do anything else.
2. Virgin the replacement and let the car learn it
A virgin file puts the ECU’s immobiliser data back into an unlearned state so the car can pair with it. On PSA cars that learning step is normally done with Diagbox or a comparable diagnostic tool, and it needs the vehicle’s access code, which the owner should have with the car’s documents. We have three virgin files for this family, including the PSA 0281012982 virgin dump and the Peugeot Bipper 0281014444 file shown above. The difference between an original, a virgin and a clone file is covered in our guide to original, virgin and FRF files.
3. Immo off
An immo off file disables the ECU’s immobiliser check, so the engine runs without the ECU confirming the key. It’s the fallback when the original ECU is gone, the BSI is being replaced too, the access code isn’t available, or an engine is running on a test stand or in a race car. We list eight immo off files for EDC16C34, a small number next to 177 originals. That tells you something: most immobiliser jobs on this family are solved by cloning or virginising, and immo off solutions often have to be prepared from the customer’s own read rather than bought off the shelf. The Fiat Scudo 0281013869 immo off file is one of the ready-made ones.
A few practical points. On the EDC16C34 units we’ve handled, the immobiliser data sits in the external EEPROM, so an immo off job normally starts with a bench read of that chip, and an EEPROM-only write won’t help if the flash is also corrupted. The immobiliser warning light may stay on, and other modules may still log that they can’t see the engine ECU’s response, depending on the model. Immo off should only be done on vehicles the customer owns or has the legal right to work on. If they can’t show you that, walk away from the job.
Reading and writing EDC16C34: OBD, bench and BDM
EDC16C34 can be read and written over OBD on most versions, which is why so many of them get tuned in car parks. OBD gives you the flash (the program and calibration), not the EEPROM, and it relies entirely on the car holding a steady voltage for the whole write.
Bench work means taking the ECU out and connecting to it directly. On EDC16, the ‘boot’ option in many tools is actually BDM, a debug interface reached through pads on the circuit board. BDM gives access to flash and EEPROM and is the usual way to recover an ECU that no longer responds on OBD. It does mean opening the case, so take care with the lid and seal if the unit is going back into an engine bay. Our guide to OBD, bench and boot mode covers the differences in more depth. It’s written around EDC17 and MED17, but the rules on power and backups are the same here.
Tools seen in our EDC16C34 files
Where a product records the tool it was read with, the numbers for this family are Flex on 80 files, New Trasdata on 35, KESS V2 on 20 and KTAG on 20, with one read done on a Hexprog. KESS V2 reads are usually OBD reads of the flash. KTAG, Flex and New Trasdata reads are more often bench or BDM reads, which is why they’re the ones you want for immobiliser work. Reads from Galletto or Autotuner are fine to send too, as long as the file is complete.
Precautions before you write anything
- Put a proper power supply on the car or the bench, not a battery charger. A voltage dip during an OBD write is the most common way to end up with a dead EDC16C34.
- Make a full backup first: flash and EEPROM, saved in two places, with the hardware and software numbers in the file name.
- Check checksums. Your tool may correct them on write, or the file may already be corrected. Confirm which before you press the button.
- Switch off anything that pulls current during an OBD write (lights, blower, heated screen), and let a hot engine cool so the radiator fan doesn’t start mid-write.
- EDC17-style TPROT tuning protection isn’t usually what blocks you on EDC16C34. A failed write here is far more often down to power, a poor OBD connection or the wrong software selected in the tool.
Bench notes and typical EDC16C34 problems
Dead after a failed OBD flash
The ECU no longer answers on OBD, the car won’t start, and the dash may show a communication fault. On most versions the processor is fine and only the flash is incomplete. Take it to the bench, read what’s left via BDM if you can, then write a matching original file for the software number that was on it.
Used ECU fitted, car won’t start
The classic breaker’s-yard problem. Before blaming anything else, compare the donor’s hardware and software with the original ECU. If the donor has different software, cloning the original’s flash and EEPROM onto it avoids odd running faults as well as the immobiliser issue. If the original ECU is gone, you’re into virgin or immo off territory (see above).
Limp mode after tuning
A 1.6 HDi or TDCi that drops into limp mode after a remap usually has a boost or rail-pressure deviation, and the file has only exposed the fault. Log boost demand against actual, check the turbo actuator and hoses, and look for oil in the intake. These engines have a well-known history of turbo failures linked to oil feed contamination and leaking injector seals, so check the engine before the software. If the car ran fine on stock and fails on the tuned file with a healthy engine, go back to the original and confirm you were given a file for your exact software number.
Wrong file for the software
A file that almost fits is the worst kind. It can start, idle and even pass a short road test, then throw faults under load or refuse to regenerate the DPF. Compare the software number from your own read with the product title every time.
Questions workshops ask about EDC16C34
Can I read the EEPROM on an EDC16C34 over OBD?
On most tools and versions, no. OBD gives you the flash. For the EEPROM, which you need for clone, virgin and most immo off work, plan on a bench or BDM read with a tool such as KTAG, Flex or New Trasdata. Check your tool’s own support list for the exact hardware number, because coverage varies.
Is a Ford 1.6 TDCi EDC16C34 file the same as a Peugeot 1.6 HDi file?
The hardware is closely related, but the software isn’t interchangeable. Ford, Volvo and Mazda calibrations have their own software numbers and their own immobiliser handling. Match the software number from your read, not the engine size.
Why do some product titles show two software numbers?
Usually because the label shows the software the ECU was built with and the read shows what it’s running now, after updates. The Volvo files with 1037375523 and a later number are good examples. Buy against the number in your read.
Do I need an immo off file, a virgin file, or neither?
If the original ECU can still be read, usually neither: clone flash and EEPROM onto the replacement. If the original is gone but you can run the PSA learning procedure with the access code, a virgin file is the cleaner route. Immo off is for cases where neither of those works, and only on a vehicle the customer owns.
Will an original file fix my EGR or DPF fault?
Only if the fault was caused by modified or corrupted software. A blocked filter, a stuck valve or a split sensor pipe needs a mechanical repair. An original file does give you a clean baseline for diagnosis, which is often why workshops buy one.
My EDC16C34 died during a write. Is it finished?
Rarely. In most cases the processor survives and the ECU can be recovered on the bench by writing a full matching original file via BDM. If you saved the EEPROM before the attempt, you’re in very good shape.
If the EDC16C34 file you need isn’t listed
We don’t hold every calibration, and immo off solutions in particular are often done to order from the customer’s own read. If your file isn’t in the catalogue, send the Bosch hardware number (0281…), the software number from the read (1037… or 1039…), any Ford, Volvo or PSA part number on the label, the vehicle, engine and year, and the tool you used. A full read of flash and EEPROM helps most of all, especially for immobiliser work. Put those details into the file request form, and have a look through the EDC16C34 family page first in case the file is listed under a slightly different title.
More ECU guides
How to Read Your ECU Label: Hardware Number, Software Number and Part Number Explained
Nine out of ten "the file does not work" cases come down to one thing: the file was made for a different software version. Every listing…
EDC16C7 and EDC16CP31 Immo Off / Virgin: Fiat, Alfa, PSA and Chrysler Diesel ECUs
Two Bosch diesel ECUs from the mid-2000s generate a steady stream of immobilizer requests: the EDC16C7 (Peugeot 307/407 2.0 HDi, Citroen C4/C5, Ford 2.0 TDCi shared…
Original File, Virgin File or FRF: Which ECU File Do You Actually Need?
Customers often ask for "the file for my ECU" and are surprised that we have three or four different kinds for the same part number. Each…