Notices
ECU Flash

Official 2 byte thread!

Thread Tools
 
Search this Thread
 
Old May 17, 2008 | 07:56 AM
  #136  
recompile's Avatar
Evolved Member
iTrader: (38)
 
Joined: Nov 2006
Posts: 1,745
Likes: 10
From: New Hampshire, USA
Edit: nevermind, fixed on April 9
Reply
Old May 30, 2008 | 10:37 AM
  #137  
nj1266's Avatar
Evolved Member
iTrader: (6)
 
Joined: Nov 2004
Posts: 3,254
Likes: 13
From: USA
94170015
2byte load
MUT 00 = 895C
MUT 01 = 895D
Do these MUT numbers translate as follows

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?
Reply
Old May 30, 2008 | 10:41 AM
  #138  
l2r99gst's Avatar
Evolved Member
iTrader: (2)
 
Joined: Mar 2004
Posts: 3,499
Likes: 4
From: CA
895C hex = 35164 decimal
895D hex = 35165 decimal

You can use Windows calculator to switch from hex to decimal and vice versa.

I think that's what you were asking, right?
Reply
Old May 30, 2008 | 01:07 PM
  #139  
Jack_of_Trades's Avatar
Thread Starter
Evolved Member
iTrader: (17)
 
Joined: Jun 2007
Posts: 3,523
Likes: 2
From: Opelika,AL
Originally Posted by nj1266
Do these MUT numbers translate as follows

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?
These hex values are 100% correct and have been tested by many members so the issue is either your MUT address locations or something else. I stopped using the individual MUT tables in ECUFlash once I realized its far easier to just use the 3D table and be done with it for any future mods.

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"/>
With these tables added to your XML file, just type in the hex address' listed on the first page.

Last edited by Jack_of_Trades; May 30, 2008 at 01:14 PM.
Reply
Old May 30, 2008 | 07:33 PM
  #140  
tephra's Avatar
EvoM Guru
15 Year Member
iTrader: (6)
 
Joined: Feb 2007
Posts: 9,486
Likes: 67
From: Melbourne, Australia
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...
Reply
Old May 30, 2008 | 09:19 PM
  #141  
nj1266's Avatar
Evolved Member
iTrader: (6)
 
Joined: Nov 2004
Posts: 3,254
Likes: 13
From: USA
Originally Posted by tephra
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...
I have had no problems with entering individual MUT ID's in my xml. All the 2 byte load numbers that I have entered in roms to cars that I have tuned have worked. The only exception has been the 94170015. I used the following xml code, which according the jack is the wrong one.

<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?
Reply
Old May 30, 2008 | 09:57 PM
  #142  
mrfred's Avatar
EvoM Guru
iTrader: (50)
 
Joined: Mar 2006
Posts: 9,675
Likes: 132
From: Tri-Cities, WA // Portland, OR
99860002

2-byte load
MUT00 = 885C
MUT01 = 885D

2-byte RPM
MUT02 = 883A
MUT03 = 883B

2-byte airflow Hz
MUT04 = 88B4
MUT05 = 88B5
Reply
Old May 31, 2008 | 01:59 AM
  #143  
cossie1's Avatar
Evolved Member
 
Joined: Aug 2007
Posts: 569
Likes: 1
From: UK
Originally Posted by mrfred
99860002

2-byte load
MUT00 = 885C
MUT01 = 885D

2-byte RPM
MUT02 = 883A
MUT03 = 883B

2-byte airflow Hz
MUT04 = 88B4
MUT05 = 88B5
the 2 byte load and rpm in that rom match the ones in 90550001, could you check and see if the airflow value is correct for 90550001 too please mate
Reply
Old May 31, 2008 | 06:38 AM
  #144  
mrfred's Avatar
EvoM Guru
iTrader: (50)
 
Joined: Mar 2006
Posts: 9,675
Likes: 132
From: Tri-Cities, WA // Portland, OR
Originally Posted by cossie1
the 2 byte load and rpm in that rom match the ones in 90550001, could you check and see if the airflow value is correct for 90550001 too please mate
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.
Reply
Old May 31, 2008 | 06:51 AM
  #145  
recompile's Avatar
Evolved Member
iTrader: (38)
 
Joined: Nov 2006
Posts: 1,745
Likes: 10
From: New Hampshire, USA
Has anyone managed to find the MUT table location for 88590013 ?
Reply
Old May 31, 2008 | 07:05 AM
  #146  
cossie1's Avatar
Evolved Member
 
Joined: Aug 2007
Posts: 569
Likes: 1
From: UK
Originally Posted by mrfred
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.
They are both evo 7 roms

1 is ralliart (90550001) the other is FQ300 and poss 320 (9986002)
Reply
Old May 31, 2008 | 07:09 AM
  #147  
tephra's Avatar
EvoM Guru
15 Year Member
iTrader: (6)
 
Joined: Feb 2007
Posts: 9,486
Likes: 67
From: Melbourne, Australia
Shameless - Try 0x3EE64
Reply
Old Jun 1, 2008 | 04:33 AM
  #148  
sub7's Avatar
Evolving Member
 
Joined: Jun 2005
Posts: 282
Likes: 5
From: Kuala Lumpur
Originally Posted by cossie1
the 2 byte load and rpm in that rom match the ones in 90550001, could you check and see if the airflow value is correct for 90550001 too please mate
2-byte airflow Hz
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)
Reply
Old Jun 1, 2008 | 06:56 AM
  #149  
recompile's Avatar
Evolved Member
iTrader: (38)
 
Joined: Nov 2006
Posts: 1,745
Likes: 10
From: New Hampshire, USA
Originally Posted by tephra
Shameless - Try 0x3EE64
Perfect, that's it. Are the Load/RPM/Airflow changes the same as, say, 88590015 ?
Reply
Old Jun 1, 2008 | 02:11 PM
  #150  
GTijoejoe's Avatar
Evolved Member
iTrader: (25)
 
Joined: May 2008
Posts: 2,110
Likes: 12
From: Ohio
Originally Posted by Shameless Tuning
Perfect, that's it. Are the Load/RPM/Airflow changes the same as, say, 88590015 ?
That's what I did, it seems the 013 and 015 are very similar. Everything seemed to work fine, although the values in EVOscan were very strange.
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?
Reply



All times are GMT -7. The time now is 11:06 AM.