Sambas has been working hard, and has produced a Vemstune installer.
http://kotisivu.dnainternet.net/sakrkorh/v3gui/vemstune.zip
I've installed it a few times, its worth far more testing than that.
Rob
Didn´t come up with a VEMS or Vemstune folder in All programs,
I´m using a laptop with MS Vista.
If VEMS Tune would have better live tuning capabilities, I'd use it all of the time. MegaTune would be fine, but there are some shortcomings that have been discussed repeatedly.
Bug is a "burn" button works as a "write". ;)
Where should we report bugs in the development of this?
I just downloaded the version put up today and it´s working for me at least alot better. I.e not crashing no matter what.
So I´d like to be able to report crashes and how they happened.
Firmware upload with temp sensor patch hangs the program, without sensor patches is okay.
What the difference at firmware/firmware upload vs. project/firmware upload (which put the ecu into boot loader mode beacuse of program errror)
Well I´ve been waiting for an update to the program for a while
and turns out there has been updates. only no updating done on the Wiki or here.
http://vems.hu/download/v3gui/
Maybe Sambas can take a look into this thread and we can report bugs so that overall usability is reached sooner.
Bugs.
Without any ecu connected or connected.
1. Can´t go into the "Firmware web tool" without it crashing.
This is what Event viewer registers.
"Faulting application vemsTune.exe, version 0.0.0.0, time stamp 0x49afd714, faulting module vemsTune.exe, version 0.0.0.0, time stamp 0x49afd714, exception code 0xc0000005, fault offset 0x0037571c, process id 0x168c, application start time 0x01c9a0f30214bdba."
2. Can´t open "project settings" without it hanging.
This is what Event viewer registers.
"The program vemsTune.exe version 0.0.0.0 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Problem Reports and Solutions control panel. Process ID: 1190 Start Time: 01c9a0f2b888b09d Termination Time: 14"
Other then that I haven´t stumpled upon anything yet.
Also in the 3d mapping how you adjust the view isn´t remembered so if you like one view you´ll have to adjust to it everytime you open the window.
Also the shortcut keys only work if you have the vemstune program selected if you have a tuning graph up.
So you can´t use the keyboard alone to switch between ignition and VE tuning for instance.
Renaming of some of the gauges would be in order such as the analog inputs to be more descriptive.
Otherwise I like the various gauges possible as that allows you to set up a pretty good tuning view
VemsTune as is MegaTune does not support dual config switcing without restarting the program.
This should be pretty obvious that it should.
Bug:
VEMSTUNE 2009.03.12 is not show egt and duty cycle on gauges, with fw 1.1.27 12x12.
Interesting, what was a reason to change almost all keyboard keys comparing to MT?
Even if VEMS tune have any advantage (is it?), it is hard to migrate.
Don't try VemsTune until you hear about it being sorted out. There is heaps of useability problems with it, but looks promising in some areas - at least compared to MegaTune.
Problem if we will not trying this software during development it will be in total isolation from real users, I suppose.
I use old good MT every day. So what can be a reason to mesh up all shortcut/tuning keys?!
In addition MT was not the only ecu using switchable arrows for migrating/changing values in tables.
I don't know, I don't know... current versions seems strange for me. Lot of work is in. But is it more handy? e. g. working with tables. MT has less features, but it is more usable to select desired area of map and do whatewer wanted.
Shortcauts from my everyday:
Alt-L for logging
Alt-F-A for saving all calibration
Alt-F-I for importing tables
Alt-F-E for exporting tables
Alt-B Burn
Alt-F fetch from ecu.
M, N rotating 3D tables
shift-arrows for fine,
shift-ctrl-arrows for coarse tuning....
Gints
I use shortcuts (Alt-B, Shift-Ctrl-Arrows etc) all the time. Absolutely no point in changing that...
A set of UI requirements needs to be specificed by a professional tuner.
Or ask a tuner about the best bits and worst bits of OMEX, Emererald, MOTEC, AEM Tuning Software.
Take these use cases and make them a reality.
Pot tuning would be a plus I heard from one tuner who tunes many MBE ignition systems for CARB engines and OMEX for EFI.
Im sure theres a usb volume/gain controller out there with two buttons that could be used for pot-tuning with VEMS!
The analogy here is that on a laptop while keyboard and touchpad is useable, a mouse works best.
Similarly for tuning ECUs, mouse, keyboard and hotkeys are good, but a pot-box would be best!
It would also require duel view of fuel and spark side by side, or, top/bottom.
Turn knob one up or down alters VE within maximum bounds, hitting the button WRITES to memory.
If you move cursor out of the box after altering but without setting it via the button,
the value remains unchanged in memory and resets on screen when moving away.
The second knob and button act in the same way but for spark table.
This is an example of the beginnig of the development from the top level that needs to be taken care of.
Software crashes and ECU crashes need to be fixed, they should never happen!
Need to control firmware releases better and test fully with a set revision of UI.
Once this is at excellent quality level, release as stable.
Then work on next agreed set of firmware features and related testing.
Try to make it backward compatible, or allow for future proofing when designing.
Once the UI is useable and intuitive and tested safely, yuo can think abotu features.
Idle control algorithms like PowerFC etc.
The requirements have been written - about 3 years ago...
Nothing has happened.
Just downloaded the latest version and
now the "firmware web tool"
doesn´t crash the program.
The overall view needs fixing though.
#1.
This should be a full screen program, nobody needs to see their desktop while tuning.
The progam itself get´s hidden behind tuning gauges or tables, which is also rather bad.
And the white part of the main program window should house the gauges and tables and not a "log" of events
occuring.
#2.
Naming conventions need to be fixed and
I do not have a injector 0-5 on a 6cyl engine, but I do have from 1-6.
This hex and 1 0 stuff just has to go from the entire user interface. I don´t care if it´s there in the background but it should not be in the user interface.
#3.
When firmware is updated so that a setting basically get´s outdated it should be dropped from the firmware and user interface.
Such as the Cold Crank PW and Crank Warm PW, since there is a 2d table that handles this now this should be automatically dropped.
#4.
Same with the accelaration enrichment , in that window the bins should be dropped in favour of the 2d maps, while keeping the
"Settings" part or combine that with another window.
#5.
Config switch should be able to be done with the software running, turning it off and on again to work on the second config is just
ridiculous. basically the software would be checking the status of the switch often, so when it flips, it knows to read the complete config from the unit. A minor delay would be alright. If you have a table open it would just update in the process.
#6.
Single column multi row windows. They are useless.
Why not have a window with many columns of settings ??
This could tie all the outputs together into a single window allowing for a quick setting up.
here is a random picture I found on the internet that shows this.
(http://i.i.com.com/cnwk.1d/i/tim/20081224/49221fb50a0f8beb678493477e3d41cc_registryff_screenshot_540x392.jpg)
Tuning user interface is about being productive and efficient. At the moment
you could have the best firmware in the world but it would be useless without an updated and properly working software.
I personally could live without firmware updates for a good while if the software get´s sorted.
Custom variable gauges would be excellent.
Such as showing the difference between target lambda and actual lambda. Showing you if your tuning efforts are off
and by how much. I´ve created this in the Megalogviewer and use that with another custom variable that calculates the new VE
for me based on any Gego correction as well. Making initial tuning a breeze. Coupled with 3d tuning and a 20-250kpa table is done rather quickly. History graph gauge with more then one input would also be EXCELLENT.