Call for standards: EPROM/cal editing software

[Squash]

A program that takes in table dimensions/locations/names and creates this TDF file would be nice. 
It would be harder to make dumb fromatting mistakes then.

Squash

--- Peter Gargano <peter at techedge.com.au> wrote:
> Skip this if ECU files (etc.) are not on your agenda today...
> 
> Dig wrote:
>  
> > I'd appreciate comments on the format, or any alter-
> > native filespecs that you would feel woul make a
> > good base for a TDF standard. This will be a public
> > domain standard.
> 
> I've seen GM use a system that defines x and y axis table legends, and 
> then the data, or calibration tables, are based on those legends. Here's 
> a "legend definition" from a bit of source that was liberated from GM:
> 
> ::TBL1  
>   SPEED                       NTRPMVE
>    RPM                           N
>    400                           0
>    600                          16
>    800                          32
>    1200                         48
>    1600                         64
>    2000                         80
>    2400                         92
>    2800                        112
>    3200                        128
>    3600                        144
>    4000                        160
>    4400                        176
>    4800                        192
>    5200                        208
>    5600                        224
>    6400                        240
>    7200                        256    ::
> 
> 
> Then, the calibration data is defined in terms of macros that use
> the previously defined legends.
> 
>    ::TBL3D,17,9,TBL1,1,TBL9,5,2 '%'  ::"
> 
> This is a 3D table with 17 rows and 9 columns. The row legend is the 
> TBL1 definition (mentioned above) starting with element 1 and a step of 1.
> The column legend uses TBL9 starting at the 5th element and a step of two 
> between elements.
> 
> I've been generating an ECU file for a $5D calibration, and I've tried to
> encapsulate this kind of thinking. I have defined TBL9 simply as follows:
> 
> TBL9, MAP, kPa, 0 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100
> 
> so that the "TBL9,5,2" bit above would produce the following legend 
> (remember it's 9 columns wide):
> 
>    20 30 40 50 60 70 80 90 100  kPa
> 
> From my fairly compact file, that could be called a TDF file, I run a simple
> script to produce an ECU file. Here's a three line definition for the 3D table
> mentioned above:
> 
> table   381, F29H, TBL3D, 17, 9, TBL1, 1, 1, TBL9, 5, 2
>         % VE, 256, 100
>         Volumetric Efficiency (VE) as a function of MAP and RPM
> 
> The first line gives a start address, a label, and then the previously 
> mentioned 3D table definition. The second line describes the table entries, 
> and the third line is a bit of descriptive text.
> 
> 
> --
> regards, Peter
> ----------------------------------------------------------------------------
> To unsubscribe from gmecm, send "unsubscribe gmecm" (without the quotes)
> in the body of a message (not the subject) to majordomo at lists.diy-efi.org
> 


__________________________________________________
Do You Yahoo!?
>From homework help to love advice, Yahoo! Experts has your answer.
http://experts.yahoo.com/
----------------------------------------------------------------------------
To unsubscribe from gmecm, send "unsubscribe gmecm" (without the quotes)
in the body of a message (not the subject) to majordomo at lists.diy-efi.org