Google search for vemstune links to this as #1 hit for VemsTune.
http://www.vems.hu/wiki/index.php?page=VemsTuneThis was what was installed previously.
I since upgraded to 20-07-30 from
http://www.vems.hu/vt/ the desktop link on my multi user account laptpop was still linking to the old vemstune.
I had assumed it overwrote the old vemstune. Hence my post.
Looks like a copied ink form one account to another was not updated during install.
Hence my posting.
Anyway, on with the problems:
Ran latest VemtsTune 1.3.1 as above and tried correcting errors in config.
before
http://skynet.ie/~eireae86/3086/BEFORE_I_SORTED_CONFLICTS___v3.3_n003086-A-2012.08.27-13.13.09.vemscfgafter
http://skynet.ie/~eireae86/3086/pt_to_upload/LAST_NOTRIGGER_CFG_ERROR___v3.3_n003086-A-2012.08.27-17.01.43.vemscfgCant fix GPS baud rate error. The drop down permanently unselectable. > Software bug <
Changed injectors to 720 duration, but theres a bug.
When you do the first 210-720 change in the first pair of cells from 25500/210 to 25500/720, the 25500 on the left changes to 0.
If you change it back it can crash vemstune.
I did it again and changed it, burned cfg and did a sanity check.
The 720 error went away, but when i reconnected, it came back and the
value on left upper most cell was back to 0?
It seemed to do this again after i changed the value.
Changed.
Burned.
Sanity check -> no 720 errors.
Waited a few seconds.
Sanity check -> 720 error has returned?
There was also an alpha-n related warning but i didnt change the value
as on screen prodding suggested it was correct for alpha n.
Something about >520kpa for item 1?
The car is setup for alpha-n so perhaps this is a bug?
There was a trigger setting that was invalid according to sanity
check which i changed. Car still runs so Ive left it but given the
above issues I'm not confidant it was correct?
Lastly, Ive an issue with live ve analyser and tune by stats.
This suggests something may be corrupt in the ecu, but thats just a guess?
http://skynet.ie/~eireae86/3086/pt_to_upload/running_nostats_filtering_errors__v3.3_n003086-2012.08.27-16.58.06.vemslogAbove is a log from the running engine making lots of nice BRAPBRAP
sounds. Running rich.
I tried gathering stats, but its filtering out all the engine input?
Same with live analyser, says filtering error on screen.
I can see the rpm/tps dot bobbing around as i jab the throttle, but no
stats are being collected in either.
Any idea?
Some of the config errors related to fuel trim settings being invalid,
I disabled some and changed others to be seemingly sensible values.
If you can confirm that nothing Ive done is borked I would be grateful.
Id like to sort config stuff before car goes to map.
Currently sounds a beast, but Im paranoid about these settings.