Deman wrote:I understood you. But so you mislead. ;) Since there really is an axis in absolute ml.bar. And you recalculate relative atmospheric.
I do not look at that way ;) (i see things little bit different) it is pretty strait forward explained with text and pictures also with answer on your question what do i represent on posted picture -> answer was relative boost : since that map is set up, it is visible that factors and offsets are entered in the map - it is just the view of the map. You could also put factor for PSI if it is better understandable for the person who operate with the map.
It is a basics that has no weight, units, factors, offsets, maps, mappaks, damoses are just a basic tools and documentation to help you to understand ECU logic and further more or less complex calculations and modifications.
Jumping thru units, views, imaginable factors, offsets is a strategy to help with work.
I know what you mean but when working with almost all possible ECU producers on market you develop pretty handy things to unify the views of the map.
I never work with absolute pressure map view, i always make view of relative - which person can feel - actual boost.
For sample, you check if it is absolute or relative and you always work the way you see relative. There are ecus that have for sample 32bit X axis, 16bit values, 16bit Y axis in one single map, and possibly inversed map with non logic factors... so when setting up map to see values that are understandable i would set it up always in relative pressure instead of absolute, BARs instead of HPA, for calculating AFR always in mg instead of mm3 when airflow is in mg,
I think it is enough to show 0bar -> 1.7bar and to say it is relative numbers represented in map view.