Can someone explain (timing related Q)
Feb 27, 2011, 07:00 PM
#17
Isn't this the map that controls that?
(for the 2010 maps)
<table name="Percent Low Temp Timing Trim vs Coolant Temp" address="561bc" category="Timing" type="2D" scaling="Percent255">
<table name="Engine Temp" address="61310" type="Y Axis" elements="8" scaling="TempFarenheit"/>
</table>
(for the 2010 maps)
<table name="Percent Low Temp Timing Trim vs Coolant Temp" address="561bc" category="Timing" type="2D" scaling="Percent255">
<table name="Engine Temp" address="61310" type="Y Axis" elements="8" scaling="TempFarenheit"/>
</table>
Feb 27, 2011, 08:38 PM
#19
Got another table:
This one seems to be linked to a MAFHz Accumulator, absolutley no idea, but it looks like it is activated when the MAFHz accumulator sees 1800 grams of air (yeh weird)
I havn't worked out the interval for the collection period yet...
This one seems to be linked to a MAFHz Accumulator, absolutley no idea, but it looks like it is activated when the MAFHz accumulator sees 1800 grams of air (yeh weird)
I havn't worked out the interval for the collection period yet...
Last edited by tephra; Feb 27, 2011 at 08:44 PM.
Feb 27, 2011, 10:22 PM
#21
This one is VERY interesting, there are two tables, but they look similar.
I am not really a fan of the +20*..
Seems to be applied when Actual MIVEC Exhaust is greater or less than the value in the map...
Might be the source of our low load knock bryan?
Feb 27, 2011, 11:42 PM
#22
ok... There are 4 tables, 2 for Intake 2 for Exhaust MIVEC.
Basically the ECU works out if the Actual Exhaust MIVEC is less than or greater than the Map Exhaust MIVEC.
Same for Intake MIVEC
Once it chooses which table to get the data from it then multiplies the actual difference by whatever the map lookup results in then divides by 0xA00
THEN it applies that as an ignition timing compensation...
ie, if you had 5* different between actual and map for the exhaust then it would be:
(5 * 32) * (whatever is in these 4 maps, ie 20*) / 0xA00 = 1.25*
so your timing would go up or down 1*
now this doesn't seem to be very much, but I just dont like the looks of these 4 tables:
The values just seem so random, 20 with 0's on either side...
I am thinking of zero'ing out these tables
Basically the ECU works out if the Actual Exhaust MIVEC is less than or greater than the Map Exhaust MIVEC.
Same for Intake MIVEC
Once it chooses which table to get the data from it then multiplies the actual difference by whatever the map lookup results in then divides by 0xA00
THEN it applies that as an ignition timing compensation...
ie, if you had 5* different between actual and map for the exhaust then it would be:
(5 * 32) * (whatever is in these 4 maps, ie 20*) / 0xA00 = 1.25*
so your timing would go up or down 1*
now this doesn't seem to be very much, but I just dont like the looks of these 4 tables:
The values just seem so random, 20 with 0's on either side...
I am thinking of zero'ing out these tables
Last edited by tephra; Feb 28, 2011 at 12:13 AM.
Feb 28, 2011, 12:31 AM
#23
Hrmm
Bryan your maps are already zero'd out.
I emailed you the def's..
a quick look at 52690022 shows they are similar to mine.. as is 2011 Au Evo.
MR vs GSR same thing almost..
Why the difference for RA vs Evo??
Bryan your maps are already zero'd out.
I emailed you the def's..
a quick look at 52690022 shows they are similar to mine.. as is 2011 Au Evo.
MR vs GSR same thing almost..
Why the difference for RA vs Evo??
Last edited by tephra; Feb 28, 2011 at 12:35 AM.
Feb 28, 2011, 10:04 AM
#25
Isn't this the map that controls that?
(for the 2010 maps)
<table name="Percent Low Temp Timing Trim vs Coolant Temp" address="561bc" category="Timing" type="2D" scaling="Percent255">
<table name="Engine Temp" address="61310" type="Y Axis" elements="8" scaling="TempFarenheit"/>
</table>
(for the 2010 maps)
<table name="Percent Low Temp Timing Trim vs Coolant Temp" address="561bc" category="Timing" type="2D" scaling="Percent255">
<table name="Engine Temp" address="61310" type="Y Axis" elements="8" scaling="TempFarenheit"/>
</table>
