GSX-R 750 MS1 Extra Megalogviewer Help

[Hank Rearden]

Hi all, this is my first post here. This forum has been a major help for my project.
My bike runs a MS1 extra, fuel only.
I been tuning with Tunerstudio, Tune analyze Live ! has been great, bike already runs very good. I want to try Megalogviewer now and VE analyze, I already downloaded and registered Megalogviewer but I can't make it work.
I made some datalogs with tunerstudio, saved the .csv and the .msq of the project, but when I try to open them with MegalogViewer I can only open the .csv.
I only see some data in the ignition logger screen and nothing in the Log Viewer screen. No gouges nor VE table.
I tried to open the .msq with /file/open/trail live file, then I could see 2 small tables on the right, one is my ve table and the other I assume is a map table, (which I don't use, I'm running TPS only without map sensor) and a big black chart in the middle of the screen.
When I hit VE analyzer below the VE chart it says that some fields are required for VE analyze to work. RPM/Gego/AFR/TP and CLT.
I think I´m doing everything wrong with megalogviewer and I don't have a clue from where to start. I been looking for a Megalogviewer manual but I couldn't find any.
Tunerstudio has been nothing but success with my project, but with Megalogviewer I'm completely lost.
Thanks in advance to all

[LT401Vette]

The log you attached is a Trigger Log, That is for high speed capture of your ignition trigger times, it only contains information pertaining to that.

To use VE Analyze you must capture a standard msl data log. To do this start a log using the main menu:
Data Logging --> Start Data Log.

[Hank Rearden]

Thanks. As usual, so obvious !
One more question: could tune analyze live and data logging run together? ( and then run VE analyze).

[LT401Vette]

You can data log while running VEAL, but you wouldn't want to run VE Analyze in MLV again using that log.

When using VE Analyze in MLV it is important that there were no tuning changes made during the data log. The msq must match the tune that it was running on during the entire data log.

[Hank Rearden]

Understood.
Thanks.

[Hank Rearden]

Can we say that once the VE table is more or less well tuned (via Veal and "butt") is more accurate to ran VE analyze than keep tuning with Veal?

[LT401Vette]

Can we say that once the VE table is more or less well tuned (via Veal and "butt") is more accurate to ran VE analyze than keep tuning with Veal?

Not really, I wouldn't say that. They both work mostly the same, but VEAL still has variable lambda delay.