-
Thanks Mr. Prick, I'll check that out.
The mystery to me though is I wonder if it is identical to B5913 (High Octane Spark). You can PID both DYNCYLAIR.DMA and CYLAIR.DMA, but with spark you can definitely tell with MAF enabled that CYLAIR determines spark irregardless of what DYNCYLAIR is.
I guess my 'theory' is that with MAF-enabled, Trims come exclusively from MAF (CYLAIR)..same as spark. I don't know whether a PID for B4107 really 'proves' it. It is more of an intuitive observation. Other than doing something ridiculous, like doubling your VE Table and logging Trims..it is hard to know.
Spark values you can log. It is easy to see it follows CYLAIR 100% from MAF when it is enabled. So no 'Airflow correction' affects the load calculation for spark. Maybe it is the same with Trims..
-
Shawn, without going deep into the code, you could pretty safely assume that the references for these tables will be whatever airmass model the pcm is using at that time. Under B0120 the Dyncylair value will be used, over this Cylair will be referenced.
-
Yea, I figured it would be far more complicated than I was assuming. Airmass and fueling would be far more complicated than how the PCM calculates spark load.
Add to it the complexity of LTFT Update Filters, Trim function, etc., it is not as simple as I was stating it.
Suffice to say that is why us MAF-enabled closed-loop guys still put in the work to nail down the VE Table. In simple terms, it would really be cool to have a PID that says, I am using 85% MAF airflow right now, 15% 'SD' right now..I just accelerated now I am using the following percentages.
I know it sounds ridiculous that it could ever be that easy..:grin:
-
If it doesn't twist your brain in a tight knot, then it's no fun at all... :hihi::hihi::hihi::hihi:
-
I've been following this theory from the get go and have been very excited about it. I'm completely new to EFI live as I have been using autotap and tunercats. If you guys can walk me through this, I can do the testing on a stock to-the-air filter 4.8L 2005 Tahoe. I had made a previous log that shawn had looked at to make sure I had the correct PID's selected.
My hurdles:
1. I'm using Tunercats to do the flashing.
2. I need to set up the new CALC PID's which I've never done before (working on that right now...I'm slow ;) ) DONE, that was retardingly simple.......
3. Limited time.
I FINALLY pulled my LM1 from my '96 WS6 so I have something to verify all this with.
Again, I've been following ALL of this and want to contribute.
-
Well, the 'limited time' aspect is about as good as it can get with this method.
You can reasonably tune VE, MAF, and Trims simultaneously.
Unfortunately, in tuning nothing is totally easy..but I think if you can successful log the PIDs, and paste and cut..then you just need some level of computer skills to go from there.
I am not that familiar with 'Tunercats', but anything we can do to help..let us know.
Thanks..
-
OK Guys,
i'm confident I have the PIDS and maps set up correctly. However, I cant select the two WBO2 PIDS as they are not there and probably need to be set up. Is this necessary for the initial log? I thought I could apply the calc PID's to a previous log but that appears to be a no go. I'll have to go for a ride in the truck which I may do tonight, definitely tomorrow. I assume we're using the WBO2 as a sanity check. Can I log and flash. Then log with the WBO2 as a check? Her truck doesnt have a bung for the WBO2 so I'll have to pull an 02 to install it (at the cat???). BTW in Atlanta we have E10 so I have to deal with that next. Tunercats is tunercats, sorta the win95 of tuning :)
-
You can add calc_pids to a log if they're dependent pids are logged and
I suggest setting PE EQ to 1.176 for E10 if you want to run aggressive timing.
I've found the GM.AFR pid to be unreliable at times and gives a different value
to what {B3601} & {B3618} are. :nixweiss:
I made a new calc_pids for commanded AFR ({B3601}/{GM.EQUIVRATIO})
and commanded Lambda: (1/{GM.EQUIVRATIO})
I use WBO2 EQ & Lambda to make a new BEN factors.
There's a spread sheet in my sig to create a new expression for your WBO2.
To find the slope & intercept for {B3601} the lambda min/max must be entered.
If you don't know the Lambda min/max for your WBO2 divide the min/max AFR by the stoich AFR.
-
I noticed the calc pid in the tutorial and the one in shawn's first post are different. The LTFT BEN in the tutorial ends in...)/2/100+1 where as the attached file ends in /200+1. Also for the sake of clarity, should the attached calc pid in the post have "displacement" instead of the actual number(5.669). For newbs to EFI live, shouldnt we make it as easy to cut and paste as possible? Also, I noticed in the tutorial when showing how to do the filtering, the second screen shot shows temp in metric where as the first is imperial.
-
I'm using 1.165 currently, the timing's not too advanced right now. I'm still trying to wrap my head around the E10 tuning and the 2005 OS but lets keep on topic....
