[nhra no 2]

First off I have been TwEECe-ing for about 3 years now, and I am perplexed. I have a twin turbo on my 306, EEC is GUFB-A9L, I am tuning with BE. I have been chasing a problem all spring. I thought it was a turbo problem, like a bad hose connection or a blow off valve leak. But tonight I found out that is not the case. Here is what happens, I can roll into the throttle with no problems, but if I floor it nothing. I mean nothing, it is as though the key has been turned off. I let out of the throttle, and the engine comes right back to life. I have a data log of me flooring it and then letting back off, and flooring it again. It looks like no fuel is being commanded, both hego's drop to 0 volts, and wide band shows full lean. Also both lambse 1&2 show high 24 to 25. I also grounded out the MIL connector to check trouble codes. I got 34, 85 & 96 KOEO, and 66, 96 continuous codes. I have the EGR type (PFEHP) set to disabled(code 34). I had fuel adaptive control (Z_ADPSW) set to enabled(code 85), I have now turned it off as I am running in OL. The MAF min (MINAM)(code 66) I had it @0.25 volt, this is my lowest value in my MAF transfer. I now have it @0.1 volt. Oh and that code 96, I have gotten that code for as long as I have owner my Mustang (17 years). I have never been able to stop that code from being set???

I am kind of lost as to what is letting the EEC think it should shut off fuel to the engine. I thought it was also my ignition box, but the EEC would be sending fuel, and just go pig rich. So I think it is not ignition.

I have a data log, and my calibration for anyone to look at.

2010_May_19_20-58-52.csv

2010_May_19_20-58-52.csv

[eric]

fn325 maybe? I believe the values you have there would greatly decrease fueling.

[nhra no 2]

I have the same variables in FN325 as the stock GUFB-A9L. As for how this would reduce fuel, can give give me an explanation? Or at least some numbers to try out?

[eric]

I was hoping one of the resident experts would finish this topic off. I compared your tune to a stock a9l and noticed that fn1360 was enabled. Here is a link viewtopic.php?f=2&t=13862&hilit=fn1360 . I believe you would want to start with 1.0's in FN325. You could later set up the temp scaling to change a/f based on ect.

[decipha]

your fueling is all over the place!

[nhra no 2]

Yes, I know my fuel is all over the place. That is what I am trying to figure out. I was looking over my log at lunch today, and I did notice that when ever my TPS voltage went over 3.2 volts is when my fueling shuts off. My log still shows TPS voltage when it is higher than 3.2 volts, so I don't think my TPS is bad. But for now that is the only trend I see that repeats when the PW's and LAMBSE's values tank. I am still lost.

[decipha]

ah ha found the problem, you screwed up on your scaling

at wot your demanding 24 afr which is pretty much no fuel

delete your bin and start a new one this time keep it basic, your doing too much at one time, keep it simple then go from there

only thing you need to do is slap in your maf transfer injector settings max airflow clip and disable egr, smog, & canister, adjust the fuel and spark tables

[nhra no 2]

Exactly were did I screw up? I would like to know what was wrong so I can see for myself. Right now as I am typing this I have the engine warming up with a brand new start from scratch A9L file, and my MAF & injector info added. But bummer no testing tonight, RAIN. Thanx for your time & help!!!

[EFI-Unlimited]

Try this. I'm not 100% on this, some things add up, others don't so, lets find out.
Brian
EFI-Unlimited

[sailorbob]

I have the same variables in FN325 as the stock GUFB-A9L. As for how this would reduce fuel, can give give me an explanation? Or at least some numbers to try out?

There is no FN325 in the GUF* strategies, this (along with FN1360, ECTSTABL and ECTSTHYS) is an added hack. You should start off with all the multipliers in this function as '1.000' and then alter as required. By having the multipliers all as '1.992' you are almost doubling the desired A/F ratio when using FN1360. Multiplier values less than 1 increase fuel, values greater than 1 reduce fuel.

[cgrey8]

I have the same variables in FN325 as the stock GUFB-A9L. As for how this would reduce fuel, can give give me an explanation? Or at least some numbers to try out?

There is no FN325 in the GUF* strategies, this (along with FN1360, ECTSTABL and ECTSTHYS) is an added hack. You should start off with all the multipliers in this function as '1.000' and then alter as required. By having the multipliers all as '1.992' you are almost doubling the desired A/F ratio when using FN1360. Multiplier values less than 1 increase fuel, values greater than 1 reduce fuel.

More to the point, you cannot compare a stock GUFx tune or any other unpatched tune to one that has had the FN1360 patch-hack applied. As sailorbob said, FN1360, FN325, and those other scalars don't exist in native GUFx tunes. Thus whatever values are at those memory locations in unpatched tunes isn't meaningful data that the EEC uses. It's like tuning a radio to an unused frequency...all you get is static. You are seeing static or junk values that just fill the unused memory. When the FN1360 patch is applied, those memory locations are referenced and used. But part of the patch process is to also populate those memory locations with lucid, meaningful data. And no, you cannot simply change the Z_TABOFT scalar and expect FN1360 to start working. The tune must be patched 1st.

To read more about how to FN1360-patch a tune and why you might want FN1360 as a part of your tune, check out this thread:
FN1360 for GUFx strategies

[nhra no 2]

...There is no FN325 in the GUF* strategies, this (along with FN1360, ECTSTABL and ECTSTHYS) is an added hack...

So let me get this right. If FN1360 & FN325 is an added hack, that they both go hand in hand. If you use FN1360 to define OL stabilized fuel, then you must also at least set the values in FN325 to 1. After that FN325 can be adjusted as need, and the 1.992 valuse that are the default values will cause the engine to run lean. Yes or No?

[cgrey8]

That's correct. FN325 gets added at the same time FN1360 is, as are those other scalars mentioned.

FN1360 is a table of actual fueling lambdas/AFRs based on RPM/Load.
FN325 is a multiplier function based on ECT.

While the values in FN1360 are intended to be warm-running temps, they could be too lean for cooler ECTs. FN325 is active at the same time FN1360 is and lets you enrich at lower ECT conditions.

Read the link I posted about FN1360, and it should explain all that as well as the transition from FN1307 to FN1360.

[nhra no 2]

...While the values in FN1360 are intended to be warm-running temps, they could be too lean for cooler ECTs. FN325 is active at the same time FN1360 is and lets you enrich at lower ECT conditions.

In the degrees F colum of FN325 the values are all -2. Can these temps be changed to reflect actual ECT's? And yes, I will read the link about FN1360 and FN325 tonight when I get home. One of the other problems I need to deal with are my ECT's in my latest logs. For some reason I get a max of 142 to 144 degrees reported. I have an Autometer temp gauge installed and I know my actual running temp is 190 degrees. All I have done so far is the measure voltage at the ECT sencor and pin#7 on the EEC. At full temp i AM GETTING plus/minus .6 volts, which is in range with engine temp. So I think the sencor itself is good. But first I have been focusing on my fueling problem, now I think this ECT problem might be related. Any ideas?

[sailorbob]

After that FN325 can be adjusted as need, and the 1.992 values that are the default values will cause the engine to run lean.

The default multiplier values for FN325 are '1.000', I suspect that you may have applied the code patch to your bin without the table/function patch.

[cgrey8]

...In the degrees F colum of FN325 the values are all -2. Can these temps be changed to reflect actual ECT's?...

That's because the values are garbage. The patch hasn't been applied, wasn't applied completely, or was applied incorrectly to the tune you are looking at. Although someone has changed the value of the Z_TABOFT scalar which is allowing you to see FN325 and FN1360. Once the patch is completely and correctly applied, those values you are seeing as -2 will be something that makes sense.

So like I said, even if you activated FN1360 and manually changed all the values in the scalars, FN325, and FN1360 to lucid-looking values, it's still not going to work until you patch the tune. There are other things the patch adds to the tune that you can't see or manually manipulate that must be in place before FN1360 will work.

...One of the other problems I need to deal with are my ECT's in my latest logs. For some reason I get a max of 142 to 144 degrees reported. I have an Autometer temp gauge installed and I know my actual running temp is 190 degrees. All I have done so far is the measure voltage at the ECT sencor and pin#7 on the EEC. At full temp i AM GETTING plus/minus .6 volts, which is in range with engine temp. So I think the sencor itself is good. But first I have been focusing on my fueling problem, now I think this ECT problem might be related. Any ideas?

Unless there's a wiring problem, there should be no reason why your ECT is not reading correctly. The only thing I can think of that affects how ECT is read is the ACT/ECT Transfer function. However I have NEVER known anybody that needed to adjust that transfer...and I'm not suggesting that you are the 1st.

Its possible your ECT is not showing accurate for some other reason. Try rewriting your entire tune to the QH just to make sure the payload code is in sync with what your laptop is setup for. If they aren't in sync, you can get weird garbage data being datalogged...things like 13467 for RPMs or 173 for Spark Advance...crazy numbers.

[nhra no 2]

...Try rewriting your entire tune to the QH just to make sure the payload code is in sync with what your laptop is setup for...

I am using the TwEECer, and programing/logging with Clint's BE. Are you suggesting I use some other software I am not aware of?

[cgrey8]

Not at all. Just rewrite the tune to the TwEECer using BE. The only reason the payload would get mismatched with the TwEECer is if:

• You changed the payload options in BE and didn't write those changes to the TwEECer
• You changed the payload options in BE, wrote those changes, but turned the tune position switch to a position that hadn't yet been written with those payload changes. The payload list is literally part of the tune. So if you change the list options in BE, each tune position in the TwEECer needs that update written to it. Changing payloads on the TwEECer is the same as if you changed a parameter somewhere in the scalars/functions/tables.

[nhra no 2]

OK my fuel shutting off problem is solved. Yes I had FN1360 enabled, and I did not have the bin hack added. This what caused both of my problems. Now with it disable, fueling dose not shut down, and my ECT displays correct again. Thanks for everyone's time and help!

[cgrey8]

So did you disable FN1360 or did you patch your tune to use FN1360?

[nhra no 2]

For now, I have disabled FN1360. I want to get my MAF transfer dialed in better first. I will eventually play around with FN1360, but I need to do some research on it. I need to learn how to apply the patch.

[cgrey8]

Details on how that is done is in that link. It may be buried a bit. But all the reading up to it is worth drudging through.