RPM freak wrote: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.

1C1A82 - Engine speed (RPM) axis, Y
1C1AB6 - Throttle position (%) axis, X

All Drivers wish maps use those, correct?

Hi RPM freak,

then I think I have something wrong with my view parameters. I see that there is something there (see picture), but I cann't make a selection, that makes maps out of this. How did you change your view parameters?

I used Text view with columns=8..

And what kind of 3D graph do you get then, with your selection? I'm still wrestling with it. Also do not understand that some data in the map goes up to the max bit value!

Ok, so with a lot or your help from this forum I (or you all also) Identified the following maps (see picture)

taktijs wrote:Ok, so with a lot or your help from this forum I (or you all also) Identified the following maps (see picture)

Nice.

I get this view - I've also used factors as found in the EDC16 guide to reprogramming.



To get best results with 3D I usually try to figure out what the map size would be, then use w and m keys in WinOLS to get the columns right. Also I "left align" the start of map in the hexdump using CTRL+ left and CTRL + right. I would then look for the start/end of a row/column by looking for incrementing values in both X and Y directions while taking into account what the axis size is. It takes few iterations to isolate possible map data this way. Looking at the data before and after the map also helps, sometimes.

I also use hexdump (text) view extensively, as I'm used to looking at those numbers. 2D probably requires more trained eye, but as RPM freak said these map are nicely 'visible' in 2D - if you know what to look for.. well now we do :)

I was kind of expecting the size of drivers wish to be the same size as inverse drivers wish.. :roll: .. it seemed kind of logical ..

Is the size of a map for a given ECU always have the same - eg. drivers wish is always 8x16?

Well I think that is really true. You know what you need to look for. I as a beginner look for familiair patterns in the 2D and 3D views, now I had different examples for the drivers wish maps, hence I couldn't find them. Furthermore,I look into the data and see if they make sense and I also look into the map size (X x Y).

Now the next thing is in what order/sequence do I need to change the maps?

1. Adjust Drivers Wish maps (1C1B04, 1C1C04, 1C1D04, 1C1E04, 1C1F04, 1C2004, 1C2104)
(What about the inverse drivers wish maps?)

2. Adjust Torque limiter (1CF328)

3. Adjust Nm to IQ (1D1BB6)

4. Adjust Boost (1DDD18), Boost limiter (1DDE84), Duration maps?, SOI (1C85AA), SOI limiter (1C8952), Smoke MAP (1D0FCO), Smoke MAF (1D0D06)

Now for 4. I do not know if there is a sequence in the adjustment of these maps? And is my sequence (1, 2, 3) correct?

Ok, next problem. We've found a number of SOI maps (see picture), now we cannot find the SOI limiter. The limiter that we've identified before (1C8952) cannot be the limiter, because the values do not make any sense for the limiter. It cannot be values BTDC, so this map is not the limiter. SO the question is, is the last SOI map also the limiter? How can we identify this?

Furthermore, it appears that there are more turbo maps. (see second picture) But for these maps the axis are missing. Does this mean the maps are not used? or am I looking in the wrong place?

taktijs wrote:Furthermore, it appears that there are more turbo maps. (see second picture) But for these maps the axis are missing. Does this mean the maps are not used? or am I looking in the wrong place?

I'm a beginner too, but I like the challenge, so I'm thinking out loud here as a sw engineer ..

[assume mode = on]
I had also asked myself whether there is some data in the bin that is not used.. I have not found a definitive answer yet, but I assume that if there is data in the bin, it is more likely to be used then not. OTOH, if some data is there it does not mean it is map or axis related hence you do not have to change it. How to know for sure? Experience I guess (I'm not stating that I have it).

Consider this: once the compiler produces bin from source, bin contains only the "required" code , one that is actually used and executed by the CPU - other code gets removed during the compilation optimization process. So if there is code/data in the bin that is unused it would be there because the programmer put it there intentionally to confuse people :?: There could be other reasons and methods, but that is out of scope..

AFAIK, many same maps might be "grouped" in the bin, without any axes. This means that they share the same axis data. Axes for these map are located somewhere else - as with the other map you located some time back.
[assume mode = off]

Good luck & remember: assumption is a mother of all fuckups ;) !