ecuEdit v2.4 - ECU Tuning & Logging solution

[Freon]

I agree. I think it would be preferred that EcuEdit create a separate .XML file for each ECU, and that EcuEdit scans the working directory for all .XML files and incorporates them. Perhaps it would default to the ECU identifier for the filename. AG700F.XML or whatever. Or maybe it scans working directory when you open an ECU file for all potentially valid XMLs to save time on program launch.

Right now we would have to manually stitch the files together.

Not a big deal now, as it is more likely any one person will only need to regularly work on one ECU, but maybe next version or so.

Anyway, looking good so far!

[MRF582]

crisspyduck. I believe what you ask of ecuEdit, it already does. The XML definition file i have I started from scratch. Basically with nothing at all in ecuEdit.xml. So people can still just copy and paste their XML definitions into a new file which only has their ECU in it.




Here is a list of XML definitions that work confirmed for the 2004 WRX ECU.

http://www.scoobypedia.co.uk/uploads/Kn ... myDesk.jpg

[epifan]

Ok, that's would be in next realease. Any files in same dir would be supported for read and write Now I'm working on HEX compare function

[epifan]

New version ecuEdit v1.2.0.41beta
- adding HEX ecu compare: split screen, color difference visualization, navigation
- suppot multi-file XML description for read and write: ecuEdit scan self directory for XML-files, finding unique ecu description and link it. You can see linked xml-files in "file_name" attribute of <ecu_struct> tag in XML viewer. In write process changes would be only in linked <ecu_struct> - another tags in XML-file would not changed

Download ecuEdit v1.2.0.41beta

[crispyduck]

New version ecuEdit v1.2.0.41beta
- adding HEX ecu compare: split screen, color difference visualization, navigation
- suppot multi-file XML description for read and write: ecuEdit scan self directory for XML-files, finding unique ecu description and link it. You can see linked xml-files in "file_name" attribute of <ecu_struct> tag in XML viewer. In write process changes would be only in linked <ecu_struct> - another tags in XML-file would not changed

epifan, this is great! Thanks very much. When I help out others now with identifying maps it's now much cleaner as I can simply create a separate XML config file and modify that - you even save back to the corresponding file - nice one.

Just looked at the new compare function. This is very impressive and works well on my wide screen laptop (1900 wide). In the software trade I use 'coloured diffs' frequently and recommend you take a look at WinMerge for a reasonable visualisation of differences. This is harder for you as ecuEdit already uses colours to shade maps. Perhaps there are some improvements here.

What are your plans for merging data? Would be good, as in WinMerge, to simply select 'merge' and that would copy across changes per difference, on a selected area, or the whole file. Again similar to say Microsoft Word's review markup. Anyway, food for thought.

Keep up the great work.
-Steve.

[epifan]

In the software trade I use 'coloured diffs' frequently and recommend you take a look at WinMerge for a reasonable visualisation of differences.

in ecuEdit you can press F8-key and switch to color-mode only for different data. Any equal data would be default color. hope, that help you

What are your plans for merging data?

Copy/paste in hex editor would be in next release

[ahains]

Why is there a delay when linking a log, with mention of it being a demo? I thought this software was going to be free? If not, I suppose I'll be inclined to get my log analyzer app to a working state so I can release it.
I don't have much free time, so I'd rather just ditch my project and use someone else's much-more-polished app

[Kha0S]

Why is there a delay when linking a log, with mention of it being a demo? I thought this software was going to be free? If not, I suppose I'll be inclined to get my log analyzer app to a working state so I can release it.
I don't have much free time, so I'd rather just ditch my project and use someone else's much-more-polished app

Agreed. The delays are quite frustrating.

[epifan]

Why is there a delay when linking a log, with mention of it being a demo? I thought this software was going to be free? If not, I suppose I'll be inclined to get my log analyzer app to a working state so I can release it.
I don't have much free time, so I'd rather just ditch my project and use someone else's much-more-polished app

What can I say? Go ahead! Release it, may be openecu members like you app... I know that some of openecu members announce that they are also developing map editor. So, you can wait while they are release they projects.

And once again: I don't use any openecu.org sources for ecuEdit project. It's my own project, I'm use in it a set of shareware components (I'm purchase license on my own money) , so I can decide what functions in ecuEdit public release would be present. I'm also have't much free time, I'm support ecuEdit only in weekends or workday night... In first posts of this thread I say that I don't decide yet what I want to do with this project: woud be it freeware or shareware...

So, good luck!

[Kha0S]

epifan --

Don't get me wrong, I love what you've come up with. I just wish there was a way to pay you some sort of shareware fee to get rid of the delays!

Keep up the great work.

[ahains]

In first posts of this thread I say that I don't decide yet what I want to do with this project: woud be it freeware or shareware...

Epifan, I saw a quote of you earlier describing it as free and misunderstood this to mean you were stating it was to be a free utility. I went back and see now that the context of this was simply that you were offering a free DLL to Calvin, not the entire program for free. My mistake.

To be clear - I fully support your right to publish for-profit software. I don't think there is anything wrong with this at all, more power to you.
Just a case of incorrect expectations on my part.
This is a very nice looking app, by the way.

I do want folks to have a free & open source log analyzer to use, so I'll try to find the time to finish it up. Mine is in c# currently, but it should be very simple to port to Java if qoncept wants to bring that functionality in. I'll take a look at the enginuity interfaces to see if I should be proceeding any differently.

[ahains]

I do want folks to have a free & open source log analyzer to use, so I'll try to find the time to finish it up. Mine is in c# currently, but it should be very simple to port to Java if qoncept wants to bring that functionality in. I'll take a look at the enginuity interfaces to see if I should be proceeding any differently.

Since the utility I was working on was very far from done and I have no idea when/if I'll have time to complete it, I just uploaded the source to the enginuity forum in case it is of any help at all to folks working on log analysis stuff:
http://www.enginuity.org/viewtopic.php?t=23

[epifan]

Epifan, I saw a quote of you earlier describing it as free and misunderstood this to mean you were stating it was to be a free utility. I went back and see now that the context of this was simply that you were offering a free DLL to Calvin, not the entire program for free. My mistake.

Yes, I'm make offer to Calvin to use free DLL only with map edit support (at this time didn't log support), but Calvin decline it. So, all be changed after that, now I'm realize 90% all that I need for tune (I have some subaru-turbo-engine tuning experience)... I don't want to support SSM logger, it's easy and unnecessary, bc we have enought of loggers: DD, ecuExplorer.

P.S. Lets wait until Calvin release they ecuExplorer with map edit support... may be this release would not be free

[calvinc]

P.S. Lets wait until Calvin release they ecuExplorer with map edit support... may be this release would not be free

any and all TARI software will forever be free!

this is not a race or game. i do this because i want free tools to be available for our community. maybe your motives are different?

calvin.

[epifan]

P.S. Lets wait until Calvin release they ecuExplorer with map edit support... may be this release would not be free

i do this because i want free tools to be available for our community

It's imho, bc you always skip my question about openness of ecu descriptions in ecuExplorer
P.S. imho, serious professional tool can't be free, may be cost would be less $50 but not free. Serious free tool smell utopian communism. OpenECU.org is not free, Colby sells his openport (imho, sell cost is much more then prime cost, and I know what for Colby spend part of openport's money) - it's clearly, bc money is motivation of development process...