VemsTune and 1.1.6x release

[gunni]

Step 1 - Open log file
Step 2 - nothing but a the initial screen. I can only hit Pause and Stop, so it looks like it´s trying to play but nothing happens.
Step 3 - move the time slider around and when it stops it shows the gauges at that time

[rob@vems.co.uk]

Response:
--8<-----------------------------------------------------------------------
Now the log playing functionality is removed from VT (we can add it again if it
is needed)

We can implement the following:
Separate the show on startup functionality to online and offline mode.

Add a new option in gauge group properties:
Show on startup offline
Show on startup online

So the default setting should look like:
online mode: the "Main" group should open automatically
offline mode: the Multi Graph should open automatically

but the user can change it.

[gunni]

Nevermind,

I just realized that the csv file works with Megalogviewer.
And I´ll continue to use that until VT has a better internal logger reviewer.

Besides gauge watching while looking for anomalies is not really good, graph trends make alot more sense

[rob@vems.co.uk]

I don't see why it needs to be in the tuning app anyway.

[gunni]

I agree in a sense, but it will be good when vems has it´s own specialized logger review program that will look and feel similar to what
vemstune does.

[lugnuts]

I don't see why it needs to be in the tuning app anyway.

It is very convenient to have the logger in the tuning program - if done correctly.

Autronic is the best example of this. You can have the tuning window and the log each sharing half of the screen.



One key "Z"turns VE or log into Full Screen
One key "Tab" changes between log and tuning,
One key (page up or page down)changes from one tuning window to next,
Box highlights VE/Spark/Lambda table cell for RPM/MAP that is in the Log cursor (*not seen in this pic)

- VEMS developers - if you are reading this - please please please do not disable MLV compatibility!
- In developing a log program to integrate into VemsTune please use Autronic as example of lightning quick useability and versatility.
- There are a hundred reasons why Autronic is the best (I love the MLV) for quick and easy custom scaling and display of log data - I could demonstrate during an on-line (teamviewer) session perhaps?

 
- Who here actually reads gauges for data viewing?? I can't think of a worse way to do it.

[emil@vems.se]

so you want something like this as a default view?

This log was downloaded from a ECU with builtin logging memory
hotkeys can be customized to have mostly the same assignments as autronic

Some features will probably be missing for some more time:
Currently you have to save a config and re-upload after working with a offline log, will be fixed maybe in next vemstune testing release
You can't zoom in on the table and scroll inside the table editor, it automatically fits the screen size
ECU log files doesnt wrap back to 0 or stop in a couple of minutes, they keep on recording for approx 400 hours, only makes a new file for each engine startup

Some things is already much better compared to autronic:
All fields are always available on ECU logs, even injector duty cycle.
You can choose if you want 2D or 3D view in any place
2D and 3D has same orientation (up is always up in the table, unless you want to flip the 3d upside down)

note: This is just an example of a screen view, you can choose any ratio between the log viewer window and the table editor, if you just want all graphs in one section or split up as in my example

[gunni]

Keep it up Emil, very nice.

[lugnuts]

I like the way you think Emil

I like the MLV and your way of multiple (2,3,4) rows of graphs. Keeping it optional will make everybody happy.

One thing we can do to improve on yours AND Autronic is to copy the way MLV does the "Hiding Field Select"
- This allows you the option of hiding the log display channels, but being able to easily access them if using the mouse.
(Autronic use of keyboard was quickest for me)

Another feature I would really like is the ability to have the time reference be "zeroed out" by the log viewer - this will allow easy time/track position referencing when you are at zero seconds at the starting line launch - for example.

Another thing I really like about MLV is the ability to user-configure the log channel min and max, and especially to create their own channel names. Example: I can turn "Misc 1" (0-5v) into "Oil PSI"
If you make this user configured - you would have less people asking you to incorporate new channel names later on.

I'd like to play with these prototypes if you feel like making them available.

Thanks for the great work.

 

[emil@vems.se]

this is all available already, http://vems.hu/download/v3gui/VemsTune-Install-2010-03-08-testing.exe
log viewer is in shift-8 view

actually time is not reset, but you can easily just mark a section in your log and see the time of that, i think thtas good enough

just need to hit alt-e with focus on the log viewer, or right click, to have a menu where you can add and remove data, and also rename if you want to

[gunni]

Logger review

#1.
it says rgba(x,x,x,x) but when I select a color it comes up as rgb(x,x,x) and the color does not get applied.
I´ve added the "a" and (x,x,x,200) just to make it work after have selected a color.

#2.
View ratio of the gauges seem to be strange, coolant line will be almost unvisible unless magnified 60times. I think
megalogviewers min-max setting would work alot better, where the program automatically ratios the gauge to show max at the top of the line chart and min at the bottom, or add the ratio option to the MultiGraph Desc editor.

#3. Gauge selection process is rather slow, again comparing to mlv where I can simply click on the lines name in the graph menu on the left and select a new gauge, all about 2-3seconds to switch gauges.

Overall it looks good and can improve, I think that each gauges configuration should be setup specifically for each gauge, but the gauge selection process should be alot simpler, i.e selecting a gauge with Q and W , then press a button and a list with all the available gauges comes up and you can select one from there. Putting in a new gauge in a specific trend graph could be that you need to have selected a gauge in that graph and then hit Alt+N and then select a new gauge from a list.

I think the people who have used MLV alot have gotten accustomed to the extreme ease of usage it provides.
I find myself creating custom gauges to aid in tuning and I use the min/max limits alot to display for instance the
lambda and lambdatarget trends in the same graph, this way it´s easy to just see how good the tuning is by how close the lines are.
I also made a re calculated Gve line(from all the gamma trends and lambda/lambdatarget ratio) where I can monitor automatically re-calculated Gve values, so I only need to look at the new value and put that in the MAP, no hand calculating.

[gunni]

Question.

I had setup quite a few turbo charged cars with a 0-5v boost controller adjustment. Now it seems
this really nice feature has been disabled without chance of enabling it.

Is there a way to bring back the 0-5v boost control option?
Mostly used with secondary pwm settings.

[gunni]

Updated somebody to 1.1.70 today.

Two things to look out for.

Anytrim is set to fuel trim and Ch0, the curve is then set to 0.78 everywhere. Disable if you don´t need it.

Also MAP sensor placement is - before throttle body, while the norm is behind.

[Sprocket]

If by setting the Injector Firing Divider to '1', Alternate Banks to '3..0', then Cranking Fire Banks While Cranking to 'All Banks' and then Cyl for Sequential, #Cyl/2 forSsemiSeq Cranking Fuel Divider to '1', will not add four times as much fuel at cranking???...

Like I said, the pulsewidth that is calculated from all the enrichments is divided over the 4-stroke cycle so the total pulsewidth is the same. To add fuel you need to alter the enrichement tables. The only thing you're doing with the cranking fuel divider is to decide how much to split the total pulsewidth over the 4-stroke cycle.

Ok, fair enough but I then fail to see the reason for 'cranking fuel divider' whether it is 1, 2 or 4 times per cycle resulting in only the exact same amount of fuel being elivered during cranking.

I thought 'fire all banks while cranking'  turned the cranking injection sequence from sequential into batch and the divider was used to then divide the calculated PW  by the number entered in 'cranking fuel divider'  1 for sequential, 2 for semi, and 4 for batch.

Its all a mystery to me why do we have settings that give the same end result. Its a lot of un necessary configuration for no gain.

Im not being awkward, i just cannot see logic lol.

I have been doing some bench testing, more of a looksie see to be honest. I noticed that upgrading to 1.1.70 and then uploading my 1.1.47 config worked really well. I am impressed . I also noticed that the cranking setting I had in 1.1.47 as 'fire all banks while cranking' has transpired into 'fire all banks while cranking' and a cranking divider of 2, which would go with my original theory that it would double the fuel at cranking without the need for silly cold crank percentages

Im off to play some more

[rob@vems.co.uk]

Step 1 - Open log file
Step 2 - nothing but a the initial screen. I can only hit Pause and Stop, so it looks like it´s trying to play but nothing happens.
Step 3 - move the time slider around and when it stops it shows the gauges at that time

This bug has been marked as completed on 31 March.  I guess a new set of executables will be out soon with the fix applied.