c4boom

i took all the fuel out out the second ve table in my bin for my 747 and put it in to the ve1 table i did this up to 2800 rpms. now i use tuner pro and win aldl to tune. the way i hav e been tuning is to take the wide correction factor and multipling it to the corisponding cell in ve1. i have not tried this method yet with the fuel all in ve1 will it work and if not how should i tune with the fuel added in. the reason i did this was i ran out of fuel to take out at low rpm's and low loads.

This ad is not displayed to registered members. Register your free account today and become a member on ThirdGen!

c4boom

is there any other information that i could give that would help you guys be able to make a educated decision

Grumpy

VE#2
15 400 rpm
15 800
15 1200
14 1600
13 2000
13 2400
11 2800
11 3200


VE#2 modified
4 400 RPM
4 800
4 1200
3 1600
2 2000
2 2400
0 2800
0 3200


If you subtract 11 from all the values in VE#1, then you can change from the VE#2 to VE#2 modified.


If your asking if #2 is just an adder, then the answer is yes.

It's typically used to maintain the same AFR as the last entry in VE#1 generates. ie slightly leans out the fuel as RPM increases.

c4boom

thank you so i can take all ofe the fuel from under 3200 and add it to the first table the zero out all of the cells under 3200. correct

second will tuning the way that i was still be effective.

Grumpy

I reedited the tables, to include rpm.
As RPM increases, you typically, need less in VE#2

dimented24x7

The best thing to do would be to shuffle the ve between the two tables in order to get the VE adder table to be flat at some constant value up to 3600 rpm. This way you can move some of the VE over to the main table and still have the VE lean out at higher rpms. In addition itll also allow you to easily see what the engines VE curve looks like. To elaborate, lets say the table is the following

VE RPM
25 400
40 800
18 1200
15 1600
30 2000
15 2400
17 2800
14 3200
18 3600
25 4000
23 4400
21 4800
...

Id pick some value that Id want the VE 2 to be, say 20 as an example. Id add and subtract the following from the main VE tables at each rpm and subtract or add to teh values in the above table to get:

VE RPM
20 400, add 5 to main VE
20 800, add 20 to main VE
20 1200, subtract 2 from main VE
.
.
.
20 3600, subtract 2 from main VE

...and Id have to add two to all the
rest of the values after 3600 rpm to
maintain the proper VE after 3600 RPM

25 4000 -> 27 4000
23 4400 -> 25 4400
21 4800 -> 23 4800
etc.

The idea is that there always has to be some VE in the adder table in order to have the VE lean out at high RPMs. If the ve adder table is zero, you cant reduce the VE after youve gone off the edge of the main table.

dimented24x7

I should also say that once youve done this you can leave the second VE table alone below 3600 rpm. Jsut work with the main VE table.

c4boom

this is what i did the first one is my stock ve2 table the second is how i set it up and the one i a questioning
ve rpm
25 0
39.06 400
39.06 800
39.06 1200
39.06 1600
39.06 2000
39.06 2400
39.06 2800
39.06 3200
41.02 3600
35.16 4000
32.03 4400
21.48 4800
17.58 5200
9.77 5600
0 6000
0 6400



now the new one looks like this
ve rpm
25 0
0 400
0 800
0 1200
0 1600
0 2000
0 2400
0 2800
39.06 3200
41.02 3600
35.16 4000
32.03 4400
21.48 4800
17.58 5200
9.77 5600
0 6000
0 6400

dimented24x7

Thats fine. So long as teh last entry at 3600 rpm isnt zero itll be ok.

c4boom

if i take the blms in my log file and devide them all by 128 then take that number that i get and multiply the corisponding cells in ve1 will this still work for tuning or with the larger number that is now in ve1


i am just worid about it swinging the blms back and forth higher and lower than 128

sorry if it seams like i am not listing but i have a hard time grasping this stuff at times

dimented24x7

Yes, you can just multiply the VE in the main table by the blm/128. The only thing is that each time the change made will be smaller then the actual change needed. This isnt a problem and is welcome because it reduces the possibility of overshoot.