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

 ___   
|  _`\ 
| (_) )
| ,  / 
| |\ \ 
(_) (_)
       
       

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

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

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

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:
'''Add issues/bugs to most recent release at the top''' Do not forget to mention at least: * VemsTune version (or release date if possible) * V3 firmware version. * Zip and publish your saved config (vemscfg) and Tools/firmware/config download when appropriate. * Other information that can be relevant to see under what exact conditions the symptoms can be seen (a report is usually useful only if it can be reproduced by the programmer) ** [http://vems.hu/vt/help/main/error_reporting.html reporting from VT] automatically includes a lot of information that can be important but easy to forget. The best way is a summary on this editable page with a link to the report generated from VT. * [http://www.chiark.greenend.org.uk/~sgtatham/bugs.html How to Report Bugs Effectively] article by Simon Tatham '''Known issues''' * On V3 ECU newer than 2011 03 01 do not use coolant and air patch files with VemsTune older than 2011 03 23 * Documentation needs to be added * CPU consumption and eye candy ** Graphics performance of gauges, multi graph, and all eye candy are dependant on certain combinations of hardware video drivers and wxWidgets. ** ATI graphics chipsets are known to have unreliable 2D grahpics acceleration. ---- '''VEMStune 2014-07-29 (development version) - NOT released''' * Downloaded file 2014-07-29 reports to be '''v1.5.26 (2014-05-09)''' ** Please update this info on every release. * The curve editor does not allow offline changes to config files. The values revert back to what they were. Importing settings from a different config file seems to work. * Dirac filtering for third trigger seems to revert back to "enabled" as well. Any versions in "Dev" are not ment to be used at all, these are merely development snapshots many of which contain some unfinished work (used for internal testing). Please restrict to either "stable" or "nightly" versions as recommended on: http://vems.hu/vt/ Best regards, Dave The problems mentioned are still there with (the real actual) v1.5.26 (2014-05-09), that was the main reason I upgraded to the version dated 2014-07-29 and reported it as I wanted to avoid reporting bugs in "old" software. ---- '''VEMStune v1.5.26 (2014-05-09)''' If you connect a GPS NMEA device through serial port you can view GPS data in VemsTune gauges and datalog them as well. I have connected my Samsung S4 telephone using [https://play.google.com/store/apps/details?id=com.Saenko.GpsOverBt GPS over BT] app. This works as expected for viewing live data except for one thing : * Speed is reported 10x too high. When viewing data in the log viewer there are other issues: * GPS speed gauge is not updated when you navigate in the log, all other gauges update properly. * GPS speed gauge will update only when you play back the log. * GPS speed graph displays only 0.0 km/h. ---- '''VEMStune v1.5.25 (2014-04-01)''' Opening logs (and using log view even offline) is horribly slow in this version, even on a very powerful laptop (core i7 -haswell- with 12GB RAM and SSD). Issues seem to almost go away (or speed is at least a lot better with previous nightly 2014-01-08, but even that was unacceptably slow with very slow PC or large logs). '''Fixed 2014-05-08''': if CPU cannot keep up drawing rate, draw only the most uptodate fresh screen (not each keystroke or scroll event). * Please upload this version asap ---- '''Vemstune 1.5.23''' Calc stat runs when update button is pressed. Causing Vemstune to crash. Ideally this feature can be completely turned off. A: It can be turned off in 1.5.23 in Preferences->Gauges->MultiValueGraph->Enable statistical calculations at start->set to disabled. (default) Perhaps you imported settings from previous version ? - DB G: It still does it when the Update button is pressed -despite the setting being set to Disabled Setting up a flag in log viewer is impossible if there are four channels already, so one must take one of the already channels and change that to flag, then add the channel again, this is inconvenient, so when you select the + sign there should be the option of adding a FLAG ---- '''Vemstune 1.5.20''' Calculating Stat when opening log viewer tab causing Vemstune to chrash. Is it possible to turn this off? * We couldn't reproduce that so far (even with loooong vemslogs). Do you have a vemslog so it becomes more likely to be possible to reproduce ? **(fphil) starting with the August dev version, "calculating stat" start automatically, but no crash in my case. Of course one does want this feature to be chosen as before *** I most certainly would like this to be choosable as it can take a number of seconds to re-update since the stream is not live and thats just a waste of time if you aren´t interested in the stats in the first place. *** or let it run in background as unimportant process. It additionally slows down use of already slow log viewer. Min/max is very welcome. But not as >10s freeze of whole application. GintsK. '''Vemstune 1.5.9''' AnalogInputCalibrationWizard doesn´t work properly. Min 1 , 100 Max 4 , 400 Gives Scale 249 * 2 Input is 3v , results should be 300, comes out as 1494 Min 1 , 100 Max 5 , 500 Gives Scale 250 * 2 . Input is 2.5v, should come out as 250, comes out as 1250 (MaxValue - MinValue / MaxV-MinV ) = Scale Offset = MinValue - (Scale * MinV) Value = Volt * Scale + Offset Unless I´m missing what A and B do? Any reason why the values aren´t just 16bit, rather then having an offset and scale multipliers? Adding new descriptors a problem when added to Misc, but Misc isn´t a selectable list, now impossible to create a new or edit said descriptor. '''VemsTune 2013-03-26 1.5.3.''' Vemstune page_config ini Small vemstune bug, when limits are set on variable range, like: ; todo - strangely vemstune does not limit input to selected range, 0-3.1, is this a bug ?? fuelcut_delay_time = scalar, U08, 29, "s",0.1,0.0, 0.0, 3.1, 1 ; eof todo - db Vemstune does not limit input on set range (in this case 3.1) but rather on max variable size times multiplier (25.5) ---- '''VemsTune 2013-06-30''' Offline editing config : Can't edit the curves with arrow keys or dragging with the mouse, only number input from keyboard works. Example: "warmup enrichment curve" Tested with VemsTune 2013-03-26 and config file from firmware 1.2.11. *We were able to reproduce the problem. We're working to fix the problem. SD card does not record the switched config (say config A) when started to record under config B Tested with VemsTune 2013-06-30 and config file from firmware 1.2.14. ---- '''VemsTune 2013-02-15''' Primary Trigger Visual doesn't understand 8+ cylinder engines (eg. 16 resets the cylinder numbers, bad). '''Fixed'''. (Get newest VT). Works upto 16 cyl. ---- Wish-item. '''Solved: just click the "recycle" icon under "Show / Hide Help F2"''': if toggled by single press, the gauges will update as cursor moved Maybe default-on would be a more intuitive... '''2013-03-26 Digital displays on left side of Multi graph''' - report started from MembersPage/KevinBlack 's sentences * also appears when doing a Fresh Install (of [http://http://vems.hu/vt/ VT 2013-08-23]) on formatted laptop Every time I install a newer VemsTune (I use 2012-06-29 because it "works") - the first thing I notice is that the * '''digital displays on the left side of the multi graph view do not change when the cursor is moved left to right''' (stuck at 0.0 sec values ?). '''OFFline editing, and Yes, stuck at 0.0 sec values (~300 rpm for example)''' * Screen pictures: http://www.vems.hu/files/KevinBlack/Graph%20Screen%201.JPG http://www.vems.hu/files/KevinBlack/Graph%20Screen%202.JPG * original sentence in email (2013-08-24 15:57) was: "digital displays on the left side of the multi graph view do not change '''then''' the cursor is moved left to right." (yes, it was "then" indeed, now we know: actual intent was "when"). * And, (most important) the "blue dot" in the Tables (VE, Ign, etc) does not move with the cursor. * The only '''way to get those things to change is to move the play log slide bar at the top of the screen.''' ** Is it related to "being connected to ECU" or "playing previously recorded .vemslog" ? '''Offline Editing''' * Hopefully this is just a (unnecessary) setting that is an easy fix? ** yes, just click the top-left icon "recycle" button to autoupdate as you like ---- '''Vemstune 1.3.1 2012-07-30''' Problem with Editor after saving a certain view. It will add more instances of the same channel, this has been a problem on many older versions as well, I don´t think any version has ever not had this problem. http://www.vems.hu/files/M50Turbo/editorproblem.jpg Also just to note : As discussed with Emil it would be nice if the whole view could be saved as a single file for export to customers, this means gauge views and multi graphs all saved into a single file. ----- Vemstune 2012-01-30 Using firmware 1.1.98 Y axis values are wrong after upgrading to this firmware. Also bug after uploading firmware is that the ecu is stuck in safety mode after firmware update. Tested back in 2011-12-21 and no problem there. ----- Vemstune 2011-15-11 * If created a table and changed table data to other then default the new layout is not being saved. Groups -> Groups editor -> new ** Fixed in the latest nightly release: [http://vems.hu/download/VemsTune/NIGHTLY/VemsTune-Install-2011-12-22.exe VemsTune-2011-12-22] * [http://www.vems.hu/wiki/index.php?action=history&page=InputTrigger%2FHondaFTwentyTrigger wish] vemstune should chage booth measure at tooth_cnt to the same number at was in 1.1.96 (when uploading a config from <=1.1.96 to a firmware >=1.1.97) ---- '''FIXED: VT 2011-06-04''' flags fake warning For the Audi trigger divide by 3 setup (default VemsTune/QuickStartAudi ) show a warning on validate. * also displays an error for the greyed out secondary trigger=25 raw value ** fixed since 2011-06-15 ** was showing fake warning with rising edge (no warning when falling edge). ** since this was a 1-liner ini fix (configcriteria) maybe also fixed with earlier releases by ini-update ? Maybe, but new VT is better anyway! ---- In vemstune/config/include page-config-[version].ini change sdcard_choice sdcard_choice = bits, U08, 149, [0:7] , "INVALID", "INVALID", "INVALID" In to sdcard_choice = bits, U08, 149, [0:7], "Disabled", "Enabled" I don't know if its good but it works getting your knock working again in channel 0. ---- '''VemsTune 2011-05-27''' (report by Mattias) * Overall : All windows with any kind of text in them are not possible to mark and copy text. This is very useful if you want to describe a problem or just cut and paste some information to anyone. ** F1 for help dialogs ** Verify config window * When making offline changes to a config, like changing values of a VE table, then pressing the remap button erases all changes you made. Very, very irritating. *In "injector settings" dialog: ** Strategy is not spelled startegy. Traditional is not spelled Tradicional. * In "PWM Idle control", make drop down for frequency wide enough ** only displays "00." ** should read "100.00" * Boost rpm bins should have reasonable defaults: 1000 rpm, 2000, 3000, etc. * In all 2D tables, when using remap function it should be possible to change the upper and lower most bins to more extreme values. Extrapolate from previous extremes? '''VemsTune 2011-01-20''' * When changing from Celcius to imperial measurements in File->Firmware parameters, digital gauges do not change unit description. * Gauges move down by 73.3px and to the left by 1.3px on Main overview each time display is changed from group to group. Gauges shrink in size by 1px in horizontal and vertical directions each time as well. Example: view Main overview group, press Shift+8, press Shift+1. Repeat to watch gauges migrate down the page. Same thing happens if Main overview tab is closed and reopened. ** How do you mean "73.3px", and "1.3px"? You can move and resize every windowed items only by whole integer value. * If all gauges are removed in gauge edit mode, then a gauge file is imported, gauges are added twice and in different positions. ---- '''Fixed items''' May not appear until 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.