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.
Issues
- Use "Page Up/Page Down" keys to move from one sub-menu item to another. Example: VE Table - Page Down to IGN Table - Page Down to Lambda Table.
- "Review Mode" like in Megatune, makes it easy to check/adjust all of the settings efficiently.
Enhanced ergonomics:
- When not in single gauge-group mode and gauge group layout behaviour is "attach within mainframe" I suggest that you can save a number of tabs as "home pages" when you open up the progam and open a project or connect to a ecu. And that you can switch between tabs with ALT-TAB(forward) and ALT-TAB-SHIFT(backwards) , this will allow users to jump quickly between various tabs to tune and various gauge-groups they like to have open. They can then change each group to suit them and their tuning needs. This should make switching between tuning various tables quick and you don´t need to close each one to open up another one. Very similar to how Internet Explorer and Firefox operate now. - Gunni
- a combined function of 'convert to csv' + 'view last log' would be fine (or other method to directly write log for megalogviewer)
- A SAVE Project button so that offline project adjustments can be made for customers and then emailed to them.
- The follow function is not implemented into the 3D table view yet! The cursor should stay in the latest position when the follow(for example SPACE) button is pressed-FERO
Can you give a more detailed info of the scenario
- Tool for Generate Trigger (does this work? Could use for testing outputs)
I would still like to maintain functionality with MegaLogViewer MSQ importing for auto VE calculation.
- Is it possible to change the export of any single dimensional array to 'rows' instead of 'cols'?
- data would need to be terminated with a 'line return', and not just a 'space'
- 'warmup_clt_bins' has an improper unit, needs to be "C"
- ultimately need a way to import veTable from MSQ. Can this be added to work like the table import for .vemscfg?
- 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
- I tried to configure 3D editing keys same as MT was. It work until two-three last releases (now 0.10.0 (2009.10.02)). Now Ctrl+Shift+up/down changes 3D window height instead increase/decrease in big steps. -GintsK
Upload stuff without using any menu-s
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.
- At the moment there is no way of just loading a project and start editing the "empty" config and then saving it to a file. It should at least have a Save as.. function so you can actually select to wich file to save the config. I´m talking about setting up a .vemscfg just like you can a .msq from scratch without connecting to a ecu at all. I don´t have a vemscfg cause I can´t save one from scratch and I don´t have a ecu to "download" one. - Gunni -
Gauges
- How can I add new gauges (especially knock_cyl_0_knock_val) to VemsTune and how Can I log it? I have tried to put vemsv3.ini, vemstune-v3-1.1.27.ini, GaugeSymbols?.xml but no success.
- __Can I log it?__ I think you mean how can I convert it to csv (*.vemslog contains all raw data).
- To convert it to CSV you have to edit manually the appropriate *.ini (for example: vemstune-v3-1.1.27.ini) and go to __[Datalog]__ section and add new __entry__ to it.
Firmware Version
- I am currently running firmware 1.0.79, but VemsTune does not seem to suport it?!?! I am also led to believe VemsTune also suports 1.0.78. FirmwareChanges also states to use VemsTune with 1.0.78. None of these firmware releases are available in the web download tool. there is 1.0.75, 1.0.76 and 1.0.80 releases, but I cannot find ANY infomation regarding these on this Wiki!?!?!?! I refuse to use any of the 1.1.XX firmware versions as i suffered a loss of 14 degrees of 'trigger tooth before TDC' and serious kickback when cranking the engine to the point it was killing the battery.
- 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?
11/11/09
Vemstune 21/10/09 produces a kpa vs kpa table on the boost vs rpm curve.i use firmware version 1.1.62
Somehow one or two users have managed to fix that by installing and reinstalling vemstune on their computer. I must say i havent managed to get that fixed.
vemstune version 2/10/09 works normaly, but as soon as you put 21/10/09 it goes back to kpa vs kpa.
vasilis