ve tables in reflash tool:mazdaedit

I used to use mazda-edit for mazda stock ecu tuning, there are three ve tables(ve a;ve b;ve c)in mazda 6 rom（LF 2.0 engine）,it totally confused me since there is no additional description for such three ve table, under what conditions would there be so many ve table for such an stock ecu .

the second question is,these ve table do not have engine load as Y axis, what signal would it take for Y axis?

does any fellow have same questions with me？

I put original VE tables here.there are three of them,my questions are

1\why would an ecu needs more than one ve map;

2\why are the values in the table not in the form of x%,there are even negative values....totally out of my mind.

3\the load axis is a myth to me,they are not in map of maf;

I know this is quite a question according to ecu definition,but since there is no detail description for such tables.

so I post it here,try to find some theoretical explanation for my questions.

hope to here from you,my friends.

Jacob from china

That isn't an ECU I'm familiar with but it's very common for OE ECUs to have multiple tables. It's also not uncommon for there to be no additional information as to which one the ECU uses or under what conditions. You will need to make isolated changes to one table at a time to find out which the ECU is referencing. A common technique with OE reflashing is to make multiple tables like this the same so that if there is a switching condition that the tuner isn't aware of, the tune will remain consistent.

The load axis for most factory ECUs is related to mass airflow. Often this is expressed in grams per cylinder or grams per revolution.

hi andre

really enlightening from your answer.

you reminder me of mass airflow as load axis,i used to play with some speed density systems taking MAP as loads but not maf.

another question,why are there negative values in these table i attached，shouldn‘t they always be in percentage?

It's hard to say as I'm not familiar with the ECU in question. The actual numbers in the table however are not true VE (just based on the magnitude of the values - 1148 for example) so it really depends what the ECU is actually representing in this table.