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

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

 ______  
(  __  \ 
| (  \  )
| |   ) |
| |   | |
| |   ) |
| (__/  )
(______/ 
         

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

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

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:
In case of bug reports please do not forget to write * VemsTune version * V3 firmware version. * Zip and publish your saved config (vemscfg) and Tools/firmware/config download when appropriate. ** I have the same problem(0.9.85) *Could it be possible to add a background to the gauges? ** Currently not. Need some implement. *I think of a simple object like jpg/bmp image? (example Kevlar background) *If we type in the firing order could the value of injector and ignition table be automatic generated if using standard inj A = cyl 1. inj B = cyl 2 same with ign. nice job -Peter An installer says: "When a customer has problems I like to be able to send finished mtt files to him, these can then be sent with command line tools or if he has communication problems I help him with bray over the phone" Finished files make a lot of sense. It was planned that one would send project file, where the RIGHT firmware and/or config can be uploaded with 1..2 clicks (not lost in menu-s). Note that the vemstune over the network will be very useful in many cases, but dealers still need a way to prepare project / vemscfg files (in a documented way!) that can be uploaded extremely quickly (without using menu-s) by a computer-illiterate child supported over the phone. * '''Remote tune''' over TCP connection feature is in integration/testing phase, planned to work only in newest firmware only with SIPR protocol. ---- '''Firmware Version''' *Can not find the new function (wheelspeed, wheelspeed-based launch and the new knock-threshold-map) in 1.1.61 non ps2 in VemsTune when i make a new empty project. ** I found a new row in the defaultfirmwareconfig directory in the new 0.10.0 VemsTune called '''CompileOptions: 0000001B''', and loaded into VemsTune, the program showed the Mics Output new settings. I played it with a bit, but not got any logics. With ff it shows the alternate knock settings to. How this varible work??? How do I get 1.0.79 to work with the current version VemsTune? ----- VT version 2010-07-16 * As alpha N mode doesn't work with tune by statistics I am using CSV exporting. CSV export scales TP to between 0-100 whereas megalogviewer expects 0-255. ** Is it possible to modify ini file so that CSV export scales TP to between 0-255? Thanks ----- VT version 2010-07-19 fw:1.1.70, when i wanted to erase the sd card (tools/sd card log/erase) vt crashed. After erasing the sd with on older VT, start, stop, extended overview functions are work. ----- VT version 2010-10-01 When attempting to establish the initial config for config B, the change will not write correctly, resulting in strange behavior. It seems that writing the config.txt manually and running ManmcS1 seems to fix the problem and afterward everything seems to work correctly. From a conversation with Marcel on IRC: (5:47:32 PM) a4kquattr: the other ecus I've tuned that have this sort of feature, the "null" second config is to be expected. usually you save out the config file (eg vemscfg), do the conf switch, then open the saved config to make both halves equal. (5:49:37 PM) cell_: yes, that works most of the time. But IIRC in rare cases when condswitch value before initialized in 2nd table is unfortunate, it won't. That's what they found recently, and dunno the state of the cure * fixed ---- '''VT 2010-11-15''' (nightly) * still '''cant save config from offline mode''' ** should be easy to reproduce and fix. TODO: fix before 2010-11-18 *** fixed (in next release) * and still cant handle ecu restart ** just '''unplugged''' (the RS232, not the usb) in and back, '''got sql error''' , also, more important, when turning on/off key in the car to try to start it. *** can't reproduce, need more details ** not the same crash as way back. Easier to reproduce than the old problem (At least i thought so, first time easy, second time has yet to happen...) * when switching between different config windows using pgup/pgdn, the new window looses focus ** works when clicking the arrow keys *** can't reproduce, need more details * When uploading 1.1.85 firmware, vemstune hung upon almost showing the dialog asking to upload a config file ** Restarted program, when i was connected, i clearly got the message "Safe Mode" - thats good. Reuploaded config and I'm back on track.. * Log viewer ** Many variables (only percent based?) in the log viewer are using the wrong symbol descriptors, als_igncutGauge is used extensively. *** It's work good, but the mentioned variables has the same descriptor type. If did not set the descriptor directly, using the first one, in this case the als_igncutGauge. You can set any descriptor (if the type matches) in the editor. *** Today(nov.15.) (or tomorrow) will be out a new VT release with correct MultiGraph profile settings. * "Table 3D" gauge size and position is not saved after editing. Switch to another gauge group or just close the current one, then bring it back up and you will see the error. *** Will be save the size and positions of the gauges when closing the group (next release)
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.