Quote from: [email protected] on April 12, 2010, 12:47:28 AM
Okay, thanks for that, now can someone let me know when a new VEMStune is available? I'll then start a new thread with the date/version number/link for users to test and comment on.
New vemstune was today released.
http://www.vems.hu/download/v3gui/VemsTune-Install-2010-04-13-testing.exe
new vemstune is released, but doesn't seem to be functioning :'(
tune by stats freezes up (tested by two different people)
Quote from: multiplex on April 14, 2010, 01:22:07 AM
new vemstune is released, but doesn't seem to be functioning :'(
tune by stats freezes up (tested by two different people)
Same here. I didn't even try loading logs, but when I close the window, the application crashes.
Any more bugs that aren't freezes when loading logs?
The tune by stats in online mode is being replaced by a realtime version, this freezing bug in online mode is currently known by the developers
I would be very interesting if anyone that earlier had comm problems can report if that is better
I currently see no comm problem on my computer, neither with real port, FTDI or prolific.
Other fixed stuff:The problem with 2D table not updating on a slow computer seems to be solved.
the editor in multigraph(log viewer) should be much improved
collission detection for output channels is much better
crash on rapid powercycling repeatedly is fixed
calculation model (expression grid) is improved and has better models
Output test functions are repaired for injectors as well, remember that for all but injectors, the testing will only flash the output, as other functions on one output keep turning it off from ECU side
For ignition test, dwell is not perfectly calculated, but within reasonable range to be able to see spark, When engine is running, dwell is started timed from a certain trigger tooth, which obviously is not available with engine not running, dont worry about this.
new stuff:Time for logging is now taken from PC instead of estimating from ECU 1 second clock timer
GPS route gauge is new, which can be used as a track map when GPS is connected, with internet connection, this also will download a map of the actual area
support for connecting to round gauges is added, also emergency revival of these in case of a failed firmware upgrade
known problems (that is scheduled for fixing) :
- Closing statistics window without using it crashes program
- Playing too much in toolbar by moving things around can cause crash
- loading statistics menu in online mode can cause crash
- There is no default screen that works good in 1024x600 screens (eee for example)
- In OFF-line mode, the burn and write buttons are greyed out, though the hot keys (alt-w and alt-b) is not locked, and this will cause reset of your changes for that offline settings, be careful with this
- False warning about trigger tooth width on all configs
- Default view angle of 3D VE table is very hard to use, adjust this with j+k and n+m keys
- Time in the SD card overview is a bit too long for each log (approx 14%), so length will mismatch for your downloaded log, time stamps are still good
Thanks for the prompt reply!
Quote from: [email protected] on April 14, 2010, 04:59:01 AMfreezing bug in online mode is currently known by the developers
Do you mean offline mode? I haven't tried it online yet.
i tried tune by stats, selected 'logs' as my source
this worked out fine.
however i know i used to be able to use stats without this extra step
also - thanks for the note about the trigger tooth width warning being an error. I was starting to track that down last night
Can anyone that had this problem with offline ve tune by statistics please describe how you do to freeze it?
I just tried this on a couple of different logs:
Start program
File -> Open Log File
Tools -> VE Tune by statistics
Clicked (Re-)Evaluate
changed some sites
closed window
While writing this post, i just realized that it actually crashes when closing this window before having any evaluation done, so this is currently in the works of getting fixed, but let me know if you found another "method" to get it to fail
thanks / emil
When Can I use vemstune msq export for Megalogviewer? It is not working now.
MSQ is the file format of megatune, this is vemstune, a completely different program
This program saves log files in vemslog format
You can though export a log file to csv format and load into excel or megalogviewer
If it's interesting for you I can not connect with the old VemsTune or the new.
I use Windows 7 and Logistics Link.
Mega Tune 1.1.18 connect fine.
B Regards
Pedersen
Copenhagen
Quote from: [email protected] on April 14, 2010, 08:00:10 PM
MSQ is the file format of megatune, this is vemstune, a completely different program
This program saves log files in vemslog format
You can though export a log file to csv format and load into excel or megalogviewer
Emil, z0tya means Tools->MSQ export.
I can't try myself, but one of my customers tried new VT on dualcore today: little better. Previous VT hangs in first minute. Now it can last five minutes... Symptoms are same: for first gauges starts to show crap, then freezes. Prolific.
I will test my FDTI later.
Oh, forgot that the msq export still is around, that will probably be removed
can anyone that wants to use it list what is exactly wrong with the msq exported?
thanks /e
i had posted up my issues on vems.hu with MSQ export previously, but have since given up trying to get it working
The only reason i wanted MSQ export was so that i could use MLV's tuning feature. Since then, vemstune has made some good advances with 'tune by stats' so i'm going to try and use that. I still prefer the graphing of MLV, but am trying to get used to VT
Here is what i posted on vems.hu, there may be other issues as well. At one point i had hand edited an MSQ for use, but it became very cumbersome.
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?
Quote from: [email protected] on April 14, 2010, 11:53:10 PM
Oh, forgot that the msq export still is around, that will probably be removed
can anyone that wants to use it list what is exactly wrong with the msq exported?
thanks /e
From my point of view it could be necessary only for MLV not Megatune. Not all config necessary to convert, but only tables (preferably all tables because MLV offers nice visual representation of operating point of engine on these).
Now it seems VT make wrong beginning of file and MLV do not opening it.
Yes - it is also my attitude: MLV shouldn't be dropped from VT as long as possible. Until built-in VT datalog review features reach same versatile level.
good point - the MSQ export could just have the lambda table and ve table, thats all that is needed for MLV tuning
problem is, there also needs to be a way to get the data back into VT. so possibly importing the ve table from an MSQ, much like you can import from vemscfg file
How to prevent loosing of my customizing at version update? Gauge groups, hotkeys, com port...
Seems 1 hour of work now disappeared - new version simply overwrite everything...
Quote from: GintsK on April 15, 2010, 02:07:47 AM
How to prevent loosing of my customizing at version update? Gauge groups, hotkeys, com port...
Seems 1 hour of work now disappeared - new version simply overwrite everything...
I'd like to see a fix for this too. For now, just find the latest-modified gauges-XxY.db file in your VEMS install directory (X and Y should be your screen rez), save it elsewhere, then overwrite the one VEMS installs.
This is a hacked exported msq which works with megalogviewer:
<?xml version="1.0" encoding="ISO-8859-1"?>
<msq xmlns="http://www.msefi.com/:msq">
<page number="2">
<constant name="veTable" rows="14" cols="16" units="%" offset="0">
59.00 63.00 67.00 69.00 72.00 76.00 80.00 84.00 89.00 91.00 96.00 98.00 98.00 98.00 98.00 98.00
64.00 69.00 75.00 81.00 84.00 89.00 92.00 94.00 95.00 99.00 103.00 105.00 107.00 107.00 107.00 107.00
71.00 77.00 81.00 86.00 93.00 95.00 97.00 99.00 102.00 103.00 108.00 111.00 108.00 108.00 108.00 108.00
75.00 80.00 86.00 93.00 99.00 102.00 103.00 105.00 107.00 110.00 112.00 114.00 114.00 114.00 114.00 114.00
74.00 83.00 89.00 95.00 104.00 108.00 110.00 111.00 112.00 112.00 112.00 114.00 114.00 114.00 114.00 114.00
73.00 83.00 89.00 95.00 104.00 108.00 111.00 112.00 114.00 116.00 116.00 117.00 117.00 117.00 117.00 117.00
71.00 82.00 88.00 96.00 105.00 109.00 112.00 113.00 115.00 117.00 117.00 118.00 118.00 118.00 118.00 118.00
68.00 80.00 86.00 95.00 104.00 109.00 112.00 113.00 115.00 117.00 117.00 117.00 117.00 117.00 117.00 117.00
66.00 79.00 86.00 95.00 104.00 109.00 112.00 113.00 115.00 117.00 117.00 117.00 117.00 117.00 117.00 117.00
64.00 79.00 86.00 95.00 104.00 109.00 112.00 113.00 115.00 117.00 117.00 117.00 117.00 117.00 117.00 117.00
64.00 79.00 86.00 95.00 104.00 109.00 112.00 113.00 115.00 117.00 117.00 117.00 117.00 117.00 117.00 117.00
64.00 79.00 86.00 95.00 104.00 109.00 112.00 113.00 115.00 117.00 117.00 117.00 117.00 117.00 117.00 117.00
64.00 79.00 86.00 95.00 104.00 109.00 112.00 113.00 115.00 117.00 117.00 117.00 117.00 117.00 117.00 117.00
64.00 79.00 86.00 95.00 104.00 109.00 112.00 113.00 115.00 117.00 117.00 117.00 117.00 117.00 117.00 117.00
</constant>
<constant name="rpmBinsVE" rows="16" units="RPM" offset="224">
600.00
900.00
1400.00
2000.00
2600.00
3200.00
3800.00
4400.00
5000.00
5600.00
6300.00
7100.00
7100.00
7100.00
7100.00
7100.00
</constant>
<constant name="mapBinsVE" rows="14" units="kPa" offset="240">
20.00
40.00
60.00
80.00
100.00
120.00
150.00
180.00
210.00
240.00
270.00
300.00
300.00
300.00
</constant>
</page>
<page number="3">
<constant name="l" rows="8" cols="8" units="Lambda" offset="0">
0.96 0.96 0.96 0.96 0.96 0.96 0.96 0.93
0.96 0.96 1.00 1.00 1.00 1.00 1.00 0.96
0.96 0.96 1.00 1.00 1.00 1.00 1.00 0.96
0.93 0.93 0.93 0.93 0.93 0.93 0.93 0.91
0.88 0.88 0.88 0.88 0.88 0.88 0.88 0.84
0.86 0.86 0.86 0.86 0.86 0.86 0.86 0.84
0.82 0.82 0.82 0.82 0.82 0.82 0.82 0.80
0.78 0.78 0.78 0.78 0.78 0.78 0.78 0.76
</constant>
<constant name="lambdaTable" rows="8" cols="8" units="Lambda" offset="0">
0.96 0.96 0.96 0.96 0.96 0.96 0.96 0.93
0.96 0.96 1.00 1.00 1.00 1.00 1.00 0.96
0.96 0.96 1.00 1.00 1.00 1.00 1.00 0.96
0.93 0.93 0.93 0.93 0.93 0.93 0.93 0.91
0.88 0.88 0.88 0.88 0.88 0.88 0.88 0.84
0.86 0.86 0.86 0.86 0.86 0.86 0.86 0.84
0.82 0.82 0.82 0.82 0.82 0.82 0.82 0.80
0.78 0.78 0.78 0.78 0.78 0.78 0.78 0.76
</constant>
<constant name="rpmBinsLambda" rows="8" units="RPM" offset="64">
600.00
900.00
2000.00
2600.00
3800.00
4400.00
5600.00
7100.00
</constant>
<constant name="mapBinsLambda" rows="8" units="kPa" offset="72">
20.00
40.00
80.00
100.00
150.00
180.00
240.00
300.00
</constant>
</page>
<page number="4">
<constant name="n" rows="12" cols="12" units="Deg" offset="0">
15.00 15.00 16.00 25.00 31.00 33.00 35.00 35.00 35.00 35.00 35.00 34.00
15.00 15.00 17.00 26.00 31.00 33.00 34.00 34.00 34.00 34.00 34.00 33.00
14.00 16.00 18.00 26.00 30.00 32.00 33.00 33.00 33.00 33.00 33.00 32.00
13.00 16.00 18.00 24.00 29.00 31.00 32.00 32.00 32.00 32.00 32.00 31.00
12.00 15.00 17.00 23.00 27.00 29.00 30.00 30.00 30.00 30.00 30.00 29.00
11.00 13.00 16.00 20.00 23.00 25.00 25.00 26.00 26.00 26.00 26.00 25.00
10.00 12.00 13.00 14.00 16.00 18.00 20.00 21.00 21.00 21.00 21.00 20.00
9.00 11.00 12.00 13.00 14.00 14.00 15.00 16.00 16.00 16.00 16.00 15.00
8.00 9.00 10.00 11.00 11.00 12.00 13.00 14.00 14.00 14.00 14.00 13.00
7.00 8.00 9.00 10.00 10.00 10.00 11.00 12.00 12.00 12.00 12.00 11.00
7.00 7.00 8.00 9.00 9.00 9.00 9.00 9.00 9.00 9.00 9.00 8.00
6.00 6.00 6.00 6.00 6.00 6.00 6.00 6.00 6.00 6.00 6.00 5.00
</constant>
<constant name="sparkTable" rows="12" cols="12" units="Deg" offset="0">
15.00 15.00 16.00 25.00 31.00 33.00 35.00 35.00 35.00 35.00 35.00 34.00
15.00 15.00 17.00 26.00 31.00 33.00 34.00 34.00 34.00 34.00 34.00 33.00
14.00 16.00 18.00 26.00 30.00 32.00 33.00 33.00 33.00 33.00 33.00 32.00
13.00 16.00 18.00 24.00 29.00 31.00 32.00 32.00 32.00 32.00 32.00 31.00
12.00 15.00 17.00 23.00 27.00 29.00 30.00 30.00 30.00 30.00 30.00 29.00
11.00 13.00 16.00 20.00 23.00 25.00 25.00 26.00 26.00 26.00 26.00 25.00
10.00 12.00 13.00 14.00 16.00 18.00 20.00 21.00 21.00 21.00 21.00 20.00
9.00 11.00 12.00 13.00 14.00 14.00 15.00 16.00 16.00 16.00 16.00 15.00
8.00 9.00 10.00 11.00 11.00 12.00 13.00 14.00 14.00 14.00 14.00 13.00
7.00 8.00 9.00 10.00 10.00 10.00 11.00 12.00 12.00 12.00 12.00 11.00
7.00 7.00 8.00 9.00 9.00 9.00 9.00 9.00 9.00 9.00 9.00 8.00
6.00 6.00 6.00 6.00 6.00 6.00 6.00 6.00 6.00 6.00 6.00 5.00
</constant>
<constant name="rpmBinsSpark" rows="12" units="RPM" offset="144">
600.00
900.00
1400.00
2000.00
2600.00
3200.00
3800.00
4400.00
5000.00
5600.00
6300.00
7100.00
</constant>
<constant name="rpmBinsSpark_0" units="deg" offset="144">600</constant>
<constant name="mapBinsSpark" rows="12" units="kPa" offset="156">
20.00
40.00
60.00
80.00
100.00
120.00
150.00
180.00
210.00
240.00
270.00
300.00
</constant>
</page>
</msq>
Quote from: z0tya on April 15, 2010, 03:31:21 PM
This is a hacked exported msq which works with megalogviewer:
<?xml version="1.0" encoding="ISO-8859-1"?>
<msq xmlns="http://www.msefi.com/:msq">
Do you think you can email this msq and the one outputted by vemstune that you fixed
Its easier to not miss any details if we can compare differences of the 2 files and just fix this.
Also we'll look into being able to drop back a ve table from msq format.
Is it enough to only support VE table import? would simplify things.
New testing release is planned with the crash in ve analysis fixed, also a crash in multigraph (log viewer)
Now I fail to crash the program, can anyone help find a new way?
2010-04-13 test release contained 3 big crashes that is now repaired
VE analysis
Multigraph in online mode was possible to crash
moving toolbar in main screen in some strange way
//Emil