http://vems.hu/download/v3gui/VemsTune-Install-2010-04-16-testing.exe (http://vems.hu/download/v3gui/VemsTune-Install-2010-04-16-testing.exe)
New thread for a new testing release
Main fixes:
MSQ export should work with MS log viewer (If this now works to everyones liking, re-import of VE table might be started next week)
Statistics should not crash like it did before
Added outlier removal to statistics, multiplier is in standard deviations(?), 2 recommended for short logs, 1 for long logs
Multigraph (log viewer) should not crash the whole program
small menu changes (cosmetics mostly)
round gauge emergency revival even more improved (used when firmware upgrade gone bad!)
changes to communications again that could improve stability
installer script update, more likely to support win7
I saw this in the last version too but if I forget to open a log file and hit Re-Evaluate in the stats, it brings my computer to its knees. If I can kill it in time, it only bloats to about 400 meg of ram. Minor bug but this probably shouldn't be available with no stats open.
pretty sure you still have to select the 'input source' as logs. It will automatically open up a window to select the log. you can then run the stats, and apply.
then i guess you save the config and upload it once you are connected to the car again?
MSQ exports, and opens in MLV. However when i try to run the analysis nothing happens. I'm trying to see what needs to be tweaked to make it happen. MLV is converted the lambda table into AFR, so that seems good but i'm wondering if the table size difference is an issue at all for MLV
I'll post back if i figure anything out
Quote from: multiplex on April 17, 2010, 12:53:34 AM
pretty sure you still have to select the 'input source' as logs. It will automatically open up a window to select the log. you can then run the stats, and apply.
You can choose either that button, or just open log in the file menu.
Quotethen i guess you save the config and upload it once you are connected to the car again?
Yes, this is one of the largest problem around now, some automatic detection of getting back online is needed, and a question if you want to upload changes or loose it.
QuoteMSQ exports, and opens in MLV. However when i try to run the analysis nothing happens. I'm trying to see what needs to be tweaked to make it happen. MLV is converted the lambda table into AFR, so that seems good but i'm wondering if the table size difference is an issue at all for MLV
I'll post back if i figure anything out
So halfway done then ;)
I hope you can find the reason, so we can go on to the next stage to re-upload the analyzed table.
Table size difference? You mean 16x14 VE and smaller Lambda table? No it is not MLV issue.
For me this new version hangs at first step I want perform - firmware upgrade.
I make little error at beginning: choose firmware (1.1.71 - non-PS) and hit upload, but at same time noticed my board was unpowered. In a second I switch it on and update process seems going as normal. After few seconds - blue screen! Didn't seen it for months! Then three times retried (after forced PC restart every time). Same happens.
System event viewer stores error ID:7023 related to Service Control Manager.
In blue screen ser2pl.sys is mentioned.
Downgrade to 2010.04.13 VT - works ok...
Gints
Ok here is a MSQ i hacked together and cleaned out, from my previous trials. It runs well in MLV, even with the different table sizes
I haven't had time to compare it to what is now coming out of VT. I'll try to work on that
<?xml version="1.0" encoding="ISO-8859-1"?>
<msq xmlns="http://www.msefi.com/:msq">
<bibliography author="MegaTune 2.25" writeDate="2008-03-11T06:39:45+00:00"/>
<versionInfo fileFormat="4.0" nPages="7" signature="VEMS v1.1 16x14 kpa=2,2"/>
<page number="1" size="254">
<constant name="mapBins" rows="14" units="kPa">
20
38
54
72
88
104
118
142
166
192
216
242
266
290
</constant>
<constant name="rpmBins" rows="16" units="RPM">
900
1300
1800
2200
2700
3100
3500
4000
4400
4900
5300
5700
6200
6600
7100
7500
</constant>
<constant cols="16" name="veTable" rows="14" units="%">
11.0 12.0 15.0 13.0 13.0 16.0 12.0 12.0 11.0 21.0 35.0 36.0 36.0 36.0 36.0 36.0
11.0 19.0 22.0 17.0 17.0 15.0 15.0 16.0 16.0 19.0 33.0 35.0 36.0 36.0 36.0 36.0
15.0 30.0 32.0 26.0 27.0 25.0 26.0 28.0 25.0 25.0 36.0 37.0 37.0 37.0 37.0 37.0
25.0 41.0 43.0 41.0 44.0 41.0 41.0 44.0 36.0 39.0 49.0 48.0 45.0 45.0 45.0 45.0
26.0 59.0 71.0 53.0 57.0 55.0 55.0 58.0 51.0 51.0 54.0 56.0 58.0 58.0 58.0 58.0
29.0 53.0 70.0 67.0 71.0 70.0 70.0 71.0 65.0 67.0 66.0 66.0 66.0 66.0 66.0 66.0
29.0 58.0 61.0 74.0 82.0 82.0 84.0 89.0 86.0 90.0 94.0 89.0 94.0 91.0 90.0 90.0
34.0 59.0 59.0 61.0 103.0 97.0 104.0 104.0 98.0 102.0 120.0 129.0 131.0 125.0 124.0 124.0
35.0 59.0 59.0 56.0 114.0 126.0 122.0 124.0 123.0 130.0 164.0 164.0 175.0 170.0 160.0 160.0
35.0 54.0 59.0 60.0 105.0 153.0 145.0 145.0 150.0 165.0 208.0 217.0 224.0 209.0 210.0 210.0
36.0 54.0 59.0 64.0 98.0 174.0 173.0 174.0 177.0 183.0 195.0 220.0 223.0 218.0 215.0 215.0
36.0 54.0 59.0 71.0 101.0 144.0 199.0 193.0 208.0 214.0 218.0 230.0 231.0 230.0 230.0 230.0
36.0 54.0 59.0 71.0 101.0 144.0 201.0 204.0 233.0 232.0 230.0 230.0 231.0 230.0 230.0 230.0
36.0 54.0 59.0 71.0 101.0 144.0 201.0 204.0 233.0 232.0 230.0 230.0 231.0 230.0 230.0 255.0
</constant>
</page>
<page number="2" size="254">
<constant cols="8" name="afrBins1" rows="8" units="Lambda">
0.99 0.99 0.99 0.99 0.99 0.99 0.99 0.99
0.99 0.99 0.99 0.99 0.99 0.99 0.99 0.99
0.99 0.99 0.99 0.99 0.99 0.99 0.99 0.99
0.86 0.86 0.86 0.86 0.86 0.86 0.86 0.86
0.81 0.81 0.81 0.81 0.81 0.81 0.81 0.81
0.80 0.80 0.80 0.80 0.80 0.80 0.80 0.80
0.80 0.80 0.80 0.80 0.80 0.80 0.80 0.80
0.80 0.80 0.80 0.80 0.80 0.80 0.80 0.80
</constant>
<constant name="mapBinsA" rows="8" units="kPa">
20
38
72
104
166
192
242
290
</constant>
<constant name="rpmBinsA" rows="8" units="RPM">
900
1300
2200
2700
4000
5300
6200
7500
</constant>
</page>
</msq>
Quote from: GintsK on April 17, 2010, 01:46:52 AM
Table size difference? You mean 16x14 VE and smaller Lambda table? No it is not MLV issue.
For me this new version hangs at first step I want perform - firmware upgrade.
I make little error at beginning: choose firmware (1.1.71 - non-PS) and hit upload, but at same time noticed my board was unpowered. In a second I switch it on and update process seems going as normal. After few seconds - blue screen! Didn't seen it for months! Then three times retried (after forced PC restart every time). Same happens.
System event viewer stores error ID:7023 related to Service Control Manager.
In blue screen ser2pl.sys is mentioned.
Downgrade to 2010.04.13 VT - works ok...
Gints
What windows version and hardware?
I just heard that "Run as administrator" might be needed for vista and win7
Sorry! Plain XP SP2 PentiumM 1.6ghz 1.25GB ram T40p Thinkpad.
cracked the issue with running VE tune in MLV with the exported MSQ
the resolution of the MAP & BIN tables is too large.. Drop the ".00" and it works
i replaced all of the ".00" with a space, and everything works as is.
;D
It would be nice to have 1024x600.support. Some windows are too big :)
Quote from: multiplex on April 18, 2010, 02:41:41 AM
cracked the issue with running VE tune in MLV with the exported MSQ
the resolution of the MAP & BIN tables is too large.. Drop the ".00" and it works
i replaced all of the ".00" with a space, and everything works as is.
;D
I will try to fix this today, Will it do with no decimals for one dimensional arrays?
QuoteIt would be nice to have 1024x600.support. Some windows are too big
An additional screen resolution will be added for the netbooks, so actually already planned.
thanks for pointing it out.
Sorry for the big post, but this is the output of msq export with my last change, just taken straight from my vemstune generated file and pasted here
<?xml version="1.0" encoding="ISO-8859-1"?>
<msq xmlns="http://www.msefi.com/:msq">
<page number="1"/>
<page number="2">
<constant name="veTable" rows="14" cols="16" units="%" offset="0">
50.0 50.0 50.0 50.0 50.0 50.0 50.0 50.0 50.0 50.0 50.0 50.0 50.0 50.0 50.0 50.0
50.0 50.0 50.0 50.0 50.0 50.0 50.0 50.0 50.0 50.0 50.0 50.0 50.0 50.0 50.0 50.0
50.0 50.0 50.0 50.0 50.0 50.0 50.0 50.0 50.0 50.0 50.0 50.0 50.0 50.0 50.0 50.0
50.0 50.0 50.0 50.0 50.0 50.0 50.0 50.0 50.0 50.0 50.0 50.0 50.0 50.0 50.0 50.0
80.0 80.0 80.0 80.0 80.0 50.0 50.0 50.0 50.0 50.0 50.0 50.0 50.0 50.0 50.0 50.0
0.0 0.0 0.0 0.0 0.0 0.0 50.0 50.0 50.0 50.0 50.0 50.0 50.0 50.0 50.0 50.0
0.0 0.0 0.0 0.0 0.0 0.0 50.0 50.0 50.0 0.0 50.0 50.0 50.0 50.0 50.0 50.0
0.0 0.0 0.0 0.0 0.0 0.0 50.0 50.0 50.0 50.0 50.0 50.0 50.0 50.0 50.0 50.0
0.0 0.0 0.0 0.0 0.0 0.0 50.0 50.0 0.0 50.0 50.0 50.0 50.0 50.0 50.0 50.0
0.0 0.0 0.0 0.0 0.0 0.0 50.0 50.0 50.0 50.0 50.0 50.0 50.0 50.0 50.0 50.0
0.0 0.0 0.0 0.0 0.0 0.0 50.0 50.0 50.0 50.0 50.0 50.0 50.0 50.0 50.0 50.0
0.0 0.0 0.0 0.0 0.0 0.0 50.0 50.0 38.0 50.0 50.0 50.0 50.0 50.0 50.0 50.0
0.0 0.0 0.0 0.0 0.0 0.0 50.0 44.0 28.0 28.0 50.0 50.0 50.0 50.0 50.0 50.0
0.0 0.0 0.0 0.0 0.0 0.0 50.0 50.0 50.0 50.0 50.0 50.0 50.0 50.0 50.0 50.0
</constant>
<constant name="rpmBinsVE" rows="16" units="RPM" offset="224">
500
800
1000
1300
1700
2000
2400
2700
3000
3500
4000
4500
5000
5500
6000
6700
</constant>
<constant name="mapBinsVE" rows="14" units="kPa" offset="240">
40
60
70
80
90
100
110
120
130
140
160
180
200
220
</constant>
</page>
<page number="3">
<constant name="lambdaTable" rows="8" cols="8" units="Lambda" offset="0">
1.00 1.00 1.00 1.00 1.00 1.00 1.00 1.00
1.00 1.00 1.00 1.00 1.00 1.00 1.00 1.00
0.94 0.94 0.94 0.94 0.96 0.96 0.98 0.99
0.88 0.88 0.88 0.88 0.94 0.95 0.96 0.97
0.86 0.86 0.87 0.87 0.89 0.92 0.92 0.92
0.86 0.86 0.86 0.86 0.88 0.90 0.90 0.90
0.82 0.82 0.81 0.79 0.83 0.85 0.83 0.83
0.81 0.81 0.81 0.79 0.79 0.79 0.76 0.76
</constant>
<constant name="rpmBinsLambda" rows="8" units="RPM" offset="64">
700
1000
2000
2600
4100
4900
6100
6700
</constant>
<constant name="mapBinsLambda" rows="8" units="kPa" offset="72">
20
30
70
80
102
116
200
320
</constant>
</page>
<page number="4">
<constant name="sparkTable" rows="12" cols="12" units="Deg" offset="0">
17 19 25 40 42 43 43 43 43 43 43 42
16 19 22 38 39 40 41 41 41 41 41 41
15 19 22 37 38 39 40 40 40 40 40 40
14 18 21 31 36 37 38 39 40 40 40 40
14 18 21 27 33 34 34 34 34 34 34 34
13 17 20 24 30 31 32 33 34 34 34 34
12 17 20 23 29 30 31 33 34 34 34 34
12 14 15 16 23 26 26 26 26 26 26 26
11 13 14 16 23 23 25 25 25 25 25 25
11 13 14 16 19 22 22 24 25 25 26 27
9 10 12 14 19 22 22 24 24 24 24 24
9 9 10 12 17 18 21 22 24 26 27 27
</constant>
<constant name="rpmBinsSpark" rows="12" units="RPM" offset="144">
700
1000
1400
2000
2600
3400
4100
4900
5500
6100
6700
8800
</constant>
<constant name="mapBinsSpark" rows="12" units="kPa" offset="156">
20
30
50
70
80
86
102
116
140
200
320
420
</constant>
</page>
<page number="5"/>
<page number="6"/>
<page number="7"/>
<page number="8"/>
<page number="9"/>
<page number="10"/>
<page number="11"/>
<page number="15"/>
</msq>
works great! ;D
as I wrote in another topic, i use noniverted drivers and inverted value in h[0]. In an earlier version was seen marked value, and not new.
Might like the option of Ignition settings -> Inverted drivers could make such an option in Settings Injection ECU or Settings?
In any version you can not select the same box for different outputs
Double posting this at the direction of Rob:
When I'm in my car, my laptop doesn't have internet access to download the new firmware via the webtool.
So, I hooked it all up, got it to recognize VEMS was there, walked into my house, got the wireless up and running, opened the firmware web tool, downloaded 1.1.70, then went out into the garage, hooked into vems, and clicked install.
It didn't give me any sort of confirmation that the firmware had been flashed, except that next to 1.1.70, in the "local" box on the right, it said "installed" next to 1.1.70.
The bottom of VT, next to the status, says I'm running 1.0.73 still. IniFile is still 1.0.73.
I Thought this was weird, oh well. I Clicked and dragged M's config file over, told it to upload, and it did, hooray, except it gave me a bunch of scalar errors and warnings and whatnot. I ran the sanity check again, and it came up fine.
I checked the wideband settings portion, and I still have my original message under "retry after".
What am I doing wrong?
I can't just upload via the "upload firmware....bat" method, because it isn't in either of the downloads I've been able to find.
Entire previous thread here:
http://195.159.109.134/vemsuk/forum/index.php/topic,1209.0.html
the install button in the webtool doesn't actually install the firmware to your ECU - it simply unzips the file, and makes it available inside Vemstune
You still need to download the firmware to VEMS, and then upload the config
tools -> firmware -> firmware upload
bahaha
Alrighty, that'll be next then.
Thanks duder
Any eta on the next vemstune build? And are they all going to be 'testing' for now or is there going to be a stable build?
Thanks,
D
Topic for previous version (Apr. 13) is locked - so I'll post here.
Very annoying things:
logging stops after ECU repower.
Vemstune do not restore communications after longer pause. Needs program restart.
Converting to csv: could it be converting to xls? Because it is MLV native file extension. Now it require type extension again and again. It would be nice if this window stores my choice for both - file extension and autoclose.
Gints
Have anybody tried it in Windows7? It doesn't work in 32bit..
Quote from: mr_g on May 16, 2010, 11:12:31 PM
Have anybody tried it in Windows7? It doesn't work in 32bit..
Do you click Run as Administrator?
I'm administrator.. :D
edit: Damn! You are right! ???