Changes by last author:
Deleted:
| * upload config (after firmware update) |
|
Failing one or more steps will cause problems
* counterintuitively, it more likely causes problems for experienced installers ** who have been using VemsTune for several years, and got used to "it just works" ** => some might expect that very old VemsTune-s can "predict the future" and would magically work well with firmwares that became available several years later, even without being updated (unfortunately it can NOT). |
| Always check "validate" results (and fix errors / warnings, ask for help on wiki MembersPage if uncertain), don't expect that a misconfigured ECU (with output conflicts, invalid values or otherwise broken config) will work (without surprises) as expected. |
|
After firmware update, config upload is essential (either as a step of "firmware upgrade wizard", or afterwards). When uploading 1.2.31 .vemscfg to newer (eg. 1.2.38) firmware, most of the new features/variables will be initialized according to sample (usually "disabled") values (assuming VT is newer than fw or newest, and "update ini from web" has been run - successfully).
Always check "validate" results (and fix errors / warnings, ask for help on wiki MembersPage if uncertain), don't expect that a misconfigured ECU (with output conflicts, invalid values or otherwise broken config) will work (without surprises) as expected. ---- Notes: * do NOT edit the .vemscfg file manually unless you know what you are doing ** if changing the serialnumber, carry the calibration values (like wbo2_pump_pw_zero): the calibration values are only uploaded from the .vemscfg to the real ECU if the serialnumber matches ** the firmware version should NOT be edited manually (that would disable the handy feature in VemsTune that fills in new variables, when, eg. uploading 1.2.31 .vemscfg to 1.2.38 firmware - resulting in many "invalid" values). |