Ignition Retard Limit
Jun 16, 2014, 09:21 AM
#136
Evolved Member
timing retard limit theres only one table in evo7 ecu
<table name="Timing Retard Limit" category="Timing" address="173e" type="1D" level="4" scaling="uint16"/>
als tables below
<table name="ALS minimum vehicle speed to trigger" category="ALS" address="2210" type="1D" level="1" scaling="VehicleSpeed"/>
<table name="ALS minimum coolant temperature to trigger" category="ALS" address="2212" type="1D" level="1" scaling="Temp"/>
<table name="ALS minimum RPM to trigger" category="ALS" address="2214" type="1D" level="1" scaling="RPMStatLimit"/>
<table name="ALS minimum load to trigger" category="ALS" address="2216" type="1D" level="1" scaling="Load16"/>
<table name="ALS minimum time to trigger" category="ALS" address="2218" type="1D" level="1" scaling="TimeSec"/>
<table name="ALS trigger valid time" category="ALS" address="221a" type="1D" level="1" scaling="TimeSec"/>
<table name="ALS Load below which active" category="ALS" address="221c" type="1D" level="1" scaling="Load16"/>
<table name="ALS active time limit" category="ALS" address="221e" type="1D" level="1" scaling="TimeSec"/>
<table name="ALS Delay before air injection" category="ALS" address="2220" type="1D" level="1" scaling="TimeSec"/>
<table name="ALS Delay before fuel injection" category="ALS" address="2222" type="1D" level="1" scaling="TimeSec"/>
<table name="ALS Fuel injector time" category="ALS" address="2224" type="1D" level="1" scaling="TimeSec"/>
<table name="ALS Air injection time" category="ALS" address="49e6" type="2D" level="1" scaling="Timesecbyte">
<table name="RPM" address="569a" type="X Axis" elements="9" scaling="RPM"/>
</table>
<table name="Timing Retard Limit" category="Timing" address="173e" type="1D" level="4" scaling="uint16"/>
als tables below
<table name="ALS minimum vehicle speed to trigger" category="ALS" address="2210" type="1D" level="1" scaling="VehicleSpeed"/>
<table name="ALS minimum coolant temperature to trigger" category="ALS" address="2212" type="1D" level="1" scaling="Temp"/>
<table name="ALS minimum RPM to trigger" category="ALS" address="2214" type="1D" level="1" scaling="RPMStatLimit"/>
<table name="ALS minimum load to trigger" category="ALS" address="2216" type="1D" level="1" scaling="Load16"/>
<table name="ALS minimum time to trigger" category="ALS" address="2218" type="1D" level="1" scaling="TimeSec"/>
<table name="ALS trigger valid time" category="ALS" address="221a" type="1D" level="1" scaling="TimeSec"/>
<table name="ALS Load below which active" category="ALS" address="221c" type="1D" level="1" scaling="Load16"/>
<table name="ALS active time limit" category="ALS" address="221e" type="1D" level="1" scaling="TimeSec"/>
<table name="ALS Delay before air injection" category="ALS" address="2220" type="1D" level="1" scaling="TimeSec"/>
<table name="ALS Delay before fuel injection" category="ALS" address="2222" type="1D" level="1" scaling="TimeSec"/>
<table name="ALS Fuel injector time" category="ALS" address="2224" type="1D" level="1" scaling="TimeSec"/>
<table name="ALS Air injection time" category="ALS" address="49e6" type="2D" level="1" scaling="Timesecbyte">
<table name="RPM" address="569a" type="X Axis" elements="9" scaling="RPM"/>
</table>
Now if i want to add the same tables for my JDM 93660005 what numbers do i need to change ? and the max retard for evo 8 is set to ?
Jun 19, 2014, 10:25 PM
#137
Evolved Member
I tried for the pops n bangs but it didnt work, set max retard to 255, 237, 203 it didnt work on either of them. Not even an odd pop. Guys any help ?
Jun 20, 2014, 04:49 PM
#138
Did you insert negative timing in low load/rpm area of the map? Do you have the SAS hardware installed on your engine?
There is no point of inserting more than 203 as ignition retard since the current E7/8 software isn't capable of less than -10.
In general pops'n'bangs don't work well on E7s, some discussions suggest blanking the EGR valve to improve p'n'b, I have personally tried that & it didn't do any good!
There is no point of inserting more than 203 as ignition retard since the current E7/8 software isn't capable of less than -10.
In general pops'n'bangs don't work well on E7s, some discussions suggest blanking the EGR valve to improve p'n'b, I have personally tried that & it didn't do any good!
Jun 20, 2014, 11:31 PM
#139
Evolved Member
Did you insert negative timing in low load/rpm area of the map? Do you have the SAS hardware installed on your engine?
There is no point of inserting more than 203 as ignition retard since the current E7/8 software isn't capable of less than -10.
In general pops'n'bangs don't work well on E7s, some discussions suggest blanking the EGR valve to improve p'n'b, I have personally tried that & it didn't do any good!
There is no point of inserting more than 203 as ignition retard since the current E7/8 software isn't capable of less than -10.
In general pops'n'bangs don't work well on E7s, some discussions suggest blanking the EGR valve to improve p'n'b, I have personally tried that & it didn't do any good!
Can you give me details about sas hardware ? or i conclude that this e7 rom is simple inert in terms of pops n bangs.
Jun 29, 2014, 10:56 AM
#140
Evolving Member
Join Date: May 2007
Location: Europe
Posts: 207
Likes: 0
Received 0 Likes
on
0 Posts
i dont have SAS hardware installed, plus the BOV is air vented , i did put max -10 retard in lower load zones. but it didnt pop but in contrast it was knocking in that zone so i re set the timing and AFR as well.
Can you give me details about sas hardware ? or i conclude that this e7 rom is simple inert in terms of pops n bangs.
Can you give me details about sas hardware ? or i conclude that this e7 rom is simple inert in terms of pops n bangs.
Jan 2, 2016, 06:06 AM
#141
Newbie
For those still looking for the ignition advance and retard limits, the following may be of interest:
scaling:
80700010:
88590015:
90550001:
94170015:
96530006:
scaling:
Code:
<scaling name="TimingMUT" units="degrees" toexpr="x-20" frexpr="x+20" format="%.0f" min="-20" max="60" inc="1" storagetype="uint8" endian="big" />
80700010:
Code:
<table name="Ignition Retard Limit" address="16fc9" category="Timing" type="1D" level="2" scaling="TimingMUT" /> <table name="Ignition Advance Limit" address="16fcb" category="Timing" type="1D" level="2" scaling="TimingMUT" />
88590015:
Code:
<table name="Ignition Retard Limit" address="1ba53" category="Timing" type="1D" level="2" scaling="TimingMUT" /> <table name="Ignition Advance Limit" address="1ba55" category="Timing" type="1D" level="2" scaling="TimingMUT" />
90550001:
Code:
<table name="Ignition Retard Limit" address="1631d" category="Timing" type="1D" level="2" scaling="TimingMUT" /> <table name="Ignition Advance Limit" address="1631f" category="Timing" type="1D" level="2" scaling="TimingMUT" />
94170015:
Code:
<table name="Ignition Retard Limit" address="182b5" category="Timing" type="1D" level="2" scaling="TimingMUT" /> <table name="Ignition Advance Limit" address="182b7" category="Timing" type="1D" level="2" scaling="TimingMUT" />
96530006:
Code:
<table name="Ignition Retard Limit" address="1813d" category="Timing" type="1D" level="2" scaling="TimingMUT" /> <table name="Ignition Advance Limit" address="1813f" category="Timing" type="1D" level="2" scaling="TimingMUT" />
Last edited by WytWun; Jul 11, 2016 at 04:56 AM. Reason: convert to code blocks & restore XML tag text
Jan 2, 2016, 06:12 PM
#143
Newbie
The advance limit has been validated in an AUDM v6 ROM (Magna AWD) and the above references are based on matching the disassemblies with that ROM.
The actual values are encoded as opcode immediate operands, which is why they're at the addresses they are. The advance limit should be easy to find in any SH2 Mitsubishi ROM disassembly by searching for "mov #0x46" as that seems to be unique in these ROMs. The retard limit will normally be a "mov #0x0A" instruction preceding the advance limit instruction in the same subroutine, though not always the immediate preceding instruction as it is for the above ROMs; note that this instruction is used in a number of other routines in each ROM which aren't timing related hence the need to search for the advance limit instruction first. NB: the operand encoding may need to be adjusted to match the disassembler output; the instruction text shown matches the output from logic's SH2 disassembler.
The actual values are encoded as opcode immediate operands, which is why they're at the addresses they are. The advance limit should be easy to find in any SH2 Mitsubishi ROM disassembly by searching for "mov #0x46" as that seems to be unique in these ROMs. The retard limit will normally be a "mov #0x0A" instruction preceding the advance limit instruction in the same subroutine, though not always the immediate preceding instruction as it is for the above ROMs; note that this instruction is used in a number of other routines in each ROM which aren't timing related hence the need to search for the advance limit instruction first. NB: the operand encoding may need to be adjusted to match the disassembler output; the instruction text shown matches the output from logic's SH2 disassembler.
Last edited by WytWun; Jan 2, 2016 at 06:23 PM. Reason: clarification
Jan 10, 2016, 09:55 AM
#149
Newbie
Join Date: Dec 2015
Location: Forfar
Posts: 17
Likes: 0
Received 0 Likes
on
0 Posts
Todd6027 I got this working too same rom as yourself although it only lasted 15 min run any ideas why what did you change/amend in settings xml files etc please help guys this has been driving me nuts for few days now ��
