So far we have a means of display individual tire air temp since it is something that I can log on my Autoenginuity tool. And if I can log it with a tool, I an emulate it with the OFT. But what tool are people using to monitor individual tire pressure? If i can get access to this tool, I can add these features into the OFT in a matter of hours.

-shiv

Found one glitch with the new template when doing real time data, if you ONLY select Adv Multiplier to show, it will show the correct value of 1.00, however if you try to add another 1 or 2 other options (MAF, KC, etc.), the Adv Multiplier value bugs out and shows a constant 0.00 even though in reality it is still at 1.00. @Shiv@Openflash

Indeed :) There is currently a bug that sometimes makes the last 2 (now 13th and 14th) channel in the realtime display bug out, regardless of what those channels are. To avoid for now, just view up to 12 channels. Should have it resolved by Monday or Tues.

[quote=Shiv@Openflash;1972321]FRS page too.
Shiv
PS. This is the strangest software release thread i've ever read.[/quote]



Strange or not, as a business you should take the critic on board instead of making excuses.

Your web site should not require fancy refresh to get the information.
At the time of my posting about MX5 that is where the file was using navigation that average person uses...

Steve, I don't care for your comments, so best you stay on your side of the fence and I will do the same.

I am sorry if I have upset the status quo and the brown noses on here.


On this note Goodbye and the END.

Its nothing fancy at all, anyone that has access to the internet, and especially tuning a vehicle. Should know how to use the refresh button on their browser (F5).

Updated OFM to v1.11.1 and updated the template last night with no problems.

Today I connected oft to download recent data log and went
back to car and reflashed with different tune. After the reflash, I tried view
realtime data display, and guess what :) it stuck. lol
I was little worried for few minutes if I screwed up something, but other
features of oft did look working fine so I checked if there was any new
template released. Of course there was~ what a dum mistake I made~ lol

Now Im really happy with this recent update~~~ :)
Thanks to Shiv and Vishnu tuning~

I guess that's why when i tried to add displayed gear to the 12th position, it always said I was in 2nd? I changed it to display vehicle speed and it worked fine.

I haven't tested the latest FW and template update, but I have a complaint about the update process...

Why does the update window force itself to be in the foreground? It's slightly annoying to have a window covering up anything else I'm trying to do.

I jusr cover it with my hand

Been experiencing some bugginess with the new OFT template. If I go from the regular 14 channel display to the 3 channel display more often than not the MAF voltage will freeze at 0.00v. Although I'm really liking the extra channels. Now I can do more with one single log.

I think that would be useful information for those of us who AutoX and track our cars and need to keep an eye on real-time pressures and temperatures of the tires...make it happen captain! You're my hero Shiv!

BIG +1 for individual tire pressures. Oh my god that would make it much more attractive for autocross and track guys alike.

Just used the new features for an autocross event. Super handy (especially the sleep mode). Thanks a bunch for the continuing updates.
@rcampici - While your concerns are valid, your method of delivering them was a trainwreck. No fanboys here, we all just really appreciate some of the best customer service I have seen in the "aftermarket performance" industry. Your temper tantrum looked pretty childish and some basic problem solving would have cleared up any issues shortly after they took place. Countless people send Shiv emails all through the day and night and you didn't acknowledge how fantastic he is at tending to all of us at once 24/7/365. Why I am even addressing this is because anyone who is considering this device to purchase shouldn't read your words and take them as the norm.

Awesome to see an auto-sleep feature. Now I don't have to keep unplugging it.

Question, does it resume to the last opened screen when it "wakes", or does it go back to the home page?

@TM /\ If you watched the video it would show it resuming.

IIRC, it goes back to same screen before sleep. I think it demonstrates in the video in OP.

OK I would like to know more about this OFT 350 coming soon. Any leaks? What is it? FI?

http://www.ft86club.com/forums/showthread.php?t=59178

Probably a more aggressive version of that.

Nope.. it's a turbo :)

Sbd?

OMG @ this thread :|

Request: can any of you who have completed the recent update and have ref lashed your ECU after the update please post some wot pulls logs showing flck? My car has not been running the same since I reflashed after updating the oft showing a large amount of flkc appearing as large spikes in the logs. Thank you!

http://www.ft86club.com/forums/showp...6&postcount=95

i had something very similar happen, it turned out to be my exhaust hitting my fuel tank right before the the diff. if youve never had knock before, and running the same fuel. itd be worth checking out.

Yeah that is something I will definitely look into. I figure if someone posts a log after updating the oft that is clearly the same as before the update then I will have ruled out the new update for causing the problem. As far as I know the fuel should be the same. At very least from same gas station. I'm running stock header and cat-back so there shouldn't be any issue with those. Only difference is that the weird flkc happened after flashing with the updated OFT with a very slight change in the maf temp compensation table that should have little to no effect on knock. All else was identical pre weird flkc logs.

Edit: I went ahead and did a once over on every single exhaust fastener and made sure it wasn't hitting anything and everything is torqued down properly, reflashed a modified tune earlier today since it was still more knock resistant vs the OTS tune then took a log:
http://datazap.me/u/solidone/stg1-20...4&zoom=136-406

Still with the spikes of flkc. As I saved and uploaded the above log the OFT auto updated. I removed my oil catch can, just to rule that out as a possible cause. Went and took another log. This time the display was obviouly more glitchy than before with knock correction stuck at -.68 most of the time and the flkc hanging at -.39 even with 0 throttle input coasting...
The following log here: http://datazap.me/u/solidone/stg1-20...zoom=2667-2930

What say you,@Shiv@Openflash?

out of curiosity what did you modify to reduce the knock between those 2 data logs? im still learning about all this stuff but it seems weird to see knock all the way across the rpm range.
Taken from http://www.zzperformance.com/blog/ab...ock-retard-kr/
"False knock is characterized by a sharp spike to an immediately high value of KR followed instantly by the KR Recovery Rate. It doesn’t grow with engine RPM or load, it jumps to a high value on throttle input and then recovers to a low value, or zero perhaps, as engine RPM continues to increase. Note that this is exactly opposite to the characterization of REAL KR. Remember, knock is simply specific noise detected by engine microphones. Because it happens to fall with in the frequency of real KR does not necessarily mean that it IS real KR."

Only difference between the two logs is an oil catch can, same tune same condition same day same road and taken no more than 30 minutes apart.

Notice how the FLKC registered increases after each up shift.
The below log was made runing pretty much the same exact tune in very similar conditions (slightly cooler ambient temps) before the OFT update aside from slight difference in the MAF scale.
http://datazap.me/u/solidone/stg1-20...-12&zoom=3-311

Very helpful link BTW. Thanks. None of the hardware was touched from this log vs the more resent logs in my last post, so I'm not sure where I could have something causing a false knock...

have you flashed back to a tune that had no knock and logged that?

So I found a bug with the new update, not a big one though. If I leave the OFT connected in realtime display mode, the next time I start the car it reports IAM of 0 or 0.01... If you tap it though it shows one and then when you go back to the full list it shows as normal.

As I said, not a big bug but I had a chuckle the first time I saw that my IAM was 0...

That was the most knock resistant tune I have right before the update. If I did not up shift while WOT, like how most people seem to do it, there would have been no knock registered. And it's what I've reverted back to from the OTS tune currently.

Certianly seems a strange co0incidence

maybe log
KC Learned
FLKC (the problem one)
Ignition timing total

You should see a corresponding drop in KC Learned and Ignition timing total when FLKC goes negative. If their was a weird logging issue then it should show up. if FLKC goes -3 their should be corresponding dip in KC learned and Total Ignition timing applied.

logging is done by the OFT software asking for the contents of a specific RAM address in the ECU a scaling factor may then be applied and the result is presented in the log. Each ROM type ie C/G/A ect and sometimes the different revisions of those ROM's will have different locations for these RAM addresses ,its possible something is wrong but everyone on same ROM would have the problem. But it may not be a universal issue for all ROM types.

I doubt they have changed anything in the Flashing side of things and if that was out of wack the FLKC would be the least of your problems. The OFT corrects the checksum and I would imagine then checks the checksum of the flashed ROM and would throw an error if that was incorrect. If the flash was bad its likely the car would not run.

As @troek said you can trigger false knock indication from loose bolts or a washer or similar dropped down near knock sensor or exhaust hitting on sub-frame ect

Wasn't able to capture much flkc spikes aside from 2 little .65 in 5th gear I was not aware what was actually going on looking at the OFT display as the flkc decided to freeze at .65 and kc at .68 seconds after I started to log... will try again in warmer weather or get my oil temps hotter before I start next time. or maybe reflash the more knock prone OTS tune.

http://datazap.me/u/solidone/stg1-20...0&data=1-12-14
No changes were made to the car or tune since yesterday BTW.

seems to correspond when you get the fLKC, KC learned drops so logging looks ok

http://datazap.me/u/solidone/stg1-20...4&zoom=236-548

The KC Learned also looks like it stayed dropped even after flkc has come back up to 0. Does not that indicate that there should still be some flkc than what is showing in the log? Thanks @steve99! :)

http://datazap.me/u/solidone/stg1-20...5&mark=377-386

That knock is very minor anything 0.7 or less no rearly anything to worry about

I cannot say I understand the exact working of the knock control system but the FLKC and FBKC you see are the result of some complex calculation the ecu does based on input from the knock sensor.

Then it appears further calculations/timers ect are done/applied and these FLKC detections are applied to the timing for a period of time. sometimes you can see positive FLKC as the ecu returns timing. FLKC appears to be applied to the total timing almost instantly and removed soon after probably if certain condition met

since the OFT interrogates the ECU at about 5 times a second its possible it may miss some FLKC events, I generally see all events when logging with tactrix at about 20 times a sec

FBKC seems to be the input to the coarse correction calculation and if certian levels and frequency of FBKC occurr then the IAM is adjusted according to the level and frequency of the FBKC detections. Some time later if no or less FBKC is detected the IAM will start to climb towards one again. This is just what I have observed and deduced after reading the romraider explaination's and may not be 100% correct.

As I understand it the FBKC and FLCK are events or detections by the knock sensor then the ecu decides what its going to do based on the level and frequency of those detections and what knock correction mode the ecu is working in which aparantly switches so rapidly it can appear to be operating in rough/fine correction mode togeather.

their is aparantly a fine learning table FLKC in ecu ram similar to this for wrx

http://www.romraider.com/forum/downl...7870&mode=view

Their is some explanation on this over at www.romraider.com (subaru knock correction) its for WRX but appears to hold true for our ecu's

Yeah nothing in this las log has me worried, it's how my logs went from looking like this: and this to something like and this with the main change being updating of the OFT.

Thanks for the heads up. We just fixed this (and a few other minor bugs). The updates should be released to all by the morning :)

Cheers,
shiv

Check this out: http://datazap.me/u/solidone/stg1-20...k=983-963-1027

Several spots where there was drop in KC learn without any corresponding FLKC or Knock Correction values...

Everything seems to point to error or problem with the latest OFT update. Not to be a ****, but I would have appreciated a response from @Shiv@Openflash. Thankfully we have @steve99 to help. Shiv really ought to pay you for what you do on this forum for OFT users. Instead, customers like myself get ignored, and he only responds to whatever he feels like. WTF, yo?!

That does look suspect, i wiil try logging my rom with tactrix and oft and see if it looks ok but i am on a different rom and it may be ok on my rom, wife has "stolen " the car again so might be a while.

try emailing that stuff to shiv at openflash

FYI I've emailed shiv before without response. Just not about this recent issue.

@Shiv@Openflash Hey shiv was able to swap over no problem to the new template, I recently picked a phantom ESC, and I am currently running your 2.0 w/1.5 dump E85 ESC UEL Headers Tune, I'm using your boost monitoring tool but its starting at -8.6 psi at idle rather than around 0 , I thought this just might be off 8 psi, but then I did a few pulls and was getting down to -1.8 psi and I am fairly certain this setup isn't capable of making 6.8 psi, I tried turning the car back off and unplugging to reset a few times, but it didn't, I figured I give you a heads up and see what you thought, could be a bad sensor but I will let you know if anything changes over time