VEMS firmware versions

[Jamo]

It cross references a load of ini files to generate the tables sizes etc, this isn't a new issue from the looks of it.

I've found it works up to 1.1.53, i'll keep messing it's fun.

If you open the 1.1.53 ini you'll see at line 1709 the curve editor to define the x and y axis for the table.

There is no such table for 1.1.62 i'm wondering if they harcoded it but I can't see why

[A80Avant]

what happens if you copy and paste that table info in the 1.1.62 ini file (or 1.1.62 for that matter, cause i only have up to 1.1.61 but marcel told me to rename the config file and it is the same as 1.1.62)

[Jamo]

what happens if you copy and paste that table info in the 1.1.62 ini file (or 1.1.62 for that matter, cause i only have up to 1.1.61 but marcel told me to rename the config file and it is the same as 1.1.62)

It crashes vemstune

they've changed the way tables are reference in the higher version, it's something simple but damned if I can be bothered to figure out their code.

If it was the same as the earlier versions very easy to fix!

[A80Avant]

at least now marcel knows about it and has replied that he will mention it to the developers.
maybe a 1.1.63 version might arise

[max_s2]

1.1.53 for me works OK! the only little problem is that tacho is jumping a bit when ignition = on, engine = off. I was told that it's a bug that is fixed in newer versions.

[A80Avant]

hopefully we'll get all major aspects fixed!

[Jamo]

at least now marcel knows about it and has replied that he will mention it to the developers.
maybe a 1.1.63 version might arise

Maybe, but this is a vemstune issue rather than the firmware. It doesn't work for any of the later 1.1.5x versions I think it's a simple thing to fix as all that needs to be changed is the array definition

[GazzaG60]

vemstune is the weakest link.


good work there jamo though.seems liek you are getting pretty familiar with the issues. the tuning is easier than the issues so you should be good to go.

[A80Avant]

i see.
well there is time to get it fixed,im not planning any radical change yet!
still like the good old 1.1.27!and still will do a proper tune on that before changing to 1.1.6x

[GazzaG60]

thought you have done a proper tune vas. is it not finished, if there ever is a finish.

tuning follows the 80-20 rule quite some.

[Jamo]

Cheers, been looking more and good the config is all over the shop multiple references in various ini's

Ah well at least i'm starting to understand somethings, i'll have to read megamanual though as the items still apply to the megatune values

[GazzaG60]

megamanual is great. not sure if its all still there from ms1 days. i had am msns setup for the 16vt to run on dizzy. never fitted it though. learned a lot from there and i really miss the use of megatune on vems.

[Jamo]

Vas check http://www.vems.hu/wiki/index.php?pa...2FFero%2FAudiS

Got the vemscfg from there and he is using the boost alternate pwm table instead. What's the difference between them?

[A80Avant]

well with alternate you are specifying solenoid duty cycle, while with boost you are specifying map wanted. I kind of like the latter because it is more down to earth to what i ask from the boost,rather than using a duty cycle value and expect to see what actual boost im getting.

i leave the duty cycle mumble to the ECU to figure out

[A80Avant]

Gary, it is always ongoing...

now that i have the headphones i will recheck for knock and im always adding something to finetune things!!