To tune part throttle to 14.7 afr
06-27-2001, 07:34 PM
#1
Junior Member
Thread Starter
Join Date: Jan 2000
Location: Mississauga, Ontario, Canada
Posts: 44
Likes: 0
Received 0 Likes
on
0 Posts
To tune part throttle to 14.7 afr
Would you suggest doing this on a dyno, in the driveway or on the street?
I think the idea is to hook up my ease scanning software to the motor and then try to run the motor at each rpm level for 30? seconds and trap the values in the scan tool for later analysis.
Is this correct?
dave
I think the idea is to hook up my ease scanning software to the motor and then try to run the motor at each rpm level for 30? seconds and trap the values in the scan tool for later analysis.
Is this correct?
dave
06-27-2001, 07:38 PM
#2
Supreme Member
Join Date: Jun 2000
Location: In reality
Posts: 7,554
Likes: 0
Received 1 Like
on
1 Post
Car: An Ol Buick
Engine: Vsick
Transmission: Janis Tranny Yank Converter
<font face="Verdana, Arial" size="2">Originally posted by mmaker:
Would you suggest doing this on a dyno, in the driveway or on the street?
I think the idea is to hook up my ease scanning software to the motor and then try to run the motor at each rpm level for 30? seconds and trap the values in the scan tool for later analysis.
Is this correct?
dave</font>
Would you suggest doing this on a dyno, in the driveway or on the street?
I think the idea is to hook up my ease scanning software to the motor and then try to run the motor at each rpm level for 30? seconds and trap the values in the scan tool for later analysis.
Is this correct?
dave</font>
You also, have to let things stabilize for several MINUTES for temps to stabilize to get accurate info..
06-27-2001, 07:38 PM
#3
TGO Supporter
Join Date: Jul 1999
Location: The Bone Yard
Posts: 10,907
Likes: 0
Received 3 Likes
on
3 Posts
Car: Death Mobile
Engine: 666 c.i.
I just took some nice long drives on a variety of roads (nice and hilly). This is with capturing all the scan data and then sorting the captured data based on RPM/MAP/INT (I locked my min/max BLM to 128) and relied on the INT for determining whether I was too lean or too rich at various RPMS/MAP readings.
06-27-2001, 07:50 PM
#4
Junior Member
Thread Starter
Join Date: Jan 2000
Location: Mississauga, Ontario, Canada
Posts: 44
Likes: 0
Received 0 Likes
on
0 Posts
<font face="Verdana, Arial" size="2">Originally posted by Glenn91L98GTA:
(I locked my min/max BLM to 128) and relied on the INT for determining whether I was too lean or too rich at various RPMS/MAP readings.</font>
(I locked my min/max BLM to 128) and relied on the INT for determining whether I was too lean or too rich at various RPMS/MAP readings.</font>
Did you lock the blm to 128 via the constants table?
dave
06-27-2001, 08:30 PM
#5
TGO Supporter
Join Date: Jul 1999
Location: The Bone Yard
Posts: 10,907
Likes: 0
Received 3 Likes
on
3 Posts
Car: Death Mobile
Engine: 666 c.i.
Yes, just change the Maximum BLM Value and Minimum BLM Value to 128. Then your INT will only vary.
BUT, you do need some reasonable BLM vaues (having minimums in the 108 range or maximums in the 160 range is too far out). Too rich or lean of a table will result in an O2 sensor error (rich or lean) when you lock the BLM values to 128...but then you know you will be having to make a large rate of change.
I found changing the VE table entries by .23 for each variation from 128 gave reasonable results. Example: At 2,000 rpm @ 40 Kpa I had an average INT Value of 115. (Average is a function of Excel) The calculation for the adjustment to the VE table entry is (INT - 128) x .23. Or, (115-128)x.23 = -2.99. Just change the VE table entry at 2,000 rpm/40 Kpa by subtracting 3. Don't worry about the "precise" -2.99 value as the VE table can only be changed in increments of .4 from the origal VE Table value. After the -3 adjustment, you may find the "actual" VE value changed from 2.8 to 3.2 when you "refresh/re-read" the VE Table.
I found the first pass (changing the VE table) got me INT values in the 120 to 138. Doing the same test a second time got me INT Values in the 125-134 range. I then unlocked the BLM (set min/max to 108/160 again). This resulted in BLMs from 126-132 range. You can continue to try to make changes, but you get caught with the minimum change increment of .4 to any VE table entry...after that, you are getting "****". (Or so my wife says).
[This message has been edited by Glenn91L98GTA (edited June 27, 2001).]
BUT, you do need some reasonable BLM vaues (having minimums in the 108 range or maximums in the 160 range is too far out). Too rich or lean of a table will result in an O2 sensor error (rich or lean) when you lock the BLM values to 128...but then you know you will be having to make a large rate of change.
I found changing the VE table entries by .23 for each variation from 128 gave reasonable results. Example: At 2,000 rpm @ 40 Kpa I had an average INT Value of 115. (Average is a function of Excel) The calculation for the adjustment to the VE table entry is (INT - 128) x .23. Or, (115-128)x.23 = -2.99. Just change the VE table entry at 2,000 rpm/40 Kpa by subtracting 3. Don't worry about the "precise" -2.99 value as the VE table can only be changed in increments of .4 from the origal VE Table value. After the -3 adjustment, you may find the "actual" VE value changed from 2.8 to 3.2 when you "refresh/re-read" the VE Table.
I found the first pass (changing the VE table) got me INT values in the 120 to 138. Doing the same test a second time got me INT Values in the 125-134 range. I then unlocked the BLM (set min/max to 108/160 again). This resulted in BLMs from 126-132 range. You can continue to try to make changes, but you get caught with the minimum change increment of .4 to any VE table entry...after that, you are getting "****". (Or so my wife says).
[This message has been edited by Glenn91L98GTA (edited June 27, 2001).]
07-02-2001, 09:50 AM
#6
Supreme Member
Join Date: Jul 2000
Posts: 1,445
Likes: 0
Received 0 Likes
on
0 Posts
I do the same as Glen but use RPM/MAP/BLM or RPM/MAP/BLM/INT as the sort as I couldn't lock the BLM because my BLM's were off too far from all of the config changes I made/make. Good stuff, man. Then, when you get BLM's close after a couple iterations, you lock the BLM to fine tune with the INT
07-03-2001, 12:11 PM
#7
Junior Member
Thread Starter
Join Date: Jan 2000
Location: Mississauga, Ontario, Canada
Posts: 44
Likes: 0
Received 0 Likes
on
0 Posts
<font face="Verdana, Arial" size="2">Originally posted by FastBroker:
I do the same as Glen but use RPM/MAP/BLM or RPM/MAP/BLM/INT as the sort as I couldn't lock the BLM because my BLM's were off too far from all of the config changes I made/make. Good stuff, man. Then, when you get BLM's close after a couple iterations, you lock the BLM to fine tune with the INT</font>
I do the same as Glen but use RPM/MAP/BLM or RPM/MAP/BLM/INT as the sort as I couldn't lock the BLM because my BLM's were off too far from all of the config changes I made/make. Good stuff, man. Then, when you get BLM's close after a couple iterations, you lock the BLM to fine tune with the INT</font>
Excellent info people...thanks for the responses!
dave
Thread
Thread Starter
Forum
Replies
Last Post
