03-26-2015, 01:08 PM | #1 |
Speed Density Vs. MAF / Pros and Cons.
Those who have actually switched over to SD, what are your thoughts ?
__________________
|
|
03-26-2015, 01:33 PM | #2 |
Geek
|
There should be very little difference assuming you have a good MAF+VE tune already. If you are running MAF only, then there are improvements to be made by getting the VE table done. You might as well keep it as a hybrid tune if you aren't flowing more air than your MAF sensor can measure. The MAF sensor is better for calculating airflow at more constant rates and the VE table is better for calculating airflow during transient conditions.
__________________
01000111011011110110111101100100001000000110110001 11010101100011011010110010000001110111011010010111 01000110100000100000011101000110100001101001011100 110010000001101111011011100110010100100001
x = ac97968bd3df8f968c8cd3df998a9c94d3df9c8a918bd3df9c 909c94df8c8a9c949a8dd3df92908b979a8ddf998a9c949a8d d3df8b968b8cd1 x = ~x |
03-26-2015, 02:35 PM | #3 | |
Quote:
__________________
|
||
03-26-2015, 03:04 PM | #4 | |
Geek
|
Quote:
The car seems to be more responsive to quick throttle changes with a good VE table. Although to be completely honest, it runs pretty well MAF only. The "VE table" doesn't really exist in a stock E38 ECM just fyi. You will have to use EQ<>VE to import the VVE coefficients and generate a table that you can modify with log data. Then you have to use the same tool to export the coefficients back to HP Tuners. It's a huge pain in the ass. You have to do it every time you re-log the vehicle and apply new data to the tune file, which will be a million times since you're just getting started! I would recommend you put in a little time up front getting the 2.5 bar custom OS working with your vehicle. The VE table will be all zeros in the custom OS. You will need to generate starting values with EQ<>VE from the VVE coefficients in your current tune. You will also need to input the correct values for your MAP sensor in the "Engine Diag" section. You will also need to edit the axis of the VE tables in the custom OS to make use of the increased 33x33 cell resolution table. When you enter the existing VE data into your custom OS table, you will have an empty square between every cell since it came from a 1/2 resolution table. You will have to interpolate the table top to bottom and left to right to get it filled all the way in. Then you're ready to start calibrating the VE and MAF airflow tables. You may have to start in closed loop and make a quick pass using fuel trims and part throttle, easy driving. All final calibrating should be done in open loop with your wideband. Good luck!
__________________
01000111011011110110111101100100001000000110110001 11010101100011011010110010000001110111011010010111 01000110100000100000011101000110100001101001011100 110010000001101111011011100110010100100001
x = ac97968bd3df8f968c8cd3df998a9c94d3df9c8a918bd3df9c 909c94df8c8a9c949a8dd3df92908b979a8ddf998a9c949a8d d3df8b968b8cd1 x = ~x |
|
03-26-2015, 05:48 PM | #5 | |
Quote:
If I attempt the VE / map tune can I use the ZL1 3bar map with the 2.5 bar os? Thanks again!
__________________
|
||
03-26-2015, 09:53 PM | #6 |
Drives: 2SS RS ABM A6 Join Date: Jun 2010
Location: Pahrump, NV
Posts: 273
|
GM VE is a value calculated from numerous PIDs. etc. You can log GMVE in the HP Tuners VCM Scanner software, MAP kPa vs. RPM.
This way, you get VE numbers that are spot-on with what the car's computer is calculating. Once you get as many as you can, you extrapolate/interpolate the rest, then use the BlueCat tool to build the equations for the table data. One of the experts on the HP Tuners forum gave me the explanation of the pros/cons of each. To condense, the car is far more drive-able below 4000 RPM w/ both VVE+MAF feeding the computer.
__________________
Jack Bilger
|
03-26-2015, 10:40 PM | #7 |
Drives: Pontiac G8GT Join Date: Feb 2010
Location: Southern California
Posts: 14
|
Is all theory until you've tried it
But you can run MAF only with a good tune, and you'll never notice the lack of the SD, post#2 summarized it very nicely. SD mode with E38's kind of suck because we have to use the dang SD calc to build the table, if you're used to the E40 pcm's, you'll know exactly what I'm talking about, the calc does the job, I just wish I had better control of the zones. Thahemp, for your lean spikes during tip-in (I believe GM does this on purpose for emissions purposes), try adjusting the transient enable delay from 56 crank references to 15, and then the impact factor/maximum mass from 2048 to 1024. also make sure your part throttle fuel in CL is within -+2%, you should not have any more lean spikes, in fact, watch your WOT fueling during the initial hit, if you go too rich in one shot, add 100 at a time to the maximum mass, but 1024 should be about right. this works for LS2's, L76's, LS7's etc, even the trucks, my 2010 5.3L Silverado Crew cab runs great with this settings. The VE is not referenced if the dynamic airflow high rpm disable/re-enable is set correctly, but you can always check your dynamic airflow status bit, high means MAF only, VE is not referenced http://www.hptuners.com/forum/showth...-Calc-Mode-PID
__________________
2012 Mustang GT, M6, 3.73's, Base/Brembo Package
3" H Pipe/Stock cats, Res!/3" pipes, Magnaflow 14419's AB, UPR Catch Can HPTuners Pro v2.25 | Street Tuned |
03-27-2015, 05:47 AM | #8 | |
Quote:
__________________
|
||
03-27-2015, 05:50 AM | #9 | |
Quote:
Lol. Agree completely with the first sentence. Looking forward to it. My brain hurts from all this theory.
__________________
|
||
03-27-2015, 09:40 AM | #10 | |
Geek
|
Quote:
Jpb972 I don't have a boosted car and have never tuned one, so I won't even start to pretend to know what to do with your different MAP setup. Best advice I can give you is to take it slow and be gentle with the throttle until your confidence catches up to your tune changes. All theory till you try it is 1000% the truth. Half the time it doesn't matter a bit what someone else says will work.
__________________
01000111011011110110111101100100001000000110110001 11010101100011011010110010000001110111011010010111 01000110100000100000011101000110100001101001011100 110010000001101111011011100110010100100001
x = ac97968bd3df8f968c8cd3df998a9c94d3df9c8a918bd3df9c 909c94df8c8a9c949a8dd3df92908b979a8ddf998a9c949a8d d3df8b968b8cd1 x = ~x |
|
03-27-2015, 11:28 AM | #11 | |
::
Quote:
__________________
|
||
|
|
|
|