These two videos capture the latest development work on e6tuner, I am adding
what I have called 'associative data' to the map editing.  What this means is
you can associate arbitrary data streams (individual haltech engine data or
techedge 2a0 data as of now) with the individual maps you are tuning.

In the two videos I have associated the WB02 AFR reading with the fuel map, the
display is still primitive but it gets the point across.  The WBO2 AFR
is being continuously sampled normally, what the associative data does is it
ties the AFR samples with specific cells within the map.  The videos are mostly
of idle, but if you pay attention closely you can see the red bars in the
area where the red arrow is pointing (where the engine is) do move up & down a little bit,
they are actively displaying the sampled AFR at those load points.

This is being done across the entire map, if I go drive around a bunch winding
out the motor and cruising in traffic, when I get back and look at the maps I
will have red bars all over the map showing the sampled AFR's at those points.

As of now, the sampled AFR's are always applied to the associative data, I
am going to work on some filters so it ignores data during transient conditions,
things like pushing the gas pedal.  This will make tuning go alot quicker
and is a significant step towards autotuning, I could easily hook an autotuning
engine into this data arrangement, which is something I plan on trying out in
the future.

Another thing I would like to figure out is a way to make the associative data
display a histogram @ each load site, the problem with the current arrangement
is it's a basically smoothed realtime display.  History is not really being
applied to the displayed value, it is averaged with only the previous sample. 
The problem with doing a histogram per cell is the memory requirements, I would
want to store every AFR sampled at every cell with a counter on each one, with a
23x32 fuel map and each cell having possible AFR's between 9:1 and 19:1
(roughly) with precision to the tenth, you suddenly have a shitload of memory
used.  

Well, a shitload by my standards, but by modern PC standards, viable.


This concept was mentioned earlier in a thread and illustrated in a mockup
found here:
http://pengaru.com/gallery/tuning/mockups/fuel_with_sampled_afrs_plot.jpg