- Code: Select all
<ecu_struct id="A4SE900D" type="Euro WRX 02">
<map name="Low Det Fuel Map" type="3">
<rows count="18" offset="#292b5" power="2" format="%.0f" func_2val="[value]*50" func_val2="[value]/50" desc="RPM"/>
<cols count="16" offset="#292d9" power="2" format="%.4f" func_2val="[value]/8192" func_val2="[value]*8192" desc="Load (Air/Cylinder charge)"/>
<data offset="#292fc" power="1" format="%.2f" func_2val="14.7/(1 + ([value] / 128))" func_val2="(14.7*128)/[value]-128" color_dir="1" inc_dir="0" desc="Air/Fuel Ratio"/>
</map>
</ecu_struct>
One suggestion I have is that it might be more intuitive to have the number of rows and cols in the <map> tag instead of having to hunt for them in the <rows> and <cols> tag.
Also, rather than defining the formula to calculate common units in every map, define them above. IE, <formula name = rpm> tag, or something like that.
Finally, rather than an 2 equations, for converting to real world numbers and then back to a byte, it'd be nice if you only needed one. I understand why epifan did this, but there should hopefully be a function in each language to reverse the formula. This could be a place we run in to a problem, if Delphi can't do that and epifan needs both equations, while in Java you'd only need one or the other. This is something we'd need to come to an agreement upon.
Anyway, that's my input for now. Anyone else?
btw, this is my next addition to functionality
I don't think that it's hard to realize. I'll try