Notices
Evo X Engine Management / Tuning Forums Discuss the major engine management systems.

Ignition Timing: Upper/Lower bound

Thread Tools
 
Search this Thread
 
Old Feb 1, 2010 | 09:24 AM
  #16  
David Buschur's Avatar
Evolved Member
iTrader: (53)
 
Joined: Mar 2003
Posts: 14,622
Likes: 32
Mitch, the low octane timing map, from what I know is there for that purpose. So setting the low side the same as the low octane map and the high side the same as your high octane map would seem to be best.
Reply
Old Feb 1, 2010 | 09:42 AM
  #17  
David Buschur's Avatar
Evolved Member
iTrader: (53)
 
Joined: Mar 2003
Posts: 14,622
Likes: 32
Something I'd like to add.

I opened my maps, ROMID 52680017.

Lower bound is a normal 16x21 map, last load cell is 320 and the entire map is set at -20.

Upper bound is 23x22 map.....last load cell AFTER 320 is (1...) the entire map is set to 30.
Reply
Old Feb 1, 2010 | 10:26 AM
  #18  
Magnumpsi's Avatar
Evolved Member
20 Year Member
iTrader: (2)
 
Joined: Aug 2005
Posts: 1,045
Likes: 0
From: Who Knows
Originally Posted by davidbuschur
Mitch, the low octane timing map, from what I know is there for that purpose. So setting the low side the same as the low octane map and the high side the same as your high octane map would seem to be best.
Agreed.
Reply
Old Feb 1, 2010 | 10:50 AM
  #19  
GST Motorsports's Avatar
Thread Starter
Account Disabled
iTrader: (8)
 
Joined: Sep 2007
Posts: 3,366
Likes: 2
From: Hayward
Originally Posted by Magnumpsi
I would think setting it up to run a lower timing could be helpful just incase there is knock present so it allows the ECU to trim it out. If you set it to the same value as you tuned for it might not be able to pull it back out in case of a knock event.

Thoughts??

Mitch
Set it the same as your hi-octane timing and see if knock events pull timing below the lower bound table.

- Bryan
Reply
Old Feb 1, 2010 | 02:25 PM
  #20  
Piper747's Avatar
Evolving Member
iTrader: (2)
 
Joined: Feb 2009
Posts: 397
Likes: 1
From: Vancouver, BC
I am having an issue that seems like it may relate to these new maps. I can not seem to have my car run more timing advance than it is during peak boost between 3000 to 3500 rpm area. I have no knock, not exceeding target boost, still well within boost limit table. I cannot figure out why this is. I have attached a partial log of a quick 3rd gear WOT just to illustrate the problem area. Shifting from 1-2-3 is also shown. My rom id is 53600010. Does anyone have the definition for the upper bound tables for my car? Any input would be appreciated.
Attached Files
Reply
Old Feb 11, 2010 | 10:39 AM
  #21  
GST Motorsports's Avatar
Thread Starter
Account Disabled
iTrader: (8)
 
Joined: Sep 2007
Posts: 3,366
Likes: 2
From: Hayward
Updated first post to included 2010 USDM Evo 10 MR - Rom ID 55580005

- Bryan
Reply
Old Feb 12, 2010 | 03:43 AM
  #22  
crimson red's Avatar
Evolving Member
 
Joined: Aug 2009
Posts: 284
Likes: 21
From: Hokkaido, Japan
Upper/Lower bound XML for 2008 JDM Evo X (ID:52360018)

Thank your for nice information, Bryan.

For JDM 52360018:
address for 'lower bound ignition timing' is 0x5078f, and for 'upper bound ignition timing' is 0x60791.
Reply
Old Feb 12, 2010 | 06:22 AM
  #23  
Hiboost's Avatar
Evolved Member
iTrader: (9)
 
Joined: Apr 2005
Posts: 3,222
Likes: 8
From: Rochester, NY
If you want the car to be able to adjust the timing downward when encountering knock I would think letting it freely adjust as much as it needs would be wise unless for some reason you want to limit how much it can reduce the timing. I guess if you tend to adjust timing often or have multiple maps for different fuels, those having a upper and lower limiter on timing would be a pain to constantly have to change those maps as well but is doable.

I can see if you are troubleshooting knock events and are absolutely certain that the 1-4 knock counts is false you can force the car to not reduce timing 1-2* by setting the lower bound the same as the values in your timing table. The question though is if real knock sets in and it starts using the low octane timing tables will it force it to stay at the higher timing values which could be really really bad for the engine.
Reply
Old Feb 12, 2010 | 04:24 PM
  #24  
crimson red's Avatar
Evolving Member
 
Joined: Aug 2009
Posts: 284
Likes: 21
From: Hokkaido, Japan
X/Y Axises addresses modified(ID:52360018):

<scaling name="Min timing" units="degrees" toexpr="x-20" frexpr="x+20" format="%.0f" min="-61" max="61" inc="1" storagetype="int8" endian="big"/>

<table name="Lower Bound Ignition Timing" category="Timing" address="5078f" type="3D" level="2" swapxy="true" scaling="Min timing">
<table name="Load" address="6134c" type="X Axis" elements="21" scaling="Load"/>
<table name="RPM" address="61300" type="Y Axis" elements="16" scaling="RPM"/>
</table>

<table name="Upper Bound Ignition Timing" category="Timing" address="60791" type="3D" level="2" swapxy="true" scaling="Timing">
<table name="Load" address="60f7a" type="X Axis" elements="22" scaling="Load"/>
<table name="RPM" address="60f46" type="Y Axis" elements="23" scaling="RPM"/>
</table>
I guess the load axis for upper bound is from '0' to '320', for lower bound is from '10' to '320'. Right?

Last edited by crimson red; Feb 12, 2010 at 04:28 PM.
Reply
Old Jun 26, 2010 | 09:01 PM
  #25  
Kasander's Avatar
Newbie
 
Joined: Apr 2009
Posts: 64
Likes: 0
From: Earth
Would it be possible to get those table definition for the RA 2009 and 2010?

Trying to work with a wather meth kit and I'm limited by the upper bound table. I can't see the table but I know my timing doesn't match at all what's in the High Timing map.

ID: 53600010 or 09 (RA 09)
ID: 55590006
Reply
Old Jun 26, 2010 | 09:04 PM
  #26  
tephra's Avatar
EvoM Guru
15 Year Member
iTrader: (6)
 
Joined: Feb 2007
Posts: 9,486
Likes: 67
From: Melbourne, Australia
this is for 55590007, should work for 0006:

Code:
<scaling name="Min timing" units="degrees" toexpr="x-20" frexpr="x+20" format="%.0f" min="-61" max="61" inc="1" storagetype="int8" endian="big"/>
<table name="Lower Bound Ignition Timing" category="Timing" address="507a5" type="3D" level="2" swapxy="true" scaling="Min timing">
	<table name="Load" address="615a0" type="X Axis" elements="21" scaling="Load"/>
	<table name="RPM" address="61554" type="Y Axis" elements="16" scaling="RPM"/>
</table>

<table name="Upper Bound Ignition Timing" category="Timing" address="608e9" type="3D" level="2" swapxy="true" scaling="Timing">
	<table name="Load" address="611a6" type="X Axis" elements="22" scaling="Load"/>
	<table name="RPM" address="61172" type="Y Axis" elements="23" scaling="RPM"/>
</table>

Last edited by tephra; Jun 26, 2010 at 10:59 PM.
Reply
Old Jun 26, 2010 | 10:12 PM
  #27  
Kasander's Avatar
Newbie
 
Joined: Apr 2009
Posts: 64
Likes: 0
From: Earth
Originally Posted by tephra
this is for 55590007, should work for 0006:


<table name="Lower Bound Ignition Timing" category="Timing" address="507a5" type="3D" level="2" swapxy="true" scaling="Min timing">
<table name="Load" address="615a0" type="X Axis" elements="21" scaling="Load"/>
<table name="RPM" address="61554" type="Y Axis" elements="16" scaling="RPM"/>
</table>

<table name="Upper Bound Ignition Timing" category="Timing" address="608e9" type="3D" level="2" swapxy="true" scaling="Timing">
<table name="Load" address="611a6" type="X Axis" elements="22" scaling="Load"/>
<table name="RPM" address="61172" type="Y Axis" elements="23" scaling="RPM"/>
</table>
Thanks D.

Could you find it for 53600009 or 0010?
If you need the rom I can email it to you.
The car I'm having issue with is using 0009.

Was planing ahead in getting the 2010 model table as well
Reply
Old Jun 26, 2010 | 10:58 PM
  #28  
tephra's Avatar
EvoM Guru
15 Year Member
iTrader: (6)
 
Joined: Feb 2007
Posts: 9,486
Likes: 67
From: Melbourne, Australia
53600010:

Code:
<scaling name="Min timing" units="degrees" toexpr="x-20" frexpr="x+20" format="%.0f" min="-61" max="61" inc="1" storagetype="int8" endian="big"/>
<table name="Lower Bound Ignition Timing" category="Timing" address="50799" type="3D" level="2" swapxy="true" scaling="Min timing">
	<table name="Load" address="613a8" type="X Axis" elements="21" scaling="Load"/>
	<table name="RPM" address="6135c" type="Y Axis" elements="16" scaling="RPM"/>
</table>

<table name="Upper Bound Ignition Timing" category="Timing" address="607d9" type="3D" level="2" swapxy="true" scaling="Timing">
	<table name="Load" address="60fd6" type="X Axis" elements="22" scaling="Load"/>
	<table name="RPM" address="60fa2" type="Y Axis" elements="23" scaling="RPM"/>
</table>
Reply
Old Jun 27, 2010 | 07:12 AM
  #29  
Kasander's Avatar
Newbie
 
Joined: Apr 2009
Posts: 64
Likes: 0
From: Earth
You're the man.

Thanks D.
Reply
Old Jun 27, 2010 | 08:04 AM
  #30  
Golden's Avatar
Evolved Member
iTrader: (1)
 
Joined: Nov 2009
Posts: 1,456
Likes: 0
From: Omaha, NE
While we are on the subject of Upper Bounds Timing Maps, did anyone notice that Mitsu started limiting the GSR in 2010?
Reply



All times are GMT -7. The time now is 12:37 PM.