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.
Add issues/bugs to most recent release at the top
VT version commodel testing 2010-12-02
- In Alpha-n mode, there is throuble with the rounding of load bins; with load bins setup to 1, 2, 3 after burn command we end up with load bins of 1, 1, 3. It seems to be something rounding related. Please look into this - DB
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 2010-11-15 (nightly)
- 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...)
- 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.
- 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
- works when clicking the arrow keys
- 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..
- 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. More recent hardware has less chance, problem is many use old laptops for tuning.
- Test case IBM R32 laptop, 1.5 GHz Intel Pentium M with Radeon Mobility chipset, with proper driver from 2005 for Windows XP (WHQL), consumes 75% cpu with main VE tune view (Ctrl+1). Only 8% if major eye candy gauges are removed (differ, graph, 3d table). It properly handles accelerated full screen 3D graphics video.
- Other test case IBM X61, Intel Core 2 Duo 1.6 GHz with Intel 950 chipset has nearly 0% CPU use in main VE tune view.
All behaviors have been noted while disconnected from ECU. Laptop used is an Asus Eee netbook with Windows XP. VT version 0.20.10 (2010.12.22). Firmware version 1.1.74.
In the future, please always use the latest version of VemsTune before reporting any bug, because maybe already fixed.
- 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 by integer value.
- Cannot move gauges in groups in gauge edit mode.
- Fixed in the latest release
- No text field is focused when selecting "Set Size and Positions" in gauge edit mode.
- Fix in the next release.
- No scroll bar presented when gauges are partially outside of window view.
- Fix in the next release.
- If all gauges are removed in gauge edit mode, then a gauge file is imported, gauges are added twice and in different positions.
- Vertical size of dialog boxes for settings should default to available vertical screen space when opened.
- Fixed in the latest release
- Injection and ignition outputs still must be entered from bottom to top. If developers are worried about confusing people with new default behavior, an option should be given to user in VT software.
- No help available for Priming, Cranking, Afterstart menu.
- Add option to lock settings windows button row buttons (Refresh Send Burn Import < > Close) for every window. Moving the mouse cursor is more time consuming on a laptop; if the cursor can be left in one position while user tabs through text boxes for settings then can click ">" without moving mouse, it should make for easier menu navigation.
- < and > buttons should be disabled when at the first and last menu, respectively. Current behavior is not bad but user may wait for next menu when it does not exist.
- In "Environment Config", setting graphics_quality_factor has no description. This menu's help is not available.
- TPS Calibration does not seem to function. Instructions on page are not interesting; when "Start Cal." is clicked, user should be walked through dialog boxes instructing them what to do. Example: User presses "Start Cal.". Dialog box pops up, says "Remove foot from throttle and press next". VT grabs 0% throttle ADC when user presses "next" button. Next dialog is displayed "Hold throttle to floor and press next". VT grabs 100% throttle ADC when user presses "next" button. VT fills text boxes with ADC values gathered from wizard.
- In "HotKey manage for 3D table editor" menu, button at bottom of window is not visible when Windows task bar is taller than default height and at taks bar position is set to the bottom of the screen.
- Fix in the next release.
- Add option to set theme style on all gauges or a selection of several gauges at once.
- No explanation of Projects. What is the point of a Project in VT?
- Add ability to save notes to configs, ie as an English description of changes since last config.
- Varying behavior for disabling settings in various dialog boxes. Some text/dropdown boxes are not disabled, etc.
- Tachometer lock does not appear to function. Observed while connected to ECU.