Notices
Tuning, Diagnostics, Electronics, and Wiring HP Tuners | EFILive | Hand Held Programmers | Stand Alone PCM's | Electronics | Wiring Diagrams

Max timing issue. I'm at a loss.

Thread Tools
 
Search this Thread
 
Old 11-17-2007, 11:13 AM
  #1  
TECH Senior Member
Thread Starter
iTrader: (6)
 
TurboGibbs's Avatar
 
Join Date: Jul 2005
Location: Decatur, AL
Posts: 5,257
Likes: 0
Received 0 Likes on 0 Posts
Default Max timing issue. I'm at a loss.

HELP! if you've got HPT. I've worked on this off and on for months. It just won't allow more than 29* timing and at 5200 it starts to pull timing all the way up to around 24* with no knock. I'm commanding around 35* and it won't go there. I've tried multiple scenarios. I'm running SD with no MAF and currently i'm in closed loop but that should have nothing to do with this. I've also changed Max tq timing on another file with no luck.
Attached Files
File Type: hpl
11.13.07 HiOct-low +4.hpl (34.7 KB, 60 views)

Last edited by TurboGibbs; 11-17-2007 at 11:19 AM.
Old 11-17-2007, 02:20 PM
  #2  
LS1TECH Sponsor
iTrader: (1)
 
foff667's Avatar
 
Join Date: Jul 2003
Location: Clermont, FL
Posts: 7,978
Likes: 0
Received 0 Likes on 0 Posts
Default

Frame 97 commanded timing ~28.5* in your high octane table
Frame 97 actual timing 28.0* via the scanner

am I missing something? but I don't see where your commanding 35*

One thing I do notice is this http://www.hptuners.com/forum/showthread.php?t=13906 which is what your probably looking at and not understanding things as well as you could.
Old 11-17-2007, 02:29 PM
  #3  
Admin
iTrader: (22)
 
03sierraslt's Avatar
 
Join Date: Jul 2004
Location: Western PA
Posts: 19,004
Received 217 Likes on 173 Posts
Default

Hmm... Are you logging burst knock.. I doubt that is it just curious. Can you post up the config. that you are logging with?
Old 11-17-2007, 02:30 PM
  #4  
Admin
iTrader: (22)
 
03sierraslt's Avatar
 
Join Date: Jul 2004
Location: Western PA
Posts: 19,004
Received 217 Likes on 173 Posts
Default

Originally Posted by foff667
Frame 97 commanded timing ~28.5* in your high octane table
Frame 97 actual timing 28.0* via the scanner

am I missing something? but I don't see where your commanding 35*

One thing I do notice is this http://www.hptuners.com/forum/showthread.php?t=13906 which is what your probably looking at and not understanding things as well as you could.
I didnt see a commanded of 35 anywhere either but, I can see where its not reaching commanded.
Old 11-17-2007, 02:32 PM
  #5  
Admin
iTrader: (22)
 
03sierraslt's Avatar
 
Join Date: Jul 2004
Location: Western PA
Posts: 19,004
Received 217 Likes on 173 Posts
Default

Originally Posted by foff667
Frame 97 commanded timing ~28.5* in your high octane table
Frame 97 actual timing 28.0* via the scanner

am I missing something? but I don't see where your commanding 35*

One thing I do notice is this http://www.hptuners.com/forum/showthread.php?t=13906 which is what your probably looking at and not understanding things as well as you could.
Ohh just checked out the link to see what you were refering too, I did that once when I first when SD my Dyn cyl air was half and it was throwing my timing all over.

Turbogibbs- Check into that link that is a very good possibility, It may be using a different section of the Timing table then you think.
Old 11-17-2007, 02:37 PM
  #6  
TECH Senior Member
Thread Starter
iTrader: (6)
 
TurboGibbs's Avatar
 
Join Date: Jul 2005
Location: Decatur, AL
Posts: 5,257
Likes: 0
Received 0 Likes on 0 Posts
Default

I've been in SD for 2 years and I never had a problem like this before but I was turbo'd then and wasn't getting his high in timing. I don't fully understand exactly what their talking about in the link you sent but i'll try to make reason of it. Where i'm talking about is in the scanner i'm using the g/cyl off the histogram table to edit the proper cells in the hi/low oct table like I always have with no issues. I guess i'm missing something here obviously.
Old 11-17-2007, 02:39 PM
  #7  
TECH Senior Member
Thread Starter
iTrader: (6)
 
TurboGibbs's Avatar
 
Join Date: Jul 2005
Location: Decatur, AL
Posts: 5,257
Likes: 0
Received 0 Likes on 0 Posts
Default

Originally Posted by 03sierraslt
Turbogibbs- Check into that link that is a very good possibility, It may be using a different section of the Timing table then you think.
yeah, but if it was half of actual then it still wouldn't be 28 at that rpm. I'll study some more so we're on the same page.
Old 11-17-2007, 02:47 PM
  #8  
TECH Senior Member
Thread Starter
iTrader: (6)
 
TurboGibbs's Avatar
 
Join Date: Jul 2005
Location: Decatur, AL
Posts: 5,257
Likes: 0
Received 0 Likes on 0 Posts
Default

well, the forum doesn't like the config file. not compatible i don't guess.
Old 11-17-2007, 02:47 PM
  #9  
LS1TECH Sponsor
iTrader: (1)
 
foff667's Avatar
 
Join Date: Jul 2003
Location: Clermont, FL
Posts: 7,978
Likes: 0
Received 0 Likes on 0 Posts
Default

Originally Posted by TurboGibbs
yeah, but if it was half of actual then it still wouldn't be 28 at that rpm. I'll study some more so we're on the same page.
Yes it would actually.

Your at 1.xx g/cyl at 5500 rpms meaning your in the last line of the high octane timing tables which you have set to 26-29* of timing depending on rpm.
Old 11-17-2007, 02:49 PM
  #10  
LS1TECH Sponsor
iTrader: (1)
 
foff667's Avatar
 
Join Date: Jul 2003
Location: Clermont, FL
Posts: 7,978
Likes: 0
Received 0 Likes on 0 Posts
Default

Originally Posted by TurboGibbs
I've been in SD for 2 years and I never had a problem like this before but I was turbo'd then and wasn't getting his high in timing. I don't fully understand exactly what their talking about in the link you sent but i'll try to make reason of it. Where i'm talking about is in the scanner i'm using the g/cyl off the histogram table to edit the proper cells in the hi/low oct table like I always have with no issues. I guess i'm missing something here obviously.
Its not that involved, it basically states if your running SD do NOT log maf(sae) otherwise it will screw up your histogram readings which is where YOU are looking in the wrong cells. But IM looking at your table display so I know what cell you ARE in. And the cell you are in matches your commanded timing so theres absolutely nothing wrong with your scans.


Quick Reply: Max timing issue. I'm at a loss.



All times are GMT -5. The time now is 01:12 AM.