Official 2 byte thread!
#16
Evolving Member
96530006
2byte load
MUT 00 = 898a
MUT 01 = 898b
Note: as we know - there are several loads used within the ecu code - baro./temp compenstated, not compenstaed etc. ect. - the one above seems to match the load used for timing. Another address is 8984, 8985 which seems to be used as reference load for boost control.
2byte load
MUT 00 = 898a
MUT 01 = 898b
Note: as we know - there are several loads used within the ecu code - baro./temp compenstated, not compenstaed etc. ect. - the one above seems to match the load used for timing. Another address is 8984, 8985 which seems to be used as reference load for boost control.
Last edited by evo828; Feb 22, 2008 at 01:47 AM.
#17
Evolving Member
iTrader: (4)
Join Date: Dec 2003
Location: Ventura County, CA
Posts: 357
Likes: 0
Received 0 Likes
on
0 Posts
Also note you're not required to log load on MUT00 and 01. You can log it from any MUT that isn't used. Same goes for any other parameter you want to log (RPM, airflow).
But setting a commonly used standard helps to avoid confusion.
I haven't confirmed this so maybe others can.
But setting a commonly used standard helps to avoid confusion.
I haven't confirmed this so maybe others can.
#19
Don't mind 2byte Airflow, it is wrong for both version. I tried and it keeps at 255. Looking at the code it *seems* to be octane number rather than airflow...
#20
96530006
2byte load
MUT 00 = 898a
MUT 01 = 898b
Note: as we know - there are several loads used within the ecu code - baro./temp compenstated, not compenstaed etc. ect. - the one above seems to match the load used for timing. Another address is 8984, 8985 which seems to be used as reference load for boost control.
2byte load
MUT 00 = 898a
MUT 01 = 898b
Note: as we know - there are several loads used within the ecu code - baro./temp compenstated, not compenstaed etc. ect. - the one above seems to match the load used for timing. Another address is 8984, 8985 which seems to be used as reference load for boost control.
#21
Evolving Member
I am attaching also a screenshot of what you need to have in the MUT table after opening and editing your ROM.
#22
Also note you're not required to log load on MUT00 and 01. You can log it from any MUT that isn't used. Same goes for any other parameter you want to log (RPM, airflow).
But setting a commonly used standard helps to avoid confusion.
I haven't confirmed this so maybe others can.
But setting a commonly used standard helps to avoid confusion.
I haven't confirmed this so maybe others can.
#25
So if you added the entire 3D MUT table, you would only need to edit the MUT00 and MUT01 locations correct? And if you added only a 1D MUT Table you'd need to edit the addresses you listed above? I've always used the 3D table so I'm just making sure I understand the process.
#29
Evolving Member
iTrader: (3)
Join Date: Jul 2004
Location: Richmond, VA
Posts: 179
Likes: 0
Received 0 Likes
on
0 Posts
96420008
Load
MUT00- 8984
MUT01- 8985
Airflow
MUT04- 89E2
MUT05- 89E3
MUT Table- 39FA0
Bump for this question:
2Byte RPM users, what improvements have you noticed with it, Particularily with logworks?
Load
MUT00- 8984
MUT01- 8985
Airflow
MUT04- 89E2
MUT05- 89E3
MUT Table- 39FA0
Bump for this question:
2Byte RPM users, what improvements have you noticed with it, Particularily with logworks?
Last edited by FuelsResearch; Feb 23, 2008 at 09:34 AM. Reason: Fix airflow boo-boo