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