theonewithin wrote: ↑Sat Apr 03, 2021 12:31 am…It is only required when there have been large changes between versions.
Correct. There are multiple ways to accomplish a FW upgrade, and for most it is simply saving your current tune with a new name (it's a backup), and uploading the new FW. When you do, differences and issues will be shown by TunerStudio.
Note them and make the settings changes. Done.
Rollback: If any issues are found (something perhaps you didn't realize was different), you can always upload the old FW, and load the tune you saved with the new name (your backup). Bingo, you are back to where you were before the change, like nothing happened.
I never use Current Tune for my tune, and always save each significant change in my tune with a new descriptive name. This allows experimenting or exploring, but rolling back at any point if issues are found later, without trying to remember what I changed and when.
If moving through a new FW with major differences, you can choose to again use the first method and make your changes afterwards; or copy chunks as mentioned earlier, or export tables. But quicker (for me) is to copy the tune's tables into the new Base Tune first, upload, then make the proper new settings changes required in the new FW. Your tables are easy to find in the tune file with a word editor. Copy and paste. Much easier.
For example, here is the VE Table section of a current tune. I just copy the table and header values in it, and paste it into the new FW's Base Tune (rename it). Repeat for other tables (Spark, AFR, dead-times, etc):
Code: Select all<constant cols="16" digits="0" name="veTable" rows="16" units="%">
[highlight=gray]69.0 65.0 65.0 65.0 49.0 51.0 52.0 54.0 55.0 55.0 55.0 55.0 56.0 56.0 56.0 56.0
69.0 65.0 65.0 68.0 53.0 56.0 57.0 58.0 58.0 58.0 58.0 58.0 58.0 59.0 59.0 59.0
71.0 65.0 66.0 74.0 57.0 59.0 60.0 61.0 61.0 61.0 61.0 61.0 61.0 62.0 62.0 62.0
74.0 72.0 70.0 67.0 60.0 62.0 63.0 64.0 64.0 64.0 64.0 64.0 64.0 65.0 65.0 65.0
79.0 78.0 76.0 73.0 64.0 64.0 65.0 65.0 66.0 67.0 67.0 67.0 67.0 68.0 68.0 68.0
84.0 83.0 82.0 79.0 82.0 84.0 87.0 91.0 91.0 91.0 91.0 89.0 87.0 85.0 83.0 81.0
90.0 89.0 87.0 86.0 88.0 89.0 91.0 94.0 95.0 95.0 94.0 92.0 90.0 88.0 86.0 84.0
95.0 94.0 93.0 92.0 93.0 94.0 95.0 97.0 98.0 98.0 97.0 96.0 94.0 91.0 89.0 87.0
100.0 100.0 99.0 98.0 98.0 97.0 98.0 100.0 100.0 99.0 99.0 98.0 96.0 94.0 91.0 89.0
106.0 99.0 97.0 99.0 101.0 103.0 104.0 106.0 106.0 105.0 105.0 104.0 101.0 99.0 96.0 94.0
112.0 104.0 103.0 105.0 107.0 108.0 109.0 111.0 111.0 111.0 110.0 109.0 107.0 104.0 102.0 99.0
118.0 110.0 108.0 110.0 112.0 114.0 115.0 117.0 117.0 117.0 116.0 115.0 112.0 109.0 107.0 104.0
124.0 115.0 113.0 115.0 117.0 119.0 121.0 122.0 123.0 122.0 122.0 120.0 117.0 115.0 112.0 109.0
130.0 121.0 118.0 120.0 122.0 125.0 127.0 128.0 129.0 128.0 128.0 126.0 122.0 120.0 117.0 114.0
136.0 126.0 124.0 126.0 128.0 130.0 132.0 133.0 134.0 134.0 133.0 131.0 128.0 125.0 123.0 119.0
142.0 132.0 129.0 131.0 133.0 136.0 138.0 139.0 140.0 140.0 139.0 137.0 133.0 130.0 128.0 124.0 [/highlight]
</constant>
<constant cols="1" digits="0" name="rpmBins" rows="16" units="RPM">
300.0
500.0
800.0
1100.0
1400.0
1700.0
2000.0
2500.0
3000.0
3500.0
4000.0
4500.0
5000.0
5500.0
6000.0
6500.0
</constant>
<constant cols="1" digits="0" name="fuelLoadBins" rows="16" units="kPa">
20.0
30.0
40.0
50.0
60.0
70.0
80.0
90.0
100.0
110.0
120.0
130.0
140.0
150.0
160.0
170.0
</constant>
</page>
Much quicker, and no re-labeling column and row headers, etc. Again, this step should only be considered or required with major FW code changes. Otherwise you can use the first method and take time to examine every setting before running.
There are other methods, and what you are wanting to do will guide the way you do it. If moving to a FW with big changes, I do suggest running the eeprom_clear sketch before uploading the new FW, then proceed as-before.