Official 2 byte thread!
94170015
2byte load
MUT 00 = 895C
MUT 01 = 895D
2byte load
MUT 00 = 895C
MUT 01 = 895D
MUT 00 = 895C = 35164
MUT 01 = 895D = 35165
I tried logging 2 byte load using 35164 and 35165 for the above quoted rom and it did not work. This is the rom that has the p0300 fix, btw.
Anyone have the correct number?
MUT00 address is 3815A
MUT01 address is 3815E
Code:
<table name="MUT00" address="3815A" type="1D" level="4" scaling="Hex16"/> <table name="MUT01" address="3815E" type="1D" level="4" scaling="Hex16"/>
Last edited by Jack_of_Trades; May 30, 2008 at 01:14 PM.
dont put individual MUT ID's in your XML, use the BIG 3d table to access MUT's.
a number of people have put the WRONG numbers in and subsequently wondered why their car wouldn't start or ran weird...
a number of people have put the WRONG numbers in and subsequently wondered why their car wouldn't start or ran weird...
<table name="00 2 byte load" address="38062" type="1D" level="1" scaling="uint16" />
<table name="01 2 byte load" address="38066" type="1D" level="1" scaling="uint16" />
With the tables defined, I then used the 35164 and 35165 numbers in the 00 2 byte load table and 01 2 byte load table respectively.
Is the xml code that I entered wrong or right?
EvoM Guru
iTrader: (50)
Joined: Mar 2006
Posts: 9,675
Likes: 132
From: Tri-Cities, WA // Portland, OR
I'm surprised that any of the values match with ROM IDs that are so different. I don't have a 90550001 ROM handy to disassemble. PM me if you want my email address to send one.
MUT04 = 88B4
MUT05 = 88B5
Just did it to my 90550001, evoscan log nothing. Change it back to 8A59 and 8A79, it will log something wasn't sure if it's accurate (eg at idling, AirflowMUT read 755, 705, 730, 755... while airflow read 50, 43.75 or 37.5)
Do I have to change the function in evoscan?
My current functions are
0.3125*x Load
3.906*x RPM
6.29*x/64 AIRFLOW
I know on the first page it states to change RPM to 1000*x/256 but my values are still very strange. Did I do something wrong?



