How To - Switch to Versa Tune

Discussion in 'Mazdaspeed 3/6 ECU Tuning' started by deldran, Jul 27, 2016.

Tags:
Watchers:
5 users.
  1. deldran

    deldran Greenie Member

    Joined:
    Feb 10, 2016
    Posts:
    45
    Trophy Points:
    18
    Location:
    Bettendorf IA
    Ratings:
    +39 / -0
    So I made the switch to VersaTune. While migrating my ATR tunes, into Versatune I documented what tables in ATR, translate to tables in VersaTune. Many translate directly into VersaTune others do not, and some tables in VersaTune do not exist in ATR.

    The document is just the table translations. I hope to use this thread to talk about any little quirks that need to be observed when making the switch, and hopefully some good discussion on what exactly some tables do.

    I hope this is helpful to the community. Maybe we can make it a sticky as more people make the switch. If anyone discovers something I missed or anything of that nature, please let me know and I will update it.

    Thanks to @phate; there are some more goodies in the document

    https://onedrive.live.com/redir?page...O5TeBCdLQ1fOUQ

    @phate; @Lex; @rfinkle2; @Justin@Freektune; @Steve@VersaTune; and any other tuners I have forgotten.

    Quirks to look out for

    The big thing is to watch your Axis values and units of measure while doing this.
    Also many tables Scale out to 8k so be sure to adjust the rows above 7k

    Absolute Limits tables

    Most of these tables are pretty straight forward. Just remember to watch your axis values

    Accelerator Pedal Calibration
    These all translate directly with the exception of "APP Multiplier Speed Adjustment" The Axis values do not line up

    Boost Control
    These all copied over nicely, just remember several of the tables in VersaTune scale out to 8k rpm. ATR only goes to 7k so make sure to adjust the 7500 and 8k columns

    Fueling
    One thing I noticed with these tables. The Closed Loop tables have lower loads listed than the OL tables. So if you copy your OL tables into the CL tables, you will notice the last couple rows did not get changed. Make sure to copy into the first load value that matches on the right, then adjust the first few rows accordingly.

    Also the Y axis, which is load, does not share the same values as ATR, so when copying from ATR into VersaTune, be mindful. What I did was copy the rows that where close into VersaTune, then I vertically interpolated between the modified rows to adjust the unmodified rows.

    VersaTune used Lambda, and does not use AFR so make sure to switch ATR into lambda

    Also it seems ATR has Fuel Specific Gravity labeled wrong. ATR shows the unit of measure as kg/m^3 when it should be kg/l. Which is how versatune labels it.

    there is also no injector scalier at the moment, so if migrating a E85 tune be aware of this

    Gear Tables
    These all translate almost exactly from ATR, they are not covered in the document for this reason

    Idle
    These also translate without any issue

    Ignition
    The big thing here is the Y axis which is Load does not line up with the Load axis in ATR. So I used the same method that I used in Fueling tables to get this translated over.

    Load Targeting
    The axis values in this tables line up between VersaTune, and ATR.
    Be aware that VersaTune only does Load based tuning. This means that the values in these tables will need to be modified, if you do boost tuning in ATR, since the have likely been set to a number that your car can not achieve. Running these tables from ATR unmodified could = ZZB. You have been warned.

    Sensor Calibration
    Be sure to set VersaTune to use Metric units. then you can copy your MAF cal from ATR directly into VT.
    It seems VersaTune has the same number of MAP related tables, but I could not figure out exactly how that correlated with the MAP tables in ATR

    Throttle Control
    These copy over without issue

    Valve Timing
    These copy over without issue
     
    • Like Like x 10
Loading...

Share This Page

Users Viewing Thread (Users: 0, Guests: 0)