PCM Diagnostics & Tuning HP Tuners | Holley | Diablo

tuning out delay in DBW

Thread Tools
 
Search this Thread
 
Old 06-11-2012 | 07:58 PM
  #21  
edcmat-l1's Avatar
Banned
iTrader: (10)
 
Joined: Jul 2006
Posts: 4,782
Likes: 4
From: Va Beach
Default

Go through them and see which ones make sense to use. How bout main spark/timing advance? That's sounds like it pertains, right?
Old 06-11-2012 | 08:00 PM
  #22  
patooyee's Avatar
Thread Starter
Launching!
iTrader: (1)
 
Joined: Sep 2009
Posts: 228
Likes: 0
From: Gulf Breeze, FL
Default

Yes, I looked at that table and see that at .68 g/cyl and 600rpms it is using -11*, but why is it doing so? The corresponding cell on the spark table does not read -11* in either high or low octane tables. Obviously one of the modifiers is doing this. Is this where I should have been logging the modifiers and looking at their histograms?

I also notice that it drops rpms just slightly for a millisecond the instant I hit the gas which is what is making it drop to the 600rpm cell. Before that it isn't retarding nearly as bad but I assume it then smoothes up which causes the period of retard before it advances?

Last edited by patooyee; 06-11-2012 at 08:06 PM.
Old 06-11-2012 | 08:08 PM
  #23  
edcmat-l1's Avatar
Banned
iTrader: (10)
 
Joined: Jul 2006
Posts: 4,782
Likes: 4
From: Va Beach
Default

Originally Posted by patooyee
Yes, I looked at that table and see that at .68 g/cyl and 600rpms it is using -11*, but why is it doing so? The corresponding cell on the spark table does not read -11* in either high or low octane tables. Obviously one of the modifiers is doing this. Is this where I should have been logging the modifiers and looking at their histograms?
That's an area of the table you're not likely to hit. If you do, and there's a bunch of spark lead there, you're very likely to spark knock badly. Low RPM high load.

Use your histogram and plot your total timing, and compare it to the table in the tune. You can also log burst knock retard, retard due to IAT, retard due to ECT, etc., but I never do, I just log actual timing, and knock retard and figure out the rest in my head. It ain't hard.
Old 06-11-2012 | 08:29 PM
  #24  
patooyee's Avatar
Thread Starter
Launching!
iTrader: (1)
 
Joined: Sep 2009
Posts: 228
Likes: 0
From: Gulf Breeze, FL
Default

This is what I am looking at. At the intersecting point on the hist the high octane table says I should be at 0* and the low octane says -16*. It is at -11* according to the graph. Based on what you are saying I am interpreting that it is either burst knock, IAT spark, or ECT spark that is causing that? So ideally I would cross reference .68g/cyl on all of those logged tables (which I wasn't logging) to find out which one was causing it? Or I can just go into my tune and cross reference?

I'm just going to forewarn you, I believe the only dumb question is the one left unasked. I care not if anyone makes fun of me. My mission in life is to learn, not to be cool. Beyond my wife and kid I couldn't care less what anyone thinks about me. Thus, no question is too dumb and I am libel to amaze you with my idiocy. But your patience and willingness to help is infinitely appreciated and will always be remembered.
Attached Thumbnails tuning out delay in DBW-hist1.jpg  
Old 06-11-2012 | 09:26 PM
  #25  
patooyee's Avatar
Thread Starter
Launching!
iTrader: (1)
 
Joined: Sep 2009
Posts: 228
Likes: 0
From: Gulf Breeze, FL
Default

Originally Posted by flame
zero out the burst knock and see what happens
I believe the Burst knock Retard vs. Run Time vs. Coolant Temp table is what you are referring to but do not see it ... I am viewing in advanced mode, and no it is not there if I scroll down either.
Attached Thumbnails tuning out delay in DBW-br2.jpg  
Old 06-11-2012 | 09:49 PM
  #26  
patooyee's Avatar
Thread Starter
Launching!
iTrader: (1)
 
Joined: Sep 2009
Posts: 228
Likes: 0
From: Gulf Breeze, FL
Default

Did some reading up on burst knock. It is basically pulling timing IN ANTICIPATION OF knock to prevent it. It pulls values from the base vs. cyl delta table and subtracts them from timing. My g/cyl jumps from .24 to 1.04 when I stomp the gas. Being that that delta is greater than any value in the base vs. cyl delta table I assume it uses the max value of -12*? That would make sense why the next reading is -11*? Am I getting this right because I feel like I just had an epiphany.
Old 06-12-2012 | 12:52 PM
  #27  
flame's Avatar
TECH Fanatic
20 Year Member
iTrader: (13)
 
Joined: Oct 2004
Posts: 1,169
Likes: 2
From: Waterloo, Ontario
Default

You can log all the timing retard pids to figure out which is pulling the timing and then you know where to start working. Most of the time it is burst knock that is why I said to zero it out and see what happens. If you zero out the base vs cylair then it will pull 0 deg. Then if you get knock retard you will have to lower those cells in the timing table. Or give the burst knock the ability to pull some timing.
Old 06-12-2012 | 03:36 PM
  #28  
white01ss's Avatar
11 Second Club
iTrader: (37)
 
Joined: Nov 2003
Posts: 656
Likes: 9
From: Dallas, TX
Default

You may have success removing burst retard completely but you might want to log it periodically for knock. GM put that there for a reason so if you start seeing knock when you stomp the throttle then you should slowly scale it back in. Safe route would be to take 50% off and leave it active. Final numbers depend on weather, IAT, ECT, A/C usage, etc. Good luck.
Old 06-27-2012 | 01:48 PM
  #29  
dirthead racing's Avatar
Teching In

 
Joined: Oct 2008
Posts: 33
Likes: 0
From: Grand Rapids, MI
Default

Any new updates?
Old 06-27-2012 | 03:43 PM
  #30  
patooyee's Avatar
Thread Starter
Launching!
iTrader: (1)
 
Joined: Sep 2009
Posts: 228
Likes: 0
From: Gulf Breeze, FL
Default

Not really. I'm still redoing my fuel system so I haven't been able to play with it.



Quick Reply: tuning out delay in DBW



All times are GMT -5. The time now is 05:46 PM.