New Stage 2 UEL (91-93 and E85) OTS tune files

[RedFRS4me]

Originally Posted by steve99

The front 02 is used as the primary sensor for fueling. however the rear o2 is used for some fuelling adjustment during cruise and to detect if cat in header is working.


The ECU compares reading from front and rear 02 sensors to work out if cat in header is working, if it detect abnormal readings it will set CEL code P0420.


your problem sounds similar to this guy who did not install rear 02


http://www.ft86club.com/forums/showp...59&postcount=9


many people have damaged their sensors using excessive force to remove or install them in new headers, best to run a thread tap through new header bungs M18 by 1.5mm pitch.


In the stage 2 tunes P0420 is disabled so you wont get it. On stock tune its enabled, so you may get it or may not

I see. Good info to know. I just find it odd that I've been running the OFH for almost a year and only this past weekend did I get this issue. Coincidently it happened when i decided to swap from e85 to the new OFH tune and went on a 800 mile trip that I saw this for the first time. I'm pretty anal about my readings when I switch them and it just baffled me. What's also weird is it only happens if I'm cruising on the hwy (about 65-75) for longer than 30 minutes, I start noticing the AFR drop and my STFT stop working. If i'm driving in intervals of 10-20 minutes it doesn't go haywire at all and everything is good.

[Dru670]

Originally Posted by Wayno

That is NOT the OTS timing map. It's targeting way too much ign adv than the OTS map does. What's displayed there is closer to the E85 timing map.

Can you provide that info showing a comparison of this MAP and the MAP you are referring to? This map is the OTS v2.076 / ZA1J___C ROMS (US 6MT) / Stage 2 UEL - 91oct / Stg 2 UEL F00C.bin

Thanks.

[steve99]

Originally Posted by RedFRS4me

I see. Good info to know. I just find it odd that I've been running the OFH for almost a year and only this past weekend did I get this issue. Coincidently it happened when i decided to swap from e85 to the new OFH tune and went on a 800 mile trip that I saw this for the first time. I'm pretty anal about my readings when I switch them and it just baffled me. What's also weird is it only happens if I'm cruising on the hwy (about 65-75) for longer than 30 minutes, I start noticing the AFR drop and my STFT stop working. If i'm driving in intervals of 10-20 minutes it doesn't go haywire at all and everything is good.

When stft goes to 0 it usually indicates open loop fueling mode, open loop is usually during hard acceleration and wot.

if your jist cruising on highway then your usually in closed loop fueling mode and stft should be varing and commanded afr and afr should be very similar.

sounds like something weird is happening and ecu is going into full time open loop, it might be because of the rear 02 sensor or exhaust leak or something else not sure

if the logging is set up for your rom the oft can monitor the rear o2 sensor its labeled in oft log as "wideband AFR", its actually calibrated for use with an aem wideband sensor but it should give you some idea if the rear o2 is actually working.


if you had to use excessive force on sensors to install then in header it can damage them, if they are not screwed in all they way they can leak causing weird issues as can exhaust gasket leaks

[tdotBRZ]

Originally Posted by Dru670

where do I get these templates? when I first got the OFT it didn't have the "G-Meter/Performance Driving Pack" data display/logging channels but I guess it automatically updated itself when I was gonna upload some tunes and now all those other data display/logging channels are appeared in the OFT.
When I'm on the OFH tune all the data stuff are working/reading/reporting fine tho.

I don't see them posted on the site anymore since they switched to the new site interface, but I think someone uploaded it the latest 7.2 template in this thread or the other OFT one. Try to find it, if not I can post it up tonite when I get home.

[BurnetRhoades]

Wouldn't the best way to get them be install the latest OFM which auto-updates itself, install the latest batch of flashes from last month and be golden, at least for knowing you've got the correct baseline stuff???

[RedFRS4me]

Originally Posted by steve99

When stft goes to 0 it usually indicates open loop fueling mode, open loop is usually during hard acceleration and wot.

if your jist cruising on highway then your usually in closed loop fueling mode and stft should be varing and commanded afr and afr should be very similar.

sounds like something weird is happening and ecu is going into full time open loop, it might be because of the rear 02 sensor or exhaust leak or something else not sure

if the logging is set up for your rom the oft can monitor the rear o2 sensor its labeled in oft log as "wideband AFR", its actually calibrated for use with an aem wideband sensor but it should give you some idea if the rear o2 is actually working.


if you had to use excessive force on sensors to install then in header it can damage them, if they are not screwed in all they way they can leak causing weird issues as can exhaust gasket leaks

Ah I was wondering about that wideband O2 in OFT. I'll make sure I log it on my next trip. As of now I can't get it to go stuck on open loop. I'll have to make a 1 hr trip somewhere to monitor it in the near future. In town it seems to have stayed ok for now. When I first installed the OFH the O2 sensors came out and went back in well. So I'm not sure if I damaged them.

[ray7792]

Hey can someone help me out please.
CAL: A00D
OFT currently states: B01D

I installed the stg2 OFH tune for A00D yesterday. Drove around at night and this morning. Just now, on the way home from work, my car went into limp mode while I was exiting the highway. I now have a permanent CEL that the OFT cannot detect and clear.



OFT was plugged in at the time, logging. Of course the log did not save. Would knocking the connector slightly loose causing it to go limp possible?

Any idea as to how to clear it without unplugging the battery. Will going back to original tune work? Do you think the tune caused some misfire or something that was responsible for sending it into limp mode?

I had a log from when I installed the new tune last night. No WOT or anything, was just staying in closed loop. Seems okay IMO. But there really wasn't any ECU learning yet since it was literally just a few minute after uploading tune.
http://www.datazap.me/u/ray7792/stg2...11-14&mark=NaN

I understand the risks that were present using this tune as I have revworks' UEL headers not the OFH.

Thanks for the help and your time~

[steve99]

Originally Posted by ray7792

Hey can someone help me out please.
CAL: A00D
OFT currently states: B01D

I installed the stg2 OFH tune for A00D yesterday. Drove around at night and this morning. Just now, on the way home from work, my car went into limp mode while I was exiting the highway. I now have a permanent CEL that the OFT cannot detect and clear.



OFT was plugged in at the time, logging. Of course the log did not save. Would knocking the connector slightly loose causing it to go limp possible?

Any idea as to how to clear it without unplugging the battery. Will going back to original tune work? Do you think the tune caused some misfire or something that was responsible for sending it into limp mode?

I had a log from when I installed the new tune last night. No WOT or anything, was just staying in closed loop. Seems okay IMO. But there really wasn't any ECU learning yet since it was literally just a few minute after uploading tune.
http://www.datazap.me/u/ray7792/stg2...11-14&mark=NaN

I understand the risks that were present using this tune as I have revworks' UEL headers not the OFH.

Thanks for the help and your time~

OFT only reads engine fault codes


I suspect its a code related to can buss error, possibly due to oft comms interrupting can buss at some time can happen if you plug in or remove oft when engine running. its likely P0700 or P0155 from memory.


If you have torque app and a Bluetooth adapter torque will clear all codes.


or just disconnect a battery terminal and press brake pedal then reconnect battery should clear it.


But you will reset your fuel trims and likely get the dead throttle pedal for a couple of drive cycles

[ray7792]

Originally Posted by steve99

OFT only reads engine fault codes


I suspect its a code related to can buss error, possibly due to oft comms interrupting can buss at some time can happen if you plug in or remove oft when engine running. its likely P0700 or P0155 from memory.


If you have torque app and a Bluetooth adapter torque will clear all codes.


or just disconnect a battery terminal and press brake pedal then reconnect battery should clear it.


But you will reset your fuel trims and likely get the dead throttle pedal for a couple of drive cycles

Thanks for the quick reply Steve, you're always the best!
I'll try the torque app and bluetooth obd2 thing when my brother comes back with the adapter =(

Thanks!

Edit: yep it worked, you're right. Thanks again!

[YMAA]

I'm running the OFH tune on Tomei UEL headers (rest of exhaust is stock) and a Perrin 2.75" intake. I applied the MAF scale for the Perrin intake to the tune as well. For fuel I'm using Sunoco 93.

I'm a little concerned about the amount of knock correction I'm seeing in the logs. One of them even shows some negative flkc. And two of them don't show any change in the MAF voltage, which shouldn't be possible so I just wonder if something happened during the datalogging process.

http://datazap.me/u/ymaa/log-6?log=0&data=1-3-5-12
http://datazap.me/u/ymaa/log-5?log=0&data=1-3-5-12
http://datazap.me/u/ymaa/log-4?log=0&data=1-3-5-12
http://datazap.me/u/ymaa/log-3?log=0&data=1-3-5-12
http://datazap.me/u/ymaa/log-2?log=0&data=1-3-5-12
http://datazap.me/u/ymaa/log-1?log=0&data=1-3-5-12

Think these tunes might be too aggressive for my setup/fuel?

[FRSBRZGT86FAN]

Originally Posted by YMAA

I'm running the OFH tune on Tomei UEL headers (rest of exhaust is stock) and a Perrin 2.75" intake. I applied the MAF scale for the Perrin intake to the tune as well. For fuel I'm using Sunoco 93.

I'm a little concerned about the amount of knock correction I'm seeing in the logs. One of them even shows some negative flkc. And two of them don't show any change in the MAF voltage, which shouldn't be possible so I just wonder if something happened during the datalogging process.

http://datazap.me/u/ymaa/log-6?log=0&data=1-3-5-12
http://datazap.me/u/ymaa/log-5?log=0&data=1-3-5-12
http://datazap.me/u/ymaa/log-4?log=0&data=1-3-5-12
http://datazap.me/u/ymaa/log-3?log=0&data=1-3-5-12
http://datazap.me/u/ymaa/log-2?log=0&data=1-3-5-12
http://datazap.me/u/ymaa/log-1?log=0&data=1-3-5-12

Think these tunes might be too aggressive for my setup/fuel?

I don't think fuel is the issue your IAM is at 1

[steve99]

Originally Posted by YMAA

I'm running the OFH tune on Tomei UEL headers (rest of exhaust is stock) and a Perrin 2.75" intake. I applied the MAF scale for the Perrin intake to the tune as well. For fuel I'm using Sunoco 93.

I'm a little concerned about the amount of knock correction I'm seeing in the logs. One of them even shows some negative flkc. And two of them don't show any change in the MAF voltage, which shouldn't be possible so I just wonder if something happened during the datalogging process.

http://datazap.me/u

/ymaa/log-6?log=0&data=1-3-5-12
http://datazap.me/u/ymaa/log-5?log=0&data=1-3-5-12
http://datazap.me/u/ymaa/log-4?log=0&data=1-3-5-12
http://datazap.me/u/ymaa/log-3?log=0&data=1-3-5-12
http://datazap.me/u/ymaa/log-2?log=0&data=1-3-5-12
http://datazap.me/u/ymaa/log-1?log=0&data=1-3-5-12

Think these tunes might be too aggressive for my setup/fuel?

Maf volatage problem is likely jist oft logging problem
ltft look ok

knock is lss than -1 correction and iam is 1 looks ok

[Dru670]

Originally Posted by HLHachiRoku

I was loving the OFH tune until WOT, for the most part, felt soooo smooth and made the car more alive. haha. Shiv did a great job imo. I'm going to look deeper into it and see if I can keep it maybe. I asked steve99, i'll see.

did you manage to tone down the OFH tune a bit?

[Noxcyn]

Hey guys, Im new to the whole logging thing. Correct me if im wrong. Knock happens or should be worried about if the Knock correction drops below -1 or the IAM goes above 1?

Will I need to correct anything or is this fine?

I have attached a few logs, i have noticed Knock Correction goes from 0 to -0.4 to -0.8 randomly.

I am running 91Oct (from ESSO) with the new Stage 2 tune with my OFH and Invidia Q300 Catback

http://www.datazap.me/u/noxcyn/log-1...log=0&data=2-8
http://www.datazap.me/u/noxcyn/log-1...log=1&data=2-8
http://www.datazap.me/u/noxcyn/log-1...log=2&data=2-8