_____
 |__  /
   / / 
  / /_ 
 /____|
       

 _       
( \      
| (      
| |      
| |      
| |      
| (____/\
(_______/
         

   ___  
  / _ \ 
 | | | |
 | |_| |
  \___/ 
        

  ______
 |___  /
    / / 
   / /  
  / /__ 
 /_____|
        
        

         
|\     /|
| )   ( |
| |   | |
| |   | |
| |   | |
| (___) |
(_______)
         

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:
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. *If we type in the firing order could the value of injector and ignition table be automatic generated if using standard inj A = cyl 1. inj B = cyl 2 same with ign. nice job -Peter * An installer says: "When a customer has problems I like to be able to send finished mtt files to him..." ** Finished files make a lot of sense. There is the concept of "projects": with a project file, the RIGHT firmware and/or config can be uploaded with 1..2 clicks. This has been used for years, eg. VemsTune/QuickStartAudi. Note that the vemstune over the network will be very useful in many cases, but dealers still need a way to prepare project / vemscfg files (in a documented way!) that can be uploaded extremely quickly (without using menu-s) by a computer-illiterate child supported over the phone. * '''Remote tune''' over TCP connection feature is in integration/testing phase, planned to work only in newest firmware only with SIPR protocol. ---- '''Firmware Version''' *Can not find the new function (wheelspeed, wheelspeed-based launch and the new knock-threshold-map) in 1.1.61 non ps2 in VemsTune when i make a new empty project. ** I found a new row in the defaultfirmwareconfig directory in the new 0.10.0 VemsTune called '''CompileOptions: 0000001B''', and loaded into VemsTune, the program showed the Mics Output new settings. I played it with a bit, but not got any logics. With ff it shows the alternate knock settings to. How this varible work??? How do I get 1.0.79 to work with the current version VemsTune? ----- 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...) * 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 * 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. ---- '''Wishlist''' This is a list of feedback made by Mattias taken from the www.vemssupport.com forums and through private PM and e-mails. Emil spends a week in Budapest in the middle of December and can use this list compare with current development. '''VemsTune general''' * 2D table graphic editing ** warmup curve, IAC ref curve, etc.. * 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 to be re-worked and integrated better into the software ** http://www.vemssupport.com/forum/index.php/topic,1186.0.html * 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. * Make sure hotkeys, gauge groups and settings can be migrated between VemsTune version, during upgrade, etc. * In ECU Communications settings. Auto-detecting the ECU needs to show better feedback, preferrably which COM port is tested. The existing progress indicator never moves. * User marker in datalog should use 'space' key, not key combination, and give visual feedback (blink on/off in part of status line). * MAT/CLT sensor curve dialogs lack 2D table graph * After firmware upload, VemsTune suggests a config file to upload, if possible make as much of the filename as possible visible in the filename dialog. Make the textbox wider ---- '''Log viewer''' Mattias created this topic on the support forums : http://www.vemssupport.com/forum/index.php/topic,1516.0.html 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: http://www.vems.hu/files/GintsK/VT_logscreen03.png * 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. From lugnuts : Log Viewer Wish List: * "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) * Make easy way to Import/Export all of the Log Viewer Settings (so we can import to new VEMSTune every 2 weeks Smiley 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?) '''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 lotsof text invalid (some uneditable like in forum posts). We do not want to confuse our installers by simple changing that ** short-run: add '''arrow to show direction''' (a few months later the top to bottom might be reconsidered). ** 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! ''' * Right mouse clicking over graph should do somewhat exact graph related, but not open general menus! E.g. open searching menu over datalog. ** Currently this is handled by marking and right clicking on the "symbol title", changing to a new channel. Maybe quick search can be added to same menu? * VT has some video problem what makes it unreadable. ** Maybe you are thinking about anti-aliasing of the graphs? This might be possible to disable, We'll check into that later ** Here is 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 VT with 2points 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.) ** 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 Answers: * 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 * While in a window the < and > arrows work great, but having it on the keyboard would also be nice, like CTRL-< and CTRL-> , makes reviewing settings easier as the arrows move around with the windows ** Page up and down does this? * Easy/Quick way to change number of graphs (and change back) (example: from 4 to 3 graphs, or sometimes I like one big graph only) ** Already exists, You have to make several descriptors with different number of graphs * "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 * Make "log viewer" easy to access and visible on the main screen (Create a box to click next to "Main" box, Shift-8 is hard to remember) Also see "Bugs" section below. ** Reworking of the quick access buttons are on its way, ETA next week * Cannot see "Time" (top right) when Background is set to Black ** You have to change color of the text, "Text color", in the theme, as that is set to black. Same goes for a blue line if you select blue background... ** in fact black background by default would be good idea. * Create custom channel names (Example: Change "Analog1" to "Oil Pressure") ** In log viewer descriptor editor, there is a Custom Symbol Title, change that and the title in graph will be changed.. * Easy (I mean fast) selection of desired graph. I mean fast changing from e.g. BoostDC to e.g. Dwell (already easy? No. MLV requires one click, VT - at least five+some droput menus!) ** right click is not too hard for me, the dropout is only to sort in the vast amount of channels available ** five clicks vs one??? It is irritating! * Representation of cursor point in tables beside of log screen. ** This is the exact behaviour today, if you aren't connected to ECU and have the gauge refresh enabled. * 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. * 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. * Analog channels can only display to "2550" arbitrary value? (Why not "5.00 Volts"?) ** Depends on the number format settings and custom symbol title '''Dropped''' /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. Sliders for RPM, MAP, Air temp, Lambda.... , ON/OFF for such inputs. 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.
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.