Data Logs! Post them here.

[Bergen23]

Originally Posted by JB86'd

You're updated here?

Reason I ask is because your FLKC is wacky

Yes

[momo3605]

Originally Posted by steve99

the high ltft at idle means the maf scaling is off a bit and ecu is applying the correction (ltft) so it targets the correct afr. At low rpm the worst that happens is maybe a bit of hesitation as you come off idle.

Maf sensors vary a bit from car to car.

After running out of my e85 tank with 1 gallon of 91, I now have a full tank of e85, and there are no knocks and IAM is at 1, but LTFT is at a ridiculous 13% at idle. How difficult would the MAF correction be to get this down to 0 at idle? Anytime other than idle, the trims are near 0. Is this something I should worry about?

[steve99]

Originally Posted by momo3605

After running out of my e85 tank with 1 gallon of 91, I now have a full tank of e85, and there are no knocks and IAM is at 1, but LTFT is at a ridiculous 13% at idle. How difficult would the MAF correction be to get this down to 0 at idle? Anytime other than idle, the trims are near 0. Is this something I should worry about?

It not a big drama at idle. Its very difficult to get trims less than about 5% at idle due large variations in temperature of intake air at idle.

If its not causing hesitation issue then just leave it.

You could just adjust the maf scaling arround idle
note the MAF Volts number at idle and note the Long Term Fuel trim.
I think you will have to log it as OFT screen only shows absolute value from memory with no + or -

If the LTFT is say 10% positive at idle then ADD 5% (ie about half the LTFT) to the maf flow rate number at the MAF Volts you noted and the maf flow numbers either side.

If the LTFT was 10% negitive then SUBTRACT 5% off the maf flow numbers at the MAF Volts you noted and at either side.

Dont change the Maf Volts numbers.

That should get the LTFT to a lower number.

[Phoenix*]

The BRZ/GT86 suffers from false knock during partial throttle between 0.5-0.8 g/rev engine load.
At times even the IAM drops and then climbs back up, once the timer threshold has been reached.
To stop this from happening, the knock sensor calibration tables need to be adjusted ever so slightly within this zone to avoid this dilemma. This is a common behaviour for Subaru motors in general, and one of the major causes is AVCS related.

@GeeTee86

The datalogs look decent.
Motor seems happy.
Just a few constructive inputs and observations:

• MAF Scaling still needs some work, i.e. LTFT's are still being carried over from CL to OL during WOT; Actual_AFR is not corresponding to the AFR_Command.

• MAF voltage is low up top. Go more aggressive on intake AVCS towards redline to aid volumetric efficiency and intake CFM delivery.

I also noticed that the Knock Correction Advance table has no ignition correction values within low engine load zones. I highly recommend that you add correction timing throughout the KCA table and then adjust the Base Timing table accordingly.

The knock events being seen are negligible.
The map is a touch aggressive for our 95 pump fuel, so be sure to run higher octane fuel or perhaps Octane Booster.

[steve99]

Originally Posted by Phoenix*

The BRZ/GT86 suffers from false knock during partial throttle between 0.5-0.8 g/rev engine load.
At times even the IAM drops and then climbs back up, once the timer threshold has been reached.
To stop this from happening, the knock sensor calibration tables need to be adjusted ever so slightly within this zone to avoid this dilemma. This is a common behaviour for Subaru motors in general, and one of the major causes is AVCS related.

@GeeTee86

The datalogs look decent.
Motor seems happy.
Just a few constructive inputs and observations:

• MAF Scaling still needs some work, i.e. LTFT's are still being carried over from CL to OL during WOT; Actual_AFR is not corresponding to the AFR_Command.

• MAF voltage is low up top. Go more aggressive on intake AVCS towards redline to aid volumetric efficiency and intake CFM delivery.

I also noticed that the Knock Correction Advance table has no ignition correction values within low engine load zones. I highly recommend that you add correction timing throughout the KCA table and then adjust the Base Timing table accordingly.

The knock events being seen are negligible.
The map is a touch aggressive for our 95 pump fuel, so be sure to run higher octane fuel or perhaps Octane Booster.

Thanks good constructive comments

Pretty sure he is running octane booster all the time.

good to hear someone else thinks you get false knock indications at times low/med load

always thought adding more to Knock Correction Max A (kc learned) table while reducing Base Timing B by same amount was a good idea to give IAM more scope to control knock was a good idea, thanks for confirming.

They have done a bit more work on maf scaling i think.

not many tuners will make constructive and helpfull comments thankyou

[GeeTee86]

Yeah what Steve said, together we learn and figure this FA20 out.

[Phantobe]

Originally Posted by JB86'd

I thought I might be..seeing 11.25. Any ideas as to why I'm running rich? Maybe just the tune?

I think its just the tune, I've seen 11.25 AFR on my WOT pulls as well. I don't think it's anything to worry about. And I've seen it in many other people's logs as well.

Better to run rich than lean, as far as an adjustment I'm not sure it may have something to do with MAF scaling.

[Bergen23]

http://www.datazap.me/u/colekmiecik/log2?log=0&data=1

Insight? How soon is my engine going to explode?

[Koa]

Originally Posted by Bergen23

http://www.datazap.me/u/colekmiecik/log2?log=0&data=1

Insight? How soon is my engine going to explode?

What is your rom? It's not logging correctly... IAM reporting 0, FLKC reporting -100...

Log the following and re-post:

Time, RPM, MAFV, Engine Load, STFT, LTFT, AFR, IAM, FBKC, FLKC, IAT, Fuel System Status, Oil Temp

[steve99]

Originally Posted by Bergen23

http://www.datazap.me/u/colekmiecik/log2?log=0&data=1

Insight? How soon is my engine going to explode?

IAM not logging correctly
FLKC not logging correctly

If you have updated oft and template file already phone or email openflash guys about that logging, send them copy or link to log

from what is logged it looks ok, but need flkc and iam for knock.

[steve99]

Originally Posted by Phantobe

I think its just the tune, I've seen 11.25 AFR on my WOT pulls as well. I don't think it's anything to worry about. And I've seen it in many other people's logs as well.

Better to run rich than lean, as far as an adjustment I'm not sure it may have something to do with MAF scaling.

@JB86'd will be Open loop maf scaling off, 11.25 is rich limit of o2 sensor scale so it may even be richer. do you have stock intake ??

however if you correct maf scaling and hence AFR, check for knock especially if your on 91 octane, you may have to pull some timing as the rich mix will buy you knock resistance.

[Bergen23]

@Koa @steve99

Updated 2 days ago before I logged my first one further up in this thread. Updated tablet again and did a fresh flash after @JB86'd said it wasn't logging correctly. It's good to know that it's a logging issue (hopefully) and not a engine on the verge of dying a fiery death (hopefully). I guess the next step is to get in touch with the open flash guys.

Cheers

[Koa]

Originally Posted by Bergen23

@Koa @steve99

Updated 2 days ago before I logged my first one further up in this thread. Updated tablet again and did a fresh flash after @JB86'd said it wasn't logging correctly. It's good to know that it's a logging issue (hopefully) and not a engine on the verge of dying a fiery death (hopefully). I guess the next step is to get in touch with the open flash guys.

Cheers

They just got to the D00C tunes, and perhaps one newer than that.. hoping its soon.. for now try and stay out of areas where that crazy fine learning knock is tipping in

[steve99]

Originally Posted by Bergen23

@Koa @steve99

Updated 2 days ago before I logged my first one further up in this thread. Updated tablet again and did a fresh flash after @JB86'd said it wasn't logging correctly. It's good to know that it's a logging issue (hopefully) and not a engine on the verge of dying a fiery death (hopefully). I guess the next step is to get in touch with the open flash guys.

Cheers

did you update template file manually ?