ECU LOGGING BRZ GT 86 FRS - what to look for the basic’s

[finch1750]

So my LTFT got pretty high the other day (post header install). If I just cruise the car should be fine for a few days til I have time to check for a leak? My AFR stayed good

Im new to this and still trying to understand but the only issue I see is the Open Loop during wot/hard pulls would be effected and possibly cause me to run lean? So if I avoid that as best I can it shouldnt be too big of a problem?

[Rodn333y]

Thanks for this info!

Sent from my SM-N920V using Tapatalk

[Swivel]

Is "IAM" the same as "Ignition Adv" on the OFT tablet? I'm assuming it is, and so I'm a bit confused.

I'm showing Ignition Adv numbers of up to 44.00. This doesn't sound right, seeing as people are mostly seeing numbers in the single digits.

Additionally, the FBKC is reading a solid 0 across the board in all of my logs.

In addition to that, I'm not seeing the FLKC available for logging on the OFT. However, this could just be a limitation with the OpenFlash Tablet.

Thoughts?

Originally Posted by steve99

Knock –detonation – pre-ignition

FLKC – Fine learning knock control
FBKC (Knock Correction) – Feed Back Knock control
IAM – Ignition Advance Multiplier

[phrosty]

Originally Posted by Swivel

Is "IAM" the same as "Ignition Adv" on the OFT tablet? I'm assuming it is, and so I'm a bit confused.

I'm showing Ignition Adv numbers of up to 44.00. This doesn't sound right, seeing as people are mostly seeing numbers in the single digits.

Additionally, the FBKC is reading a solid 0 across the board in all of my logs.

In addition to that, I'm not seeing the FLKC available for logging on the OFT. However, this could just be a limitation with the OpenFlash Tablet.

Thoughts?

Ignition advance is not what you're looking for.

Been a while since I logged with my OFT but I believe IAM = "Adv Multipler" and FLKC = "Knock Correction".

[Swivel]

Originally Posted by phrosty

Ignition advance is not what you're looking for.

Been a while since I logged with my OFT but I believe IAM = "Adv Multipler" and FLKC = "Knock Correction".

Oops! I knew that, actually. Sorry. Really long day! I should probably get some sleep...

[MikeFrs]

I think i have a problem. My FLKC is at -5.30 and my Adv multiplier is at 0... Stage2 UEL tune with headers and catback only...

https://datazap.me/u/mike1234/log-15...ta=1-5-8-11-12

[Tor]

Originally Posted by MikeFrs

I think i have a problem. My FLKC is at -5.30 and my Adv multiplier is at 0... Stage2 UEL tune with headers and catback only...

https://datazap.me/u/mike1234/log-15...ta=1-5-8-11-12

Yes, you have a logging problem. This is the knock you have:

https://datazap.me/u/mike1234/log-15...2&mark=127-130

[Wayno]

Originally Posted by MikeFrs

I think i have a problem. My FLKC is at -5.30 and my Adv multiplier is at 0... Stage2 UEL tune with headers and catback only...

https://datazap.me/u/mike1234/log-15...ta=1-5-8-11-12

You have a native D00C, D00D, F00C, F00D, etc rom that the OFT doesn't have all the logging addresses built into the firmware for.

If you use a B01C/B01D that's been hacked to appear like your calibration code, logging will work.

You can get hacked B01C/D from the OFH release on openflash site, then copy the tables from the OTS release. You will need the romraider definition for your cal code from the OFH release, and any romraider definition for B01C/D from OTS OR OFH realease (B01C/D is always B01C/D).

Or see the link in my sig for roms already cal-hacked.

[steve99]

Originally Posted by MikeFrs

I think i have a problem. My FLKC is at -5.30 and my Adv multiplier is at 0... Stage2 UEL tune with headers and catback only...

https://datazap.me/u/mike1234/log-15...ta=1-5-8-11-12

Tune is fine its just logging issue.

You can derive iam and flkc knock from the KC Learned parameter, and it looks fine iam is 1 and you have a little spike of knock about -0.7 at about 4800 thats that chomp out of the kc learned curve.

If kc learned matches the values in the Knock corrdction maxA table for given rpm and load tgen your fine knock wise

[TofuJoe]

@steve99 - basic question - is it possible to log the key data points with an iPhone or Android app?

I'm looking at DashCommand, but don't see all of the fields.
I have oil temp, coolant temp, fuel trims, AFR (commanded and actual), MAP, MAF, KCLV, KFV, IAT, and SPARKADV. Apparently missing IAM, FLKC, FBKC.

It'd be great to be able to log a mostly stock car/tune without buying an OFT.

Update: After some more digging around, I see the missing fields are calculated from a mix of data points: http://www.romraider.com/forum/topic1840.html
Is there a way to log with an iPhone or Android app, export to Excel, and get these numbers?

[steve99]

Originally Posted by TofuJoe

@steve99 - basic question - is it possible to log the key data points with an iPhone or Android app?

I'm looking at DashCommand, but don't see all of the fields.
I have oil temp, coolant temp, fuel trims, AFR (commanded and actual), MAP, MAF, KCLV, KFV, IAT, and SPARKADV. Apparently missing IAM, FLKC, FBKC.

It'd be great to be able to log a mostly stock car/tune without buying an OFT.

Update: After some more digging around, I see the missing fields are calculated from a mix of data points: http://www.romraider.com/forum/topic1840.html
Is there a way to log with an iPhone or Android app, export to Excel, and get these numbers?

You cannot effectivly log fast changing parameters like knock flkc or fbkc or even maf volts ignition timing cam parameters with the basic obd logging interfaces like elm327 to iPhones or Android devices. The refresh rate is way too slow about 2 times a second, you need at least 5 times a second and 10 or 20 is better.

Also they only log the more basic parameters that manufactures are required by law to allow to be monitored.

They are fine for slow moving stuff like oil and water temps intake air temps etc but not good for tuning.

You will need to use tactrix ecutek or brzedit or oft for tuning level monitoring or logging

[TofuJoe]

Thanks, @steve99

Great info. Always appreciate you sharing your knowledge here.

[TofuJoe]

Just found out on the OFT Facebook group that the OFT doesn't log IAM, MAF v, or FLKC on 2017 cars yet. Shiv said he's finishing up some other projects before he gets around to 2017 ECU logging.

[Northern_18]

I just tried logging on my 2016 FR-S and I can't see any of the accelerometer stuff that was supposed to have been released. I have the latest version of OFM (1.28.0) and it seems to have updated the OFT but still can't see that. I tried logging everything that was mentioned for knock detection (RPM, Engine load, FBKC (knock correction), iam, KC Learned and FLCK). IAM is nowhere to be found for logging, FLCK is pretty much always at -100, 100 or 0. Not sure what any of that gives me. Not sure how to find the iam if I can't log it.

Here is a link to my log with all those parameters plus I added a couple.
https://datazap.me/u/northern18/first-log?log=0&data=

I don't know if it's because I can't log some of the stuff yet for a 2016 FR-S (It is automatic) or if I need to update the template (I thought I read somewhere that we no longer need to touch templates and that it's all automatic now for updating).

EDIT: I haven't flashed a tune to my car yet since I want to make sure I know how to log and use this beforehand. Not sure if that makes a difference regarding missing parameters when logging?