Bucking on throttle application?

[steve99]

Originally Posted by Mr_Eyo

I don't see it in the OFT defs.

Thats because the defs dont have those tables

But i dont think thats your problem, switching between pi and di is usually seemless unless you have messed with the scaling or pressure tables. and you dont appear to have an AFR issue

your last logs show your ignition timing going to "0" or "2" degrees when on throttle transients like changing gears, normally this would be arround +10 degrees as a minim

you may have adjusted something in tune thats causing this like transient retard settings or have some very strange ignition maps.

https://datazap.me/u/protoformx/log-...5209&mark=5115

[Mr_Eyo]

Originally Posted by steve99

Thats because the defs dont have those tables

But i dont think thats your problem, switching between pi and di is usually seemless unless you have messed with the scaling or pressure tables. and you dont appear to have an AFR issue

your last logs show your ignition timing going to "0" or "2" degrees when on throttle transients like changing gears, normally this would be arround +10 degrees as a minim

you may have adjusted something in tune thats causing this like transient retard settings or have some very strange ignition maps.

https://datazap.me/u/protoformx/log-...5209&mark=5115

The OTS transient retard tables have nearly the same magnitudes as the advance table, so transients do cause timing to drop quite a lot. How much retard can I remove from the table safely?

[steve99]

Originally Posted by Mr_Eyo

The OTS transient retard tables have nearly the same magnitudes as the advance table, so transients do cause timing to drop quite a lot. How much retard can I remove from the table safely?

If your using standard values in the transient tables and the associated trigger tavles then that may not be the issue as everyone would experience that.


Look at what you have changed , stuff lioe adding exhaist pops can also do that.

[Mr_Eyo]

Originally Posted by steve99

If your using standard values in the transient tables and the associated trigger tavles then that may not be the issue as everyone would experience that.


Look at what you have changed , stuff lioe adding exhaist pops can also do that.

I don't have anything like that changed. I also notice a drop to 0 deg ignition timing after cold start after about 70 seconds. Fueling mode goes from CL to OL at that same time. I wonder if that is an instance of transient response retard kicking in.

[steve99]

Originally Posted by Mr_Eyo

I don't have anything like that changed. I also notice a drop to 0 deg ignition timing after cold start after about 70 seconds. Fueling mode goes from CL to OL at that same time. I wonder if that is an instance of transient response retard kicking in.

Ignition timing poxt start waemup phase is set to 0.04 ie 0 degrees in oft v4 tunes so thats normal. Car will cold start in open loop till o2 sensor warms up then go closed loop again normal.


Load a stock tune into car if your on petrol , see if you get same issue. This will tell you if its tune or hardware

[Mr_Eyo]

I haven't tried returning to stock because I haven't had time and I don't really want to considering I haven't changed anything substantial in the tune. I did some searching and stumbled on this old post talking about a TSB that resulted in retard being added to mitigate the knock/DI seal destruction issue when shifting at high loads. The icture of the transient retard table is waaaay different from the one in OFT OTS v4.03. Which table is it supposed to look like? Looking in my logs, it's pulling ~20 deg per upshift.

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


OFT v4.03:

<table type="3D" name="Transient Ignition Retard" category="Alpha - BRZ" storagetype="uint8" endian="big" sizex="7" sizey="24" userlevel="4">
<scaling units="Ignition Timing Correction (degrees)" expression="(x*.3515625)-50" to_byte="(x+50)/.3515625" format="0.000" fineincrement=".2" coarseincrement="1" />
<table type="X Axis" name="Engine Load" storagetype="float" endian="little" logparam="E32">
<scaling units="g/rev" expression="x" to_byte="x" format="0.00" fineincrement=".01" coarseincrement=".1" />
</table>
<table type="Y Axis" name="Engine Speed" storagetype="float" endian="little" logparam="P8">
<scaling units="RPM" expression="x" to_byte="x" format="#" fineincrement="50" coarseincrement="100" />
</table>

[tomm.brz]

that table is identical to stock >my17, subaru made it really aggressive probably to eliminate totally knocks on transients
it s a bit up to you, you can reduce it to improve driveability but then you must accept the risk

[Mr_Eyo]

OK, that helps a bit. I'm confused though that transient retard is near 0 for high load at all RPMs. I thought knock was very bad at high load & RPM.

For tuning these down, can I just gradually decrement them and just watch AFR and knock correction? Or would it be much harder to monitor for?

[steve99]

Originally Posted by Mr_Eyo

OK, that helps a bit. I'm confused though that transient retard is near 0 for high load at all RPMs. I thought knock was very bad at high load & RPM.

For tuning these down, can I just gradually decrement them and just watch AFR and knock correction? Or would it be much harder to monitor for?

Transient retard is mainly for when your full throttle high rpm then you lift off to shift , the "load" is not rearly load its a derived parameter from rpm and air flow. But as you lift off quickly the load drops hence the ecu wouod normally increase timing as per the ignition tables, but if its considered a transient ie its passed the checks in the transient retard section the transient retard table becomes active and reduces timing.


Now usually at low loads your running say 30 or 40 degrees advance but if transient retard is active it will subtract that value and you should end up with about 10 degrees advance.


But for some reason your getting zero


Did you change any of fhe activation ot threshold tables

[Rezi]

Personally i wouldnt recommend to dig at the trans ign retard table around for this issue.
Copy the "minimum cfp delta for trans ign retard" from the MY17 over onto yours should solve the issue for 99%.

I had the same.

[tomm.brz]

Originally Posted by Rezi

Personally i wouldnt recommend to dig at the trans ign retard table around for this issue.
Copy the "minimum cfp delta for trans ign retard" from the MY17 over onto yours should solve the issue for 99%.

I had the same.

That was nice to know.. i never paid attention to this map and always kept the lower values of ots maps. Tried it today and going back to stock my17 improved a lot the driveability for me
thanks

[Mr_Eyo]

Originally Posted by Rezi

Personally i wouldnt recommend to dig at the trans ign retard table around for this issue.
Copy the "minimum cfp delta for trans ign retard" from the MY17 over onto yours should solve the issue for 99%.

I had the same.

Soooo... I have the USDM MY17 AT, downloaded the ROM from the car when marrying the OFT, and the v4.03 def I got for it from OFT (OFTv4_ZA1JK00D.xml) can't read it in RomRaider...

1. Where can I get a def that works?
2. In the meantime, what are the 8 factory values in the table if you have them handy?

Thanks guys.

[steve99]

Originally Posted by Mr_Eyo

Soooo... I have the USDM MY17 AT, downloaded the ROM from the car when marrying the OFT, and the v4.03 def I got for it from OFT (OFTv4_ZA1JK00D.xml) can't read it in RomRaider...

1. Where can I get a def that works?
2. In the meantime, what are the 8 factory values in the table if you have them handy?

Thanks guys.

their is no opensource def for K00D

you oft K00D rom is actually an K01I rom internally

[Mr_Eyo]

Originally Posted by steve99

their is no opensource def for K00D

you oft K00D rom is actually an K01I rom internally

So where can I find the stock min CFP Delta retard table if I can't read my own stock ROM?😢