current methods for ve analysis

[multiplex]

my world has been turned upside down since getting started with vemstune.  I recently upgraded from 1.1.27 to 1.1.58.

Car is running good now, but I need to spend some time road tuning the fuel on the top end.

previously i would log in megatune. open up in MLV, analyze, resave MSQ. Download to Vems and was good to go.

Of course this required some tweaks to the MLV config to make it all work.

Now with vemstune, i can log. convert to MSQ. convert log to csv. Open csv in MLV, but MSQ fails to open. Says its not compatible.

My question is, even if i tweak the config to make it work. How do i go from the revised MSQ to a format vems can use?

Should i just be using megatune for everything except for firmware?

Is there a megatune config for the new firmware?

one step forward - two steps back

[GintsK]

It is biggest flaw of VT from my point of view too. Everything else works more and more comfortable and reliable with every new version.
Seems developers didn't take in to account this tuning method.
I think we are not alone. And someone will make vemsV3.ini for MT.

And it would be very nice if in future VT and MLV will be compatible.

Currently you can try tuning applet from Andrey. May be it works for 1.1.57

Gints

[multiplex]

thanks for the response. whats the tool from Andrey you are referring to? I couldn't find anything in my search

someone in another forum suggested or asked if it was possible to copy / paste the table from VT to MLV.  MLV lets you paste tables, but VT doesn't let you copy.

that could be an easy way to get things back and forth if that function was available.  Obviously you'd have to get table sizes to match first,etc

[z0tya]

http://www.vems.hu/wiki/index.php?page=MembersPage%2FAndrey%2FTuneApplet

but I can't see download link

[GintsK]

Here is his contacts: http://www.vems.hu/wiki/index.php?page=MembersPage%2FAndrey

[multiplex]

thanks - sent him an email, lets see what happens 

[multiplex]

one small find

the reason MLV won't open up the exported MSQ file from VT, is because the VE tables are exported wrong.  Instead of being 16x14, they are exported 14x16 so some of the columns are truncated and there are two extra rows of zeros.

I manually edited this, and the MSQ opens.

Wondering if this is hard coded in VT, or in a config file somewhere.  I checked around, but couldn't find anything.