Versatile Engine Management Systems - VEMS wiki

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.

• I have the same problem(0.9.85)

• Could it be possible to add a background to the gauges?
  • Currently not. Need some implement.
• I think of a simple object like jpg/bmp image? (example Kevlar background)

• 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, these can then be sent with command line tools or if he has communication problems I help him with bray over the phone"

Finished files make a lot of sense. It was planned that one would send project file, where the RIGHT firmware and/or config can be uploaded with 1..2 clicks (not lost in menu-s).

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
  • WU 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 useability 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
  • 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.

• 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.

• 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

• Make sure hotkeys, gauge groups and settings can be migrated between VemsTune version, during upgrade, etc.
  • MT alike key combinations are asked for, template file can be provided by GintsK.

• 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).

• Easy way to brake VT completely is remove dot from %.1f in gauge descriptors and hit save.

• 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. The problem is visible here in the Youtube video at 1:08 : http://www.youtube.com/watch?v=oeEjaGW_r3Q

• 0-720deg event diagram based on ignition, injection settings, this would help with setting up visually the outputs to their corresponding pins.

• remove backwards running injection, trigger tooth and ignition order in output tables. No real reason to continue with this. Makes no logical sense to start from end of table (especially to new users and tuners).

• 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

• 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.

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.

Points from GintsK, needs further explanation from him:

• MLV has very easy migrating trough log. With mouse you can get centred exactly that pixel you click on. And it works with no delay. (keep graph centred should be selected - it means cursor is in the middle of screen always except half screens of the start end end of log. Mouse clicking on desired point do not move cursor, but graph under cursor.)

• Values at cursor crossing is at cursor not disperced over all screen. Your know where to look intuitively. (?)

• 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.

• MLV is super fast in migration. VT has some lag. And it do not allow to scroll smoothly. VT each time redraw when mouse button is released. I mean using scrollbar. (migration = means movement, drawing of graph)

• Easy (I mean fast) finding of maximal or minimal values.

• Minimal/maximal values is visible on side of screen.

• 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!)

• Immediate average calculations in selected area of screen.

• Each graph is automatically maximized in vertical direction: lowest and highest values are on bottom and top. Can be configured. If during logging min rpm was 900 and maximal 1700, then it will be top and bottom of graph. If it is not reconfigured for exact min/max.

• Possibility of calculated graphs. e.g.it is possible to divide gpsspeed/rpm. Or scale TPS from % to raw. Or calculate AFR from lambda. And so on.

• Representation of cursor point in tables beside of log screen.

• VT has some video problem what makes it unreadable.
  • Here is two screenshots of same datalog:
    • [1]
    • [2]
  • here is 10 time magnified fragments from screenshots above:
    • [3]
    • [4]
  • and VT with 2points wide line:
    • [5]

• Right mouse clicking over graph should do somewhat exact graph related, but not open general menus! E.g. open searching menu over datalog.

From Gunni (gstuning) :

• 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.

From lugnuts :

Log Viewer Wish List:

• 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.
• Create custom channel names (Example: Change "Analog1" to "Oil Pressure")
• Apply math formulas to channels (Example: Convert voltage in MLV to Bar, PSI, MPH, Degrees F, etc.)
• "Cursor stay in center" mode (I propose toggle using the "C" Key)
• "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.
• Improve speed (VemsTune viewer navigation is inconsistent and often slower than MLV 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/Quick way to change number of graphs (and change back) (example: from 4 to 3 graphs, or sometimes I like one big graph only)
• Make easy way to Import/Export all of the Log Viewer Settings (so we can import to new VEMSTune every 2 weeks Smiley
• Move channel values to right side of screen (out of the way) like in MLV.

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?)
• Analog channels can only display to "2550" arbitrary value? (Why not "5.00 Volts"?)

Log Viewer:

• Cannot see "Time" (top right) when Background is set to Black

Document last modified 2010-12-08 17:36:53

Search: