PCR2.1 (CAYC 1.6TDI) - Loud hardcut, no bang with external limiter

First, a reality check on the goal so you don't chase something the platform can't really give you: on a PCR2.1 diesel you're not going to get proper petrol-style bangs/pops. The "bang" on gasoline comes from unburnt fuel igniting in the exhaust on overrun/cut. On a CR diesel with the injectors shut during fuel cut there's no spark and no throttle plate to build the conditions — best case you get a sharp mechanical hardcut sound plus some soot chuff, not real crackles. Just so expectations are set before you burn hours in the map.

On what your attachment actually confirms: the strings line up with your description — EV_ECM16TDI02103L997557M, the 03L906023A 03L997557M pairing, CAYCJ623 and the 9983 revision marker. So it's the right file/SW and it reads clean (the visible regions are just FF padding, which is normal for the flash windows shown). Nothing in the sampled preview exposes the actual map area, so I can't point you at real offsets from this — the body tables aren't in the stratified sample.

On the addresses from the other thread: do not blind-transfer 1A612A / 1D0860 from a 03L906023M file into your 557M. RM vs M (and different 906023 hardware refs) means the compiler layout and table anchors can shift, so an address that's a limiter map in one build can land in the middle of something unrelated in yours. Those addresses are only a starting hint for a WinOLS compare, not a copy-paste.

Practical path:

• Get a DAMOS/A2L or a solid map pack for exactly 03L997557M and identify the RPM/torque limiter and the DFPM / post-injection (Nacheinspritzung) maps in your own file.
• No damos? Load your bin + a known reference of the same SW in WinOLS and diff, then verify each candidate table by axis/shape before touching it.
• The real "hardcut" behavior is the RPM limiter's fuel-cut vs re-enable window — tightening that is what gives the aggressive cut, not disabling overrun DFCO.

To help further, can you confirm: what tool you're reading/writing with (KESS/others, and is this a full OBD or bench/boot read), and whether you actually have a DAMOS/A2L or WinOLS project for 557M or just the raw bin? If someone here has the 557M damos that's the fastest route — otherwise it's a compare job.

I dont have Damos, for this SW. Kess v2 Master

Without a DAMOS for 557M you've got two realistic routes:

• WinOLS + damos search / auto-detect on a known-good project. Load your 557M read in WinOLS, run the checksum module for PCR2.1, then use auto-search to build maps. It won't label DFPM/post-injection for you, but it gets the map structure so you can compare against a reference.
• Compare against the 03L906023M file from the other thread. Even though the SW differs, PCR2.1 diesel layouts are usually similar enough that a byte/structure compare in WinOLS will show you where the limiter/overrun regions moved. That's how you translate 1A612A / 1D0860 into your build instead of blind-copying.

One thing to be clear about: KESS v2 Master only reads/writes the file. It does no map identification at all — you still need WinOLS (or similar) plus a reference/damos to actually find and edit the tables. KESS is just the flashing tool here.

Also worth repeating from before — even if you nail the map hardcut, on a CR diesel don't expect real bangs, just a sharp cut and maybe some soot.

Two things that would help narrow it down:

• Do you have WinOLS (and which version), or only KESS + a hex editor?
• Can you post/link the actual 03L906023M file or its map pack from that other thread? If I can see both structures side by side I can tell you whether a compare is viable for translating those addresses.