Notices
ECU Flash

Let's see your fully tuned timing maps

Thread Tools
 
Search this Thread
 
Old Apr 17, 2012 | 08:11 AM
  #1561  
C6C6CH3vo's Avatar
Evolved Member
iTrader: (9)
 
Joined: Feb 2005
Posts: 4,223
Likes: 4
From: sc
Originally Posted by Raptord
but it could definitely stand to be smoother.
It's lack of smoothness fits well with my personality.



I should have posted logs, I hit 260 max with the modified MAF (30psi- 27psi redline)

thanks for the feedback though
Reply
Old Apr 17, 2012 | 09:54 AM
  #1562  
Ian0611's Avatar
Evolved Member
iTrader: (41)
 
Joined: Feb 2010
Posts: 1,049
Likes: 5
From: IL
Originally Posted by chetrickerman
All evo's I tune, I run the low octane timing map the same as the high octane. Reason is, because the ECU uses an algorithm when reducing timing when knock occurs, in which it takes into account the difference between the high oct and low oct map at that load and rpm, then applies that value into the knock algorithm.

So say just for example, you have 4* of difference between the 2 maps, and you get 5 counts of knock. The ECU may pull 2 or 3 degrees because of the .33* it drops per knock count, as well as overcompensating because the 4* difference between the maps. Now dropping that 3 degrees may cause more knock, and I goes into a kind of downward spiral.

Now if you don't have any difference between the 2 maps, the ECU will still pull 1* for every 3 knock counts, but it won't overcompensate or round up. If you get 5 counts, the ECU may only pull 1*, then it will check to see if that eliminated the knock (which most times it does), then bring the timing back up that 1* the next cycle.

Hopefull this all makes sense.

I use this with great results.
Chetrickerman (or anyone else) let me know if you can explain this- The graph below is from runs yesterday and today. Same stretch of road and weather was pretty much the same as well. The only change between the two runs is that I did what you said above for today's run. I modified the low oct. fuel and timing maps to be the same as the high oct. maps. Prior to that I was running the low oct. timing map 3* less than the high oct. map and the low oct. fuel map was about .5 richer. Unfortunately I forgot to log boost for yesterdays run but boost went up about 1 psi throughout the entire rev range and peak boost almost 2 psi higher, even though I made no changes to the boost tables.

I never would have guessed that such a minor change would have such a large effect. I need to do a few more runs to verify results, but the mere change in boost kinda has me baffeled. Good luck explaining this one

Reply
Old Apr 17, 2012 | 10:16 AM
  #1563  
Raptord's Avatar
Evolved Member
iTrader: (10)
 
Joined: Mar 2009
Posts: 3,525
Likes: 20
From: Gatineau, Quebec, Canada
Originally Posted by Ian0611
Chetrickerman (or anyone else) let me know if you can explain this- The graph below is from runs yesterday and today. Same stretch of road and weather was pretty much the same as well. The only change between the two runs is that I did what you said above for today's run. I modified the low oct. fuel and timing maps to be the same as the high oct. maps. Prior to that I was running the low oct. timing map 3* less than the high oct. map and the low oct. fuel map was about .5 richer. Unfortunately I forgot to log boost for yesterdays run but boost went up about 1 psi throughout the entire rev range and peak boost almost 2 psi higher, even though I made no changes to the boost tables.

I never would have guessed that such a minor change would have such a large effect. I need to do a few more runs to verify results, but the mere change in boost kinda has me baffeled. Good luck explaining this one

Are the timing curves in both logs similar?
Reply
Old Apr 17, 2012 | 10:28 AM
  #1564  
Ian0611's Avatar
Evolved Member
iTrader: (41)
 
Joined: Feb 2010
Posts: 1,049
Likes: 5
From: IL
Originally Posted by Raptord
Are the timing curves in both logs similar?
Yes, timing curves are almost identical.
Reply
Old Apr 17, 2012 | 10:29 AM
  #1565  
killerpenguin21's Avatar
Evolved Member
iTrader: (20)
 
Joined: Mar 2009
Posts: 2,389
Likes: 11
From: Big city, Bright lights
nvm, you beat me to it.
Reply
Old Apr 17, 2012 | 10:45 AM
  #1566  
chetrickerman's Avatar
Evolved Member
Veteran: Army
iTrader: (7)
 
Joined: Dec 2008
Posts: 575
Likes: 1
From: Colorado Springs
Originally Posted by Ian0611
Chetrickerman (or anyone else) let me know if you can explain this- The graph below is from runs yesterday and today. Same stretch of road and weather was pretty much the same as well. The only change between the two runs is that I did what you said above for today's run. I modified the low oct. fuel and timing maps to be the same as the high oct. maps. Prior to that I was running the low oct. timing map 3* less than the high oct. map and the low oct. fuel map was about .5 richer. Unfortunately I forgot to log boost for yesterdays run but boost went up about 1 psi throughout the entire rev range and peak boost almost 2 psi higher, even though I made no changes to the boost tables.

I never would have guessed that such a minor change would have such a large effect. I need to do a few more runs to verify results, but the mere change in boost kinda has me baffeled. Good luck explaining this one

Like I said. When the high and low timing maps are the same (doing this with the fuel maps doesn't really have the same effect) the ECU doesn't do a "downward" spiral of timing reduction upon the event of knock. Putting the maps the same minimizes the amount of timing pulled per count of knock, rather than maximizing it (which makes sense as OEM engineers think that less timing = less chance of knock). Well with our modified engines, that isnt necessarily the case. In most cases, only 1 or 2 degrees of timing needs to be pulled to eliminate the knock. Pulling too much timing can also cause knock, just like too much fuel, or too little fuel will cause knock.

Im not like Tephra or MrFred that uses ECU dissasembly to confirm this (their work is immensely appreciated), but as I and tephra have found out, the ECU does not always do what the programming says to do.

I have used this method on numerous Evo's that I have tuned, and the end result is always the same. In most cases, the less timing pulled the better.
Reply
Old Apr 17, 2012 | 10:48 AM
  #1567  
Ian0611's Avatar
Evolved Member
iTrader: (41)
 
Joined: Feb 2010
Posts: 1,049
Likes: 5
From: IL
Originally Posted by chetrickerman
Like I said. When the high and low timing maps are the same (doing this with the fuel maps doesn't really have the same effect) the ECU doesn't do a "downward" spiral of timing reduction upon the event of knock. Putting the maps the same minimizes the amount of timing pulled per count of knock, rather than maximizing it (which makes sense as OEM engineers think that less timing = less chance of knock). Well with our modified engines, that isnt necessarily the case. In most cases, only 1 or 2 degrees of timing needs to be pulled to eliminate the knock. Pulling too much timing can also cause knock, just like too much fuel, or too little fuel will cause knock.

Im not like Tephra or MrFred that uses ECU dissasembly to confirm this (their work is immensely appreciated), but as I and tephra have found out, the ECU does not always do what the programming says to do.

I have used this method on numerous Evo's that I have tuned, and the end result is always the same. In most cases, the less timing pulled the better.
Timing seems to have stayed the same. What I don't understand is why boost changed at all.
Reply
Old Apr 17, 2012 | 10:55 AM
  #1568  
chetrickerman's Avatar
Evolved Member
Veteran: Army
iTrader: (7)
 
Joined: Dec 2008
Posts: 575
Likes: 1
From: Colorado Springs
Originally Posted by Ian0611
Timing seems to have stayed the same. What I don't understand is why boost changed at all.
It may look the same, but modern ECU's can do hundreds of thousands, if not millions of operations per second. In that, the ECU may detect knock, eliminate it, then increase the timing back to where it was in the time it takes to go from one grid row to the next in your log.

timing does affect boost a little bit
Reply
Old Apr 17, 2012 | 12:04 PM
  #1569  
Ian0611's Avatar
Evolved Member
iTrader: (41)
 
Joined: Feb 2010
Posts: 1,049
Likes: 5
From: IL
OK. I went and did another pull on my lunch break and the difference isn't quite as dramatic as the last graph I posted. I never really noticed it before, but the stretch of road that I use on my way to work does have a slight downhill grade at the beginning of it so that's probably why the first pull was so much higher than the previous one. Personally, I always take VD numbers with a grain of salt anyway so you guys can kind of ignore the huge power variance in that graph.

Lke I said, the thing that still gets me is that regardless of what road I'm on, boost is still higher than it was yesterday and I don't understand why.

I really need to get back to my normal tuning road and spend some quality time dialing this thing in. #sigh
Reply
Old Apr 19, 2012 | 11:50 AM
  #1570  
Blitz's Avatar
Evolved Member
iTrader: (11)
 
Joined: Jan 2007
Posts: 1,201
Likes: 3
From: Earth
I apologize for posting this here but I wasn't about to start my own thread and this thread seems to be full of smart people.



This is from the "How to tune an Evo" thread. What program is this from/how do I view my logs in this format? I want to be able to view my timing/AFR/boost on a load vs RPM grid like this.

Also, for this purpose, is logging 1byte load sufficient or should I be logging 2byteload or loadcalc instead?

Thanks guys.
Reply
Old Apr 19, 2012 | 12:06 PM
  #1571  
Raptord's Avatar
Evolved Member
iTrader: (10)
 
Joined: Mar 2009
Posts: 3,525
Likes: 20
From: Gatineau, Quebec, Canada
Just 1byte load

That's from DLL I think. You can have a similar map tracing in evoscan
Reply
Old Apr 19, 2012 | 08:49 PM
  #1572  
killerpenguin21's Avatar
Evolved Member
iTrader: (20)
 
Joined: Mar 2009
Posts: 2,389
Likes: 11
From: Big city, Bright lights
Originally Posted by chetrickerman
Like I said. When the high and low timing maps are the same (doing this with the fuel maps doesn't really have the same effect) the ECU doesn't do a "downward" spiral of timing reduction upon the event of knock.
so it looks like this may have been my issue.

i did a test tonight with the new low octane maps i made (high octane map minus 3 degrees above 140 load). result was no knock like the old logs (above 6800), and in fact no knock abover 5k. 4th gear came back very clean also. i got a tad of knock at peak torque since it was cold out and i went very right on the load scale. it was about 50 degrees out tonight with 75% humidity. ill have to keep testing this map in the warm.

next step is ecu boost/boost by gear since i was over boosting in 5th down the front stretch last weekend.
Reply
Old Apr 19, 2012 | 10:07 PM
  #1573  
10isace's Avatar
Evolved Member
15 Year Member
Liked
Loved
Community Favorite
iTrader: (12)
 
Joined: Nov 2008
Posts: 1,058
Likes: 16
From: East of the Rockies
Originally Posted by killerpenguin21
so it looks like this may have been my issue.

i did a test tonight with the new low octane maps i made (high octane map minus 3 degrees above 140 load). result was no knock like the old logs (above 6800), and in fact no knock abover 5k. 4th gear came back very clean also. i got a tad of knock at peak torque since it was cold out and i went very right on the load scale. it was about 50 degrees out tonight with 75% humidity. ill have to keep testing this map in the warm.

next step is ecu boost/boost by gear since i was over boosting in 5th down the front stretch last weekend.
I did the same, but only 2 degrees lower and it turned out great! I hope this is not a "placebo".
Reply
Old Apr 19, 2012 | 10:11 PM
  #1574  
killerpenguin21's Avatar
Evolved Member
iTrader: (20)
 
Joined: Mar 2009
Posts: 2,389
Likes: 11
From: Big city, Bright lights
the only odd thing is my boost got a little weird, when normally its rock solid.
Reply
Old Apr 19, 2012 | 10:13 PM
  #1575  
akeric's Avatar
Evolving Member
15 Year Member
iTrader: (2)
 
Joined: Sep 2006
Posts: 329
Likes: 2
From: Alaska
Originally Posted by Blitz
I apologize for posting this here but I wasn't about to start my own thread and this thread seems to be full of smart people.



This is from the "How to tune an Evo" thread. What program is this from/how do I view my logs in this format? I want to be able to view my timing/AFR/boost on a load vs RPM grid like this.

Also, for this purpose, is logging 1byte load sufficient or should I be logging 2byteload or loadcalc instead?

Thanks guys.
You can use the map tracer function in evoscan to view in a smiliar fashion.
Reply



All times are GMT -7. The time now is 08:49 PM.