A little hint might be also be found here ;)

edc16-introduction-to-reprogramming-t220

Thnx, I know this document, it's quite usefull, but not all information is in there. For example the drivers wish maps in this document are different from where the drivers wish maps are in my file. Different SW numbers and different EDC16 ECU are the cause of that.

Hi,
for all information you would have to get source code for compiling sw to bin ;)
Thats's quite a top secret...

There is no easy way for sure.
Its bad that every sw no. has maps and data on different addresses.
But everything can be done.

I totally agree, but in the end I think I will get there. First step now for me is identify all the maps that are relevant in my ECU.
Step 2 is to change them. For this step a lot of information on what to change can be found also. How to change it with what software is a little more difficult. Momentarily I've used my MPPS cable to read the memory of my ECU. I use WinOls demo for finding the maps. Now from what I've understand, with WinOls demo I cannot change the maps, so I still need to find a solution for that. Furthermore, I also don't know how I will correct the checksum, after updating the maps. Some posts say that the MPPS software will do this automatically, but I'm not sure on that. Does this mean that the MPPS software also changes the BIN file, or is the checksum stored outside the BIN file in a different memory allocation?
Last thing I want to do is flash a wrong BIN file with no checksum correction onto my ECU.
So as you can read, there is still a long way to go for me, and a lot to learn. I will take it step by step, and every help I can get is very much appreciated!

taktijs wrote:Thnx, I know this document, it's quite usefull, but not all information is in there. For example the drivers wish maps in this document are different from where the drivers wish maps are in my file. Different SW numbers and different EDC16 ECU are the cause of that.

This is expected. As ecuedit said we would need software source and probably the compiler that was used to produce bin file - both with correct versions as used at the factory. But that would not be reverse engineering anymore, which we all so much like to do. ;)

What will get you started is gathering information about the maps you need, as you already figured out. Like size, axis type, map values, 3D map view, damos files, similar bins, ... then, processing and compiling this info into something useful. It is hard, especially because you need to understand a lot of stuff. You need to rely on forums and others experiences which may or may not be adequate. Then start looking at your bin. And other bins, too. Anything you can't confirm - try to reject. Does it make sense? Yes, no .. repeat the process.

Since I'm an absolute beginner in this area, I try to do it like this, described in a bash shell while loop syntax :)

while [ "I HAVE A PROBLEM" = "YES" ]
do
- define PROBLEM (whatever it is, hw, sw, address, values, map, ..)
- learn about the PROBLEM
- search the forums / net for info
- gather & organize info,
- ask questions
- experiment, compare, suggest, test, confirm, reject
- log results, make reports, start thread, reply with post
done

So if you have any information about the map you a looking for - give it up, I'm tempted to look for it :geek:

First I started with the 1st file from this topic:
post1063#p1063
this is a file from an Audi A4 1.9TDI BKE Engine, with the same EDC16U31 ECU as my own.
Now recently I've received my MPPS cable so I downloaded the ORI file from my own car (this file is the second post in the topic) and I continued with this file. From this file I found these maps:

1DDE84 Boost limiter
1DA3C4 Duration1
1DA646 Duration2
1DA8C8 Duration3
1DAB4A Duration4
1C3CEE EGR
1E0218 Inverse drivers wish
1D12E0 Lambda
1DCF24 N75
1D1BB6 Nm to IQ
1D0D06 Smoke limiter
1D0FC0 2nd smoke limiter??
1C8952 SOI limiter
1C85AA SOI
1CF328 Torque limiter
1DDD18 Turbo

Still I need to find the drivers wish maps (RPM freak says there in the beginning of the file (I still have to find them, but I do not have WinOls here (am at work))). Furthermore I am unsure about the duration maps, if you look at them, there are some negative values, so duration can never be negative. (Unless there is an offset?)

Anyway, what your way of working is, I use more or less the same. Define what maps I need to have -> try to find them -> know what to look for -> look at forums in order to see what the maps look like -> see if I can find similar maps in WinOls in my own file -> check if they make sense -> ask if they make sense on forums -> learn from that. As you I am an absolute beginner.

RPM freak wrote:At the beginning of the map area.

Still searching for the drivers wish maps. Do you mean at the beginning where the slide bar s now, or the area more to the right? (see picture)

Maybe another tip: Are the maps between the potential maps? Now I'm trying to find them manually, looking at the 2D graphs...

If I look for example in a different file, then the drivers wish maps are easy to spot (see picture). Now I've scrolled through my file many times, but no luck so far.

For the first file Drivers Wish maps start at 41B04, for the second file Drivers Wish maps start at 1C1B04.
These maps can be seen very easy looking at the 2D graphs.

1D0D06 Smoke limiter - MAF
1D0FC0 Smoke limiter - MAP