Just Released: OFT Data Display Updates

[Boofneenee]

OK I would like to know more about this OFT 350 coming soon. Any leaks? What is it? FI?

[Thorpedo]

Originally Posted by Boofneenee

OK I would like to know more about this OFT 350 coming soon. Any leaks? What is it? FI?

http://www.ft86club.com/forums/showthread.php?t=59178

Probably a more aggressive version of that.

[Shiv@Openflash]

Originally Posted by Thorpedo

http://www.ft86club.com/forums/showthread.php?t=59178

Probably a more aggressive version of that.

Nope.. it's a turbo

[Thorpedo]

Originally Posted by Shiv@Openflash

Nope.. it's a turbo

Sbd?

[ZZT86]

OMG @ this thread :|

[solidONE]

Request: can any of you who have completed the recent update and have ref lashed your ECU after the update please post some wot pulls logs showing flck? My car has not been running the same since I reflashed after updating the oft showing a large amount of flkc appearing as large spikes in the logs. Thank you!

http://www.ft86club.com/forums/showp...6&postcount=95

[troek]

i had something very similar happen, it turned out to be my exhaust hitting my fuel tank right before the the diff. if youve never had knock before, and running the same fuel. itd be worth checking out.

[solidONE]

Originally Posted by troek

i had something very similar happen, it turned out to be my exhaust hitting my fuel tank right before the the diff. if youve never had knock before, and running the same fuel. itd be worth checking out.

Yeah that is something I will definitely look into. I figure if someone posts a log after updating the oft that is clearly the same as before the update then I will have ruled out the new update for causing the problem. As far as I know the fuel should be the same. At very least from same gas station. I'm running stock header and cat-back so there shouldn't be any issue with those. Only difference is that the weird flkc happened after flashing with the updated OFT with a very slight change in the maf temp compensation table that should have little to no effect on knock. All else was identical pre weird flkc logs.

Edit: I went ahead and did a once over on every single exhaust fastener and made sure it wasn't hitting anything and everything is torqued down properly, reflashed a modified tune earlier today since it was still more knock resistant vs the OTS tune then took a log:
http://datazap.me/u/solidone/stg1-20...4&zoom=136-406

Still with the spikes of flkc. As I saved and uploaded the above log the OFT auto updated. I removed my oil catch can, just to rule that out as a possible cause. Went and took another log. This time the display was obviouly more glitchy than before with knock correction stuck at -.68 most of the time and the flkc hanging at -.39 even with 0 throttle input coasting...
The following log here: http://datazap.me/u/solidone/stg1-20...zoom=2667-2930

What say you,@Shiv@Openflash?

[troek]

out of curiosity what did you modify to reduce the knock between those 2 data logs? im still learning about all this stuff but it seems weird to see knock all the way across the rpm range.
Taken from http://www.zzperformance.com/blog/ab...ock-retard-kr/
"False knock is characterized by a sharp spike to an immediately high value of KR followed instantly by the KR Recovery Rate. It doesn’t grow with engine RPM or load, it jumps to a high value on throttle input and then recovers to a low value, or zero perhaps, as engine RPM continues to increase. Note that this is exactly opposite to the characterization of REAL KR. Remember, knock is simply specific noise detected by engine microphones. Because it happens to fall with in the frequency of real KR does not necessarily mean that it IS real KR."

[solidONE]

Originally Posted by troek

out of curiosity what did you modify to reduce the knock between those 2 data logs? im still learning about all this stuff but it seems weird to see knock all the way across the rpm range.
Taken from http://www.zzperformance.com/blog/ab...ock-retard-kr/
"False knock is characterized by a sharp spike to an immediately high value of KR followed instantly by the KR Recovery Rate. It doesn’t grow with engine RPM or load, it jumps to a high value on throttle input and then recovers to a low value, or zero perhaps, as engine RPM continues to increase. Note that this is exactly opposite to the characterization of REAL KR. Remember, knock is simply specific noise detected by engine microphones. Because it happens to fall with in the frequency of real KR does not necessarily mean that it IS real KR."

Only difference between the two logs is an oil catch can, same tune same condition same day same road and taken no more than 30 minutes apart.

Notice how the FLKC registered increases after each up shift.
The below log was made runing pretty much the same exact tune in very similar conditions (slightly cooler ambient temps) before the OFT update aside from slight difference in the MAF scale.
http://datazap.me/u/solidone/stg1-20...-12&zoom=3-311

Very helpful link BTW. Thanks. None of the hardware was touched from this log vs the more resent logs in my last post, so I'm not sure where I could have something causing a false knock...

[troek]

have you flashed back to a tune that had no knock and logged that?

[AdrianG]

So I found a bug with the new update, not a big one though. If I leave the OFT connected in realtime display mode, the next time I start the car it reports IAM of 0 or 0.01... If you tap it though it shows one and then when you go back to the full list it shows as normal.

As I said, not a big bug but I had a chuckle the first time I saw that my IAM was 0...

[solidONE]

Originally Posted by troek

have you flashed back to a tune that had no knock and logged that?

That was the most knock resistant tune I have right before the update. If I did not up shift while WOT, like how most people seem to do it, there would have been no knock registered. And it's what I've reverted back to from the OTS tune currently.

[steve99]

Originally Posted by solidONE

That was the most knock resistant tune I have right before the update. If I did not up shift while WOT, like how most people seem to do it, there would have been no knock registered. And it's what I've reverted back to from the OTS tune currently.

Certianly seems a strange co0incidence

maybe log
KC Learned
FLKC (the problem one)
Ignition timing total

You should see a corresponding drop in KC Learned and Ignition timing total when FLKC goes negative. If their was a weird logging issue then it should show up. if FLKC goes -3 their should be corresponding dip in KC learned and Total Ignition timing applied.

logging is done by the OFT software asking for the contents of a specific RAM address in the ECU a scaling factor may then be applied and the result is presented in the log. Each ROM type ie C/G/A ect and sometimes the different revisions of those ROM's will have different locations for these RAM addresses ,its possible something is wrong but everyone on same ROM would have the problem. But it may not be a universal issue for all ROM types.

I doubt they have changed anything in the Flashing side of things and if that was out of wack the FLKC would be the least of your problems. The OFT corrects the checksum and I would imagine then checks the checksum of the flashed ROM and would throw an error if that was incorrect. If the flash was bad its likely the car would not run.

As @troek said you can trigger false knock indication from loose bolts or a washer or similar dropped down near knock sensor or exhaust hitting on sub-frame ect