Introducing EcmEdit
Thread Starter
TGO Supporter
Joined: Jul 2000
Posts: 812
Likes: 1
Engine: 5.7L V8
Transmission: 700R4
Introducing EcmEdit
http://ecmedit.sourceforge.net
I've put up a very, *very* early release of a program I've been working on for bin editing. Right now it's somewhat functional (you can edit everything in raw values, calc the checksum, save it), but ugly.
The important thing is that it's cross platform. This means that you can use it on Macs, Linux, Windows, Palm, Pocket PC, etc.
It's just a developer's release for now, there is only source code to download from SourceForge, but it's a start.
There are tons of TODOs scattered throughout the code, so feel free to send me corrections.
Alex
I've put up a very, *very* early release of a program I've been working on for bin editing. Right now it's somewhat functional (you can edit everything in raw values, calc the checksum, save it), but ugly.
The important thing is that it's cross platform. This means that you can use it on Macs, Linux, Windows, Palm, Pocket PC, etc.
It's just a developer's release for now, there is only source code to download from SourceForge, but it's a start.
There are tons of TODOs scattered throughout the code, so feel free to send me corrections.

Alex
TGO Supporter
Joined: Jan 2000
Posts: 1,861
Likes: 0
From: In your ear. No, the other one.
Car: '89 Trans Am WS6
Engine: 350 TPI
Transmission: T5WC
Axle/Gears: 3.08 posi
Sweet! Keep it up. The more options, the better.
Edit:
You're going to want to be careful with space-delimiting the axis labels. There are ECUs out there have spaces for some of the individual labels (5 char Y axis), as they use strings. I don't have an example off-hand, but they're out there.
Also, you might consider writing your own definition format and just write an ECU importer for it. I'd avoid polluting the ECU format with your own modifications (trust me, I've done it myself), as it may break compatibility with other software that makes use of the ECU format.
Just a couple suggestions from someone who's familiar with the path. =)
Looks good, keep going!
Edit:
You're going to want to be careful with space-delimiting the axis labels. There are ECUs out there have spaces for some of the individual labels (5 char Y axis), as they use strings. I don't have an example off-hand, but they're out there.
Also, you might consider writing your own definition format and just write an ECU importer for it. I'd avoid polluting the ECU format with your own modifications (trust me, I've done it myself), as it may break compatibility with other software that makes use of the ECU format.
Just a couple suggestions from someone who's familiar with the path. =)
Looks good, keep going!
Last edited by Mangus; Nov 30, 2004 at 03:14 PM.
Thread Starter
TGO Supporter
Joined: Jul 2000
Posts: 812
Likes: 1
Engine: 5.7L V8
Transmission: 700R4
Ya, right now you need to check it out through CVS, there are instructions on the SourceForge website on how to do this.
I don't have any executables yet so there's no point in releasing any files right now.
I don't have any executables yet so there's no point in releasing any files right now.
Thread
Thread Starter
Forum
Replies
Last Post
Hotrodboba400
Firebirds for Sale
3
Dec 10, 2019 07:07 PM
Mongoose462ci
North East Region
0
Sep 16, 2015 11:46 PM




