Help to decipher maps diesel land rover Td5

[Def89]

A greeting to all,
I write this my first topic to ask you for a hand to try to understand the values that are found in the maps, as written in my other post to this link st? handling the ecu of the engines, land rover td5, both defender and discovery, for? I have almost no knowledge of how you run maps, or rather I have read several documents regarding the mappings, but in this unit I can handle.
I would try starting with the order, posting some maps, the map data are "right" in the sense that the indices of the row and column, as well as? the size of the table, are at the head of the block of data contained in the memory, the addresses of the heads of the blocks are located in a table contained in the same file to the address 0x1CEFE (referring to the entire file of 256k content in the flash of the ecu) the addresses in this table will vary from one firmware version to another (defender, discovery, as well as? several years of production)? you keep positionally equal, the cio? having 2 of these tables from 2 stations in different versions, taking the first address and the first address of the other, which are usually different between them, if you go to the corresponding addresses are 2 tables that are identical in both size and the indexes for the values, then do the same thing.
My "problem" ? understand what these tables, and most of all, what indicate the indexes, below I'm attaching some pictures of these tables maps that I assume have been deciphered, but I have not very clear the meaning of the axes.

this table manages the egr, and I know that by putting all the values to 16000 disables the functionality? (but I don't know what are the values on the axes)
Egr.jpg

these two tables if you vary the behavior of the engine, respectively, with the gearbox in a range of fast (Hi) or low (Low), the control unit knows the gear reducer through a contact on the gearbox itself, I have seen that variandole you vary the performance, but I don't know what to do, they would seem to limit values to which the engine is coming, a kind of limiter. there are 2 pictures of the Hi why? in only 1 I couldn't put all of the values in the table.
reference hi cut parte2.jpg
reference cut hi.jpg
reference cut low.jpg

[Def89]

I have to write another message, why? I mistakenly sent the message before temrinarlo...

these two tables if you vary the response of the accelerator pedal, in the sense that it will change the values you have a pedal more? or less sensitive? does not increase anything ****s performance, only changes the way the engine delivers power to equality? pressure of the pedal, are 2 why? the control unit reveals if the gearbox ? in a range of slow or fast, and on the basis of there? to change the behaviour of the pedal (it happens even in the source)
For? also, I do not understand the values on the axes.... I sense that they are the engine rpm on the lines, and the percentage of the pressure of the pedal on the columns, but I'm not sure....

trottle Hi.jpg
trottle low.jpg

This other table (really? 4 are very similar, I attach only one, but if needed I also have the other 3), instead, influence significantly the behavior of the engine, by increasing the values you get more performance, but if touched excessively also increases the fumosit?, here for? I do not understand the values on the axes, I assume that on the rows there are the engine rpm, but on the y-axis I don't know....
fuell map.jpg


I thank anyone who is willing to give me a hand to understand, I'm not a mapper (pass the sick temrine) for the profession to make money, I do it for passion and to understand how they work, as well as? to be able to hack on this controller for a racing engine...

Greeting

[Def89]

Anyone that can help me, I dispace that the attached images are not visible to those who have less of 80messaggi, may be useful also to those who, like me, doesn't it ? arrived at the threshold, but maybe she would have the ability? - -thanks for help me, tonight I try to move some of the tables on a text format, as well? maybe you can't see anything...

Greeting

[magi1984]

the sample file ? what did you put in the other thread?

let's start with the EGR map, the first...the aces are definitely the turns and then not?.

the 3 successive images are torque limiters, limit the torque of the motor according to the number of turns. if you split the data in the table to 0.1 you will get the value of the torque, as 4250/0.1 =425nm

on the accelerator pedal as you say you have RPM and pedal position, also in this case, divide the values in the table to 0.1, and you will get the required torque on the basis of speed and pedal position

the 4 maps are very similar to the time of the injection, the axis are rpm and according to me the deal? of fuel injected. in the table you have the value in milliseconds of the time of opening the injectors
of course, pi? increases in pi values? the injectors are opened by injecting diesel fuel for the pi? time. if you misjudge it, the car smokes why? inject diesel even when you should not pi? it

[Def89]

Thanks Magi for giving me a hand, I have a little lightened ideas

Being a unit created and designed in england, I know that the torque values are in Nm, but in Lbf.ft, I say there? why? the tables in question are of an original map, and because the manufacturer declared 330Nm of maximum torque, here, by converting the maximum value 435.0 Lbf.ft in Nm is 322Nm, that could easily be the 330 declared

On the table of the pedal, therefore, should always be the couples request, from us? I gather that the value of "common denominator" for the ecu is precisely the required torque?


There are other tables that in some way are decrypted, tonight I try to post them

Then a strange curiosity?, this unit also manages a modulator wastegate, you have a vague idea of what kind of table should I look for to find it?

p.s. Is the file ? what I put in the other discussion, if you need him back here.

Greeting

[magi1984]

no you do not need to say here, it was to understand which file we were talking about

[Def89]

Then, I try to continue in the exploration

there are 2 tables case (size 1x2) and exactly the same, I put only 1 for comfort?, I don't understand what to do, even if the value of 740 to me looks a lot like the idling speed of the engine, the regime that in the case of the temperature is very cold can? to climb, but I don't know if the 1000 ? the maximum value that can? climb.... or are tuttaltra what?!
#040.JPG

This table instead ? dimensionally equal to those of the accelerator pedal, it has the same indexes on the asssi, but the values are different, I don't know if it is possible, but may be connected to the IDLE SPEED ERROR?
#057.jpg

Now, however, the tables that I can not figure out for nothing.... I know that they somehow influence the performance, but I infer solely from the fact that among the myriad of maps that I've found, made by professionals (mainly british) these tables, and others, the times are changed.....
#059.jpg
#069.jpg
#070.jpg

[Def89]

the other 2 mppe also misunderstood, like the 3 previous
#090.jpg
#094.jpg


While this table, I think goes to handle the pressure of the turbo, he would return with the data written in the other discossione for? I can't understand how "works", to me it would seem possible that the indices of the row is the engine rpm, but the column does not understand them....
#085.jpg


Thanks for the help
Greeting

[Def89]

St? trying to decipher these maps, but for now, I have not done very well, I have to? understood that the two tables tiny 1x2 are the minimum, in particular, the first value ? the "maximum" at least that is the value to which the controller to the pi? accelerates the motor if the temperature of the liquid cooling ? VERY low, whereas the second one ? the minimum "normal"; they are why? as I imagined vary between normal speed and reduced

For the other I hope in a help from your side I st? stuck
Greeting

[magi1984]

? hard to help you looking only at the screen
if you can mail ori and mod that let's take a look...
PS: ori and mod in a format readable by the common sw tuning so you can see the maps in 2d