Data analysis software for mapping based on log files

[GintsK]

I use MLV for a while. Including lambda tables and VE analyzer. My hack was rename lambda table to afrtable inside vemsv3.ini.
Awesome software for VE building!

Gints

[LT401Vette]

GintsK,
Good hacking..
Sorry I'm not sure how this Thread fell off my radar. I'll get VEMS support into MLV next build.

[LT401Vette]

Try a Check for updates from the help menu.
0.952 should make VE Analyze work with the VEMS logs and msq's.

I also put in a filter to take out those crazy high lambda log records. So VE Analyze won't ever see Lambda as over 2.0

Your lambda tables are still going to be converted to AFR. In MLV 3.0 I am going to change that, because I really think it should always be working with Lambda, but if a user prefers to view in afr, well that should be the view. Inside Lambda makes more sense, but right now it is using AFR inside.

[GintsK]

Phil, thanks for being here!!!

I have some questions about MLV:
When tuning n/a engines with race camshafts it is usual VE table becomes with waves. Sometimes VE changes a lot in narrow rpm range. It looks to me that MLV does some averaging and do not allow beside values be with big difference. Even when RPM bins is chosen very close to real breakpoints and engine works exact at this points during logging. How to solve this?

VEMS can use 16x14 tables. MLV for some reason can't export this tables. It give message:

Error saving VEX file:
Unable to write C:\....\yyyy.vex
15

Why so?
Instead it allow save whole msq. Looks without errors!

16x14 VEX looks so:

Code: [Select]

EVEME 1.0
UserRev: 1.00
UserComment:
Date: 10-01-2008
Time: 11:47
Page 0
VE Table RPM Range              [16]
   [  0] =  10
   [  1] =  13
   [  2] =  17
   [  3] =  21
   [  4] =  26
   [  5] =  31
   [  6] =  36
   [  7] =  40
   [  8] =  43
   [  9] =  45
   [ 10] =  48
   [ 11] =  53
   [ 12] =  62
   [ 13] =  69
   [ 14] =  76
   [ 15] =  84
VE Table Load Range (MAP)       [14]
   [  0] =   0
   [  1] =  10
   [  2] =  20
   [  3] =  30
   [  4] =  45
   [  5] =  65
   [  6] =  90
   [  7] = 115
   [  8] = 140
   [  9] = 165
   [ 10] = 185
   [ 11] = 210
   [ 12] = 230
   [ 13] = 255
VE Table                        [ 16][ 14]
           [  0] [  1] [  2] [  3] [  4] [  5] [  6] [  7] [  8] [  9] [ 10] [ 11] [ 12] [ 13] [ 14] [ 15]
   [  0] =   33    26    25    24    23    42    34    31    28    32    35    26    13     5     1     1
   [  1] =   37    30    27    29    32    36    32    31    32    31    28    23    16    13     9     7
   [  2] =   47    40    33    32    31    26    26    27    24    23    23    20    15    14    13    13
   [  3] =   55    46    39    40    36    30    28    26    25    23    23    23    22    19    18    17
   [  4] =   57    54    47    47    42    39    36    38    34    35    33    33    31    27    27    24
   [  5] =   65    62    59    58    51    48    45    49    44    43    43    42    38    31    29    31
   [  6] =   84    72    71    67    60    55    50    52    57    54    55    61    55    34    33    38
   [  7] =   92    84    78    82    69    65    62    63    67    71    71    74    71    48    45    44
   [  8] =   92    88    83    86    85    77    80    85    89    88    91    89    82    74    69    62
   [  9] =   95    98   102    98    99   106   101   105   121   128   144   138   115   111    96    80
   [ 10] =   95   101   107   108   109   107   104   115   143   153   173   164   142   127   118   100
   [ 11] =   95   100   105   111   111   103   104   112   154   172   188   181   171   158   140   119
   [ 12] =   97   103   111   114   117   106   104   130   161   179   207   201   179   173   142   123
   [ 13] =   94   103   114   114   113   103   106   133   167   183   208   203   179   173   144   126

Regards
Gints

[LT401Vette]

The msq saves and Vex saves are completely different and I the msq's are much more adaptable by nature being xml. The Vex format is terrible, it doesn't have a well formed structure. I was just finally implementing Vex import for compatibility, but I really am looking to have MLV and TunerStudio default table export to a new .table format that is xml based.

But in short, the msq saves should be good. The 16x14 Vex export should also work though. I'm guessing the only problem is that I've never tested it . Send me an msq with a 16x14 table and i will fix it.

The way VE analyze works it does pull values closer together if it the RPM & MAP is hitting anywhere in between. If you are dead on a cell, then only that cell will get changed, but typically the input VE value is interpolated from 4 cells. The when the correction is applied, it is applied to all the cells that provided input with a weighting that corresponds to the strength of that cells voice.

There are actually 2 ways each record produces a recommended
1) The interpolated value is corrected and the corrected value is applied to all for input cells with weighting.
2) The correction percentage is calculated and that percentage is applied to the value of all 4 input cells with a weighting.

So, #1 helps to smooth the table, #2 prevents edge cells from getting way off base. An Edge cell being one that only has input data on one side. Like the top row may be 100, but it always ends up getting input from 95 kPa, so it doesn't know that at 98kPa more fuel is needed.

It sounds like #1 is what is getting you. But I think I may have fixed your problem in this last release. I noticed that the VEMS logs let the Lambda go wild. There is Lambda of 60 in there. That is an AFR of 882:1, so naturally even if any input from that record is of very small weight, it is REALLY lean . So it was quickly sending some of the cells to crazy high numbers.

In the new version 2.952, VE Analyze takes any Lambda greater than 2 as 2.0. I even considered making that threshold lower, like 1.6, but see how it works here.

I have not put together an installer for 2.952 yet, first i figure we'll see how this one works. I'm expecting a few more tweaks.

[GintsK]

Hi!

I upload project files here:
http://rapidshare.com/files/149979529/BMW1800.rar.html

There is datalog and related msq too. 16x14. alpha-N.

I hope it is downloadable.

Gints

[LT401Vette]

That msq appears to be 12x12

[GintsK]

Sorry!
At start I tune with 12x12 later migrate to 16x14.
It must 16x14:
http://rapidshare.com/files/150053490/BMW1800.rar.html

Gints

[LT401Vette]

Gints,
That was pretty simple, the array was being sized backwards 14x16 vs 16x14.
I guess most tables are square so it never broke it before.

It is fixed. I'll put another update out tonight.

[jrussell]

Thanks Phil. I updated MLV tonight and it so much nicer not having to open up Excel and mess with the log file first.

[Karl Buchka]

Phil,

Many thanks for adding native VEMS support. Coming from a Megasquirt background it literally cuts the software learning curve to zero.