Add issues/bugs to most recent release at the top
Do not forget to mention :
- VemsTune version (or release date if possible)
- V3 firmware version.
- Zip and publish your saved config (vemscfg) and Tools/firmware/config download when appropriate.
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 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. Please fix so that it works within limitations of the firmware (up to 16). If you have defined 8+ cylinders in the Engine Setup dialog, simply skipping through this dialog will reset the cylinder numbers! This should not happen, the dialog should not write/change any setting unless asked to do so.
- We fixed this problem. It will be in the next nightly release that we wolud like to publish next week.
VemsTune 2013-01-09 reluctant to connect to 1.1.x firmware with some (rare) serial-connection-chains. Assumedly also older nightly from 2012-Q4 are effected
- although tested and works fine for 1.2.x firmware,
- but sometimes connects reluctantly to 1.1.9x (or older firmware)
- seems to be an issue with certain (rare) USB-serial adapter/windows driver / windows combinations: VemsTune turned out to be somewhat impatient for the worst (slowest, or slow when switching baudrate) combinations of windows/USB-serial adapter/windows driver that we only met recently. Sometimes just does not connect, connects slowly, or the "boot loader mode detected" message is displayed (confusingly)
- New ["dev" vemstune] was actually improved to be more patient during initial connection.
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.