ecuEdit v2.4 - ECU Tuning & Logging solution

[mtxfrk2k1]

it keeps telling me i need a file.. where do i get it?

[epifan]

new ecuEdit v1.2.0.55beta
- big/little Endian for <ecu_struct>
- big/little Endian, signed/unsigned support for <rows>,<cols>,<data>
- 3d data order: "cols, then rows" (default), "rows, then cols" (used in EVO 3d maps)
- map help support <map ...help="line 1|line 2"...>
- map advance level support <map ...level="1"...> - for organize maps
- ecu ID description support series of different ID's bytes in char and BCD format, functions and char-constants. Allow to assemble ID like JM9653-06
- columns in 1d maps <map type="1" ...cols="5"...>
- 1D map like string <map type="1" ...view="str"...>
- BIN representation in HEXViewer
- HEX,BIN,CHAR,NUM view representation in 1D map <map type="1" ...view="hex"...>
- some bug fixes and improvement

Download ecuEdit v1.2.0.55beta
P.S. I'm include in this package main ecuEdit config tags with some functions

[epifan]

new ecuEdit v1.2.0.57beta
- ECU compare by map list with Source,Compared,Difference table and graph view ability
- Quick map assign from compared ECU
- automatic position of map windows (at left of map list window)
- some bug fixes and improvements

Download ecuEdit v1.2.0.57beta

[epifan]

new ecuEdit v1.2.0.60beta
- single map compare from any ECU
- automatic fill offsets, power, length by map type byte: <map_stuct> in <ecu_tools>
- irregular graph in 3d maps

Download ecuEdit v1.2.0.60beta

This is example of <map_struct> tag for describe Subaru map types:

Code: Select all

<ecu_tools>
   <map_struct id="#05" type="3">
      <element attr="cols_power" value="2"/>
      <element attr="rows_power" value="2"/>
      <element attr="data_power" value="1"/>
      <element attr="data_offset" value="[offset]+1"/>
      <element offset="-1" attr="cols" value="[byte]+1"/>
      <element offset="-([cols]*[cols_power])" attr="cols_offset" value="[offset]"/>
      <element offset="-1" attr="rows" value="[byte]+1"/>
      <element offset="-([rows]*[rows_power])" attr="rows_offset" value="[offset]"/>
   </map_struct>
   <map_struct id="#04" type="3">
      <element attr="cols_power" value="1"/>
      <element attr="rows_power" value="2"/>
      <element attr="data_power" value="1"/>
      <element attr="data_offset" value="[offset]+1"/>
      <element offset="-1" attr="cols" value="[byte]+1"/>
      <element offset="-([cols]*[cols_power])" attr="cols_offset" value="[offset]"/>
      <element offset="-1" attr="rows" value="[byte]+1"/>
      <element offset="-([rows]*[rows_power])" attr="rows_offset" value="[offset]"/>
   </map_struct>
   <map_struct id="#14" type="3">
      <element attr="cols_power" value="1"/>
      <element attr="rows_power" value="2"/>
      <element attr="data_power" value="2"/>
      <element attr="data_offset" value="[offset]+1"/>
      <element offset="-1" attr="cols" value="[byte]+1"/>
      <element offset="-([cols]*[cols_power])" attr="cols_offset" value="[offset]"/>
      <element offset="-1" attr="rows" value="[byte]+1"/>
      <element offset="-([rows]*[rows_power])" attr="rows_offset" value="[offset]"/>
   </map_struct>
   <map_struct id="#85" type="3">
      <element attr="cols_power" value="2"/>
      <element attr="rows_power" value="2"/>
      <element attr="data_power" value="1"/>
      <element attr="data_offset" value="[offset]+1"/>
      <element offset="-1" attr="cols" value="[byte]+1"/>
      <element offset="-([cols_power])" attr="cols_offset" value="[offset]"/>
      <element offset="-([cols_power])" attr="cols_inc_offset" value="[offset]"/>
      <element offset="-1" attr="rows" value="[byte]+1"/>
      <element offset="-([rows_power])" attr="rows_offset" value="[offset]"/>
      <element offset="-([rows_power])" attr="rows_inc_offset" value="[offset]"/>
   </map_struct>
   <map_struct id="#91" type="2">
      <element attr="rows_power" value="2"/>
      <element attr="data_power" value="2"/>
      <element attr="data_offset" value="[offset]+1"/>
      <element offset="-1" attr="rows" value="[byte]+1"/>
      <element offset="-[rows_power]" attr="rows_offset" value="[offset]"/>
      <element offset="-[rows_power]" attr="rows_inc_offset" value="[offset]"/>
   </map_struct>
   <map_struct id="#81" type="2">
      <element attr="rows_power" value="2"/>
      <element attr="data_power" value="1"/>
      <element attr="data_offset" value="[offset]+1"/>
      <element offset="-1" attr="rows" value="[byte]+1"/>
      <element offset="-[rows_power]" attr="rows_offset" value="[offset]"/>
      <element offset="-[rows_power]" attr="rows_inc_offset" value="[offset]"/>
   </map_struct>
   <map_struct id="#80" type="2">
      <element attr="rows_power" value="1"/>
      <element attr="data_power" value="1"/>
      <element attr="data_offset" value="[offset]+1"/>
      <element offset="-1" attr="rows" value="[byte]+1"/>
      <element offset="-[rows_power]" attr="rows_offset" value="[offset]"/>
      <element offset="-[rows_power]" attr="rows_inc_offset" value="[offset]"/>
   </map_struct>
   <map_struct id="#11" type="2">
      <element attr="rows_power" value="2"/>
      <element attr="data_power" value="2"/>
      <element attr="data_offset" value="[offset]+1"/>
      <element offset="-1" attr="rows" value="[byte]+1"/>
      <element offset="-([rows_power]*[rows])" attr="rows_offset" value="[offset]"/>
   </map_struct>
</ecu_tools>


[Jeramie]

Anyone have ECUedit Map Defs for the A4TF500?

[west_minist]

Can you explain the info you stated a little bit more epifan?

[epifan]

Can you explain the info you stated a little bit more epifan?

Subaru ECU have "map type" byte for each 2d or 3d map. Each "map type" describe data size (8bit, 16bit, etc) and dimensions. All offsets in Calvin's ECU archive specify this "map type" byte.

3d map struct is:
<y-axis values><y-axis length - 1><x-axis values><x-axis length - 1><type><z-axis values>

So, example for 3d map with map type 0x05:

<map_struct id="#05" type="3"> //map_type=0x05, type="3" - 3d maps
<element attr="cols_power" value="2"/> //assign cols power to 16bit
<element attr="rows_power" value="2"/> //assign rows power to 16bit
<element attr="data_power" value="1"/> //assign data power to 8bit
<element attr="data_offset" value="[offset]+1"/> //assign data offset to entered offset+1 byte
<element offset="-1" attr="cols" value="[byte]+1"/> //seek offset to -1 from current pos and assgin count of cols
<element offset="-([cols]*[cols_power])" attr="cols_offset" value="[offset]"/> //seek offset to start of cools and assign cols_offset
<element offset="-1" attr="rows" value="[byte]+1"/> //seek offset to -1 and assgin number of rows
<element offset="-([rows]*[rows_power])" attr="rows_offset" value="[offset]"/> //seek offset to start rows and assign rows_offset
</map_struct>

[xswrex]

awesome epifan!

i also have been working on an app that produced a fully working xml file for ecuedit using the map definitions and the cpu dump files

[calvinc]

Anyone have ECUedit Map Defs for the A4TF500?

what is the last letter of your rom revision? i have the offset for A4TF500F in the list i published - http://www.tari.co.za/cgi-bin/yabb2/YaBB.pl?num=1143012452. use those to create the xml file, its not that difficult.

calvin.

[Jeramie]

Anyone have ECUedit Map Defs for the A4TF500?

what is the last letter of your rom revision? i have the offset for A4TF500F in the list i published - http://www.tari.co.za/cgi-bin/yabb2/YaBB.pl?num=1143012452. use those to create the xml file, its not that difficult.

calvin.

F (MTX)

I know exactly what you mean but I'm lazy! If someone else creates one, if would be great if they could post it.

[NeverLies]

You can add this one :

Code: Select all

   <map_struct id="#94" type="3">
      <element attr="cols_power" value="1"/>
      <element attr="rows_power" value="2"/>
      <element attr="data_power" value="2"/>
      <element attr="data_offset" value="[offset]+1"/>
      <element offset="-1" attr="cols" value="[byte]+1"/>
      <element offset="-([cols_power])" attr="cols_offset" value="[offset]"/>
      <element offset="-([cols_power])" attr="cols_inc_offset" value="[offset]"/>
      <element offset="-1" attr="rows" value="[byte]+1"/>
      <element offset="-([rows_power])" attr="rows_offset" value="[offset]"/>
      <element offset="-([rows_power])" attr="rows_inc_offset" value="[offset]"/>
   </map_struct>


[x99percent]

Can you explain the info you stated a little bit more epifan?

Subaru ECU have "map type" byte for each 2d or 3d map. Each "map type" describe data size (8bit, 16bit, etc) and dimensions. All offsets in Calvin's ECU archive specify this "map type" byte.

3d map struct is:
<y-axis values><y-axis length - 1><x-axis values><x-axis length - 1><type><z-axis values>

So, example for 3d map with map type 0x05:

<map_struct id="#05" type="3"> //map_type=0x05, type="3" - 3d maps
<element attr="cols_power" value="2"/> //assign cols power to 16bit
<element attr="rows_power" value="2"/> //assign rows power to 16bit
<element attr="data_power" value="1"/> //assign data power to 8bit
<element attr="data_offset" value="[offset]+1"/> //assign data offset to entered offset+1 byte
<element offset="-1" attr="cols" value="[byte]+1"/> //seek offset to -1 from current pos and assgin count of cols
<element offset="-([cols]*[cols_power])" attr="cols_offset" value="[offset]"/> //seek offset to start of cools and assign cols_offset
<element offset="-1" attr="rows" value="[byte]+1"/> //seek offset to -1 and assgin number of rows
<element offset="-([rows]*[rows_power])" attr="rows_offset" value="[offset]"/> //seek offset to start rows and assign rows_offset
</map_struct>

OK, but how do you use this when defining a <map> now? Can anyone please post an example?

I'm missing something obvious or I'm just not getting it...

[gethin]

Can you update the first post so we can keep track of the version numbers

Thanks

[JRSCCivic98]

Anyone have ECUedit Map Defs for the A4TF500?

what is the last letter of your rom revision? i have the offset for A4TF500F in the list i published - http://www.tari.co.za/cgi-bin/yabb2/YaBB.pl?num=1143012452. use those to create the xml file, its not that difficult.

calvin.

Someone needs to take all those and build an xml out of them... or one for each one. Apperently you can have multiple XML files in the ecuEdit directory as long as they are named differently... ecuEdit seems to read all of them to load up it's parameters. All the xml defs I've had so far for the 300 and 500 roms have been wrong. Either the RPMs are way off in the maps or the offset for certain things like revlimit and injector size have been all wrong. The problems on the defs I've had so far have been the "power" values... people are making mistakes on the xml files they are publishing (not to mention they are not even complete) and someone's going to fug up their map because of this.

I've said it before and I'll say it again... STOP WRITING 20 BILLION MAP EDITING PROGRAMS... STANDARIZE ON ONE AND START WRITING THE DEFINITION FILES FOR IT!!! Otherwise maybe the community might have a complete and bug free working package by the end of 2010.

[qoncept]

Someone needs to take all those and build an xml out of them... or one for each one.

This is a very tired argument. Shut up and do it. Your 'my way is the best for the community' BS is based on no more insight than anyone else's opinion, and you are doing nothing to help.