NefMoto

So I'm doing some logging on my mostly stock bin, only thing I've touched is the necessary parameters to disable VVT since this AWM ECU was used for my wideband swap onto an ATW that doesn't have a VVT solenoid. Car has been running great, making proper boost numbers and not throwing any CEL codes. Did a quick logging run the other night and had a chance to do a third gear pull. Car felt great. When I checked the log to see what things were doing, I noticed my AFR was way more rich than what the LAMFA map should be. Did some digging in the bin and it looks like my AFR was following the KFLBTS map. Looked at my EGT calc and it shows that it barely hits 800*c, which is below what is set in TABGBTS. Is there something else going on that would cause the use of KFLBTS over LAMFA? Want to get this figured out before I start trying to add fueling to LAMFA and proceeding with the rest of tuning. As it is, with my car using KFLBTS, my injector duty cycle is pretty much maxed out.

Do I need to change anything in the CWLAMFAW, DLAMFAW, TABGBTS, or CWLAMBTS parameters?

Attaching my bin, xdf i'm using and log (3rd gear pull from 2k to ~7k is towards the end of the log, should pull up fine in the ecuxplot filter) can't post my log, so here is a .png

IAT? Knock? Did you actually check if its lambts , how does KFLBTS look etc. Post the log... what is stopping you?

Every time I try to post the log, the forum says my post attempt timed out. I'll try to post it again after work. Might be the file is too big? Is there a way to trim the log to just the important part? I started the log when I left work and it's about ten minutes worth of driving time.

Make a smaller one on a flat piece of road - start it when you are about to do it or if you need to start it before engine on then pull over I guess, tho the max file size is like 28MB is it over that?

Set KFLBTS table to something normal, make it that your lowest value to about 11 AFR.
Tune BTS for you AFR not LAMFA(set LAMFA to somehing like 12.5-13 AFR) , sometimes you will go uphill in summer days, with 70% throotle, than is good that BTS kick in to cool engine. If you set BTS threshold too high in that situation you can melt engine

No idea why it won't let me post this as normal. It is only 11mb  ???
Here it is zipped.
Did another logging run last night, and didn't see the same behavior. Looking at my log from the first night I thought it was KFLBTS because the AFR matched that map perfectly at the load points.

Jeez just take smaller logs, you can pull over to start and pull over to stop the logger.

Yeah, may have been a little over ambitious with logging. Will take smaller ones in the future. Still learning the process, want to make sure I know what I'm doing before I start really changing parameters.

didn't look at your log yet but i hope you're logging lamfa_w, lamfawkr, and lambts

not sure why you didn't post pictures of them

It really looks like its triggering at 670C ish

That's what it looked like to me. I did not see this when I did my run last night, but I'm going to keep logging for a little while and learn more about how all of these things work together. Adding lamfawkr_w and lambts_w to my future logs as well. Thought I had them, must not have saved the profile.
Tabgbts is set for 839.99*c, are there other things that would trigger this?

not that i know of but i'm used to me7.1 not 7.5

Hmmmmm, I looked at what LAMFAW was doing in that log, and it's just a flat line and all of the numerical fields on the y axis are gibberish. Compared that to my newest log where LAMFAW was behaving normally. Something else is probably going on that corrupted that signal I think. Gonna keep at it like I said and keep an eye out for weirdness. Thanks for taking a look.

Check this out
http://nefariousmotorsports.com/forum/index.php?topic=19682.msg147013#msg147013

My 512kb ecu (non turbo) has KFLBTS disabled only runs lamfa, its not a 512kb ME7.5 thing, maybe 1.8t 512kb. Check the codewords though.

Thank you both! I'll take a deeper look at this on a day I'm not working a double, but I think this sets me on the right path. Interesting that it seems like there's a few stock files that use BTS regardless of egts.

I've read that tuning that map has better resolution than LAMFA, but is not as newbie friendly. Honestly though, seeing as that one is load and rpm based, rather than throttle position based, it does seem like the better option. Only downside seems to be losing high egt component protection.  If I'm not planning on going any bigger than a k04, how realistic is it that I'll see egts get high enough to worry about? Seems to me I'll run into knock issues before that ever happens.

Figured it out! CWLAMBTS had bit 2 set to use tabgkrm_w for EGT temperature, which uses a different calculation for EGT temps and pays no attention to what is set in TABGBTS. I zeroed out the bit and now the ECU follows LAMFA just fine. Thanks for the help folks, led me to look in the right places.

I dont see a good reason to do it this way, honestly, other than just for getting a finer understanding of the lambda request path.

Why not just BTS and LAMFA in concert? There is no good reason to keep BTS disabled for so much.

From what I understand on the way it was worded, this isn't disabling BTS, just changing which calculation it uses/follows for EGTs. When it was following tabgkrm, it was switching to BTS fueling a lot earlier. Now it sticks to LAMFA until EGTs hit my actual specified temp set in TABGBTS.

There is no reason to delay BTS, really, especially if the stock file doesn't delay it.