Notices
ECU Flash

Disable FAA bit 9?

Thread Tools
 
Search this Thread
 
Old Oct 31, 2012 | 09:34 AM
  #1  
fireroasted's Avatar
Thread Starter
Evolved Member
15 Year Member
iTrader: (3)
 
Joined: Apr 2008
Posts: 904
Likes: 7
From: CA
Disable FAA bit 9?

Just wanted to make sure my info on the Periphery bits is up to date. I am working on timing map, and some issues logging that. Wanted to know if I should disable FAA bit 9 if I am running straight pipe on track car?

bit 09. 0=Disable Cat-Warmup ignition retard tables.
Reply
Old Oct 31, 2012 | 11:10 AM
  #2  
boosted91t's Avatar
Evolved Member
iTrader: (65)
 
Joined: Oct 2007
Posts: 723
Likes: 1
From: New Oxford, Pa
That bit will have nothing to do with the timing map at normal operating temperature. What type of logging issues are you having?

I never disabled that bit on any of the cars I tune and 99% of them do not have cats..
Reply
Old Oct 31, 2012 | 11:29 AM
  #3  
fireroasted's Avatar
Thread Starter
Evolved Member
15 Year Member
iTrader: (3)
 
Joined: Apr 2008
Posts: 904
Likes: 7
From: CA
I am working in a couple of other threads with ratsbud211 and Boostedtuning about matching my timingadv and timing map values considering knock or no knock values. One of the take aways was to disable FAA bit 10 (weird timing pull below 4k).

https://www.evolutionm.net/forums/ec...-vs-log-5.html

I backed into some things because I am trying to fine tune my timing map according to information on the 'lets see your fully tuned timing maps' thread, and doing so I noticed cruise knock. I started to tune that out by reducing timing and started noticing this other stuff about the map and expected advance not matching.

I started worrying about if I was using the wrong load formula for logging too.

I kind of got all over, so I noticed this bit and I don't have a cat in this setup, so I was thinking to turn it off. But if most never do, then its likely not a factor.

The questions started because I couldn't figure out why something like this 15 was a 12 in my map, and then if I was using the wrong load for logging.
Reply
Old Nov 2, 2012 | 04:04 PM
  #4  
211Ratsbud's Avatar
EvoM Guru
15 Year Member
Liked
Loved
Community Favorite
iTrader: (1)
 
Joined: Oct 2010
Posts: 4,286
Likes: 43
From: Watertown, NY
Any luck with your knock issue or timing issue ?
Reply
Old Nov 2, 2012 | 11:25 PM
  #5  
fireroasted's Avatar
Thread Starter
Evolved Member
15 Year Member
iTrader: (3)
 
Joined: Apr 2008
Posts: 904
Likes: 7
From: CA
I haven't resolved but it's low enough for tomorrow. Counts that is. I have pulled enough timing to feel safe on track and just got here. Laguna secs. And just came from SEMA, so i ve busy driving all over CA! I have logged on the way and cruise knock never exceeded 3. I will have tons of on track data to eval after Sunday. I'll report back when this driving marathon finishes. Thanks!!
Reply
Old Jan 23, 2013 | 04:13 PM
  #6  
fireroasted's Avatar
Thread Starter
Evolved Member
15 Year Member
iTrader: (3)
 
Joined: Apr 2008
Posts: 904
Likes: 7
From: CA
Originally Posted by 211ratsbud
Any luck with your knock issue or timing issue ?
No, not actually, unless you count progress by going backwards first. It seems to be worse, and I have completed a number of critical tests. I confirmed EGR table values zero'd out didn't make a difference.

I then tested for baseline issues, which showed significant knock at cruise and significant knock at peak torque, to make sure the behavior was still consistent it was. I then trial and error'd around with the knock sensitivity to make sure I understood how it worked. Those tests just confirmed I was masking the knock for lower values, so I put it back to stock sensitivity.

I then filled with a tank of 100 oct and that gave me mixed results. I would have hoped for no knock, or no change, but I got exactly in between so my results are not completely conclusive. All knock counts went down somewhat, which indicated 'real' knock was happening. However even with 100oct it was unacceptable levels of occasional 5s at cruise and sometimes higher at peak torque.

So octane made a difference, but didn't resolve. I have pulled lots of timing without a resolution, so now I am again looking at AFR, and have richened things up.

Does it make logical sense that too lean of a cruise area or otherwise would induce knock values?

Could it just be my valve springs rattling away (cosworth)?
Reply
Related Topics
Thread
Thread Starter
Forum
Replies
Last Post
vicore
ECU Flash
3
Mar 26, 2017 11:12 AM
fireroasted
ECU Flash
1
Aug 31, 2013 09:52 AM
Kracka
ECU Flash
339
Jun 14, 2012 03:31 PM
dimacoupe
ECU Flash
0
Sep 1, 2011 05:31 AM
Kracka
ECU Flash
16
Mar 5, 2009 07:59 AM




All times are GMT -7. The time now is 05:38 PM.