Data Logs! Post them here.

[steve99]

Originally Posted by Dru670

@Shiv@Openflash @steve99 is my car (with a 1320 Performance UEL Header) running better with the latest OFH 91 UEL tune than the OTS Stage 2 91 UEL tune? Shiv mentioned that I was getting "too much knock retard (neg FLKC) above 7k RPM" on the OFH tune but looking at the OTS Stage 2 91 UEL my FLKC is all over the place. I even went back and looked at all my other logs with the OTS Stage 2 91 UEL tune and the FLKC is averaging at -5 through the entire log but with the OFH tune it seems to be at 0 for the most part.

see my other reply check the tune ignition timing values in romraider

[HLHachiRoku]

@steve99 could i possibly work this new OFH tune to my car(or there just to much knock going on(and i don't know what else was changed), or just continue working on my stage 2 uel tune? The new OFH tune is missing tables that the stage 2 91 uel isn't. I counted them last night, haha.

Originally Posted by HLHachiRoku

So I installed the OFH tune and data logged a lot yesterday. I added commanded AFR and took out kc learned since that isn't really used to see knock and I wanted to see the difference between the two if there was much at all. I can tell you that it felt better down low, and up high. My adv mult also stayed at 1 the entire time!!! (been having issues with it dropping a ton =( Also noticed smoother revs, nothing jerky at all like in the ofs tune i was using. The car felt way more "alive" then before thats for sure. Let me know what you think of these. =D Thanks! (some of the roads were bumpy, not just a small bump, so not sure if that has anything do do with some of the cruising readings)

See below:

Cruising:

http://www.datazap.me/u/hlhachiroku/...data=1-5-11-12

This one has a bad dip of -2.55 flkc, but other then that everything is smooth from what I can see.

http://www.datazap.me/u/hlhachiroku/...data=1-5-11-12

This had a dip of knoc corr but flkc stated at 0 entire time

http://www.datazap.me/u/hlhachiroku/...data=1-5-11-12

Starting to see more flkc =o

http://www.datazap.me/u/hlhachiroku/...data=1-5-11-12

Freeway bursts:

This doesn't look good under WOT however. Not really sure what was going on, car felt super strong (when i went from 2nd to 3rd, the traction control kicked in for a bit (1st part of the polt and I had to let off and then punch it again) Adv mult stated at 1, knoc corr wasnt scary but flkc under WOT... ahhh... don't think thats good.. lol

http://www.datazap.me/u/hlhachiroku/...data=1-5-11-12

http://www.datazap.me/u/hlhachiroku/...data=1-5-11-12


This was mainly cruising, with a WOT burst. Starting to get worried about these numbers =O


http://www.datazap.me/u/hlhachiroku/...data=1-5-11-12



NEW logs today 4/17/16

What happened here?!?!

http://www.datazap.me/u/hlhachiroku/...data=1-5-11-12

-1024 knock!? everything went to 0?!.... I didn't feel anything in the car while cruising along....

http://www.datazap.me/u/hlhachiroku/...zoom=7370-7733 ZOOMED IN.... that can't be good...


http://www.datazap.me/u/hlhachiroku/...data=1-5-11-12

http://www.datazap.me/u/hlhachiroku/...data=1-5-11-12 freeway gear run through

http://www.datazap.me/u/hlhachiroku/...data=1-5-11-12

http://www.datazap.me/u/hlhachiroku/...data=1-5-11-12

http://www.datazap.me/u/hlhachiroku/...data=1-5-11-12

http://www.datazap.me/u/hlhachiroku/...data=1-5-11-12

perfect here though.. grrr lol
http://www.datazap.me/u/hlhachiroku/...data=1-5-11-12

[steve99]

Originally Posted by HLHachiRoku

@steve99 could i possibly work this new OFH tune to my car(or there just to much knock going on(and i don't know what else was changed), or just continue working on my stage 2 uel tune? The new OFH tune is missing tables that the stage 2 91 uel isn't. I counted them last night, haha.

I don't think the OFT logging is working correctly for your rom, its logging FBKC values of -1000 that's bogus and ive never seen IAM drop from 1 to 0 then back to 1 in a couple of seconds. Usually when ian drops it takes quite a period to recover as ECU wants to see no knock in the rpm range that caused problem for a much longer period.


Then in other places you getting heaps of flkc knock -5 which seems legitimate but your iam is not dropping its weird.


as @Wayno said to another guy unless this is an E85 tune the ignition timing seem way advanced, its logging ignition advance at 25 degrees with -5 flkc which seems to indicate the ecu was asking for 30 degrees advance at 7000 rpm at load 1.2. seems way to much for petrol if log values can be believed.
I think the IAM logging is bogus with that much knock it should be dropping below 1, if the knock is real.


http://www.datazap.me/u/hlhachiroku/...&zoom=868-2883


can you post up the tune your using and I will look at tables in rom if this is a petrol tune it seems "off"

[Dru670]

Originally Posted by steve99

I don't think the OFT logging is working correctly for your rom, its logging FBKC values of -1000 that's bogus and ive never seen IAM drop from 1 to 0 then back to 1 in a couple of seconds. Usually when ian drops it takes quite a period to recover as ECU wants to see no knock in the rpm range that caused problem for a much longer period.


Then in other places you getting heaps of flkc knock -5 which seems legitimate but your iam is not dropping its weird.


as @Wayno said to another guy unless this is an E85 tune the ignition timing seem way advanced, its logging ignition advance at 25 degrees with -5 flkc which seems to indicate the ecu was asking for 30 degrees advance at 7000 rpm at load 1.2. seems way to much for petrol if log values can be believed.
I think the IAM logging is bogus with that much knock it should be dropping below 1, if the knock is real.


http://www.datazap.me/u/hlhachiroku/...&zoom=868-2883


can you post up the tune your using and I will look at tables in rom if this is a petrol tune it seems "off"

What if that's just it. What if the OFT is reporting bogus or false numbers (when infact you are running fine) and you make adjustments to your tune based on these false readings and you actually start doing bad to your car? My OFT reads 0 for IAM and -5 on FLKC most of the time. The OFH rom allowed the OFT to read all the data log channels and what ever steve99 says about timing and IAM and knock might make more sense when data logged by the OFT under the OFH rom. Im new to this and im trying to make sense to myself lol

[HLHachiRoku]

Originally Posted by steve99

I don't think the OFT logging is working correctly for your rom, its logging FBKC values of -1000 that's bogus and ive never seen IAM drop from 1 to 0 then back to 1 in a couple of seconds. Usually when ian drops it takes quite a period to recover as ECU wants to see no knock in the rpm range that caused problem for a much longer period.


Then in other places you getting heaps of flkc knock -5 which seems legitimate but your iam is not dropping its weird.


as @Wayno said to another guy unless this is an E85 tune the ignition timing seem way advanced, its logging ignition advance at 25 degrees with -5 flkc which seems to indicate the ecu was asking for 30 degrees advance at 7000 rpm at load 1.2. seems way to much for petrol if log values can be believed.
I think the IAM logging is bogus with that much knock it should be dropping below 1, if the knock is real.


http://www.datazap.me/u/hlhachiroku/...&zoom=868-2883


can you post up the tune your using and I will look at tables in rom if this is a petrol tune it seems "off"

Ya when I get home tonight I'll post it, its the new ofh uel tune havnt changed anything on it yet but ill post it here.

[steve99]

Originally Posted by HLHachiRoku

Ya when I get home tonight I'll post it, its the new ofh uel tune havnt changed anything on it yet but ill post it here.

If your on F00C rom it looks like some of the logging parameters are not working correctly at least ignition timing and FLKC seems to be incorrect, as does FBKC in your logs.


Talk to the OFT guys and send them some logs.


hopefully they can identify the issue and sort it out


until they do I would not make any adjustment to tune based on the logs your taking on F00C roms

[steve99]

Originally Posted by Dru670

What if that's just it. What if the OFT is reporting bogus or false numbers (when infact you are running fine) and you make adjustments to your tune based on these false readings and you actually start doing bad to your car? My OFT reads 0 for IAM and -5 on FLKC most of the time. The OFH rom allowed the OFT to read all the data log channels and what ever steve99 says about timing and IAM and knock might make more sense when data logged by the OFT under the OFH rom. Im new to this and im trying to make sense to myself lol

correct I think the logging is "off" on F00C roms


logging uses independent parameters for each rom calid so other calid's may log ok, it likely its just related to F00C roms but may extend to some other newer rom id's


talk to the oft guys , send them some logs to show them the problems.


and yes don't make adjustments to your tune till the logging is sorted

[Dru670]

Originally Posted by steve99

correct I think the logging is "off" on F00C roms


logging uses independent parameters for each rom calid so other calid's may log ok, it likely its just related to F00C roms but may extend to some other newer rom id's


talk to the oft guys , send them some logs to show them the problems.


and yes don't make adjustments to your tune till the logging is sorted

Thanks so much @steve99 you have been biggest help I really appreciate that you make the time to respond to many of our concerns.

[HLHachiRoku]

@steve99 here is the one I uploaded. Ya I thought that was really weird of it to drop like that unless there was a MAJOR event, but I didn't feel anything of the like.

Originally Posted by steve99

If your on F00C rom it looks like some of the logging parameters are not working correctly at least ignition timing and FLKC seems to be incorrect, as does FBKC in your logs.


Talk to the OFT guys and send them some logs.


hopefully they can identify the issue and sort it out


until they do I would not make any adjustment to tune based on the logs your taking on F00C roms

[Wayno]

Originally Posted by Dru670

What if that's just it. What if the OFT is reporting bogus or false numbers (when infact you are running fine) and you make adjustments to your tune based on these false readings and you actually start doing bad to your car? My OFT reads 0 for IAM and -5 on FLKC most of the time. The OFH rom allowed the OFT to read all the data log channels and what ever steve99 says about timing and IAM and knock might make more sense when data logged by the OFT under the OFH rom. Im new to this and im trying to make sense to myself lol

As the OFT is marketing as a tuning tool and the base maps are included for free, I would suggest this warrants a refund as the tablet itself is not fit for purpose if you have a calibration code later than B01C/D00C.

As far as I can see, neither the non calid hacked F00C and the F00C hacked to B01C log correctly. If none of the data displayed can be trusted, there's no point to the tablet.

I don't think any of these hacks were tested by openflash before released to public. Maybe one or two US cals were, but not the likes of the AU/EU E00I being overwritten with older A01I.

This needs to be addressed by openflash immediately. MAFV or IAM or some other non-essential logging parameter not working is one minor thing, this is a whole other level.

You guys are at the point where you need to talk to openflash directly and get them to sort this shit out. No one here can help you if the data the OFT is spitting out is all junk.

[steve99]

Originally Posted by HLHachiRoku

@steve99 here is the one I uploaded. Ya I thought that was really weird of it to drop like that unless there was a MAJOR event, but I didn't feel anything of the like.

Ok that D00C rom is actually a B01C but that should not cause the knock you have oft guys do this calid alteration on quite a number of roms not just this one.

The ignition timing in these new OFT header maps is very aggressive as shiv said, they have added about 2 degrees of timing top end rpm 5000-7000. Your going to need very good 93 fuel to be able to run that and as shiv said its optimized for their ofh header so running a different header may also cause more problems with such an agressive map , shiv also mentioned this.


Its also likely that you IAM logging and FBKC logging and maybe some other parameters are now not working correctly.

The oft should pick up that your actual rom is a B01C and not a D00C, but maybe for some reason its not doing that. Make sure your on the latest Open Flash manager software and update oft via internet. The OFT now auto updates template, dont manually apply old templates you find on forums as it may stuff up the logging

I think the FLKC knock is likely real and you should go back to the older tunes as your fuel or header is causing that knock over 5000 rpm.

maybe talk to oft guys and get them to look at logging on the new D00C tunes as well as it does not seem right for all parameters.

[Dru670]

Originally Posted by Wayno

As the OFT is marketing as a tuning tool and the base maps are included for free, I would suggest this warrants a refund as the tablet itself is not fit for purpose if you have a calibration code later than B01C/D00C.

As far as I can see, neither the non calid hacked F00C and the F00C hacked to B01C log correctly. If none of the data displayed can be trusted, there's no point to the tablet.

I don't think any of these hacks were tested by openflash before released to public. Maybe one or two US cals were, but not the likes of the AU/EU E00I being overwritten with older A01I.

This needs to be addressed by openflash immediately. MAFV or IAM or some other non-essential logging parameter not working is one minor thing, this is a whole other level.

You guys are at the point where you need to talk to openflash directly and get them to sort this shit out. No one here can help you if the data the OFT is spitting out is all junk.

Spot on. I have been emailing shiv for the past month and he never responded to this particular issue but he did respond to other unrelated questions. Before buying the OFT I told him I had a 2016 fr-s and asked if it would work perfectly fine with it and he said yes and so I ordered from him. And so here I am getting retarded data from this OFT asking for help in the forums and being ignored by techsupport at Openflash Performance. Ain't that a bitch.

[HLHachiRoku]

Originally Posted by steve99

Ok that D00C rom is actually a B01C but that should not cause the knock you have oft guys do this calid alteration on quite a number of roms not just this one.

The ignition timing in these new OFT header maps is very aggressive as shiv said, they have added about 2 degrees of timing top end rpm 5000-7000. Your going to need very good 93 fuel to be able to run that and as shiv said its optimized for their ofh header so running a different header may also cause more problems with such an agressive map , shiv also mentioned this.


Its also likely that you IAM logging and FBKC logging and maybe some other parameters are now not working correctly.

The oft should pick up that your actual rom is a B01C and not a D00C, but maybe for some reason its not doing that. Make sure your on the latest Open Flash manager software and update oft via internet. The OFT now auto updates template, dont manually apply old templates you find on forums as it may stuff up the logging

I think the FLKC knock is likely real and you should go back to the older tunes as your fuel or header is causing that knock over 5000 rpm.

maybe talk to oft guys and get them to look at logging on the new D00C tunes as well as it does not seem right for all parameters.

I have since gone back to the old D00C stage 2 uel 91 gas tune. Being in AZ we only get 91, E85 or 100(super over priced) When i saw @Shiv@Openflash post about those OFH tunes running super aggressive. I went and checked the tune out. oooohhh boy its aggressive haha. I loved everything else about it though, as you can see from the logs, everything but WOT top end seemed normal and but that glitch. I'll be working on my old stage2 uel 91 tho, and get that dialed in, then work on my e85 as I want to try that gas out as we have more stations supplying it =D

I have let the tablet update manually when I connect to OFM 1.25.1 right from the start after DL'ing it from their site. I don't know why its not seeing that. Its always said I have had a D00C tune and states that calid on the info upon loading OFM as well. Also wouldn't let me load any other tune on to the tablet as well but the D00C. Says file not compliant for even B01C. (which i figured it would do for safety so I wouldn't brick my ecu im gathering lol) Thanks again @steve99

[steve99]

Originally Posted by HLHachiRoku

I have since gone back to the old D00C stage 2 uel 91 gas tune. Being in AZ we only get 91, E85 or 100(super over priced) When i saw @Shiv@Openflash post about those OFH tunes running super aggressive. I went and checked the tune out. oooohhh boy its aggressive haha. I loved everything else about it though, as you can see from the logs, everything but WOT top end seemed normal and but that glitch. I'll be working on my old stage2 uel 91 tho, and get that dialed in, then work on my e85 as I want to try that gas out as we have more stations supplying it =D

I have let the tablet update manually when I connect to OFM 1.25.1 right from the start after DL'ing it from their site. I don't know why its not seeing that. Its always said I have had a D00C tune and states that calid on the info upon loading OFM as well. Also wouldn't let me load any other tune on to the tablet as well but the D00C. Says file not compliant for even B01C. (which i figured it would do for safety so I wouldn't brick my ecu im gathering lol) Thanks again @steve99

if your on 91 yeah those new tunes are way too aggressive its good 93 only or better.

if you want the lower\mid rpm benifits of the new tune without the aggressive top end then grab @Wayno s 98 ron tune and port the tables accross with romraider to your d00C map, you will get the best result on 91 as its close to our 98.