Yes those two maps are quite different.
I'm going to try this with BBL today, I'll post up later.
Printable View
Joe, I like that idea of a manual ECT/IAT blend. Had thought of it before, but could not quite figure out how to introduce the bias factor (unless you use 5.7ute's lookup Temp bias method..you know MAF/DYNAIR flow, etc..).
On the addition of ECT/IAT blend. It took simulating a MAF failure to see the difference. When you log DYNAIR and CYLAIR a .20-.22 difference, does not look like much..but that is a 10% difference.
Because of your previous point(s) on B0120..and if/when you use 4000 Rpms, it tends to take some 'smooth' out some of the LTFTBEN differences vs the direct MAF failure example. You see more of an 5-10% increase in 'VE Values' at 800-2000 Rpm, less as airflow increases.
But, nevertheless it really makes you understand and appreciate that charge temperature weight in the DYNAIR calculation.
Mr. P., We figured out it wanted Liters..I could not get it using CC's.
We may not have communicated that effectively (sorry).
Hopefully Joe will comment on Point #2. That charge Temperature Blending B4901 is a moving target..
It wants Liters...
The term "5.669*61.024" in the equation is a conversion of 5.669L to cubic inches...
61.024 has units ci/L... i.e. it converts Liters to cubic inches.
Here are a few examples of a log showing the effects of DYNAIRTMP on CALC.VE & CALC.VE TABLE.
This was done with MAF FAULTED (SDCL)..
1. Tried to keep ECT the same
2. Very cold IAT's (tried to keep steady).
Whether DYNAIRTMP includes B4902 Charge Temperature Filter..I can not tell. But it follows B4901 quite well..
1. WOT
2. IDLE
3. Cruise
4. DYNAIRTMP AVG
I guess 273.15+IAT+((ECT-IAT)*lookup {B4901} would be the same. :nixweiss:
Yes!
Whether B4901 comes into play..I can not tell. I was looking over some logs to see if DYNAIRTMP changes with the same ECT and rapid change in IAT..but I followed my own advice and picked cold mornings where I kept ECT and IAT steady.
But, I think your statement is correct. I think it must indeed by the 'TMP' that the PCM sees. Maybe that is more important than knowing if other tables come into play??