patsmx5

iTrader: (16)

I also do this method. If I do what poobs is doing, sometimes the changes don't show up on the msq. No idea why, but sometimes it works, sometimes it doesn't. So I will analyze, accept, rightclick table, export, save VE table as whatever. Then close out MLV and reopen my msq in megatune, go to ve table, then file, import, click my new table, open, burn changes. THEN save my msq. Then it's there.

poobs

iTrader: (1)

Going to have to try that way too, thanks.

Now here is something ....
It is just a thought however - The MSQ that I started with was donated by a friend who has virtually the same car. I liked the way he rescaled the tables for a normally aspirated car so I used it instead of the base tune that came with my PNP.

He had already done a lot of tuning using MLV etc

Could the fact that I was using the "Easy" setting in MLV have sort of forced changes ?

Thank you all for the great advice.

Joe Perez

iTrader: (8)

I just ran your log and MSQ through MLV and it worked fine. I set my min MAP to 30 and my min RPM to 1500.

Now, it did make a change in the 1200 RPM at 28kPa cell, but understand the reason for this. The limints you set (RPM and MAP) refer to datapoints in the log. In other words, it will ignore all datapoints below the limits.

However, the scaling of your table is such that 1500 falls between two columns (1200 and 1800) and 30 falls between two rows (28 and 36). This is perfectly OK, you just need to understand what's going on. The beauty of MLV is that it interpolates very intelligently between cells. When it encounters a datapoint that's between two (or four) cells it will distribute the correction between those cells weighted by the distance from center to each one. So it's simply spreading correction from the 1500-1800 RPM datapoints between the 1500 and 1800 columns, and spreading correction from 30-36 kPa datapoints between the 28 and 36 kPa rows.


As a note, I always export VEX files from MLV and then import them into MT, rather than doing whole MSQ files. It's quicker and easier.


As a second note, there was some discussion earlier about using the manual 12x12 AFR table in MLV, rather than letting MLV operate on the 8x8 AFR table out of the MSQ. For the love of gods, please don't do this. You never get it absolutely zeroed in if MLV is making corrections based upon one table and EGO is working off another. It's like having your stock ECU fight with a piggyback.

poobs

iTrader: (1)

Great!!! Thanks soooo much Joe !!!

As far as choosing AFR tables - All I am doing is choosing the one that have values that I recognize as the same as those on the AFR values in MT.

On my MLV that is AFR#1 or something like that and it is an 8x8 -Is this ok?

Joe Perez

iTrader: (8)

That's good- on the VE Analyzer window, you want to be looking at afrBins1 on the dropdown shown below, which causes it to read the AFR Targets 1 table from the MSQ. This way, VEA is working towards the exact same AFR targets that the EGO function in the MS is.



What you don't want is to select Default AFR. This gives you a 12x12 table which has no correlation at all to the MS's own AFR targets table. You can enter values manually if you want, and MLV will try to achieve them, but it's a lot of extra work and it actually makes MLV do a worse job, since even if you get a VE table that's absolutely 100% perfect from MLV's point of view, the MSs EGO function will be constantly trying to achieve slightly different targets.

AbeFM

iTrader: (3)

It's not even an MS-II thing, I just never thought to use anything but the AFR one. It's just easier to carry the targets around in the MS, so I know it's tied.

Yeah - maybe it's an MS-II thing that it doesn't work. I'm not sure why not, but I had lots of issues with it. Plus, I like having a record of saved .vex's which show how things developed. You can even (though it's a formatting nightmare) do much of this in excel. When I was first scaling maps from MS-I to MS-II I used this.

Also, though for me it's touchy and half the time I have to email the guy who wrote MLV... it will (from my request) read mulitple files. So instead of saving loading saving loading... just load multiple logs in the same dialog (shift-click with the alternate dialog), and then run autotune. Timestamps are off but it works well.

Someone on the forum also made a log-appender which will accomplish a similar thing.

poobs

iTrader: (1)

Thanks joe & I totally agree about the table !!! No need to do more work than I need to.

I'm not sure if my logic is right but I took a drive with the Original version of my friend's MSQ while watching my A/F on the lap top ( not an easy feat).

I guess because of his handy work on a virtually equal miata the A/F ratios are great. They are somewhat lean on light cruise, increase with KPA and RPM yada, yada, yada. So I'm going to leave this probably pretty much alone.

Maybe take a long log and analyze with MLV set to "hard"

I'd really like to move on to do the VTPS so I can cure my tumbling idle