Yes, the pid SAE.FUELSYS gives OL/CL for each bank... and it takes up 2 pid channels... we're looking for something that takes up 1 pid channel (or less) and is bank-less.
Yes, the pid SAE.FUELSYS gives OL/CL for each bank... and it takes up 2 pid channels... we're looking for something that takes up 1 pid channel (or less) and is bank-less.
Last edited by joecar; June 3rd, 2011 at 06:17 AM.
Yes, we were thinking of renaming CALC.PE to CALC.OL or CALC.CL (and then rippling this thru the tutorial(s)).
Is this (Fuel Loop Status) what you were thinking of?
That would work great - but which is the low bit, and which is the high bit?! I'm starting to get a little critical of the documentation!!!
The value we are after is "Fuel Trim Learn" - but is that bit #3, or bit #6?
Actually, DFCO and Fuel Loop Status would be handy as well, you could craft some really trick logic knowing those three values; i.e. "when fuel trim learn is enabled, and decel fuel cutoff is inactive, and fuel loop status is closed - then use TRIMS, else use WB02" or something like that. ???
Or just K.I.S.S. and use TRIMS when EQR = 1.00 and MAP between 40 and 85, or some such thinking.....
Mr. P.
Last edited by Mr. P.; June 3rd, 2011 at 05:08 AM.
2003 Silverado SS, with Novi-1500 "CAI mod"
EFILive V 7.5 COS-3 (OLSD, for now!)
When I look at my logs, Fuel Loop Status seems to lock at CL once warm up is achieved...Originally Posted by Ninety8C5
Is this (Fuel Loop Status) what you were thinking of?
I see that when SAE.FUELSYS indicates OL on banks A and B, Fuel Loop Status still indicates CL.
The bits are numbered starting at zero from the bottom and going up...
see here:
No, not Fuel Trim Learn, this indicates when trims are being learned or not, it goes on and off during Closed Loop.
Yes, those would be very very handy, but:
- DFCO does not seem to work, the bit is always off,
- Fuel Loop Status reads OL during warm up and then reads CL always after that;
keep in mind that it is the PCM that is not filling in these bits.
Yes I agree, that is how we arrived at the CALC.PE pid (altho we misnamed it).
The only other brainstorm I had was to use an 'iff' for the PE Enabler Tables (via look-up).
I.E., iff RPM & TPS% this..then..
Every other solution is a lot of work. Remember, we just want to know if LTFT's are active.
You can always default LTFT's to 1.00 and use WO2BENS for the entire practice.
We may be stuck with a 'stupid', but easy solution as is..
Question is, how does the PCM determine when it is in PE Mode?
The PCM has the advantage that it knows what it is doing and we do not...
us -><- PCM
altho, the 411 PCM is way simpler/easier than the E38/E67 and others.
We can safely say that when GM.EQIVRATIO is not 1.00 then fuel mode is Open Loop...
there are a few exceptions to this, but when EQR is not 1.00 then trimming cannot proceed.
We could define either of these:
- CALC.OL = "{GM.EQIVRATIO} != 1"
- CALC.CL = "{GM.EQIVRATIO} == 1"
whichever one reads more better/correctly (I like the first on better);
then we would use this as the condition in the SELBEN iff.
There is a PE/enrichment bit in one of the TSTATE pids, it appears to not correspond to actual PE active... I meant to log this some more;
(and what is it doing in a transmission TSTATE pid).
Posting Permissions
Reply With Quote
