Official OpenFlash Tablet FA20 Tuning Tech Discussion Thread

[jamesm]

Originally Posted by solidONE

Will this excel app work without intake air temps? OFT does not have IAT logging capabilities yet. Hope to see this added soon, along with option to display selected inputs like a gauge(s) with larger high visible readouts.

It will, you'll just lose a bit of accuracy. You could either go through and manually remove the rows at idle with high iat or not, then just put the same value in for all the cells so it won't reject any.

[solidONE]

Originally Posted by jeebus

My ltft is at around 2...noshing crazy.. And my stft doesn't wildly fluctuate. Front pipe is Berk. 2.5"

So there is a difference in front pipe diameter, everything else is more or less the same. Mine is 2.75"

Your IAM fluctuating is supposedly normal on pump gas. One way to make it come back up to 1, I found, is to make some easy pulls to high RPM with more than half throttle. When you do this, and the computer does not sense knock your KC Learned value goes past 5 up to 6. Each time KC goes past 5 and above the computer adds more IAM value until it's back at 1.

I'm guessing the IAM value is dictated by knock or lack thereof while under load. No knock, increase IAM. Knock? IAM gets dialed back. Any value less than 1 is due to knock retard basically. Am I right?

[jamesm]

Originally Posted by solidONE

So there is a difference in front pipe diameter, everything else is more or less the same. Mine is 2.75"

Your IAM fluctuating is supposedly normal on pump gas. One way to make it come back up to 1, I found, is to make some easy pulls to high RPM with more than half throttle. When you do this, and the computer does not sense knock your KC Learned value goes past 5 up to 6. Each time KC goes past 5 and above the computer adds more IAM value until it's back at 1.

I'm guessing the IAM value is dictated by knock or lack thereof while under load. No knock, increase IAM. Knock? IAM gets dialed back. Any value less than 1 is due to knock retard basically. Am I right?

that's pretty much it. iam is part of 'coarse correction'. so, it's one of three knock control strategies being employed one at a time, at any given time. when the ecu hears what it believes to be a knock event, it'll decrement fine learning in the cell you were in when it happened. if the pulled timing from that event is great enough (usually around 3 degrees) it'll drop the iam. this pulls timing blindly across the board, as total timing = base + (iam * advance) + compensations + corrections.

so the long and short of it is that iam (coarse correction) is the nuclear option. if your iam isn't 1, the engine already saw what it considers to be serious knock. also, since it's only one of three strategies with only one active at any given time, an iam of 1 doesn't mean your car isn't knocking somewhere. it's actually quite easy to disable the iam altogether and just make it always read 1, which i've found many tuners do to combat iam dropping due to insignificant tip-in knock. so, you have to look at the whole picture to know what's going on: coarse correction, fine learning, and feedback correction.

[Thongpocket]

Because of this post I am looking into getting one of these. Thank you for all your hard work.

[jamesm]

Originally Posted by jeebus

I haven't logged in a bit. Decided to take a look today and WTF my AM was at .5? I managed to get it up to .7 but by the end of my drive it was at .2....bad gas??

if your iam is 0.2 then you're damn near in limp mode. that's bad. log every knock param you can and see what is going on. it's very likely that you're running more than 3 degrees advance in the 0.5-0.9 load range, thus enabling coarse correction in this range where just about every 86 i've ever seen knocks like hell, and causing the iam to drop precipitously.

moral of the story: if you iam is ever 0.2, that's a #1 priority, figure it out now kinda problem. it may be that it's pulling 5 degrees under full load (bad) or as simple as tip in, low load knock messing up your day (not so bad), but in either case you want to know and want it fixed.

you iam should be 1. all the time. if not something is wrong. it can be argued that our car drop iam stock, so it must be ok. but it's not, the stock tune just has knock issues. the point of tuning is to make it better than stock .

fwiw i'm still not able to get rid of all the knock (i get -1 and -2fbkc occassionally down there), so i just disable coarse correction in those areas. bad idea? maybe, but i've seen no ill effects thus far. it still knocks less than a stock 86 lol.

[vgi]

Maybe running pump gas on e85 tune?

[jeebus]

Originally Posted by jamesm

if your iam is 0.2 then you're damn near in limp mode. that's bad. log every knock param you can and see what is going on. it's very likely that you're running more than 3 degrees advance in the 0.5-0.9 load range, thus enabling coarse correction in this range where just about every 86 i've ever seen knocks like hell, and causing the iam to drop precipitously.

moral of the story: if you iam is ever 0.2, that's a #1 priority, figure it out now kinda problem. it may be that it's pulling 5 degrees under full load (bad) or as simple as tip in, low load knock messing up your day (not so bad), but in either case you want to know and want it fixed.

you iam should be 1. all the time. if not something is wrong. it can be argued that our car drop iam stock, so it must be ok. but it's not, the stock tune just has knock issues. the point of tuning is to make it better than stock .

fwiw i'm still not able to get rid of all the knock (i get -1 and -2fbkc occassionally down there), so i just disable coarse correction in those areas. bad idea? maybe, but i've seen no ill effects thus far. it still knocks less than a stock 86 lol.

It seemed to be all transient stuff causing it. However a fresh tank of gas seems to have corrected the issue. Must have been some bad 91.

[Terrapin77]

I just tried to flash a new map, but my OFT says it can't write due being out of sync. Any ideas on how to fix this?

[Apoc]

Originally Posted by Terrapin77

I just tried to flash a new map, but my OFT says it can't write due being out of sync. Any ideas on how to fix this?

Yes this happened to me. This is a quote from Shiv

"That error occurs when you delete the map that you were previous running. For example, if you were running map bank 4 and then you delete it and only load maps in bank 1, 2 and 3.

Simple fix: just load maps in each of the 5 map banks and you'll be good to go."

[Jdmr2]

my tablet is giving me "error 0x87 while communicating with the device" when i try to upload my map. any ideas???

[vynervt]

Originally Posted by Jdmr2

my tablet is giving me "error 0x87 while communicating with the device" when i try to upload my map. any ideas???

@Jdmr2, I having the same issue before, just uninstall your OpenFlash Manager from your PC and download open flash Manager v 1.04V from the website again it will update accordingly..

[Jdmr2]

Cool I'll give that a try when I get home in an hour or so

[brn12345]

Originally Posted by Jdmr2

my tablet is giving me "error 0x87 while communicating with the device" when i try to upload my map. any ideas???

I have the same error. Tried uninstalling and reinstalling but get same result. I also now get a Map incompatible message when I try to write to the ecu.

[Shiv@Openflash]

Originally Posted by Jdmr2

my tablet is giving me "error 0x87 while communicating with the device" when i try to upload my map. any ideas???

This is because you probably tried to upload more than 2 modified roms before updating to the newest firmware 119. This corrupted the memory. To solve this, you will have to uninstall the OFT, erase it, and reinstall it.

So basically:

-flash your original file back to ecu
-erase data in OF manager software
-reinstall as if new (do initial read)
-then procede as usual. You will be able to load up to 5 files since the unit should have auto updated to firmware 119 by then.

Cheers
Shiv