new firmware releases

[AVP]

where can i get a vemscfg for the 1.1.67 then? as a base tune?

[gunni]

you can make one,

create a new project with the firmware you want to use, then save and load it, then you are free to change it and save as a new cfg file.

[AVP]

i dont see the option of 'create new file' in the options.
if i open vemstune, then with the latest firmware uploaded, how do i start a new cfg from scratch?

[gunni]

Have you created a project?
And loaded the project?

when you have that done you can save a config file.

[AVP]

ooook gotcha! going to play around a bit now then...

[AVP]

Is there a place in this forum or the VEMS wiki, where developers or other VEMS tuners can explain the differences of the new implemented features in various areas?

For example, on the megatune era, there were large documents where someone would be able to go and read, and get an idea what feature is doing what. Now with vemstune it seems that we are jumping into settings that are not explained anywhere and some need to be just tested with trial and error to see what the correct values are.

It would be interesting to have someone present a document comparing the old official version that VEMS was sold with (1.1.27) to the new versions and just add some explanations to the new features, same as it is in the VEMS wiki as the main start page of vems installation.

The list im finding so far goes like:

1) soft ignition cut
2) Partial fuelcut mode
3) accel.enrichment fadeout factor
4) accel. enrichment ign.retard at accel=reqfuel
5) fuel film
6) IAC PWM frequency
7) IAC PWM duty cycle allowed min/max
IAC close delay
9) refpos for mat slope (IAC)


more things may come up from other users, but a list of all these different features will help us understand how to manipulate them

thanks

[AVP]

also another thing that i havent clearly figured out.

I create a new project on version 1.1.67, drag and drop the settings from my 1.1.61 setup, then go to save my new config as 1.1.67 and when i reopen the new saved config, it is back to 1.1.61.

how can i save a config after having created a new project?

if i open the config first, at 1.1.61, and then load the project on 1.1.67, what i get is: firmware: 1.1.61 and project config:1.1.67.
BUT this cannot be saved as 1.1.67 config thereafter!

[z0tya]

also another thing that i havent clearly figured out.

I create a new project on version 1.1.67, drag and drop the settings from my 1.1.61 setup, then go to save my new config as 1.1.67 and when i reopen the new saved config, it is back to 1.1.61.

how can i save a config after having created a new project?

if i open the config first, at 1.1.61, and then load the project on 1.1.67, what i get is: firmware: 1.1.61 and project config:1.1.67.
BUT this cannot be saved as 1.1.67 config thereafter!

Try to edit by hand the config file header

[mattias]

AVP: I'm not sure what you're trying to do.

Here is my advice, don't use the project majiggytyhingy.

Just save the config (1.1.61) before you upgrade.
After upgrade open config, choose upload and go through all the complaints that the compatibility checker spits out.
Done.

[AVP]

im trying to setup a config with the 1.167 firmware.

but i have a previous config with the 1.1.61 firmware. So im trying to upgrade it to the new firmaware and play around with the new settings.

once i have the 1.1.67 project loaded, with my settings from 1.1.61, it doesnt seem to be able to be saved as an 1.1.67 config though.

[AVP]

here is an idea..

how about a 6 or 9 bin table only dedicated for idle manipulation, so that the basic tables of VE/lamda/spark can get rid of those bins and so have a larger area to play with?

just a thought...

[rob@vems.co.uk]

How do you manage and detect the transition between idle and running?

[AVP]

i imagined it as a magnifying glass being placed on the initial bins on the VE/lamda/spark tables. So that if you have say a 6 bin table and you have bins of 500-800-1200rpm and kpa: 40-55, you can then start the VE above those values and perhaps vemstune can use that. In that case you end up with a few extra bins to use which may be usefull on lamda and spark tables which are now much smaller on vemstune.

[GintsK]

Sorry, I can't follow. For what reason? Is there some succesive examples around? What is disadvantages of current strategy?

Gints

[gunni]

idle would be triggered by TPS below a surten point.

Common for many ecu´s to have separate idle maps. Especially with high cam engines or similar, I know mattias is very interested in
getting a idle specific table.