Can't increase timing while brake stalling (tune and log attached)
Jan 17, 2007 | 09:17 AM
#1
Thread Starter
High on diesel fumes
iTrader: (70)
Joined: Mar 2005
Posts: 12,658
Likes: 3
From: Phoenix, AZ
Can't increase timing while brake stalling (tune and log attached)
I'm trying to bump up my timing while brake stalling. I'm commanding 30 degrees at .64 g/cyl and 2400 RPM in both my high and low octane spark tables, but my base spark PID and timing advance PID are both only showing 25 degrees. It doesn't seem to matter what I command at that point (.64/2400), I always get right around 25*. Can someone take a look at my log and tune and see if you can figure out what's up?
The log file is long - take a look right around frame 2640, that's where I stalled it up.
The log file is long - take a look right around frame 2640, that's where I stalled it up.
Jan 17, 2007 | 09:56 AM
#2
Im at work and cant pull up the program but I bet if you raise best tq table (its the one that says dont mess with) in that area the rest will fall into place, also look at your adder tables.
Jan 17, 2007 | 03:02 PM
#3
Originally Posted by 02sierraz71_5.3
Im at work and cant pull up the program but I bet if you raise best tq table (its the one that says dont mess with) in that area the rest will fall into place, also look at your adder tables.
Jan 17, 2007 | 07:09 PM
#5
Originally Posted by 02sierraz71_5.3
Im at work and cant pull up the program but I bet if you raise best tq table (its the one that says dont mess with) in that area the rest will fall into place, also look at your adder tables.
At any rate, it's showing 31* at this particular load point (2400/0.64), so that's not the culprit...
Chris, A few thoughts...
First off, since I see that your MAF is enabled, try changing the GM.DYNCYLAIR_DMA PID to GM.DYNCYLAIR (in the Air section). I've discovered that DYNCYLAIR_DMA is not the correct PID for spark lookup. I've sent an email to the EFI Live guys about this with my reasoning and evidence, but have not received a response yet.
DYNCYLAIR_DMA directly looks up the ve table value corresponding to the rpm/map load point that you are at and calculates airmass based on that. Since your MAF is connected, if your VE table is off in this area, this PID will incorrectly report the actual airmass.
Otherwise, unless there are hidden tables (like run-launch spark modifier), the only thing I can see is: Axle torque limiting is still enabled {B6601}, but {B1902} is zero'd out, so that shouldn't be the case.
Justin
Jan 17, 2007 | 08:12 PM
#6
Adkoonerstrator
iTrader: (4)
Joined: Nov 2001
Posts: 21,436
Likes: 3
From: Deep in the seedy underworld of Koonerville
Zero out table B6212(Burst knock retard). That could be your culprit. It activates off the B6210 Burst knock delta air mass table and even though you don't seem to be exceeding those limits you are missing the exact amount of timing that it takes out at 2400rpm.
Jan 17, 2007 | 09:37 PM
#7
Thread Starter
High on diesel fumes
iTrader: (70)
Joined: Mar 2005
Posts: 12,658
Likes: 3
From: Phoenix, AZ
Originally Posted by XLR8NSS
Zero out table B6212(Burst knock retard). That could be your culprit. It activates off the B6210 Burst knock delta air mass table and even though you don't seem to be exceeding those limits you are missing the exact amount of timing that it takes out at 2400rpm.
Originally Posted by dc_justin
Chris, A few thoughts...
First off, since I see that your MAF is enabled, try changing the GM.DYNCYLAIR_DMA PID to GM.DYNCYLAIR (in the Air section). I've discovered that DYNCYLAIR_DMA is not the correct PID for spark lookup. I've sent an email to the EFI Live guys about this with my reasoning and evidence, but have not received a response yet.
DYNCYLAIR_DMA directly looks up the ve table value corresponding to the rpm/map load point that you are at and calculates airmass based on that. Since your MAF is connected, if your VE table is off in this area, this PID will incorrectly report the actual airmass.
Justin
First off, since I see that your MAF is enabled, try changing the GM.DYNCYLAIR_DMA PID to GM.DYNCYLAIR (in the Air section). I've discovered that DYNCYLAIR_DMA is not the correct PID for spark lookup. I've sent an email to the EFI Live guys about this with my reasoning and evidence, but have not received a response yet.
DYNCYLAIR_DMA directly looks up the ve table value corresponding to the rpm/map load point that you are at and calculates airmass based on that. Since your MAF is connected, if your VE table is off in this area, this PID will incorrectly report the actual airmass.
Justin
Trending Topics
Jan 17, 2007 | 10:19 PM
#8
Originally Posted by thunder550
Should I zero it out or max it out? It enables BKR when the values are exceeded....
I'll give that a shot, you're thinking that with the wrong PID selected the log is showing a different cell than the PCM is actually referencing?
I'll give that a shot, you're thinking that with the wrong PID selected the log is showing a different cell than the PCM is actually referencing?
Jan 18, 2007 | 09:46 AM
#9
Thread Starter
High on diesel fumes
iTrader: (70)
Joined: Mar 2005
Posts: 12,658
Likes: 3
From: Phoenix, AZ
You guys got it! I replied in the EFILive thread already, but when I changed the airflow PID it's actually referencing the .72/2400 cell, not the .64 cell that I was adjusting. I messed with the .72 cell and now I'm seeing the changes in effect. Thanks!
