[Showdown]

Hey Rutager, et al…

Not to hijack thread but it’s topical. I can create a separate thread later with pics if there’s interest. I’m out of town for a few days though so it may be a week…

There are two ways; table switching and secondary table.

I wasn’t having great luck with table switching (jamie and I were comparing approaches in real time and he had luck but he has a PC and I have a Mac and we suspect there may be a software difference as we set them up the same.) but I had success with secondary tables.

Secondary tables and table switching are ostensibly used for boost applications but we can trick TunerStudio and Megasquirt into using them for load in non boost applications.

I’ll have to reference my TunerStudio setup and I’m away but IIRC, the setting is in “Advanced/Boost” and you turn secondary table on and set what y axis is uses (alpha-n, SD, %baro…) and it MUST be the same as your primary VE table 1. You then set the switch point (80kpa, 90% baro, etc) and whether the formula is additive or multiplicative. I use additive which adds the bottom row of VE table 3 (your secondary table) to the top row of VE table 1 (your primary table) this is only for secondary table not table switching.

If you’re using table switching that gets setup in general settings and it creates VE 1 and VE 2.

Then you tune. You have to run two VEAL windows, one on each table at the same time (it works) in order to autotune. But really, autotune should only be used to get a basic basic running setup and manual tuning should be the primary way (I firmly believe this for any efi system: autotune is just to get you in the stadium). Plus, you now have a lot more resolution so you really don’t want to leave it up to the computer which is kinda dumb.

It really helps to start off with a good single table tune and use those numbers in the bins on the two tables. Just transfer over the applicable values and manually interpolate (or you can use the auto interpolate) between the known points.

On my setup, the only odd part that took me a minute to figure out was the transition from VE 1 to VE 3. With additive I had to set the values in VE 3 as if I were adding them to the last, top row value of VE 1. So some of the bins on VE 3 were 2 & 3 because they were added to the previous VE bins of 50 & 51. If I used 52 & 54 the car was so rich it died because the actual bin values were 50 & 51 (from VE 1) PLUS 52 & 54 (from VE 3) making 102 & 105 which was way too rich. But by using bin value 2 & 3 on VE 3 they were added to 50 & 51 from VE 1 giving me 52 & 44… make sense?

It’s a bit more convoluted as you have two tables to manage now but the resolution is amazing.

Not super easy, but worth a try on a second, experimental tune.