ecuEdit v2.4 - ECU Tuning & Logging solution

[JRSCCivic98]

Here is a small app which will try and write the XML files for you.
It currently knows more than 100 ecu versions.
How to use:
1. unzip it in a directory
2. in order to compile the map offsets, the ecu hex file is required. Place it in the same directory with the app files. The filename must be [CALID].HEX where [CALID] is the id found in the ECU hex file at offset 0x200
3. Run the app and it will prompt you for a CALID, type it, press enter and ......the XML will be ready!

Halleluja Jesus!!! Finally! This is exactly what I wanted... I'll shut up now. It would be great if you could implement this into ecuEdit so that when you open a map it auto-generates the xml file as needed, but this will work just fine for now.

THANK YOU VERY MUCH!!!

[Tarascon]

the ROM file must be 192KB. Convert it with ecuedit, File->Convert 160K to 192K

xswrex, thanks a lot, it works like a charm.

[JRSCCivic98]

Problem with ecuEdit... didn't have time to replicate it because it pissed me off. Had 2 maps open, comparing and contrasting and basically copying and pasting from the first map to the second where I found differences in the various tables. Anyway, I went through the first 3D sections and was about 2/3's through the 2D maps when ecuEdit just closed out. Of course when it did this it didn't save any of my changes to the second map. Needless to say I was pissed for wasting 30 minutes so I don't feel like reproducing the problem immediately, but will try just to make sure, but I'm pretty sure it's an issue with ecuEdit... Here's the deal... the amount of memory that ecuEdit uses grows with every open of any of the maps, but does not release that memory once that map window is closed. So, once the amount of memory that ecuEdit uses gets to a certain amount (don't know this amount just yet) it crashes without any errors, just closes. Might want to look at this.

Update
Ok, so as I said before each time you check a map in a rom the memory usage of ecuEdit in TaskManager goes up a certain number. When that number reaches somewhere at or right after 41MB of memory usage the program just crashes to the desktop (closes out without any errors). I've duplicated this 3 times in a row on multiple systems. It's definatly a problem.

[west_minist]

Here is a small app which will try and write the XML files for you.
It currently knows more than 100 ecu versions.
How to use:
1. unzip it in a directory
2. in order to compile the map offsets, the ecu hex file is required. Place it in the same directory with the app files. The filename must be [CALID].HEX where [CALID] is the id found in the ECU hex file at offset 0x200
3. Run the app and it will prompt you for a CALID, type it, press enter and ......the XML will be ready!

Very nice. We can view the params, but to write would need the conversion entries.

Keep up the good work. We can really see something like this help others w/ xml formats, until we can get a database of roms definitions growing.

[JRSCCivic98]

Very nice. We can view the params, but to write would need the conversion entries.

Keep up the good work. We can really see something like this help others w/ xml formats, until we can get a database of roms definitions growing.

What do you mean by this? I created some xml files and was able to modify the entries with ecuEdit and save them to the map. Haven't tried flashing the rom yet, but want to know what's up.

[west_minist]

I am assuming that the change format would have to be back to what the ecu will understand. I stand corrected on this.

[Spiider]

The system works very painlessly.

1. Ecuflash->Download ROM

2. XMLwrite->Ecuedit XML def

3. Ecuedit rom editing

4. Ecuflash-> Upload new ROM into ecu

I just did this with my AH581 (A4TE002B), and it worked perfectly.

[west_minist]

There are 2 entries in the xml for formatting from ecu to value and value to ecu. I assume that you will need value to ecu for writing.

Thats good to hear.

When you copy the rom again, were the ettings changed?

[epifan]

new ecuEdit v1.2.0.61beta
- ini-file added for some additional config parameters
- XMLDir in ecuedit.ini - path for ecu xmls
- XML save improved
- XMLWrite V2.0 support If programm don't find ecu description, it execute XMLWrite to generate XML description and place XML-file to XMLDir. EcuEdit use TEMP directory described in Windows System Environment. XMLWrite.exe and XMLWrite.dat must be in same directory with ecuEdit.exe

Download ecuEdit v1.2.0.61beta

[epifan]

Ok, so as I said before each time you check a map in a rom the memory usage of ecuEdit in TaskManager goes up a certain number. When that number reaches somewhere at or right after 41MB of memory usage the program just crashes to the desktop (closes out without any errors). I've duplicated this 3 times in a row on multiple systems. It's definatly a problem.

I build 200 xml-files with total size 15Mb for test ecuEdit, it use 74Mb of system memory (it's MS XML parser work ) and all work fine, no crashes, etc... Please let me know, step-by-step, what are you doing. Thx.

[JRSCCivic98]

The system works very painlessly.

1. Ecuflash->Download ROM

2. XMLwrite->Ecuedit XML def

3. Ecuedit rom editing

4. Ecuflash-> Upload new ROM into ecu

I just did this with my AH581 (A4TE002B), and it worked perfectly.

That's what I thought... because the changes took on the ROM I changed. I just haven't uploaded it yet to the ECU. Also, the changes I was making were very broad... as in taking entire maps from one and copying the whole selection to the new one. Seemed to work fine with the exception of the memory crash issue I posted about above.

[JRSCCivic98]

I build 200 xml-files with total size 15Mb for test ecuEdit, it use 74Mb of system memory (it's MS XML parser work ) and all work fine, no crashes, etc... Please let me know, step-by-step, what are you doing. Thx.

I don't think that's what I meant. Do this, open ecuEdit, open a rom or 2 in it... whatever. Open up Task Manager in XP and look under Processes and find eduEdit. Then look at the memory usage column for ecuEdit. You will see that as you check the various map listings for the roms the memory will continue to grow on what ecuEdit uses. (You will have to check and uncheck pretty much all of the maps to get it to go up high in the memory usage, but once it reaches about 41MB it will crash ecuEdit.)

I haven't tried the new version to see if that one does it also, but I will. Also, what's with the anoying 60 sec Save delay when you want to save a ROM? I know you say it's just the demo version, but it's going to be free in the end anyway, right? So why the anoying time delay. Just wondering. I'll let you know if the crash thing happens on the new version you just posted. Thanks.

[west_minist]

Very nice efipan.

[JRSCCivic98]

Ok, the new version you just posted seems to also crash... here's what I did.

8,032K memory usage when ecuEdit open without any ROMs loaded (only have a 2 ROM XML definition files).
14,008K with 2 ROMs open.
start selecting map on the ROM lists to bring up the memory usage of ecuEdit while watching Task Manager.
43,992K when it crashes to the desktop.

Also, if your ecuEdit opens up with a lot more memory usage then mine then obviously that's because of your large list of XML definitions. In that case it might be the growth of memory usage rather then the exact memory usage size when it crashes. If that's the case it seems that somewhere around a memory usage increase (after you open and start using ecuEdit) of 35960K the program crashes. Hope this helps.

[xswrex]

new ecuEdit v1.2.0.61beta
- ini-file added for some additional config parameters
- XMLDir in ecuedit.ini - path for ecu xmls
- XML save improved
- XMLWrite V2.0 support If programm don't find ecu description, it execute XMLWrite to generate XML description and place XML-file to XMLDir. EcuEdit use TEMP directory described in Windows System Environment. XMLWrite.exe and XMLWrite.dat must be in same directory with ecuEdit.exe

i knew the command line would be handy!

it would be also good to add an option to write the definitions using the single address offset and the type byte. This will reduce the size of the xml a whole lot!
Can you give an example how to write this?