Wishlist
This page should generally contain only wishes and observations about functionality, not bug reports. Use IssueReports/VemsTune for bug reports.
VemsTune general
- 3D table editing
- Too limited rotation up/down (J+K keys)
- Add coloured polygons to get a 3D surface look, custom and default yellow-green-red palette. It is useful while tuning to more quickly grasp the shape and values of the table. Example : The 3D tables in TunerStudio for MegaSquirt looks pretty good and is a step-up in usability from the wire grid in VemsTune.
- VE tune by statistics needs more documentation, re-worked and integrated better into the software
- Boost control needs documentation and a stable feature set (clearly defined) with examples
- Store folder locations in memory, remember which folder the user last saved/opened file to/from.
- In ECU Communications settings
- User marker while datalogging should use 'space' key, not key combination, and give visual feedback (blink on/off in part of status line).
Bugs / Strange Things
VemsTune General:
- When opening a Config (offline), the Log Viewer appears (Why?)
- When Gauges are displayed, and opening a Log, the log viewer is *NOT displayed (Why not?)
Log viewer
See separate topic on support forums : [link]
Comparison with MegaLogViewer
Much of this is in comparison with MegaLogViewer which a lot of tuners prefer to the built-in log viewer. The developers should strive to make the built-in log viewer the first choice.
- In MLV values at cursor crossing is at cursor not dispersed over all screen. Your know where to look intuitively. Like this: [example]
- In MLV zooming (up/down arrows) works efficiently. Together with mouse and pageup/down (shift full screen on right or left) it makes migration even through long log very easy.
![[example]](http://www.vems.hu/files/GintsK/MLV_screen03.png){kind=link}
- In MLV minimal/maximal values is visible on side of screen.
- More sane would be next to the symbol title.
- MLV has immediate average calculations in selected area of screen. Sometimes very usable!
- MLV has auto-adjusting min/max values for graph lines by default.
- "Cursor stay in center" mode (I propose toggle using the "C" Key)
- Improve speed - VemsTune viewer navigation is inconsistent and often slower than MLV with the same PC
Postponed ideas /Emil:
- 0-720deg event diagram based on ignition, injection settings, this would help with setting up visually the outputs to their corresponding pins.
- Good idea, time consuming though
- remove backwards running injection, trigger tooth and ignition order in output tables.
- going from top to bottom would cause a big confusion and render lots of text invalid (some uneditable like in forum posts). We do not want to confuse our installers simply by changing that
- short-run: add arrow to show direction (already implemented).
- Going in a circle (it should be clockwise, I guess): this would not cause confusion. Arrow is still good.
- Even more useful: marking which cylinder it relates to!
- Video problems make lines hard to see
![[1]](http://www.vems.hu/files/GintsK/VT_logscreen01.png){kind=link}
![[2]](http://www.vems.hu/files/GintsK/MLV_screen.png){kind=link}
![[3]](http://www.vems.hu/files/GintsK/MLV_screen02.png){kind=link}
![[4]](http://www.vems.hu/files/GintsK/VT_logscreen02.png){kind=link}
![[5]](http://www.vems.hu/files/GintsK/VT_logscreen03.png){kind=link}
- Move channel values to right side of screen (out of the way) like in MLV.
- Apply math formulas to channels (Example: Convert voltage in MLV to Bar, PSI, MPH, Degrees F, etc., calculate power from torque input and rpm)
- For a long while I have had MLV display new VE values for fuel tables based on lambda target, lambda, ego closed loop correction and air temp correction. This along with a math channel that displays Lambda error I can very quickly identify how far off the VE value is so this seeing problems with VE is just instant, and then apply the new VE value to the fuel table.
- When we have calculated channels easily available, you can do any calculations.
- Definately a good idea, will be postponed until more stability is reached
- "Compare to" mode (overlay a log over another) - also have a quick on/off key for this (I propose "Insert" key to add/remove 2nd log) and also have a way to move 2nd graph forward and back easily. It is MLV feature for ages.
- Good idea, a bit complex for now, but will be kept until time can be allocated
- Colours for flags/indicators can be adapted to colour-blind people, 7% of tuners have some kind of colour blindness!
- Fixed through templates
- Better to have contrast or other shape to display active vs inactive state
- "Time Re-set Mode" - allow time line to be set at "0.0 sec" on cursor (I propose using the "T" Key) (To start time at "0.000 sec on Drag Launch)
- I usually mark in the log, and time is automatically measured for the actual marked area.
- Easy (I mean fast) finding of maximal or minimal values.
- Like a find max value, when right clicking a channel? Will be thought about, but postponed for now.
- look on MLV behaviour. Easy and fast.
Dropped ideas /Emil:
- Virtual ecu , doing offline simulation using a config or log for ecu setup, i.e being able to see a running ecu without having a test bench, helps with setting up configs and settings and allows firmware function testing without having to flash a test bench ecu with the firmware.
Examples :
- Testing config switching, antilag behaviour, boost control behaviour, EGO control speed, anytrim functions.
- Focus is on getting Vems software working good, 'not having megasquirt compatibility
- Must equal MegaLogViewer in how well it can find a good tune.
- Export datalogs and export/import MSQ for use with MegaLogViewer should be maintained, currently
- Super time saving if csv converter store destination folder in memory! Same with msq export.
- MT alike key combinations are asked for, template file can be provided by GintsK. Here is my file for 3D editing. For those who historicaly used MT it could be way more handy. And it seems more handy anyway than current dafault Q W E R keys. everything is under same keys, same fingers: migrating over graph, editing, fast editing, selection, graph moving. Instuctions inside: http://www.vems.hu/files/GintsK/3DTableEditor_GintsK3D.zip
- As i answered before, keys collide with megasquirt, because we use shift for marking in graphs.
- please find word "marking" in this wiki page.
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.