Where's the 2 Bar SD OS for the 98 PCM?
03-22-2006, 12:36 PM
#24
TECH Fanatic
iTrader: (6)
Join Date: Jan 2002
Location: Springfield, IL
Posts: 1,194
Likes: 0
Received 0 Likes
on
0 Posts
Originally Posted by Billiumss
Once we get all our ducks in a row, it should be very interesting to get this to work. Hopefully when I use the VE AFR Histogram in my HP Tuner scanner, it will be as easy as: scan, cut, and paste in the Main & Secondary VE tables.
Or is the value splitting more correlated to the actual VE values themselves?
03-22-2006, 12:48 PM
#25
TECH Senior Member
You're basically halving your resolution...
to use the 2 bar you'll be using the secondary VE on a 98
secondary VE is 10kpa resolution
So w/2 bar w/out an OS enhancement, it now becomes 20kpa resolution
so 50kpa reported would need to be tuned for 100kpa actual
to use the 2 bar you'll be using the secondary VE on a 98
secondary VE is 10kpa resolution
So w/2 bar w/out an OS enhancement, it now becomes 20kpa resolution
so 50kpa reported would need to be tuned for 100kpa actual
03-22-2006, 01:36 PM
#27
TECH Fanatic
iTrader: (6)
Join Date: Jan 2002
Location: Springfield, IL
Posts: 1,194
Likes: 0
Received 0 Likes
on
0 Posts
Originally Posted by horist
You're basically halving your resolution...
to use the 2 bar you'll be using the secondary VE on a 98
secondary VE is 10kpa resolution
So w/2 bar w/out an OS enhancement, it now becomes 20kpa resolution
so 50kpa reported would need to be tuned for 100kpa actual
to use the 2 bar you'll be using the secondary VE on a 98
secondary VE is 10kpa resolution
So w/2 bar w/out an OS enhancement, it now becomes 20kpa resolution
so 50kpa reported would need to be tuned for 100kpa actual
03-22-2006, 01:56 PM
#28
TECH Senior Member
yup... but keep in mind you have to do this at any table VE is referenced... not sure about the load values (If they're calculated off of the MAP value, so may have to half the resolution of spark tables and such too)
03-22-2006, 02:06 PM
#29
10 Second Club
iTrader: (80)
Join Date: Sep 2002
Location: Reynoldsburg, Ohio
Posts: 812
Likes: 0
Received 0 Likes
on
0 Posts
Unfortunately we're at a loss for tuning, unlike our 99+ bretheren.
You may not like the idea, but from what people are proving with their '98s, it's working and providing a fine solution for the time being.
Shall I show you what years of 10:1 A/F due to a maxed MAF does to pistons?
You may not like the idea, but from what people are proving with their '98s, it's working and providing a fine solution for the time being.
Shall I show you what years of 10:1 A/F due to a maxed MAF does to pistons?
maybe reading it another 10 times ill make more sense of it 
03-22-2006, 02:42 PM
#31
TECH Fanatic
iTrader: (6)
Join Date: Jan 2002
Location: Springfield, IL
Posts: 1,194
Likes: 0
Received 0 Likes
on
0 Posts
Originally Posted by horist
yup... but keep in mind you have to do this at any table VE is referenced... not sure about the load values (If they're calculated off of the MAP value, so may have to half the resolution of spark tables and such too)
DarkFormula - If you drove around for years on a 10:1 A:F ratio, you've got bigger problems than your cylinder walls.
03-22-2006, 02:45 PM
#32
TECH Fanatic
iTrader: (6)
Join Date: Jan 2002
Location: Springfield, IL
Posts: 1,194
Likes: 0
Received 0 Likes
on
0 Posts
ninobrn- This might help it make sense... Basic Speed density tuning (for forced induction apps) is done through an extended range of MAP readings (thanks to the 2-bar sensor) which read higher than the stock sensor can read. Stock sensors read from about 15kPa to 105kPa. 2-bar sensors read from 15kPa to about 200kPa, or whatever ~14psi is. So in the tuning program, instead of your VE table going from 15kPa to 105kPa, it goes from 15kPa to 200kPa, with larger steps in between each MAP range.
