There are a couple of programs (promedit, GMECM Edit, GMPCM, Winbin) out there now that use the ecu file format as description files for editing bins.

I'd like to propose that some of us get together and talk about furthering this file format to include fields that would be great for all of us. Because of the fact that many programs use it, we should probably try to get this to be "standardized" and typically, that means a committee should be constructed.

As an example, I'd like to add a field to the file format to include "help" information (or more information in general).

The current format looks like this:

/* Constant 5: Maximum Spark Advance */
{
/*startAddr =1E,
/*columns =1,
/*rows =1,
/*elementSize =1,
/*bitMask =0,
/*offset =0.000000,
/*mulOrDivOrBit =0,
/*factor =0.351567,
/*map_name =Maximum Spark Advance,
/*ylabel =,
/*yaxis =,
/*xlabel =Degrees,
/*xaxis =,,
};

Id like to add one more field:

/*help =Max Spark Advance sets the maximum that the ECU can advance the engines spark.,



There are a number of other neat features that we, as programmers could add using various fields. What we'd need, though, is to be able to agree on a format (the current ecu file format ID is 2) and then increment the format number. Then we add the supported functionality to our programs.

These needs to be standardized so that we dont have a bunch of "bastard" formats the each program cannot support (which then voids the purpose of the single, universal ecu file format).

Should this be the correct forum for creating such a union?

 

For a unification to occur, you'd have to get all the authors to update their software. Not likely.

An alternative compromise would be to issue a help file in addition to the ECU file, so you would have a 165.ECU and 165.HLP which corresponded to one another. There could be some sort of check between the two (checksum, etc) to ensure that they really corresponded to one another, and options during modification/creation of ECU for editing the HLP content.

Not elegant, but it is possible unlike the other path.

 

It wouldnt so much be necessary to have all the authors support the updated ECU, but rather have them be sure that their software supports the

/*Format = 2*/

line in the file. I know that Winbin and Promedit do. (and it *should* be supported by any good program).

If this line is supported, in addition to future programs supporting an "export to format XX" feature, there shouldnt be a problem maintaining interchangeability.

The secondary file is a good idea, but convolutes the idea of a single description file. I cerainly may consider it. I also may consider furthering the ECU file format for my program alone, and offer a "convert to Format 2" option.

 

i like the idea of the built in help file for the ECU's. i dont know about the winbin though but i imagine a few emails with its writer might help clear it up.