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)
- [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.
- [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.
Version 2018-01-4 (latest nightly) ini files updated
Import previous config broken/no export
Seems like something is now completely preventing you from taking an existing VT install and moving/copying it to another laptop or backing it up.
All custom views, gauges, log descriptors/profiles, VT options will break a new installation if using the import option or if manually copying config files over to new installation on Windows 10.
This is very, very bad and needs to be addressed ASAP (should have been addressed long ago!) - hours upon hours of customization, etc. with no way of importing it.
Version 1.5.57 (2018.01.04) with all updates ini files
VEMStune multigraph problem
When I put the background to black all the text with time and selection points can?t be seen anymore as that colour doesn?t seem to be changeable, can it be changeable so it could be made white for instance?
At the same time in the Multi Graph theme editor is it possible to get a button that updates the GUI so your changes can be tested quickly without having to go change to another theme and then back to what you want to test?
At the same time the settings for colors of the symbol should be theme dependent, as if you have white with black background and change it to white background you can?t see the channel anymore.
limit of 4 symbols per node, would be good to be able to increase this
Analog CAL channels can?t be viewed in multi graph viewer, this is pretty frustrating as sometimes data is best viewed via a graph, especially when trying to compare similar data like backpressure and manifold pressure or pre throttle pressure etc.
More problems with this version.
Fuel injector PW in the multigraph is not the same as the gauges are saying.
Please fix this basic problem.
Screenshot uploaded here - http://vems.hu/vemstune/bugreports/reports.php?cmd=view&key=wwKeOC
VEMStune channel problem
BOOST PID value are not correct, there is no way of tuning PID properly without knowing what each is doing so you can trace the culprit when things aren?t happening as they should. this has been mentioned years ago.
VEMSTune gauges don?t update with data from log and sometimes live.
This seems to happen sometimes, the gauges just stay dead even though the data is known to be there, opening vemstune again sometimes solves the problem.
To much data trying to be shown?
In multigraph "Third trigger position" is locked at -10000000.0 (on 1.2.45 firmware, maybe others too?)
Also echo the Boost PID values not being correct
Retest: with nightly release 2017-11-28 (or newer). Does any symptom of 2017-03-22 still hold ?
I have been using 2017-03-22 with firmware 1.2.38 without issue until I updated the ini files in the last week or so, cannot be sure when as I only noticed 21/12/2017 when trying to change Acceleration Enrichments.
NOTE: seem to be upgrade transient (fetched ini-s were for VT 2017-11-28 which was under dev for some time, moved to nightly later), should work with that
- Vemstune crashes when I open the Acceleration Enrichment table.
- MAT and CLT custom curve is broken "Variable 'mat_curveX' not found in the ini file!!!"
Vemstune Log
- Include not found: C:\Program Files (x86)\VemsTune-2017-03-22\config\include/page-config-ext-1.2.38.ini
- Include not found: C:\Program Files (x86)\VemsTune-2017-03-22\config\include/expression-grid-launchrpmlimit-1.2.32.ini
- Include not found: C:\Program Files (x86)\VemsTune-2017-03-22\config\include/calc-model-1.2.38.ini
- The selected symbol ( isLaunchCalc ) not found! The gauge is broken.
Observations
- File updater says there are 21 files available, clicking yes, files start to download until it reaches V3_ignition_settings.html. It looks like several attempts are made to download, but the file updater just closes. Starting the file updater again still suggests there are 21 files to download.
- I have changed the name of the install directory, downloded a fresh Vemstine install package, and re installed it. but it is still the same, missing ini files and Vemstune crash when opening some tables
- Released version of Vemstune 2016-06-06 works fine with ini files updated.
Pop up window works in Windows 7,8,10
Config Sanity Check
Config sanity check throws up unnecessary warning
- Advance change max advance should be less than or equal to 4 degrees. Please check iac_ign_advance_limit
- iac-ign_advance_limit and iac_ign_retard_limit both set to 5 degrees (+-5 degrees) as per OEM specification. No warning needed.
No real biggie, but a fix would help my sanity too.
- Resolved I have found the file I needed to edit to change from 4 to 5 degrees. I also changed iac_ign_retard_limit from 6 to 5, thus still keeping the 10 degree variance. Perfect in my setup.
Resolved in Nightly release 1.5.51 (2017.02.05)
VemsTune crash / curve editor change in IAC gauge group
- Trying to change the curve editor 'Idle Air Reference Position' in the IAC gauge group from RefDC? curve, to RefStep?. In edit mode, selecting 'Change curve to' brings up a selection that extends way beyond and off the right side of the screen with no way to scroll across. Blind attempts to find the column and row where the desired curve may reside, result in VemsTune crash.
Latest Nightly VemsTune 1.5.47 (2016.10.01)Up to date ini files.
Windows 10
VEMStune all latest versions
DONE (VT 2017-11-28): bubble popup workaround for Windows 7, 8, 8.1 and 10
These windows versions could not properly execute the programs that earlier XP / Win7 could.
Symptom was: "Bubble" Popup windows/ dialog boxes (bottom right corner) appear blank. (luckily the status at bottom left corner and flags at the top are displayed properly, so no information is lost).
Workaround implemented for windows versions with the misbehavior: VT 2017-11-28 and newer.
http://www.vemssupport.com/forum/index.php/topic,2361.0.html
DONE: VEMStune 2014-09-09 (nightly) (please confirm)
Cell-traverse order changes and some convenience Keys mapped (2015-09). Unless any new information comes up: Marked closed.
Curve editor has never worked right for me (tried others but mainly use Windows XP). The only way to change values other than dragging with mouse is using QWER which works for a couple of changes and then crashes hard (specifically tried map/tps acc enrichment table with fw 1.2.28). - Mattias
[ latest VT, currently 2014-11-27]
- Unfortunately we couldn't reproduce the crash (we tried slow and fast notebooks and PCs with no luck). However, with some refactoring there is hope that it might be fixed in latest.
- Any positive or negative report would be nice. Mattias, can you try ?
- or anyone else, especially who experienced the curveeditor crash before
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.
Very true; This issue has been traced and fixed. Together with curve editor upgrades: multi point select, edit and interpolate function all will be included in upcoming release.
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 [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.
- (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
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 [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:
- 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.
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: [VemsTune-2011-12-22]
- [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, [1] , "INVALID", "INVALID", "INVALID"
In to
sdcard_choice = bits, U08, 149, [2], "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.