Renault Clio II 1.5 dci - DELPHI HW: 8200318851 - Need HELP

Posts related to map selection, map location, correct map treatment.

Renault Clio II 1.5 dci - DELPHI HW: 8200318851 - Need HELP

Postby luuluu735 » Sun Sep 20, 2026 10:42 pm

Hi everyone,

I'm fairly new to ECU remapping and I'm currently learning by working on my own car, so please bear with me if some of my questions seem basic!

Here's what I'm working with:
- Renault Clio 2, 1.5 dCi, 65hp
- ECU: Delphi DDCR
- Hardware: 8200318851
- Software: 8200420213

My goal is to do a Stage 1 tune with EGR off, but I'm a bit stuck. I can't find the axes for this ECU anywhere, and without them it's tricky for me to tell the maps apart - a lot of them look pretty similar in the hexdump (progressive curves), so I can't really confirm which one is torque, injection, EGR, boost, etc. I've searched around but haven't found anything solid that matches this exact hardware/software combo.

If anyone has a KP/Damos file for this Delphi DDCR, or even just knows some known map addresses/axes for this platform, I'd be super grateful for a hand. Happy to post screenshots of specific maps if that helps anyone help me identify them.

Thanks a lot in advance, and looking forward to learning from you all!

Here's my original ECU dump, in case it helps: https://files.catbox.moe/5536g1.rar

luuluu735
New user
 
Posts: 3
Joined: Sat Sep 12, 2026 4:27 pm
Location: france

Re: Renault Clio II 1.5 dci - DELPHI HW: 8200318851 - Need H

Postby DDCRJimny » Wed Oct 28, 2026 9:19 am

I am analysing another 65 hp DDCR at the moment. A few things may help before you transfer addresses from a different software version:

These calibrations are normally unsigned 16-bit little-endian. In the 40 KB reads I checked, the compact file corresponds to the 0x6000 calibration area of a 256 KB image. Be careful with 256 KB files found online: some are only a calibration block padded with FF and contain no executable code.

For my 8200334540 software, the likely EGR table is around compact offset 0x51A6, but I would not use that address directly for 8200420213. First compare the surrounding bytes and both axes. RPM axes are easy to recognize as sequences such as 500, 1000, 1500, 2000 etc. in little-endian form.

Also verify the checksum before writing. On my file the checksum word is at compact offset 0x0002 and is the 16-bit sum of bytes over the range declared in the header. The exact end address is software-specific, so read the header rather than copying my range.

DDCRJimny
New user
 
Posts: 7
Joined: Wed Oct 28, 2026 8:58 am
Location: Bucharest


Return to Map Location and Addresses

Who is online

Users browsing this forum: No registered users and 0 guests