____ 
  / ___|
 | |    
 | |___ 
  \____|
        

         
         
  ####   
 #    #  
 #    #  
 #    #  
  ####   
         

   ###   
  ## ##  
  ##     
 ####    
  ##     
  ##     
 ####    
         

 _____ 
/  __ \
| /  \/
| |    
| \__/\
 \____/
       
       

         
         
 # ###   
 ##   #  
 ##   #  
 # ###   
 #       
 #       

IMPORTANT: enter the case-INsensitive alphabetic (no numbers) code AND WRITE SOME SHORT summary of changes (below) if you are saving changes. (not required for previewing changes). Wiki-spamming is not tolerated, will be removed, so it does NOT even show up in history. Spammers go away now.


Visit Preferences to set your user name
Summary of change:
* '''VemsTune must be newer than firmware, or newest available''' (eg. latest [http://vems.hu/vt/ nightly] ) * '''"Help/update ini files from web"''' * '''upload config''' (after firmware update) * '''check "validate"''' ** fix errors / warnings ** ask for help on wiki MembersPage if uncertain 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). ---- If '''ECU seems to misbehave''' * check above (VT version, "update ini files", validate) * document outputs and functions * configure accordingly * on MembersPage detail how ECU is connected ** checklist of outputs in all cases; also inputs if relevant, and anything special, eg. how the harness and GenBoard/Manual/GroundConnections were made and installed ** how configured ( upload annotated .vemslog with characteristic filename - zipped or .vemscfg ) ** and detail what is intended ** list of important URLs (examples, or doc, VT pages) ** list of configuration items that need review (and related information to make it possible !!!) ** what is expected and what is surprising ( behaves differently from what is expected, if any) ** Sending ECU for repair is no substitute for project page, uploading '''actual''' config, using new and updated VT, checking validate and fixing warnings/errors ** Swapping ECUs is usually NO substitute for ... (see above) ** Even if you '''assume''' that config is same in both ECUs, save and publish config from both (even text compare can be used, ECU serialnumber, date, and some calibration values might differ normally) ---- '''We've seen some cases with 1.2.38 and 1.2.43''' where * ECU was sent back with invalid config (in a case, very different config than reported in issuereport) * same ECU behaved perfectly with correct config Using VT older than firmware (unless VT is the newest available, and "Help/update ini files from web" had been completed) is the wrong way of doing things, unsupported, does not make any sense, and might result in unspecified behavior. 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).
Optional: Add document to category:
Wiki formatting: * is Bullet list ** Bullet list subentry ... '''Bold''', ---- is horizontal ruler, <code> preformatted text... </code> See wiki editing HELP for tables and other formatting tips and tricks.