DIYEFI.org Forum

I'm going to start simple and just do 2D tables for the time being.

A 2D table has:

• Name
• Description
• Axis name
• Axis unit
• Axis conversion
• Data name
• Data unit
• Data conversion

Each conversion needs at least offset and scaling, BUT, that's not flexible. So, I propose a set of operations such as:

multiplyBy X
divideBy Y
Add Z
Subtract W

etc...

Support can be added as required.

The list would be ordered. Follow it as is to get from ECU format to human format, and in reverse inverted to return to ECU from human and save.

Display of these 2D tables should be in the following format:

Visualisation with optional drag editing:

• axis left and bottom, at minimum, preferably both left and right and top and bottom. Maybe have check boxes for turning each on and off? Icing.
• background black
• single-pixel line white
• light grey and/or dotted grid aligned to the axis breaks
• some indicator for data points
• straight lines between point
• min/max of both X and Y axis should be auto scale to 110 or 120 of the range used and updated dynamically. 110 would mean 5 on one side, 5 on the other, 100 in the middle.

Two row spreadsheet style table below the graph view. Some visual differentiator like bold for axis. Names on left and maybe right too. Editable cells, changes reflected in graph view.

This should work without the above meta data:

• Name = "2D Table <ID>"
• Description = "Not available!"
• Axis name = 'X'
• Axis unit = '?'
• Axis conversion = use as is
• Data name = 'Y'
• Data unit = '?'
• Data conversion = use as is

Go forth sir Mike! :-)

Fred.

Current format of all 2D tables is 16 times 16 bit unsigned for both axis and data, FYI. Your impl should be in double precision and not care about underlying format.

You mean something like this?

Yep, just like that, but 14 months on, no generic hex edit, and no generic label-less table editors. That looks MS-esque too. Pretty though, digging the coloured tabular cells. Prefer horizontal values across the bottom under the curve, especially with more cells. Also, choosing nearest round numbers for axis breaks would be better for understandability.

A few more things about the above:

1) the green highlight line should stop at the edge of the axis, not obscure the labels.
2) The axis values don't even need to be weird numbers. The numbers in the cells are all nice and round.

EMStudio now has a basic 2D editor and works with FreeEMS which isn't true of the above:



Onwards and upwards!

Fred.

Fred wrote:Yep, just like that, but 14 months on, no generic hex edit, and no generic label-less table editors. That looks MS-esque too. Pretty though, digging the coloured tabular cells. Prefer horizontal values across the bottom under the curve, especially with more cells. Also, choosing nearest round numbers for axis breaks would be better for understandability.

David Andruczyk wrote:commit bb98ee19b1998d3abc8f80847f37092ec4a63368
Author: David Andruczyk <dandruczyk@gmail.com>
Date: Mon Jul 23 17:31:01 2012 -0400

Keep markers from going to the edge of the window, an actual GOOD suggestion from Fr3d

I wonder what the 3 in Fred is about LOL :-p