VEMS firmware versions

[Jamo]

jamo, if you plan to handle stuff on your own, then here is what you have to do.

if you start with a map of 16x14 tables, all you have to do is remodel the spark map to 12x12 and lamda to 8x8. the VE table is still 16x14.

then the new tables is just trial and error. Where your spark advance/retard will happen is where the knock will appear. what EGTs you want boost to be lowered, is your choise. How MAT will effect fueling is something that you can determine. If you dont want to customise them, you can just leave them untouched and your engine will still work fine.

for those who will always rely on a tuner to fix things, well they will have to ask them to do the change for them.

I dont see any trouble going from one to the other firmware. My only issue is installing the firmware to the ECU and succesfully communicating with it.

1.1.62 will take a while before Marc or others confirm it's stability.

My car is being professionally tuned therefore I do not want to retune post firmware change.

I will be doing some stuff myself yes but the major I wont

[A80Avant]

so basically, if you think that once the tune is done on any firmware, you will be able to succesfully do a transfer to the new tables, then you are ok to use the 1.1.27 and then switch to the 1.1.62.

who is going to be tuning your vems by the way?

[Jamo]

Repo will be, that's been in the pipeline for a while but i've got a bit of work to do before i'm ready

[A80Avant]

nicee!

im going to have it done localy (UK)!

[Jamo]

1.1.62 in an S2 http://www.vems.hu/wiki/index.php?pa...Page%2FAlexHoy

Vas has noticed something that Vemstune has a bug in the rpm vs boost table is wrong. I've been thinking this must be an .ini problem

[A80Avant]

yes, i spotted that and havent heard any responce for a fix yet. it needs mending surely

[Jamo]

I've just fixed it in my version

[Jamo]

Go to Boost Controller Settings make sure there is a PID entry in the Boost P setting I've entered 250
Set the Boost Config to 32, PWM Period to 16ms and changed the target to boost-target

Closed the config went back into boost vs rpm curve and it showed RPM and allowed me to enter rpm values such as 4000



I've noticed the table name changed as well

[A80Avant]

hmm
i had the 250 at pid and 16ms.
boost config though was different.
also it should be map target. if you put it at map target,does it still work?

[Jamo]

hmm
i had the 250 at pid and 16ms.
boost config though was different.
also it should be map target. if you put it at map target,does it still work?

Just checked and it works with either config selected.

Table looks the same the word curve goes, I think it is a bug but if you change the settings then change it back it works.

The boost pwm table also updates with the rpm values entered now

[GazzaG60]

the joys of eboost.

[A80Avant]

thats brilliant. im going to try it when i get home

[Jamo]

the joys of eboost.

Each to their own, I have an EBC also but there are fault conditions in the later vems firmware that can reduce boost so i'll be using that.

Vas have you seen anything that can covert the msq to the vemstune?

Looks like everything has to be entered manually?

[GazzaG60]

no but it controls boost well and a firmware update will make no difference whatsoever.

get the mapping correct and it should be ok.

precautions are for those who throw caution to the wind or dont understand or maybe worry about the lack of precautions or both/all.

id expect Repo will use his skills rather than potentially troublesome precautionary code. i am 100% sure it will be mapped with those off and maybe turned on at a later date. skills over precaution.

how much use is reducing boost on a melted piston. the same as how much use is retarding timing once the damage is done. you gotta set thresholds first.

i can see why you want them and applaud your seaching for the best feature set your suit your needs.

my experience so far with vemstune has not been the best. maybe why 1.1.27 is still so popular

[A80Avant]

i have entered mine all manually.i thiink you have to upload 1.1.27 to vemstune, make it into a vemsconfig file and then change it to 1.1.62 but i thought it was too complicated.

it took me roughly 45mins to put all the info manually