OpenFlash Manager v1.08.3 now available for download (FLKC)

[Shiv@Openflash]

Originally Posted by Boofneenee

Taking advantage of the new flkc data logging feature.

Here in this log I see flkc occurs on the highway at a certain rpm.

http://www.datazap.me/u/boofneenee/s...og=0&data=1-12

I typically get some knock correction on the highways so I believe it makes sense to see some flkc, or does it?

Also, watch has my advanced mult. progresses its way back to 1.0. I just flashed over to E85 for the first time and I am really enjoying the drive. No tq dip is fun!

* hmm.. it appears that I did not get the most recent patch to properly display the flkc. *

You need to update to the new OpenFlash Manager (v1.08.3) in order to save FLKC data to .csv properly. Looks like you are still running an older version of OF Manager.

[Fizz]

@shiv@vishnu do you have an ETA on FLKC for your Aussie customers?

[Boofneenee]

Originally Posted by shiv@vishnu

You need to update to the new OpenFlash Manager (v1.08.3) in order to save FLKC data to .csv properly. Looks like you are still running an older version of OF Manager.

ok.. updated to the latest openflash manager and the flkc is now showing properly. Looks like their is some + flkc on both of my 3rd gear pulls. I have no idea how to interpret this. Perhaps I will run another pull as now my IAM is at 1.0 where it was not during those pulls.

http://www.datazap.me/u/boofneenee/s...og=0&data=1-12

thanks

[Wepeel]

Originally Posted by Boofneenee

ok.. updated to the latest openflash manager and the flkc is now showing properly. Looks like their is some + flkc on both of my 3rd gear pulls. I have no idea how to interpret this. Perhaps I will run another pull as now my IAM is at 1.0 where it was not during those pulls.

http://www.datazap.me/u/boofneenee/s...og=0&data=1-12

thanks

Positive FLKC happens when IAM is less than 1, because there is headroom there to advance timing. Once IAM is 1 FLKC can only be negative, and indicates some perceived knock events in those load/rpm ranges. I see only very very little negative FLKC in that log, and once IAM hits 1 it doesn't look like there is any FLKC.

[Boofneenee]

Originally Posted by Wepeel

Positive FLKC happens when IAM is less than 1, because there is headroom there to advance timing. Once IAM is 1 FLKC can only be negative, and indicates some perceived knock events in those load/rpm ranges. I see only very very little negative FLKC in that log, and once IAM hits 1 it doesn't look like there is any FLKC.

I see. Positive means adding timing to be more aggresive . once IAM is at 1their is no more advancing timing based on the map in the car. Flkc will become negative pulling timing if it senses knock. Knock can be perceived as engine noise or clatter happening around the engine like gear changing so not all negative flkc is actually knock. At least this is what I understand.
Thx

[Shiv@Openflash]

Another update for you FLKC lovers, OFT should now support FLKC logging all non-USDM ROMs. Hard for me to confirm this on this end but please email me (shiv@vishnutuning.com) if you are having any problems logging

Cheers,
Shiv

[Boofneenee]

Originally Posted by Wepeel

Positive FLKC happens when IAM is less than 1, because there is headroom there to advance timing. Once IAM is 1 FLKC can only be negative, and indicates some perceived knock events in those load/rpm ranges. I see only very very little negative FLKC in that log, and once IAM hits 1 it doesn't look like there is any FLKC.

After our discussion I wanted to log a bit more to monitor the data including FLKC. Funny thing is FLKC is showing a -.5 from beginning to the end of my entire trip. I tried unplugging and plugging in the OFT a few times to see if its a glitch. IAM is reading a solid 1

here is the log:
http://www.datazap.me/u/boofneenee/s...og=0&data=1-12

Is this normal?

[Malt]

Originally Posted by Boofneenee

After our discussion I wanted to log a bit more to monitor the data including FLKC. Funny thing is FLKC is showing a -.5 from beginning to the end of my entire trip. I tried unplugging and plugging in the OFT a few times to see if its a glitch. IAM is reading a solid 1

here is the log:
http://www.datazap.me/u/boofneenee/s...og=0&data=1-12

Is this normal?

Sounds like the rounding error Shiv mentioned that would be resolved soon.

[Boofneenee]

Originally Posted by Malt

Sounds like the rounding error Shiv mentioned that would be resolved soon.

[355rockit]

Speaking of logging... what app do people use to view the .prolog files that OFT produces. The log viewer on the OFT site only opens .csv files as far as I can tell.

[Malt]

Originally Posted by 355rockit

Speaking of logging... what app do people use to view the .prolog files that OFT produces. The log viewer on the OFT site only opens .csv files as far as I can tell.

You need to goto Data logging, click read and then export to CSV instead of clicking Download LOG within OpenFlash Manager. That log file is for something completely different.

[Vmax911]

Originally Posted by Boofneenee

After our discussion I wanted to log a bit more to monitor the data including FLKC. Funny thing is FLKC is showing a -.5 from beginning to the end of my entire trip. I tried unplugging and plugging in the OFT a few times to see if its a glitch. IAM is reading a solid 1

here is the log:
http://www.datazap.me/u/boofneenee/s...og=0&data=1-12

Is this normal?

I'm getting FLKC as 0.5 for the entire run. I'm on the 700C ROM, which are you using?

[steve99]

Originally Posted by Vmax911

I'm getting FLKC as 0.5 for the entire run. I'm on the 700C ROM, which are you using?

Sounds like a scaling offset problem

if you iam is one flkc should be zero or negitive value on knock

if your iam is less than one then flkc can be positive

so if your seeing iam is one and flkc positive it some kind of scaling error

try updating your oft via ofm and ofm should be latest ver 1.08.3

[Boofneenee]

Originally Posted by steve99

Sounds like a scaling offset problem

if you iam is one flkc should be zero or negitive value on knock

if your iam is less than one then flkc can be positive

so if your seeing iam is one and flkc positive it some kind of scaling error

try updating your oft via ofm and ofm should be latest ver 1.08.3

Before I updated my manager flkc was not reading any numbers correctly. I recently updated the manager and the numbers appeared to read normal. After running an additional log I noticed the new log is showing me +.5. I agree with an IAM of 1 it should only be reporting a negative which is the result of the ecu pulling timing. Someone in this forum mentioned earlier today that Shiv made mention of this issue and that its being resolved. I can't imagine at this point the error is something I did with updates.

E85 is almost to good to be true. The engine is more sensitive and snappy. Puts a smile on my face and my logs look legit therefore it may be good to be true. Question, I noticed that my timing is holding higher numbers to redline than with petrol. As high as ignition advance 35! This is normal correct? With this higher octane fuel the additional power is available because one can run a more aggressive map I.e. more timing. Am I learning here?