OpenFlash Tablet: OTS v2.0 Beta (132 new maps, 12 new XMLs) Available for Download

[riboyster]

I don't think anyone here would endorse cruising at 7300rpm though.

[steve99]

Originally Posted by justinco

Sorry if I missed it somewhere...but, does OFT "smooth out" the rev-limiter by chance? For example, if I am in 2nd gear and hit the rev-limiter, will it "bounce" off the limiter by cutting fuel/spark (or whatever it does to cause the bouncing off the limiter)? Or, will it cruise along smoothly at the limiter with no bouncing?

Thanks!

It wont bounce its soft rev limiter, it uses ignition retard then fuel cut, it will just sit at the limiter

[riboyster]

Hey Steve, could you take a look at todays charts when you get a chance? Updated the post with my dyno chart on it with the new links. Kinda scared. I don't think my car is detecting knock or lowering IAM.

[JB86'd]

Originally Posted by riboyster

Hey Steve, could you take a look at todays charts when you get a chance? Updated the post with my dyno chart on it with the new links. Kinda scared. I don't think my car is detecting knock or lowering IAM.

How many miles do you have on the latest tune? The car won't register FLKC or lower IAM for a while after flashing. Also, why are you scared? Your AFR looks pretty spot on and LTFT is in good ranges on that recent 2nd gear wot run.

[riboyster]

Plugged it in while driving yesterday at some point and got a CEL, had to clear. So I'm thinking it isn't yet listening for knocks. Scared because my torque curve is acting different than it did yesterday (specifically around 7k)

Yesterday = Blue
Today = Red.
I think I need to wait for it to pull some timing again before I can accurately log stuff.

[JB86'd]

Originally Posted by riboyster

Plugged it in while driving yesterday at some point and got a CEL, had to clear. So I'm thinking it isn't yet listening for knocks. Scared because my torque curve is acting different than it did yesterday (specifically around 7k)

Yesterday = Blue
Today = Red.
I think I need to wait for it to pull some timing again before I can accurately log stuff.

Okay, don't plug in the tablet with the car on, or even key turned because it causes communication errors and CEL. You let it idle for a minute before touching throttle right? Drive for 60 miles to learn fuel trims then do another log.

Also, are you doing these logs in the same exact place at similar temperatures? I wouldn't read into a virtual dyno too much. The datalog is whats important.

[riboyster]

Sounds good. I've already got my corrected timing .bin from yesterday's results ready. Just wanted more data before I commit to a flash

[Kodename47]

Unless you're using Virtual Dyno on the same road under similar conditions it is, essentially, useless. I note that one of your pulls is labelled as downhill so that immediately renders it unreliable (in VD at least).

@JB86'd what do you mean that FLKC isn't immediately active? AFAIK so long as you're in the FLKC region it should be active, FBKC should also be the same. As far as I know there is no learning or similar, although I could be wrong.

[riboyster]

Originally Posted by Kodename47

Unless you're using Virtual Dyno on the same road under similar conditions it is, essentially, useless. I note that one of your pulls is labelled as downhill so that immediately renders it unreliable (in VD at least).

Same spot on the road, same conditions every time. Barely downhill, and I've adjusted the dyno to compensate.

[steve99]

Originally Posted by riboyster

Plugged it in while driving yesterday at some point and got a CEL, had to clear. So I'm thinking it isn't yet listening for knocks. Scared because my torque curve is acting different than it did yesterday (specifically around 7k)

Yesterday = Blue
Today = Red.
I think I need to wait for it to pull some timing again before I can accurately log stuff.

new log look good no knock good ltft afr good.

maybe you had bit of bad fuel last time ?? but all ok now

[solidONE]

Originally Posted by riboyster

Plugged it in while driving yesterday at some point and got a CEL, had to clear. So I'm thinking it isn't yet listening for knocks. Scared because my torque curve is acting different than it did yesterday (specifically around 7k)

Yesterday = Blue
Today = Red.
I think I need to wait for it to pull some timing again before I can accurately log stuff.

If you do 10 pulls on that same road back to back (this is what I do using 3rd gear on the flattest road I can find) at least 8 or 7 out of the 10 should look almost exactly the same. For virtual dyno to have any use it has to be consistent, road has to be flat, the logs used cannot have any wheel slip. 4th gear pulls will be better than 3rd gear pulls. 2nd gear pulls happen too fast to be any good, IMO. If you're only doing one single pull and converting that each time, it will be extremely inconsistent and the data useless. Any log with inconsistencies, such as sudden rpm rise due to wheels slip, are throwaways and useless.

Good luck!

[justinco]

Originally Posted by riboyster

I don't think anyone here would endorse cruising at 7300rpm though.

Nor would I. Specific use case is for autocross, where sometimes I momentarily have to be on the rev-limiter where shifting doesn't make sense.

Originally Posted by steve99

It wont bounce its soft rev limiter, it uses ignition retard then fuel cut, it will just sit at the limiter

Thanks.

[JB86'd]

@Kodename47 That's my bad, I meant IAM will not drop immediately after, although FLKC may still be active and learning.

[riboyster]

Not sure that it's learning or active. The only indication I have that it is active is that it's transmitting a single value for the duration. It won't move on my trouble areas yet, so there's definitely nothing to learn.