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.
VEMS firmware versions
Collapse
X
-
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.6xLeave a comment:
-
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.Leave a comment:
-
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 definitionLeave a comment:
-
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.
Leave a comment:
-
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 ariseLeave a comment:
-
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!Leave a comment:
-
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)Leave a comment:
-
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 whyLast edited by Jamo; 10 November 2009, 11:29.Leave a comment:
-
if you do try something out, send me the ini file that you have corrected so i can try it out
i tried looking in the ini files and couldnt find the boostcurve on the text to see what needs to be altered..Leave a comment:
-
I know what the problem is, it's the ini files for the various versions I hadn't noticed that it shows the ini version at the bottom of your project.
The ini for 1.1.27 gives you the correct table but any 1.1.5x or 1.1.6x ini gives the wrong table
I might try some sneaking messingLeave a comment:
-
can you make a photo of the PID boost settings as you have them now?
which ini files did you look up?
i had a look in them trying to find the one that has the boost curve data to change it,but i could not locate it.
did you change anything from the ini files?Last edited by A80Avant; 10 November 2009, 07:42.Leave a comment:
-
I have no idea, ever since I messed with it I was reading the ini files so I open them up closed them the table reads correctly even if I load a blank map with no configuration.
The table shows correctly!!!
I'd have to reinstall from scratch to try and replicate it on a different machineLeave a comment:
Leave a comment: