OFT v2.06 Non-Beta
 

Hi guys,
On Monday we plan to release the first non-beta version of our v2.0x maps. With this release we will add support for all the other Cal IDs that are currently not support with our v2.0x beta maps. We will also disable the U0155 code (as we have always done before in our non-beta map releases). This code/CEL is triggered the OFT is disconnected from the OBD2 plug in the middle of communication (datalogging, data displays, etc,.) It's harmless but annoying nonetheless.

In additional to releasing the new maps in non-beta format, we will be preloading all OFTs with v2.0 maps prior to shipping. So now there will be no need to manually upload the v2.0 maps using your laptop. For those who already have OFTs, we will also be releasing the database file (.dev) that will auto generate all compatible v2.0 maps for you. But by now you've probably already loaded the v2.0 maps you needed anyway :)

If there is any other suggestions you have with regards to beta->non beta changes, let me know and I can look into implementing them.

Cheers,
Shiv

PS. The sales team is also running a sale: http://www.ft86club.com/forums/showp...0&postcount=21

@Shiv@Openflash which rom will the G series tunes be based on as i still having problems with the D00G rom in my late 2013 car was originally A01G , after all the U0155 issues after about an houts drive on D00G it threw a P0620 alternator start pulse could not clear, never thrown a code on A01G , flashed back to A01G based rom and no more code.

For CAL IDs that we have not been able to successful test updating-to-2015 compatibility, we are going to retail the current CAL ID base (A01_ or B01_) and just update the mapping data to what we use in the v2.0x maps. It's the safest thing to do :)

Well jeez, one week after I finally ordered one? Sigh...

Can you guys please provide a ballpark update for the OFH shipment date?

Why the Sigh?

It only takes two seconds to load the new maps. I just got my OFT 2 days ago. It didn't have the ROM for my 2015 FRS. I just downloaded the zip file from the site and loaded up the one I needed in the Open Flash Manager software.

My car runs great now!

Easy Peasy

For OFH shipping times, you need to contact their sales department and find out what number you are in line. They should be able to give you at least a rough estimate, depending on how far out you are.

He's sighing because of the sale before he's received his OFT, but after he's paid I'm guessing.

My openflash manager was unusable the last time I tried loading the dev file, so I'll stick to manually loading.

Make sure you delete all the existing tune files in OFT ( except your original tune) before you load .dev file you cannot mix tune types

It's $10 off the normal price :iono:

i have had the OFT close to the time it was first released. I have succesfully uploaded new ROMS every time an updated one was made available. its as easy as breathing.. it blows my mind that people still cant figure it out. Maybe older folks with no computer knowledge need some assistance but us younger guys? really? just download, upload to device and transfer to car. simple. glad to see Shiv back in this forum again

:) I didn't go anywhere. Just been spending a lot of time developing OTS maps for all our supported vehicles (FRS/Porsche/MX5/BMW/Ducati). Even when I'm not posting too often, I'm always lurking. And our sales team (Garrett and Robert) are always here to help as well :party0030:

Option of Oil temp reading in Celcius, Please?

That would require a firmware update (nothing to do with tune files themselves). Selecting metric vs USA is definitely on the list of things go do but it won't happen next week unfortunately.

over seas IAM and FLKC datalogging?

Shiv any plans for more FI tunes?
All I see are the ESC tunes and Im trying to decided which direction to go with my OFT :)

IAM logging for 2015 ROMs should be up and running win the next few days. FLKC will come shortly thereafter :)

Edit. They should both be functional tomorrow. Hopefully... I can't really test them myself.

We are always open to supporting for FI set ups. Currently, we only have OTS map support for Vortech, SBD Turbo and Phantom ESC. It's just a matter of time before we support more. But for that to happen, we need to be given a car for a couple of weeks. And most people can't do without their boost FRS for that long :)

@Shiv@Openflash One enhancement I'd really like to see is some way to save the channels I want to monitor and log.

You can do this already. Once you configure your channels in the configure channel menu, your selections stay persistent until you go back in there and change them.

But next time I plug in the OFT I need to select the channels again. Am I forgetting something?

Mine stays until i change them, no matter what.

Probably just my unit then.

On another note, I've been able to log IAM and FLKC with my 700G ROM for some time, still no FBKC though.

I noticed the same thing, but only once and I think it was because I did a firmware flash or update or something like that.

U have the latest firmware installed and latest oft? And as far is iam, its gona be fixed shortly as per shivs earlier post.

should work if you are on G rom as it works for me. you will actually be on an A01G rom as the oft guys base their tunes on latest rom even though your original was 700G.

Try deselecting all the channels then re selecting. Also as @troek says make sure you are on OFM V1.10 and then plug in oft to computer let your OFT update when connected to PC and internet.

mine now remembers channels as well

Yup, latest firmware, latest OFM with v2.0 ROM baked up by steve99.

hmmm I'm running that rom and its logging iam flkc and Knock Correction (FBKC) all ok

Yeah just noticed FBKC worked: http://www.datazap.me/u/akyp/stg-1-v...zoom=3913-4081

Didn't notice it the first time I read the log, since it only dropped once.:)

I will try messing with the channels and see if they are memorised.

Edit: Come to think of it I haven't updated the template file for a while, so I'll do that first.

This might be a stupid question, but for those of us running a 2.x beta rom, any reason to update?

Shiv,s 2x tunes are much better knock wise and i pulled a bit of timing in problem areas for 98 ron fuels so the amount of fbkc or flkc will b verry little hopefully :)

During the beta I keep getting code p2096, due to my after market header. Is that code now disabled? Tired of always plugging in my OFT and clearing it.

Wait, is this true? I deleted one of the 1.x 93 tunes and replaced it with a 2.x 91 tune (and renamed it so it'd be obvious). But everything else was 1.x. If it didn't flash a 2.x, then what the heck am I currently running?

The code that is disabled for catless headers is P0420 Cat efficiency.

The code your getting is P2096 post catalyst fuel trim system too lean .

You may have exhaust leak did you use new gaskets when headers installed.

Are you running stock intake as you may get this code if fuel trims are high due maf scaling off. could also be leak in intake after maf sensor or maf sensor gasket.

I think you got the wrong end of the stick mate :D ,as we say over here.

I'm talking about .bin format (editable full format tunes) tunes and .dev database format non-editable tunes.

Not tune revisions like 1.5x or 2xx ect you can mix those no problem. but oft will only hold either all .dev format or all full format .bin tunes at any one time.

Yea I installed new gaskets when I installed the header.I have 0 leaks, Funny thing is the previous tune didn't give me the code. I'm running the TRD intake. Going to take some logs maybe you can let me know what's happening.

@Shiv@Openflash,
do we need to re-upload non-beta map if we already have beta?

Read first post appears only change is to disable CEL code U0155 can buss comms to dash panel error code no tunning changes aparantly. If you can put up with clearing that cel if you plug/unplug oft while car running then all good

hey steve when you get a chance can you let me know if you see anything in my log that might point out the reson im getting that code. thanks!
http://www.datazap.me/u/juanito08/206log?log=0&data=1

That log looks fine your LTFT is only around 3% max so thats good
Your AFR look fine and appears to be folowing the Open loop fuel tables well

P2096 is a lean condition and that log is not showing it but it could be an intermittent exhaust or, intake leak near maf sensor or downstream of maf sensor . check that as well as exhaust flanges near O2 sensors

The AFR is based of the readings of the front 02 sensor, but its likely the rear O2 sensor that causes code p0420 and p2096 or the difference in readings of the front and rear 02 sensors.

As you have an OFT you can monitor the rear O2 sensor as well by selecting WIDEBAND AFR log parameter the scaling might be a bit off as your supposed to install an aftermarket sensor., but for the purpose of checking the rear 02 sensor it should work.

I just tried it on my car and the front and rear reading move in sync once the sensors are warmed up

do another log and log

Wideband Afr
afr
afr commanded
ltft
maf v
rpm engine speed
throttle
fuel pressure

the afr , wideband afr and commanded afr should all follow each other. The second 02 sensor appears to take a couple of minutes to heat up and produce a reliable signal.
If you definitly dont have any intake or exhaust leaks its possible the rear o2 sensor may be damaged or not working properly or cross threaded loose cable not plugged in correctly ect.

is the p2096 code permanent can it be cleared ?

So we're going to be getting v2.06 maps on Monday- sweet! I just have one minor and probably redundant question but, will there be much of a difference from the v2.03 and the v2.06? Please excuse my ignorance, as I haven't caught up to recent updates since the release of the v2.03 maps. Even with that said, I'll probably still load my car up with the v2.06 map and boot out the v2.03 map that I'm currently running, just to be safe and updated.