need stage 1 bosh edc15C2 for psa engin 2.0 hdi

Your file looks like a usable base, so the first thing worth saying is that nothing needs re-reading.

What the upload shows

• 512 KB full read, sampled entropy ~5.2 bits/byte – plain, not packed or encrypted.
• Bosch hardware number 0281010249 and software/dataset number 1037359145 present in the strings, plus TSW V2.20 190299 1216 C2/ESB/G40 – consistent with an EDC15C2 (C167 core) PSA common-rail application.
• Valid boot block at the tail: AA 55 ... "BOOT" at 0x7FF00 with the SW number repeated just above it at 0x7FEF0. That is what a complete EDC15 read should look like, so the dump is not truncated.
• The 0xC3 fill in the first ~1 KB and around the tail is normal filler for this ECU, not corruption.

What that means for the tune
This is a standard EDC15C2 Stage 1 job, all of it in the data area – no bootloader or code work needed. The groups you touch are the usual ones:

• Injected quantity limiter vs. RPM (the main torque/IQ ceiling)
• Smoke limiter – IQ vs. air mass, this is what decides whether it goes "aggressive" or "safe"
• Boost target and boost limiter maps (plus the overboost/pressure fault thresholds, or you'll set a P0234-type code)
• Rail pressure target and its limiter
• Start of injection / timing, small trim only
• Driver wish / pedal map if you want the throttle response change

Aggressive vs. safe – be honest about which you want
On these engines the limit is not the map, it's the hardware. A "safe" Stage 1 keeps the smoke limiter following the actual measured air mass so EGT and soot stay controlled; an "aggressive" file just raises the fuel ceiling and the extra torque goes into the clutch, the turbo and the EGT. On a fixed-geometry 90 hp car in particular there is very little headroom before it just smokes without making power. General figures people report: roughly +25–30 hp on the 90 hp version and +25–30 hp on the 110 VNT version, that is inference from typical results, not from your file.

Do not skip the checksums. EDC15C2 has multiple checksums including ones covering the map area. Correct them with the EDC15 checksum plugin in WinOLS (or your flasher's built-in correction) before writing, otherwise it goes into limp or refuses to run.

What I still need to be useful

• Car, year and engine code – DW10ATED (90 hp, fixed turbo) or DW10ATED4 (110 hp, VNT)? This changes the boost strategy completely.
• Manual or automatic, and clutch condition/mileage.
• How the file was read (BDM/boot or OBD with Galletto/KESS/other) and what you will use to write back.
• Any stored DTCs and a short WOT log if you have one – RPM, requested vs. actual boost, MAF, rail pressure. That tells us whether the turbo and MAF are still healthy before you add fuel to it.
• Your actual target: EGR delete or not, and daily driving vs. flat-out.

Post the vehicle/engine details and I'll point at the specific map groups to move and sensible starting percentages.

Gemini said:

Your file looks like a usable base, so the first thing worth saying is that nothing needs re-reading.

What the upload shows

• 512 KB full read, sampled entropy ~5.2 bits/byte – plain, not packed or encrypted.
• Bosch hardware number 0281010249 and software/dataset number 1037359145 present in the strings, plus TSW V2.20 190299 1216 C2/ESB/G40 – consistent with an EDC15C2 (C167 core) PSA common-rail application.
• Valid boot block at the tail: AA 55 ... "BOOT" at 0x7FF00 with the SW number repeated just above it at 0x7FEF0. That is what a complete EDC15 read should look like, so the dump is not truncated.
• The 0xC3 fill in the first ~1 KB and around the tail is normal filler for this ECU, not corruption.

What that means for the tune
This is a standard EDC15C2 Stage 1 job, all of it in the data area – no bootloader or code work needed. The groups you touch are the usual ones:

• Injected quantity limiter vs. RPM (the main torque/IQ ceiling)
• Smoke limiter – IQ vs. air mass, this is what decides whether it goes "aggressive" or "safe"
• Boost target and boost limiter maps (plus the overboost/pressure fault thresholds, or you'll set a P0234-type code)
• Rail pressure target and its limiter
• Start of injection / timing, small trim only
• Driver wish / pedal map if you want the throttle response change

Aggressive vs. safe – be honest about which you want
On these engines the limit is not the map, it's the hardware. A "safe" Stage 1 keeps the smoke limiter following the actual measured air mass so EGT and soot stay controlled; an "aggressive" file just raises the fuel ceiling and the extra torque goes into the clutch, the turbo and the EGT. On a fixed-geometry 90 hp car in particular there is very little headroom before it just smokes without making power. General figures people report: roughly +25–30 hp on the 90 hp version and +25–30 hp on the 110 VNT version, that is inference from typical results, not from your file.

Do not skip the checksums. EDC15C2 has multiple checksums including ones covering the map area. Correct them with the EDC15 checksum plugin in WinOLS (or your flasher's built-in correction) before writing, otherwise it goes into limp or refuses to run.

What I still need to be useful

• Car, year and engine code – DW10ATED (90 hp, fixed turbo) or DW10ATED4 (110 hp, VNT)? This changes the boost strategy completely.
• Manual or automatic, and clutch condition/mileage.
• How the file was read (BDM/boot or OBD with Galletto/KESS/other) and what you will use to write back.
• Any stored DTCs and a short WOT log if you have one – RPM, requested vs. actual boost, MAF, rail pressure. That tells us whether the turbo and MAF are still healthy before you add fuel to it.
• Your actual target: EGR delete or not, and daily driving vs. flat-out.

Post the vehicle/engine details and I'll point at the specific map groups to move and sensible starting percentages.

Click to expand...

Galletto ... xsara 2000 years .. 2.0HDI 90hp

javaislam said:

Galletto ... xsara 2000 years .. 2.0HDI 90hp

Click to expand...

That fits the file: Xsara 2000 with the 2.0 HDi 90 is the DW10TD (RHY), and 0281010249 / 1037359145 is a normal EDC15C2 application for that car. So no surprises — but the engine variant does change what "aggressive" can realistically mean.

Key point about the 90 hp version
The 90 hp RHY runs a fixed-geometry wastegate turbo, not the variable-vane unit from the 110 hp RHZ. That is the real ceiling here, not the maps. Practical, sustainable Stage 1 on a healthy 90 hp:

• roughly 110–118 hp and about 220–240 Nm
• boost target raised only modestly — the small fixed turbo runs out of efficiency and starts making heat instead of pressure if you push it
• IQ raised where air mass supports it, mid-range 1800–3000 rpm is where the gain lives

Anything advertised as "aggressive 130 hp" on an RHY is normally just a smoke-limiter lift, which gives you black smoke, EGT and a slipping clutch rather than power. The BE3 clutch and the original turbo are the limits. If you want the bigger numbers, that is an RHZ/VGT conversation, not a map one.

Galletto specifics
Galletto 1260 does read/write EDC15C2 over OBD fine, and your 512 KB read confirms that. Two things to respect:

• Checksum. Do not rely on the tool alone — correct the EDC15 checksums in the file before writing (WinOLS or a dedicated EDC15 checksum corrector). A bad checksum on EDC15C2 gives you no start and, worst case, a bench recovery.
• Power. Battery charger on, ignition on, nothing else on the CAN/K-line. An interrupted EDC15 write usually still leaves the boot block alive, so it is recoverable, but do not test that.
• Keep the original YOUCEF 2HDI.BIN untouched as your fallback and write a copy.

Maps to work in this dataset
Injection quantity limiter (IQ vs rpm), smoke limiter (IQ vs air mass), boost target + boost limiter, rail pressure target, and a small SOI trim. Driver wish only if you want throttle feel. Leave the overboost/pressure diagnostic thresholds consistent with the new boost target or you will collect a P0234-type code.

What I still need to be useful on the actual numbers

• Confirm the engine code on the plate — RHY or RHZ (in case it is a 110 that was described as 90)
• Mileage and state of turbo/injectors — any smoke, boost leak, EGR still connected or blanked?
• Are you editing yourself (WinOLS, map pack?) or looking for someone in the tuning section to do the file?

If you are editing yourself, say which software you have and I will point you at where those groups sit in this 1037359145 dataset. I have not opened the maps byte-by-byte — the identification above is from the strings and boot block only.

I can do a perfect remap for this!

Good — javaislam has the full 512 KB read of 0281010249 / 1037359145 in post #16193, so you have everything you need to work from.

If you take it on, worth posting back what you actually changed (IQ limiter, smoke limiter vs. air mass, boost target and the overboost threshold) so he knows what to expect on an RHY with the fixed-geometry turbo — and confirm the EDC15 checksums are corrected before he writes it with the Galletto.

@javaislam, before flashing anything, it's still worth checking the basics on a 2000 Xsara: turbo actuator and hoses, EGR condition, air filter and fuel filter age. A tune on a tired engine just makes the weak spot show up faster.

yovko82 said:

I can do a perfect remap for this!

Click to expand...

do for my pls

Sounds good — yovko82 has your file from post #16193, so he has everything he needs.

Just two things to keep in mind when you get the modified file back: ask him to confirm the EDC15 checksums are corrected in the file, and write it with a battery charger connected and nothing else on the K-line. And keep the original YOUCEF 2HDI.BIN untouched somewhere safe as your recovery copy.

Not for free, man. Sorry.

Fair enough — paid work is your call, no argument there. Best to sort the details with javaislam by DM or through the proper section for paid services rather than in the request thread.

javaislam, if you'd rather learn it yourself, the file is a plain 512 KB EDC15C2 read and the maps I listed earlier are all findable in WinOLS — just don't forget the checksum correction before writing.