Quote:
fueling is static in open loop modes, the only thing that is constantly adjusted for temperature and MAP input is the ignition advance/retard
slowolej wrote:Quote:
fueling is static in open loop modes, the only thing that is constantly adjusted for temperature and MAP input is the ignition advance/retard
Huh??
This would be a first. Although "constantly adjusted" may be the point of misunderstanding, as long as the ecm is in open loop it will be delivering fuel based on desired afr vs temp, or a desired afr times a temp based multiplier. Imagine how difficult it would be to try and drive a car with a cold engine and IAT's at -30 deg F if the AFR were 14.7:1!
-->Slow
BlackEco wrote:slowolej wrote:Quote:
fueling is static in open loop modes, the only thing that is constantly adjusted for temperature and MAP input is the ignition advance/retard
Huh??
This would be a first. Although "constantly adjusted" may be the point of misunderstanding, as long as the ecm is in open loop it will be delivering fuel based on desired afr vs temp, or a desired afr times a temp based multiplier. Imagine how difficult it would be to try and drive a car with a cold engine and IAT's at -30 deg F if the AFR were 14.7:1!
-->Slow
You are mistaken, the computer only uses IAT and MAP sensors for fuel adjustment in Closed Loop mode. The car will run open loop when it is cold, which is why it will run richer and get worse fuel economy (more common during winter) It also runs in Open Loop during Power Enrich (PE) Mode.
slowolej wrote:Quote:
fueling is static in open loop modes, the only thing that is constantly adjusted for temperature and MAP input is the ignition advance/retard
Huh??
This would be a first. Although "constantly adjusted" may be the point of misunderstanding, as long as the ecm is in open loop it will be delivering fuel based on desired afr vs temp, or a desired afr times a temp based multiplier. Imagine how difficult it would be to try and drive a car with a cold engine and IAT's at -30 deg F if the AFR were 14.7:1!
-->Slow
DaFlyinSkwir(LS61) /PJ/ OEM+ wrote:
I'm sorry but I've never heard of that.
My understanding of the Jbody ecu is that In open loop, the ecu ignores other sensors, and delivers fuel based on the VE maps. It figures out the targeted AFR via the AFR vs ECT map (which is very broad in its definitions, and at op temp wants 13:1 AFR). There is a multiplier based on RPM which is all 1s, rendering it useless. There is also an injector pulsewidth multiplier that is based on MAP, which I'd imagine takes into consideration elevation and air temperature changes.
other than these tables, nothing effects fueling. There is an ECT startup vs closed loop ECT which the ecu looks at the startup ECT, and is then told what ECT it can begin to run for stoich.
Anything in relation to startup is not seen by HPT.
Anything in relation to closed loop fueling is not seen by HPT.
The only maps with IAT as a reference control spark advance.
Does that mean IAT doesn't have a multiplier attached to it that effects pulsewidth? not necessarily, but its null because it cannot be edited in HPT.
Quote:
But if there IS a multiplier for IAT in open loop, than temperature (density) changes will be compensated for, even if running off the VE maps. Or am I misunderstanding?
DaFlyinSkwir(LS61) /PJ/ OEM+ wrote:
I'm sorry but I've never heard of that.
My understanding of the Jbody ecu is that In open loop, the ecu ignores other sensors, and delivers fuel based on the VE maps.
DaFlyinSkwir(LS61) /PJ/ OEM+ wrote: It figures out the targeted AFR via the AFR vs ECT map (which is very broad in its definitions, and at op temp wants 13:1 AFR).
DaFlyinSkwir(LS61) /PJ/ OEM+ wrote: There is a multiplier based on RPM which is all 1s, rendering it useless.
DaFlyinSkwir(LS61) /PJ/ OEM+ wrote: There is also an injector pulsewidth multiplier that is based on MAP, which I'd imagine takes into consideration elevation and air temperature changes.
DaFlyinSkwir(LS61) /PJ/ OEM+ wrote: other than these tables, nothing effects fueling. There is an ECT startup vs closed loop ECT which the ecu looks at the startup ECT, and is then told what ECT it can begin to run for stoich.
Anything in relation to startup is not seen by HPT.
Anything in relation to closed loop fueling is not seen by HPT.
The only maps with IAT as a reference control spark advance.
Does that mean IAT doesn't have a multiplier attached to it that effects pulsewidth? not necessarily, but its null because it cannot be edited in HPT.
we can only really control when and if the ecu goes into closed loop. Everything we can edit (fueling wise) is open loop related.. other than multipliers.
oldskool wrote:Pertains to 2004 eco cavalier. In open loop or PE modes, does the ECU adjust the fuel for the temperature it sees with the IAT sensor? Or is the fueling in these modes totally static?
protomec wrote:DaFlyinSkwir(LS61) /PJ/ OEM+ wrote:
I'm sorry but I've never heard of that.
My understanding of the Jbody ecu is that In open loop, the ecu ignores other sensors, and delivers fuel based on the VE maps.
Actually it only ignores one sensor, the oxygen sensor. It very definitely pays close attention to all the others... exactly the same as it does all the time.
DaFlyinSkwir(LS61) /PJ/ OEM+ wrote: It figures out the targeted AFR via the AFR vs ECT map (which is very broad in its definitions, and at op temp wants 13:1 AFR).
No, it reads the target AFR from the AFR vs ECT map. It figures out how much fuel to spray to achieve it by calculating the mass of the air injested for that event. It calculates the mass of the air using the VE % it looks up for that operating point and the air temperature to know the density of that air. Cold air is more dense and has a higher mass than hot air.
DaFlyinSkwir(LS61) /PJ/ OEM+ wrote: There is a multiplier based on RPM which is all 1s, rendering it useless.
It means the table is not used for that application and is "zero'ed out" from a function standpoint so it does not affect that calibration. There are instances when you would want it changed. One such reason would be to not go boost rich with a large turbo that cannot spool down low where there is no reason to run 10.5:1 if no boost is possible. Sometimes engines respond very well to slightly different AFRs at different RPMs.
DaFlyinSkwir(LS61) /PJ/ OEM+ wrote: There is also an injector pulsewidth multiplier that is based on MAP, which I'd imagine takes into consideration elevation and air temperature changes.
Not at all. 1st issue with that statement is how would it know temperature from a MAP reading?
The IPW function is used on cars with returnless fuel or where the fuel regulator is not referenced to intake manifold pressure.
If fuel pressure is constant, a 3ms spray into a -20inhg manifold pressure (as in idle) will spray much more fuel than the same 3ms into 0inhg (WOT). With a vacuum referenced regulator, the fuel pressure delta is constant (the pressure difference between the rain and the tip). The IPW table is like an electronic version of a vacuum referenced regulator. And for the record, as delivered from GM, ECOs are not manifold vacuum referenced.
DaFlyinSkwir(LS61) /PJ/ OEM+ wrote: other than these tables, nothing effects fueling. There is an ECT startup vs closed loop ECT which the ecu looks at the startup ECT, and is then told what ECT it can begin to run for stoich.
Anything in relation to startup is not seen by HPT.
Anything in relation to closed loop fueling is not seen by HPT.
The only maps with IAT as a reference control spark advance.
Does that mean IAT doesn't have a multiplier attached to it that effects pulsewidth? not necessarily, but its null because it cannot be edited in HPT.
we can only really control when and if the ecu goes into closed loop. Everything we can edit (fueling wise) is open loop related.. other than multipliers.
Just because you can't edit it does not mean you should simply ignore its influence.
protomec wrote:Back on to the original question...
oldskool wrote:Pertains to 2004 eco cavalier. In open loop or PE modes, does the ECU adjust the fuel for the temperature it sees with the IAT sensor? Or is the fueling in these modes totally static?
Yes it does. The fueling is not static.
John Higgins wrote:Well I disagree. I'm by no means a pro at tuning, and most of the ones in this post know more than I do in that field. I have seen a major difference in my AFR's between Winter and Summer.
oldskool wrote:John Higgins wrote:Well I disagree. I'm by no means a pro at tuning, and most of the ones in this post know more than I do in that field. I have seen a major difference in my AFR's between Winter and Summer.
That's why I'm asking. Is your experience on a boosted application, n/a, or both? I mean, under what conditions did you see the difference?
John Higgins wrote:oldskool wrote:John Higgins wrote:Well I disagree. I'm by no means a pro at tuning, and most of the ones in this post know more than I do in that field. I have seen a major difference in my AFR's between Winter and Summer.
That's why I'm asking. Is your experience on a boosted application, n/a, or both? I mean, under what conditions did you see the difference?
Actually both. My personal 01 Z24 n/a, and a 99 z24 with GM charger. The 99 I expected it because it is a Alpa N program running boost. as the weather changes so does the boost, which then requires a new tune.
My 01 has seen the same, but not as drastic, more than liveable as well. Most would probably never know it. I'm still ok with it because I have the program and wideband to change it, and really I'm always tweaking it anyways.
oldskool wrote:John Higgins wrote:oldskool wrote:John Higgins wrote:Well I disagree. I'm by no means a pro at tuning, and most of the ones in this post know more than I do in that field. I have seen a major difference in my AFR's between Winter and Summer.
That's why I'm asking. Is your experience on a boosted application, n/a, or both? I mean, under what conditions did you see the difference?
Actually both. My personal 01 Z24 n/a, and a 99 z24 with GM charger. The 99 I expected it because it is a Alpa N program running boost. as the weather changes so does the boost, which then requires a new tune.
My 01 has seen the same, but not as drastic, more than liveable as well. Most would probably never know it. I'm still ok with it because I have the program and wideband to change it, and really I'm always tweaking it anyways.
Yea, i figured it would probably be worse with boosted apps and alpha-n. So when you say "most would probably never know it" what does that mean? What differences in AFR did you notice from season to season. As long as it can maintain +/- 0.2 AFR between seasons, I'm quite happy with that.