OpenFlash Tablet

[TIE Pilot]

Originally Posted by troek

ahh thanks, i guess i figured the OFT side of the cable was OFT specific. but i didnt even realize you could extend it on the obd side. i was just thinking of a single longer cable.

I would look for a Flat OBDii Right Angle Extension.

[ame="http://www.amazon.com/Profile-Right-Angle-Extension-Ribbon/dp/B00EECXAY8"]Amazon.com: Low Profile Right/Left Angle OBD 2 II Extension with Flat Ribbon Cable 3'/1m: Automotive[/ame]

[mid_life_crisis]

Originally Posted by s2d4

The OCD in me find this process rather soothing for some reason..

That's C D O, get the letters in the correct order damnit.

I don't have OCD but my sister in law does and she thought that was funny so I figured I'd share.

[phrosty]

Does this log look alright? Been driving it for about a week, looks like fuel trims have stabilized.

http://datazap.me/u/phrosty/oft-stag...&zoom=318-1308

It's 1.58 Stage 1 700D w/ scaled MAF for Perrin's CAI.

[Kodename47]

Originally Posted by phrosty

Does this log look alright? Been driving it for about a week, looks like fuel trims have stabilized.

http://datazap.me/u/phrosty/oft-stag...&zoom=318-1308

It's 1.58 Stage 1 700D w/ scaled MAF for Perrin's CAI.

Looks a little lean. The LTFT is taking out about 0.8% fuel under WOT and it still looks like it's running lean even if the trims are spon on.


Did you scale the MAF yourself or use a provided scale?


Next time, can you log the commanded AFR as well? Then it's easily comparable.

[HSayaovong]

Originally Posted by mid_life_crisis

This appears to be proof that if you have 93 readily available there is room to play.

True to some extent, I'm not sure if you've read my other thread but there seems to be a limit to the extent of these ots maps, once you stray to far from the ots settings it'll pretty much scale itself down to what its default base map "safe map?"is. I'm sure you can mess with the backup map so that it won't do that but it's probably safer the leave it alone just incase you went to crazy with the tweaks can always fall back on the base safe map.
My lingo is probably wrong but that's the jest of it

[phrosty]

Originally Posted by Kodename47

Looks a little lean. The LTFT is taking out about 0.8% fuel under WOT and it still looks like it's running lean even if the trims are spon on.


Did you scale the MAF yourself or use a provided scale?


Next time, can you log the commanded AFR as well? Then it's easily comparable.

I'm using Perrin's provided scale. Still not confident enough with my understanding of the steps to scale it myself, but I hope to get there.

I'll set up to log commanded AFR next time I do a pull. What's the difference between AFR and commanded AFR?

[s2d4]

Originally Posted by phrosty

What's the difference between AFR and commanded AFR?

AFR is what is measured by the stock o2 sensor, commanded is what the ECU was targeting at the time.

[s2d4]

Originally Posted by HSayaovong

True to some extent, I'm not sure if you've read my other thread but there seems to be a limit to the extent of these ots maps, once you stray to far from the ots settings it'll pretty much scale itself down to what its default base map "safe map?"is. I'm sure you can mess with the backup map so that it won't do that but it's probably safer the leave it alone just incase you went to crazy with the tweaks can always fall back on the base safe map.
My lingo is probably wrong but that's the jest of it

"The higher the octane, the more compression the fuel can withstand detonation. "

[mid_life_crisis]

Originally Posted by phrosty

I'll set up to log commanded AFR next time I do a pull. What's the difference between AFR and commanded AFR?

Originally Posted by s2d4

AFR is what is measured by the stock o2 sensor, commanded is what the ECU was targeting at the time.

Reasonable to expect that you can learn a lot by comparing what you told the system to produce (commanded AFR) and what it actually did produce (AFR).

[s2d4]

Originally Posted by mid_life_crisis

Reasonable to expect that you can learn a lot by comparing what you told the system to produce (commanded AFR) and what it actually did produce (AFR).

What you do with it is the important part, which is what kodename47 was referring to, what would you do with it?

[mid_life_crisis]

Originally Posted by s2d4

What you do with it is the important part, which is what kodename47 was referring to, what would you do with it?

Don't ask me. I'm not going to even start to delude myself that I have any business making changes to the tune on one of these things. Some things just make sense, and I believe the information mentioned earlier would be dead useful to someone who knows what they are doing, but I'm just not that guy.

[Kodename47]

Well here's the sort of tools I've created to use to look at the data. This is after some filtering though to clear erroneous data. This is just OL changes. I've already taken into account the LTFT, in this case it's 0 anyway. If you have a LTFT set, fill the AFR column with (100 + LTFT)/100 x Actual AFR (from the log)

Data table:



Comparing original MAF scaling to those derived from the calculations (Resultant MAF):



And a MAFv vs RPM chart. This is useful to know where you are hitting certain MAFv and so you can correlate to CL MAF scaling.

[Shiv@Openflash]

Hi guys,
Quick FYI for those who plan on purchasing an OFT soon: We have less than 20 in stock as of now. New stocking order probably wont be arrive until end of next week so if you want one to ship the same (or next) day you order, we advise ordering soon. We expect to be out of stock within 24hrs.

[Andrew025]

Originally Posted by troek

ahh thanks, i guess i figured the OFT side of the cable was OFT specific. but i didnt even realize you could extend it on the obd side. i was just thinking of a single longer cable.

I've got a right angle one and tuck it into the trim.