OpenFlash Tablet v1.55b: BIN files added!

[AdrianG]

1.24 is the version of the OFT firmware, which is different from the OTS tunes. Nothing for you to update at this time.

- AdrianG

[zc06_kisstherain]

Originally Posted by zc06_kisstherain

I just did the datalogging on Stage 1 V1.56b map. with Avo Silicon inlet, Motiv Catless Front pipe, Nameless axle back
http://www.datazap.me/u/zc06kissther...4?log=0&data=1

somehow, except time and engine speed, all other fields shows as colum1~11

FIXED file!
http://www.datazap.me/u/zc06kissther...0&data=1-2-8-9

when i compare this datalog file from my previous tune, it seems very similar. i guess looks ok?

EDIT: i updated template file and shows all colums now!

@shiv@vishnu
mine looks ok? if i compare previous tune of v1.42 VS 1.56b, i feel much smoother than before.

[Yobiwan]

@shiv@vishnu

I use JDL UEL with OFT OTS stage 2 map via ECUtek cable.
( and MY OFT is shipped to my country , it will be here this week. )


Flickr에서 Yobi-Wan님의 datazap-chart (1)

http://www.datazap.me/u/yobiwan/v16-...7&zoom=606-761
I did maf rescaling my self.
and there are AFR mismatch in 3000~4500 range.
I can't fix that area with MAF scaling. I tried several times. but nothing work.

( http://www.datazap.me/u/yobiwan/oft-...3&zoom=325-481

http://www.datazap.me/u/yobiwan/maf-...3&zoom=199-357

http://www.datazap.me/u/yobiwan/oft-...-5&zoom=47-268 )

What should I do for this problem ?
my suspicion is it's due to "not perfectly fitting cam table"
should I buy E-tuning option? or is there any way to adjust my self?

[Shiv@Openflash]

Originally Posted by zc06_kisstherain

@shiv@vishnu
mine looks ok? if i compare previous tune of v1.42 VS 1.56b, i feel much smoother than before.

Looks great. Nothing out of the ordinary at all

[steve99]

Originally Posted by Yobiwan

@shiv@vishnu

I use JDL UEL with OFT OTS stage 2 map via ECUtek cable.
( and MY OFT is shipped to my country , it will be here this week. )


Flickr에서 Yobi-Wan님의 datazap-chart (1)

http://www.datazap.me/u/yobiwan/v16-...7&zoom=606-761
I did maf rescaling my self.
and there are AFR mismatch in 3000~4500 range.
I can't fix that area with MAF scaling. I tried several times. but nothing work.

( http://www.datazap.me/u/yobiwan/oft-...3&zoom=325-481

http://www.datazap.me/u/yobiwan/maf-...3&zoom=199-357

http://www.datazap.me/u/yobiwan/oft-...-5&zoom=47-268 )

What should I do for this problem ?
my suspicion is it's due to "not perfectly fitting cam table"
should I buy E-tuning option? or is there any way to adjust my self?

Have you disabled fuel trims ?? noticed STFT and LTFT are always zero or you have wrong RAM addresses for those parameters for logging.

[Jolaessss]

so whats this i hear about v1.6? @shiv@vishnu

[Yobiwan]

Originally Posted by steve99

Have you disabled fuel trims ?? noticed STFT and LTFT are always zero or you have wrong RAM addresses for those parameters for logging.

no i didn't disabled them.
if you zoom out that log, you can see LTFT & STFT
http://www.datazap.me/u/yobiwan/v16-...g=0&data=3-6-7
but I did that log right after tune. so it moved not so much.

LTFT of that range ( 3000~5000) will be -4~-6 eventually like this log
http://www.datazap.me/u/yobiwan/test-log?log=0&data=1-4


I attatched another post learned log capture too. STLT & LTFT works fine.

[steve99]

Originally Posted by Yobiwan

no i didn't disabled them.
if you zoom out that log, you can see LTFT & STFT are moved.
http://www.datazap.me/u/yobiwan/v16-...g=0&data=3-6-7
but I did log right after tune. so it moved not so much.

LTFT of that range ( 3000~5000) will be -4~-6 eventually.

even in that log the fuel trims seem incredibly stable at 0 to 0.8 even when your on and off the throttle

you will have to wait for some experts to come and look at it

[l0aded]

Don't know if this is the right thead but just pulled the trigger =). Can't wait to see what the hype is all about and excited for FI options in the future.

[wparsons]

Originally Posted by steve99

nope thats not what I did see here
http://www.ft86club.com/forums/showp...0&postcount=64

most of the values in the knock prone area are still above 3.9. Some were already below this threshold .

I specifically did not want to "effectively" disable coarse correction by moving all the timing to the base map or reducing values below 3.9.

The max retard amount was 0.35 of a degree.

I have used tactrix logging which can monitor fbck & flck at 20Hz and have logged noticeably less occurrences of both and the values are also less for fbck and flck in the knock prone areas with these changes.

I believe it the less knock severity and less occurrences that are resulting in the ECU not entering coarse correction mode and dropping IAM.

If your IAM is dropping to even to 0.7 then your pulling 30% of the timing values in the entire knock correction table for the entire rpm/load range which is going to result in retard amount somewhere from 1 to 3 degrees which is going to rob you of far more power than my 0.35 degree adjustments in a few cells I believe.

I am not saying this will work for everyone but its working for me on Aussie 100 RON fuel.will try on 98 next week.

Ahh, I think we're talking about different scenarios then. My IAM drops like a stone in stop and go traffic with really light throttle application (like <15% throttle).

Originally Posted by steve99

even in that log the fuel trims seem incredibly stable at 0 to 0.8 even when your on and off the throttle

you will have to wait for some experts to come and look at it

Small and stable trims = well scaled MAF

[8686]

Originally Posted by 8686

Thank you all for the comments. Will do another log soon with AFR comanded, STFT, and LTFT.
Unfortunately I don't know how to modify maps. At least I will know what is needed to be done.

I did another Log this morning as adviced. The AFR look too rich after 5,500 rpm.

http://www.datazap.me/u/haririmm/155...ata=1-2-7-9-11

I did 3 runs starting in third and then shifting to fourth. Below video for the second run. Note, Speed is in KM/H

[ame]http://youtu.be/6rM7MYMn5hk[/ame]

Appreciate your comments

[steve99]

Originally Posted by wparsons

Ahh, I think we're talking about different scenarios then. My IAM drops like a stone in stop and go traffic with really light throttle application (like <15% throttle).

Possibly but have a look at the engine load at 15% throttle it can still be quite high in high gear low rpm driving . The other thing I found is it appears to be cumulative, if you only get one knock event (fbck generally) of greater than say -1 then its fine but get several in a relatively short period maybe a minute or two then you see IAM drop.

Would be good to know the exact logic ie x number of fbkc events greater than y value in time period z causes coarse correction, but its probably more complex. The stuff on RR is ok but its for WRX ECU so imagine may not apply totally to FA20

Originally Posted by wparsons

Small and stable trims = well scaled MAF

Yep agree with that, they did seem incredibly stable though with large throttle movements

[Shiv@Openflash]

Originally Posted by Jolaessss

so whats this i hear about v1.6? @shiv@vishnu

We are still a while away from releasing the new maps. Currently working on them now. But still plenty of testing to do!

[nelsmar]

Originally Posted by 8686

I did another Log this morning as adviced. The AFR look too rich after 5,500 rpm.

http://www.datazap.me/u/haririmm/155...ata=1-2-7-9-11

I did 3 runs starting in third and then shifting to fourth. Below video for the second run. Note, Speed is in KM/H

Appreciate your comments

How many miles since flash, are you, and what intake?
With a quick glance i see what looks like possibly minor FLKC @ 3600-~4600 and then from 5200 to 5800 again some minor FLKC. This is minor knock but if you are getting it at the 5200+ mark running that rich some minor timing may need to be pulled from the ignition map. Also what fuel are you on?