Updating tune to current firmware
06-19-2014, 10:40 AM
#1
Senior Member
Thread Starter
iTrader: (1)
Join Date: Apr 2011
Location: Columbia, SC
Posts: 1,332
Total Cats: 87
Updating tune to current firmware
I'd like to apologize in advance, as I spent my evening last night resoldering my MS harness and forgot to take screenshots of the menus in question below. So, this will probably end up being a somewhat vague post, but hopefully I can portray enough of what I'm dealing with so somewhat can suggest a possible resolution.
So I have a base tune that is on an older firmware, and I wish to use it on the newest beta firmware that has alternator control added. My MS3 has the newest firmware loaded to it.
So, I created a new project, and used the .ini file for the newest firmware. Then when I go to file>open msq, and load the tune, I am presented with a series of warnings. Most of these warnings were unit mismatches I suppose I'll have to go back and manually convert. Some of them, like kPa -> % I don't understand as of now, but that is likely because I haven't looked enough into the settings of them yet to see if there is more than one way to run those settings. I'll post the error logs from the two tunes I'm working with below. Some are also just false positives, such as "s" to "sec" being recognized as an invalid unit change.
Secondly, and the issue that has made me more curious as to whether my process for doing this is correct, is with new menus. It seems that with a menu that did not exist in the old firmware (say, alternator control), ALL the values default to -214748364.8, even some that are enabled in menus such as the one pertaining to the fuel pump.
Basic question I guess I'm asking is: Is this the proper way to get a tune on older firmware running on newer firmware?
Here are the errors logs. Sorry, pastebin is blocked at work (who knows why), so I've included them in <code> tags.
EDIT: I had to attach the other log, as I exceeded the 15k character limit.
So I have a base tune that is on an older firmware, and I wish to use it on the newest beta firmware that has alternator control added. My MS3 has the newest firmware loaded to it.
So, I created a new project, and used the .ini file for the newest firmware. Then when I go to file>open msq, and load the tune, I am presented with a series of warnings. Most of these warnings were unit mismatches I suppose I'll have to go back and manually convert. Some of them, like kPa -> % I don't understand as of now, but that is likely because I haven't looked enough into the settings of them yet to see if there is more than one way to run those settings. I'll post the error logs from the two tunes I'm working with below. Some are also just false positives, such as "s" to "sec" being recognized as an invalid unit change.
Secondly, and the issue that has made me more curious as to whether my process for doing this is correct, is with new menus. It seems that with a menu that did not exist in the old firmware (say, alternator control), ALL the values default to -214748364.8, even some that are enabled in menus such as the one pertaining to the fuel pump.
Basic question I guess I'm asking is: Is this the proper way to get a tune on older firmware running on newer firmware?
Here are the errors logs. Sorry, pastebin is blocked at work (who knows why), so I've included them in <code> tags.
Code:
58 Warnings: Warning: Parameter in .msq, but not valid for current firmware: No options found for Bit EcuParameter:IdleCtl equal to the proposed PWM Closed-loop Warning: MSQ Units Mismatch for IACcrankxt! s found in current configuration, sec found in MSQ, values were not converted to new units. Warning: MSQ Units Mismatch for ego_startdelay! s found in current configuration, sec found in MSQ, values were not converted to new units. Warning: MSQ Units Mismatch for knk_trtd! s found in current configuration, sec found in MSQ, values were not converted to new units. Warning: MSQ Units Mismatch for knk_tadv! s found in current configuration, sec found in MSQ, values were not converted to new units. Warning: knk_maxmap row:0, col:0, One or more value higher than maximum: 350.0, Set to the maximum value: 210.0 Warning: knk_hirpm row:0, col:0, One or more value higher than maximum: 8000.0, Set to the maximum value: 7500.0 Warning: MSQ Units Mismatch for pwmidle_shift_open_time! s found in current configuration, sec found in MSQ, values were not converted to new units. Warning: Value in .msq '"Off"' for parameter: spk_conf2_gm is of a type that is not compatible with the current firmware.This will be ignored, please correct manually. Warning: Value in .msq '"Off"' for parameter: spk_conf2_tfi is of a type that is not compatible with the current firmware.This will be ignored, please correct manually. Warning: Value in .msq '"Off"' for parameter: spk_conf2_ngc is of a type that is not compatible with the current firmware.This will be ignored, please correct manually. Warning: Value in .msq '"16x16"' for parameter: feature4_0VEtblsize is of a type that is not compatible with the current firmware.This will be ignored, please correct manually. Warning: MSQ Units Mismatch for fc_ego_delay! s found in current configuration, seconds found in MSQ, values were not converted to new units. Warning: MSQ Units Mismatch for pwmidle_close_delay! s found in current configuration, sec found in MSQ, values were not converted to new units. Warning: MSQ Units Mismatch for pwmidle_pid_wait_timer! s found in current configuration, sec found in MSQ, values were not converted to new units. Warning: MSQ Units Mismatch for pwmidle_targ_ramptime! s found in current configuration, sec found in MSQ, values were not converted to new units. Warning: MSQ Units Mismatch for idleadvance_delay! s found in current configuration, sec found in MSQ, values were not converted to new units. Warning: Parameter in .msq, but not valid for current firmware: No options found for Bit EcuParameter:vss_opt2 equal to the proposed Off Warning: Parameter in .msq, but not valid for current firmware: No options found for Bit EcuParameter:vss1_an equal to the proposed Off Warning: Parameter in .msq, but not valid for current firmware: No options found for Bit EcuParameter:vss2_an equal to the proposed Off Warning: Parameter in .msq, but not valid for current firmware: No options found for Bit EcuParameter:water_pins_pump equal to the proposed Off Warning: MSQ Units Mismatch for boost_ctl_lowerlimit! kPa found in current configuration, % found in MSQ, values were not converted to new units. Warning: Parameter in .msq, but not valid for current firmware: No options found for Bit EcuParameter:MAFOption equal to the proposed Off Warning: MSQ Units Mismatch for ac_delay_since_last_on! s found in current configuration, sec found in MSQ, values were not converted to new units. Warning: MSQ Units Mismatch for idleve_delay! s found in current configuration, sec found in MSQ, values were not converted to new units. Warning: MSQ Units Mismatch for boost_ctl_lowerlimit2! kPa found in current configuration, % found in MSQ, values were not converted to new units. Warning: shift_cut_rpm row:0, col:0, One or more value higher than maximum: 8000.0, Set to the maximum value: 7500.0 Warning: shift_cut_rpm12 row:0, col:0, One or more value higher than maximum: 10000.0, Set to the maximum value: 7500.0 Warning: shift_cut_rpm23 row:0, col:0, One or more value higher than maximum: 10000.0, Set to the maximum value: 7500.0 Warning: shift_cut_rpm34 row:0, col:0, One or more value higher than maximum: 10000.0, Set to the maximum value: 7500.0 Warning: shift_cut_rpm45 row:0, col:0, One or more value higher than maximum: 10000.0, Set to the maximum value: 7500.0 Warning: shift_cut_rpm56 row:0, col:0, One or more value higher than maximum: 10000.0, Set to the maximum value: 7500.0 Warning: Value in .msq '"On-Off"' for parameter: pwm_opt_var_a is of a type that is not compatible with the current firmware.This will be ignored, please correct manually. Warning: Value in .msq '"On-Off"' for parameter: pwm_opt_var_b is of a type that is not compatible with the current firmware.This will be ignored, please correct manually. Warning: Value in .msq '"On-Off"' for parameter: pwm_opt_var_c is of a type that is not compatible with the current firmware.This will be ignored, please correct manually. Warning: Value in .msq '"On-Off"' for parameter: pwm_opt_var_d is of a type that is not compatible with the current firmware.This will be ignored, please correct manually. Warning: Value in .msq '"On-Off"' for parameter: pwm_opt_var_e is of a type that is not compatible with the current firmware.This will be ignored, please correct manually. Warning: Value in .msq '"On-Off"' for parameter: pwm_opt_var_f is of a type that is not compatible with the current firmware.This will be ignored, please correct manually. Warning: MSQ Units Mismatch for RotarySplitLoad! kPa found in current configuration, % found in MSQ, values were not converted to new units. Warning: MSQ Units Mismatch for inj_trim_load! kPa found in current configuration, % found in MSQ, values were not converted to new units. Warning: MSQ Units Mismatch for amap_table1! kPa found in current configuration, % found in MSQ, values were not converted to new units. Warning: MSQ Units Mismatch for amap_table2! kPa found in current configuration, % found in MSQ, values were not converted to new units. Warning: waterinj_map row:2, col:0, One or more value higher than maximum: 300.0, Set to the maximum value: 210.0 Warning: MSQ Units Mismatch for spk_trim_load! kPa found in current configuration, % found in MSQ, values were not converted to new units. Warning: MSQ Units Mismatch for TauAcc! ms found in current configuration, msec found in MSQ, values were not converted to new units. Warning: MSQ Units Mismatch for TauDec! ms found in current configuration, msec found in MSQ, values were not converted to new units. Warning: MSQ Units Mismatch for fmap_table1! kPa found in current configuration, % found in MSQ, values were not converted to new units. Warning: MSQ Units Mismatch for fmap_table2! INVALID found in current configuration, % found in MSQ, values were not converted to new units. Warning: MSQ Units Mismatch for fmap_table3! kPa found in current configuration, % found in MSQ, values were not converted to new units. Warning: MSQ Units Mismatch for smap_table1! kPa found in current configuration, % found in MSQ, values were not converted to new units. Warning: MSQ Units Mismatch for smap_table2! INVALID found in current configuration, % found in MSQ, values were not converted to new units. Warning: MSQ Units Mismatch for smap_table3! kPa found in current configuration, % found in MSQ, values were not converted to new units. Warning: MSQ Units Mismatch for EAEAWCKPAbins2! kPa found in current configuration, % found in MSQ, values were not converted to new units. Warning: MSQ Units Mismatch for EAESOCKPAbins2! kPa found in current configuration, % found in MSQ, values were not converted to new units. Warning: MSQ Units Mismatch for fmap_table4! INVALID found in current configuration, % found in MSQ, values were not converted to new units. Warning: MSQ Units Mismatch for smap_table4! INVALID found in current configuration, % found in MSQ, values were not converted to new units. Warning: dualfuel_press row:0, col:0, One or more value below minimum: 20.0, Set to the minimum value: 70.0 Warning: MSQ Units Mismatch for psEnabled! found in current configuration, on/off found in MSQ, values were not converted to new units.
Reply
0
0
06-19-2014, 01:30 PM
#2
Senior Member
iTrader: (1)
Join Date: Sep 2011
Location: Lambertville, NJ
Posts: 1,215
Total Cats: 74
The warnings shouldn't cause you any trouble- I had over 100 and the car ran fine.
But you can get rid of them with a little work:
1. From your current tune save all the tables separately. Like VE, AFR target, ignition, boost etc.
2. Create a new project, for the current firmware (this project shouldn't show any wanrings)
3. Adjust all the settings to reflect what you had before and import the tuned tables
It took me a few hours/beers, but I'm glad I did it.
Result: You have an identical tune, but all the warnings are gone.
There may be an easier way, but I haven't found it yet....
But you can get rid of them with a little work:
1. From your current tune save all the tables separately. Like VE, AFR target, ignition, boost etc.
2. Create a new project, for the current firmware (this project shouldn't show any wanrings)
3. Adjust all the settings to reflect what you had before and import the tuned tables
It took me a few hours/beers, but I'm glad I did it.
Result: You have an identical tune, but all the warnings are gone.
There may be an easier way, but I haven't found it yet....
Reply
0
0
06-19-2014, 01:35 PM
#3
Senior Member
Thread Starter
iTrader: (1)
Join Date: Apr 2011
Location: Columbia, SC
Posts: 1,332
Total Cats: 87
The warnings shouldn't cause you any trouble- I had over 100 and the car ran fine.
But you can get rid of them with a little work:
1. From your current tune save all the tables separately. Like VE, AFR target, ignition, boost etc.
2. Create a new project, for the current firmware (this project shouldn't show any wanrings)
3. Adjust all the settings to reflect what you had before and import the tuned tables
It took me a few hours/beers, but I'm glad I did it.
Result: You have an identical tune, but all the warnings are gone.
There may be an easier way, but I haven't found it yet....
But you can get rid of them with a little work:
1. From your current tune save all the tables separately. Like VE, AFR target, ignition, boost etc.
2. Create a new project, for the current firmware (this project shouldn't show any wanrings)
3. Adjust all the settings to reflect what you had before and import the tuned tables
It took me a few hours/beers, but I'm glad I did it.
Result: You have an identical tune, but all the warnings are gone.
There may be an easier way, but I haven't found it yet....
Reply
0
0
06-19-2014, 02:12 PM
#4
Boost Czar
iTrader: (62)
Join Date: May 2005
Location: Chantilly, VA
Posts: 79,499
Total Cats: 4,080
they are already all gone.
the errors were differences in tune settings between the two firmwares. Now that you've loaded your map, the file has been converted, move along.
if you wanna feel better about it, save tune as, load tune. volia, no errors.
the errors were differences in tune settings between the two firmwares. Now that you've loaded your map, the file has been converted, move along.
if you wanna feel better about it, save tune as, load tune. volia, no errors.
Reply
0
0
Thread
Thread Starter
Forum
Replies
Last Post
StratoBlue1109
Miata parts for sale/trade
21
09-30-2018 01:09 PM
