ecuEdit v2.4 - ECU Tuning & Logging solution

[crispyduck]

new ecuEdit v1.2.0.47beta
- Log Viewer support logs overlay (shifting, hiding)
- Copy map to Windows clipboard in HTML-format (Excel direct paste support)

epifan,
Fantastic! Just tried the copy and paste to Excel from within a map and it works great. Thanks very much.

Out of interest I was trying to use the Log -> Map Linking the other day and could not get it working. Can you provide a brief walk through of how one would configure this function say using a typical map e.g. timing, boost etc. I'm sure I'm being stupid some where along the way.
Cheers,
-Steve.

[Jeramie]

Agreed! The program is comming along very nicely! Keep up the good work!

[epifan]

Fantastic! Just tried the copy and paste to Excel from within a map and it works great. Thanks very much.

Can you provide a brief walk through of how one would configure this function say using a typical map e.g. timing, boost etc.

Ok
1. Start ecuEdit
2. Open ECU hex-file
3. Open log-file
4. Select log time interval (red highlighting) by move "Start" and "End" trackbars or other "select interval" functions like "Select by Range"
5. Open map in ECU maps window, for example Fuel Map
6. Run "Log Link" function
7. In "Log Link Set" window choose your "Log window", Log for Rows (ex: Engine Speed), Log for Cols (ex: Eng. Load), Log for Data (ex: A/F Sensor #1)
8. In map window used in log cels are stay in color, not used would be white (or other main window color)
9. By DblClick on color cell you can see all log entrance in this cell
10. You may change log-time interval in Log window and "Log Link" would be updated automaticly

good luck!

[crispyduck]

... 4. Select log time interval (red highlighting) by move "Start" and "End" trackbars or other "select interval" functions like "Select by Range"

Was doing all but that - thought that zooming in by dragging the mouse was the same as 'selecting'. I can see that moving the start/end sliders shades the selection in red - doh!
Cheers, for the pointers.
-Steve.

[cc492]

can someone please tell me where i can find xml definition for ah581?

[Spiider]

I think I'm the only other one on the board with that ecu.

The offsets are listed in the twinscroll section along with my rom.

I never made an xml definition up, as I have just been working in hex and haven't bothered with all the tuning software.

It would be nice to have one, if you make one up please post it. If I do one I'll post mine too.

[evoman]

Extended ECU descriptions in <config> tag:

Code: Select all

<ecu_desc file_size="#30000" name="Subaru 16bit ECU">
   <map_id offset="#00200" length="8"/>
   <region offset="#00209" length="2"/>
</ecu_desc>
<ecu_desc file_size="#40000" name="EVO 16bit ECU">
   <map_id offset="#3FFFA" length="6"/>
   <region offset="#00000" length="0"/>
</ecu_desc>
<ecu_desc file_size="#80000" name="Subaru 32bit ECU">
   <map_id offset="#02000" length="8"/>
   <region offset="#0200B" length="2"/>
</ecu_desc>
<ecu_desc file_size="#80000" name="EVO 32bit ECU">
   <map_id offset="#3FFFA" length="6"/>
   <region offset="#00000" length="0"/>
</ecu_desc>


AFAIK some EVO ECUs haven't ID ASCI-string at the file end. For example ECU from R***art.
May be it's better to recognize ECU-type using BCD-coded marking?

$F44 - 2bytes ECU type and $F55 - 1 byte ECU version for EVO7/8/9.
The same info for EVO5/6 is at $20C/$21D addresses.
Than we have the full calibration ID info as follows: JMxxxx-yy or EMxxxx-yy.

[cboles]

I ran into this problem when I first started reading out EVOs. I'm not sure what the best solution is... my software already supports non-ascii pattern matching but what I would really like to do is get the "JM/EM" characters from 0x3FFFA if they are there and then the "9693-12" from the 3 bcd characters at 0xF44/0xF55. Obviously, it's easy enough to program this, but I want to keep the software completely generic, and that would lead to a cumbersome ECU identifier expression in this case... I might have to employ the expression parser in this case

Colby

Extended ECU descriptions in <config> tag:

Code: Select all

<ecu_desc file_size="#30000" name="Subaru 16bit ECU">
   <map_id offset="#00200" length="8"/>
   <region offset="#00209" length="2"/>
</ecu_desc>
<ecu_desc file_size="#40000" name="EVO 16bit ECU">
   <map_id offset="#3FFFA" length="6"/>
   <region offset="#00000" length="0"/>
</ecu_desc>
<ecu_desc file_size="#80000" name="Subaru 32bit ECU">
   <map_id offset="#02000" length="8"/>
   <region offset="#0200B" length="2"/>
</ecu_desc>
<ecu_desc file_size="#80000" name="EVO 32bit ECU">
   <map_id offset="#3FFFA" length="6"/>
   <region offset="#00000" length="0"/>
</ecu_desc>


AFAIK some EVO ECUs haven't ID ASCI-string at the file end. For example ECU from R***art.
May be it's better to recognize ECU-type using BCD-coded marking?

$F44 - 2bytes ECU type and $F55 - 1 byte ECU version for EVO7/8/9.
The same info for EVO5/6 is at $20C/$21D addresses.
Than we have the full calibration ID info as follows: JMxxxx-yy or EMxxxx-yy.

[evoman]

And what about EVO axises (2 bytes/big endian type) descriptions and signed 8-bit data in some EVO maps?

Here is EVO axis example: lenght data
00 0F 00 80 01 00 01 80 02 00 02 80 ........ 07 00 07 80

It seems that ecuedit needs new buttons in Map params window.
At least "big/little endian" in axis power selector and "signed-unsigned" data will be very usefull...

[NeverLies]

I have just tested 2D maps with 16 bit virtual axis and it seems that it does not work correclty :S

How did you handle the value ? In little or big endian ? Or do u use value in the config tag ?


EDIT : Using latest release (build 47), even 8 bit axis does not work. It was working in previous release.
When using edit box to edit axis description, it works until i do not stop application. If i check in xml file, i can notice that offset startvalue/inc is not saved at all. So when I reopen my rom, it goes back to standard 2D maps display

[GTODesign]

Hi all, just stumbled on this thread. Up till now I hadn't tried ecuEdit but I've just downloaded it and am going to give it a try.

How far has everyone got with breaking down the evo rom images? Has anyone got as far as k-value, rev limit and boost cut? If not, are there any disassemblers that will work with these ROMs other than IDA pro?

[mtxfrk2k1]

the link provided doesnt work. where else can i get it?

[epifan]

How did you handle the value ? In little or big endian ? Or do u use value in the config tag ?

Main offset of increment row is a first value of sequence. Increment value may defined by 2 ways:
1. inc_data_offset="#00000" with same bit-power and inc-convert functions support
2. inc_value="2345" constant increment

In this version "endian" in config tag used for all operations.

EDIT : Using latest release (build 47), even 8 bit axis does not work. It was working in previous release.
When using edit box to edit axis description, it works until i do not stop application. If i check in xml file, i can notice that offset startvalue/inc is not saved at all. So when I reopen my rom, it goes back to standard 2D maps display

May be it's a bug You can change XML directly in text editor. All be worked...

Now, I'm made many changes in ecuEdit for supporting col increment axis, different view types, data ordering, ecu ID defintion with BCD support, EVO maps specific support, etc. So I'm uploading new release soon, may be monday.

[epifan]

the link provided doesnt work. where else can i get it?

http://forums.openecu.org/viewtopic.php?p=2864#2864

[NeverLies]

Yes, XML manual edition works. Will ait for new release for GUI edition so