_ (_) | | | | | | (_)
## # ## ## # # ## ## # ### ## ## ## # #
##### ## ## ## ## ##### ## ##
_______ (_____ ) /'/' /'/' /'/'___ (_______)
______ |___ / / / / / ./ /___ \_____/
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: ---- '''Wishlist''' This page should generally contain only wishes and observations about functionality, not bug reports. Use IssueReports/VemsTune for bug reports. ---- '''General wishes''' * TPS Calibration wizard, a few easy steps to calibrate the throttle position sensor. ** The wizard figures out the sensor polarity and enters the numbers for the user. * Store folder locations in memory, remember which folder the user last saved/opened file to/from. * User marker while datalogging should give visual feedback (blink on/off in part of status line). * 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 ** http://www.vemssupport.com/forum/index.php/topic,1186.0.html * Boost control ** needs documentation ** clearly defined features with examples * Triggerlog ** 0-720 degree event diagram based on ignition and injection settings ** helps set up ignition order and timed injection * 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. * Add option to set theme style on all gauges or a selection of several gauges at once. * 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. ---- '''Log viewer''' * Improve speed - VemsTune viewer navigation is inconsistent and often slower than megalogviewer with the same PC * "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) * 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. '''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. Separate topic on support forums : [http://www.vemssupport.com/forum/index.php/topic,1516.0.html link] * In MLV values at cursor crossing is at cursor not dispersed over all screen. Your know where to look intuitively. Like this: [http://www.vems.hu/files/GintsK/MLV_screen03.png 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. * 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) ---- '''Postponed ideas''' * "Compare to" mode through overlay of a log over another ** quick on/off key for the overlay ("Insert" key to add/remove 2nd log) ** easily shift the 2nd log in time to align to events occuring in both logs * 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 ** Is that improper anti-aliasing? ** Here are two screenshots of same datalog: *** [http://www.vems.hu/files/GintsK/VT_logscreen01.png] *** [http://www.vems.hu/files/GintsK/MLV_screen.png] ** here is 10 time magnified fragments from screenshots above: *** [http://www.vems.hu/files/GintsK/MLV_screen02.png] *** [http://www.vems.hu/files/GintsK/VT_logscreen02.png] ** and VemsTune with 2 points wide line: *** [http://www.vems.hu/files/GintsK/VT_logscreen03.png] * 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. 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.