VEMS firmware versions

[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

[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]

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

[Jamo]

I've just fixed it in my version

[A80Avant]

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

[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]

nicee!

im going to have it done localy (UK)!

[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]

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]

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

[Bram]

Correct, 1.1.62 is out and available and works, but what I am trying to do is provide a smooth upgrade path for my customers. As has been mentioned, if a firmware upgrade is not done correctly things can go south in a hurry...

Bram: even in a perfect world where I am able to map the upgrade as smoothly as possible I would still highly recommend a double and tripple check on your tuning (sending me a log file should be sufficient) when the time comes.

OK, that sounds great. I will wait for your confirmation to start testing it if it has passed your test protocols. Thanks Marc!

[A80Avant]

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.

[Jamo]

1.1.62 is already out and downloadable from vems website.however i am too worried in doing something like that on my own before marc has fully tested it.

also because of the new tables im afraid you will probably need to retune the car.

bingo so if you upgrade you have to retune!

Wondering whether to go 1.1.62 from the off then

[a4kquattro]

excellent! Another reason to upgrade to a new VEMS firmware then. Do I also need to adjust the software of the VEMS round gauge itself? Or is it P&P?

I'm not sure on the VEMS round software, I think with it wired up it will pick up the settings automatically but I will test for you (I have a vems round test gauge here that I will play with). How it works: the serial output on your VEMS gets hooked up to the serial input on the vems round. A 'chirp' is sent over the serial line that feeds a data stream to the vems round for all the relevant data (egt and lambda). The same feature is used by aftermarket dashes as well, such as the AIM MXL.

[a4kquattro]

1.1.62 is already out and downloadable from vems website.however i am too worried in doing something like that on my own before marc has fully tested it.

also because of the new tables im afraid you will probably need to retune the car.

Correct, 1.1.62 is out and available and works, but what I am trying to do is provide a smooth upgrade path for my customers. As has been mentioned, if a firmware upgrade is not done correctly things can go south in a hurry...

Bram: even in a perfect world where I am able to map the upgrade as smoothly as possible I would still highly recommend a double and tripple check on your tuning (sending me a log file should be sufficient) when the time comes.