Notices
ECU Flash

Need some help tuning my car, just got her back from being built

Thread Tools
 
Search this Thread
 
Old Jan 30, 2013 | 05:48 AM
  #61  
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
Originally Posted by Raptord
I go a bit leaner than that. These are my rough targets:

PSIAFR
014.7
513.5
1012.5
1511.9-12
2011.6
Is that rough target true for all rpm?
Reply
Old Jan 30, 2013 | 06:25 AM
  #62  
Raptord's Avatar
Evolved Member
iTrader: (10)
 
Joined: Mar 2009
Posts: 3,525
Likes: 20
From: Gatineau, Quebec, Canada
Originally Posted by 211ratsbud
Is that rough target true for all rpm?
Those targets are basically when I'm spooling up from 3k or so. At higher rpm I aim for the same or slightly richer. However in the map that requires slightly more pronounced changes from cell to cell since it takes less time to spool at 3k than it does at 5k.
Reply
Old Jan 31, 2013 | 11:23 AM
  #63  
tjac357's Avatar
Thread Starter
Evolved Member
iTrader: (1)
 
Joined: Apr 2009
Posts: 617
Likes: 0
From: Ohio
I'm running the knock sensitivity settings Aaron recommended. Leaned my car up a little and that help. I've been pulling a good amount of timing and it's helping in some portions but not others. I don't know how to make my timing map any smoother. Also, seems like my car is adding timing in areas outside of the EGR advance. Here's a log and current ROM. A lot better but this false knock is really bugging me.

https://www.dropbox.com/s/p9y0zhqcgq...15-IX13113.bin

https://www.dropbox.com/s/fosoacszr4...1_13.50.50.csv
Reply
Old Jan 31, 2013 | 12:13 PM
  #64  
tjac357's Avatar
Thread Starter
Evolved Member
iTrader: (1)
 
Joined: Apr 2009
Posts: 617
Likes: 0
From: Ohio
Could my car be running not enough timing? I know that sounds dumb. But I feel like I'm pulling a lot of timing.

I was under the impression a cop setup with cdi allowed for more timing to be ran not less. I understand that cams increase the amount of air which would cause less timing to be able to be ran

Last edited by tjac357; Jan 31, 2013 at 12:16 PM.
Reply
Old Jan 31, 2013 | 12:33 PM
  #65  
tjac357's Avatar
Thread Starter
Evolved Member
iTrader: (1)
 
Joined: Apr 2009
Posts: 617
Likes: 0
From: Ohio
timing and knock. afrs are about 1 pt richer than most people run but i'm still playing it safe.

Reply
Old Jan 31, 2013 | 12:46 PM
  #66  
JohnBradley's Avatar
Evolved Member
Shutterbug
Liked
Loved
Community Favorite
iTrader: (30)
 
Joined: Jan 2004
Posts: 11,406
Likes: 78
From: Northwest
looking into it right now
Reply
Old Jan 31, 2013 | 12:48 PM
  #67  
tjac357's Avatar
Thread Starter
Evolved Member
iTrader: (1)
 
Joined: Apr 2009
Posts: 617
Likes: 0
From: Ohio
You're awesome Aaron!
Reply
Old Jan 31, 2013 | 02:39 PM
  #68  
fireroasted's Avatar
Evolved Member
15 Year Member
iTrader: (3)
 
Joined: Apr 2008
Posts: 909
Likes: 7
From: CA
Originally Posted by tjac357
timing and knock. afrs are about 1 pt richer than most people run but i'm still playing it safe.

I would think that drop from 15 to 7 would induce knock, but that doesn't help you in the 20 count cell. Are the values in the pic 'maximums'? Is that 20 ish repeatable. So that you get around there in that or very near cells every time? Or does it do 10s once, 2s once, and then you think its solved and you get 20s again. (that's like mine).

If you still have your AFRs in the 10s like the older posts, I would be interested in seeing that data as minimums and maximums, and make everything at least a point leaner. If its normally consistent going 1 point leaner and see how it impacts your knock data.

Though considering the other cells, the 20 looks not real.
Reply
Old Jan 31, 2013 | 02:57 PM
  #69  
tjac357's Avatar
Thread Starter
Evolved Member
iTrader: (1)
 
Joined: Apr 2009
Posts: 617
Likes: 0
From: Ohio
here's both my afr



and boost



Those are all averages. I didn't realize that you could change what was displayed until just now. After looking at the averages they're a fair estimates of the max's and min's since it was only one pull.
Reply
Old Jan 31, 2013 | 05:15 PM
  #70  
fireroasted's Avatar
Evolved Member
15 Year Member
iTrader: (3)
 
Joined: Apr 2008
Posts: 909
Likes: 7
From: CA
Was that 20 and 16 count cell and average, Or the maximum knock you got for that log?
Reply
Old Jan 31, 2013 | 05:59 PM
  #71  
tjac357's Avatar
Thread Starter
Evolved Member
iTrader: (1)
 
Joined: Apr 2009
Posts: 617
Likes: 0
From: Ohio
It was the max. The one portion of the run knocked 3, 20, 16, 4, 4, 1. and then at the higher RPM range it was 4, 3, 8, 8, 9, 1
Reply
Old Jan 31, 2013 | 07:21 PM
  #72  
fireroasted's Avatar
Evolved Member
15 Year Member
iTrader: (3)
 
Joined: Apr 2008
Posts: 909
Likes: 7
From: CA
Originally Posted by tjac357
It was the max. The one portion of the run knocked 3, 20, 16, 4, 4, 1. and then at the higher RPM range it was 4, 3, 8, 8, 9, 1
OK, good, I see it in the log now. More a question for the guru's, but I see the WGDC goto 100 there, and it also pulls timing quickly based on that 20 count, 31 to 14. The other tell there is its your 'tip in', or what guys refer to as that, because you are just getting on your TPS there. The biggest thing I see is kind of lean at a jump to 15.5 just before there.

I also think it might help to unselect the things you don't really need for these logs. Battery voltage, fuel trims, and some other stuff won't likely tell you anything and is just hogging up bandwidth of your logging tools.

Curious if we can't get some comments from the more knowledgable about that data around the 20 count and if that could be a consequence of events logged around there or not.
Reply
Old Jan 31, 2013 | 08:07 PM
  #73  
tjac357's Avatar
Thread Starter
Evolved Member
iTrader: (1)
 
Joined: Apr 2009
Posts: 617
Likes: 0
From: Ohio
Originally Posted by fireroasted
OK, good, I see it in the log now. More a question for the guru's, but I see the WGDC goto 100 there, and it also pulls timing quickly based on that 20 count, 31 to 14. The other tell there is its your 'tip in', or what guys refer to as that, because you are just getting on your TPS there. The biggest thing I see is kind of lean at a jump to 15.5 just before there.

I also think it might help to unselect the things you don't really need for these logs. Battery voltage, fuel trims, and some other stuff won't likely tell you anything and is just hogging up bandwidth of your logging tools.

Curious if we can't get some comments from the more knowledgable about that data around the 20 count and if that could be a consequence of events logged around there or not.
I'll do they and do some more logs right now.

Also, I tried pulling 5 degrees timing on my whole ignition map minus the idle regions and my car still knocked in the same areas.

Thanks guys.
Reply
Old Feb 9, 2013 | 06:58 PM
  #74  
tjac357's Avatar
Thread Starter
Evolved Member
iTrader: (1)
 
Joined: Apr 2009
Posts: 617
Likes: 0
From: Ohio
So, most of my knock problems were being caused by my sensor being finger lose. However that didn't completely solve them and I'm still getting some partial throttle knock. However I have no knock at WOT.

I edited my Min Load for Boost Control table and seemed to help with the partial throttle knock. Here's a pic of my stock and changed settings. My new settings are closer to what Merlin says as stock.





fireroasted. I see you have an EBC so maybe this is table can help you out.
Reply
Old Feb 10, 2013 | 09:21 PM
  #75  
fireroasted's Avatar
Evolved Member
15 Year Member
iTrader: (3)
 
Joined: Apr 2008
Posts: 909
Likes: 7
From: CA
Originally Posted by tjac357
So, most of my knock problems were being caused by my sensor being finger lose. However that didn't completely solve them and I'm still getting some partial throttle knock. However I have no knock at WOT.

I edited my Min Load for Boost Control table and seemed to help with the partial throttle knock. Here's a pic of my stock and changed settings. My new settings are closer to what Merlin says as stock.





fireroasted. I see you have an EBC so maybe this is table can help you out.
So I have the stock one (one on top). I am not sure I ever really understood how that table works though. The load value has to be surpassed before boost control kicks in, but how is that helping you to reduce knock? You are actually having boost control kick in earlier, under 100 load in those RPM ranges. I need to try it with some logging, but I wish I understood that one better. Someone else mentioned that to me before too. I think it was Raptord and BoostedTuning.
Reply



All times are GMT -7. The time now is 07:47 AM.