Another question, is there another way around only for goal to delete emission related DTC? I am not looking forward to modify performance. What other method can I use to open and edit the .bin file? I know C language. I also learned assembly language in college. It is not something I'd love to do for living but I don't mind to pick it up again.

Yes sir. Please see the attached Flash file.
Thank you for your help.

Thank you so much. I loved the way you not only shine light to my question but also showed me how to get there. Just one more dumb question and I like to confirm. Will the 3.2 VR6 motor ME 7.1.1 definition file work for my 2.8 VR6 motor bin file with ME7.1.1? What factors are the key here in order to decide if the definition files are same between two flash file?

Large parts of the BDF and BDE map addresses line up with that BFH file but some need offsets.

-8  -4  -2  -1  0  1  2  4  8  are the most common offsets that find them with that file (all ME7.1.1 24V/R32 seem to be very closely related) if you line it up in winOLS demo, but I have just lined it up against my BDE master file and the offset 1 has lined some areas up so those values may need to be changed by that amount.

PROKON - Codeword SLS - 181C3

No files really line up with the variances in the code and neither will this one.

It is a full def file though so you will have to learn how to pick out the maps  - there should be about 4 lambda maps in the definition file - these always seem to line up with the R32/V6 4motion/VR6 24V files.

As said earlier - try the offsets from -8 to 8 and scroll up and down the ecu, some maps should line up.

Sorry, I didn't mean to post lambda, was doing three things at once and playing with those maps on another ecu at the time!   

I actually meant the 14x14 maps in the R32 ecu which are usually the easiest to find and together on these ecu's (should be GGHFM for the MAF corrections if I remember right).

Try this;

Ctrl + 2 to line the maps up. Go to the BFH file and go to GGHFM (I think it is) and in there are some 14x14 maps. Right click one of them with your mouse and go to "view in hexdump" and it will flash where the point is in the binary code.
Usually with these maps as they are so large, they can be easily found by winols and as such, should be able to find them in the other ecu and the buttons will light up with the offset for those maps. If they look right then transfer the map details (button second from bottom on the connecting join), just transfer structure instead of values (I have seen some things switched off and on with that VR6 24V/R32 file compared with oem bins) at which point it should say "x axis values are not the same, same ones found at offset x" and you can make notes of the offsets and see if they are correct and see what lines up.

I will have a look at this ecu with the R32 one and pick out some bits and take a couple of screenshots if it makes it easier? I have spent a couple of minutes on it and -4 came up and 0 offset too for a few maps. Will find out when I get on that computer and post some up next time.

Here you go - easy one to do first.

Open the two files and connect them (ctrl+2)
Scroll down the R32 file till you come to ignition coil closing time - ZUESZ in blue -in that there is a map I've also highlighted in blue, right click "view in hexdump" which it will in yellow on the R32 file - the 5A5A bit - winols will then pick up this map with the offset -FA and you can then line it up.
The bit I have highlighted in red at the bottom is where you can add the map structure, I would leave the values alone on any reference file and just do the axis data and then have a look to see if it looks okay.

You can now do a couple more in that area as can be seen where the maps are defined in blue - have a play!