Notices
ECU Flash

2 byte load the same for 94170015 as 94170008?

Thread Tools
 
Search this Thread
 
Old Nov 23, 2007 | 05:45 PM
  #1  
Slo_crx1's Avatar
Thread Starter
Evolved Member
iTrader: (9)
 
Joined: Sep 2007
Posts: 821
Likes: 1
From: Simpson, PA
2 byte load the same for 94170015 as 94170008?

Are the add on .xml definitions the same as for the 0008 roms? I did the SES knock light add on that Tephra posted (works good btw) and I'm seeing up to 8 counts of knock arount the 4500-5000rpm range in LogWorks, but atm I'm limited to seeing up to 160% load and I really want to get rid of the knocking.
Reply
Old Nov 24, 2007 | 06:37 AM
  #2  
Slo_crx1's Avatar
Thread Starter
Evolved Member
iTrader: (9)
 
Joined: Sep 2007
Posts: 821
Likes: 1
From: Simpson, PA
C'mon guys...someobody's got to know. I got my knock count down under 3 now, but it's like searching in the dark to try and find which cells to change.
Reply
Old Nov 25, 2007 | 09:23 AM
  #3  
Slo_crx1's Avatar
Thread Starter
Evolved Member
iTrader: (9)
 
Joined: Sep 2007
Posts: 821
Likes: 1
From: Simpson, PA
Ok, after digging around some I found that the 2 byte load is the same setup for 94170008 and 94170014, so I'm going to take a stab and see if it's the same for the 70015 as well. I added the coding into the .xml in EcuFlash and it does show up ok with no errors, so next step is adding the coding to the LogWorks openport .xml file and see what the output values are.
Reply
Old Nov 25, 2007 | 10:32 AM
  #4  
JohnBradley's Avatar
Evolved Member
Shutterbug
Liked
Loved
Community Favorite
iTrader: (30)
 
Joined: Jan 2004
Posts: 11,406
Likes: 78
From: Northwest
If its not the same its probably only offset by 20 in the hex address if its the same differences as the IX 13/14 to the 15 rom. For isntance lets say the hex address (not using the MUT table) was 3ee62 for the 08 and if its not the same for the 15 try something like 3ee82. I have noticed it tends to be a common theme in Mitsu ROMs.
Reply
Old Nov 25, 2007 | 12:44 PM
  #5  
Slo_crx1's Avatar
Thread Starter
Evolved Member
iTrader: (9)
 
Joined: Sep 2007
Posts: 821
Likes: 1
From: Simpson, PA
Originally Posted by JohnBradley
If its not the same its probably only offset by 20 in the hex address if its the same differences as the IX 13/14 to the 15 rom. For isntance lets say the hex address (not using the MUT table) was 3ee62 for the 08 and if its not the same for the 15 try something like 3ee82. I have noticed it tends to be a common theme in Mitsu ROMs.
So far the values for the 70008 rom aren't correct for the 70015, when I logged the 2 channels it pretty much looked like a digital on/off switch signal. I'm a little confused by the address settings, when I opened them up in the edit tab it reads "38062" and "38066". I'm guessing I have to enter the address values in hex instead of decimal?


*NVM* Just thought about that last sentence...ignore the hex to decimal comment lol.
For now what can I do for calculating load using the standard load input? Last time I tried adding one of the math algorithms into LogWorks it told me I was seeing 350% load lol.

Last edited by Slo_crx1; Nov 25, 2007 at 01:02 PM.
Reply
Old Nov 25, 2007 | 07:04 PM
  #6  
Slo_crx1's Avatar
Thread Starter
Evolved Member
iTrader: (9)
 
Joined: Sep 2007
Posts: 821
Likes: 1
From: Simpson, PA
I added in the coding for a MUT table, but from what it looks like the mut start point is different from the 70008 rom. I stumbled across address 895C (0x895C or however it's stated in hex form, forgive me it's been a very long time since I used hex...mostly in my pre-obd0 honda days) and the top half of the table is cluttered garbage, but the bottom half looks more like the table should, with the typical FFFF followed by coding the next cell over. Could that halfway point be the beginning of the MUT table?
Reply
Old Nov 25, 2007 | 07:22 PM
  #7  
tephra's Avatar
EvoM Guru
15 Year Member
iTrader: (6)
 
Joined: Feb 2007
Posts: 9,486
Likes: 67
From: Melbourne, Australia
I was going to reply to this yesterday but fell asleep :P

MUT_TABLE = 0x38158
2byte load = 0xFFFF895C
2byte RPM = 0xFFFF893A
Reply
Old Nov 26, 2007 | 02:54 PM
  #8  
Slo_crx1's Avatar
Thread Starter
Evolved Member
iTrader: (9)
 
Joined: Sep 2007
Posts: 821
Likes: 1
From: Simpson, PA
Originally Posted by tephra
I was going to reply to this yesterday but fell asleep :P

MUT_TABLE = 0x38158
2byte load = 0xFFFF895C
2byte RPM = 0xFFFF893A
You are the man! I can honestly say in a non-gay man to man way that right now I love you lol. I tried playing around with different values all day yesterday and the most I found was half the MUT table on my own, but the load and rpm addresses I still hadn't pinpointed. Thank you, you saved me quite a bit of work tonight.
Reply
Old Nov 26, 2007 | 03:55 PM
  #9  
Slo_crx1's Avatar
Thread Starter
Evolved Member
iTrader: (9)
 
Joined: Sep 2007
Posts: 821
Likes: 1
From: Simpson, PA
Ok, so let me make sure I get this right, don't want to screw anything up on my car...
895C is the first load address, so in the table marked "00" I would input 35164, and in "01" 35165...I think I've got that. Now to the MUT table...the first cell after the "FFFF" is 888F (34959) and the second cell is 888E (34958). I take it these are the numbers that get put in the addresses for "00" and "01" respectively in order to transfer the data? If so that would make sense, as before my values for the "00" and "01" tables was 38062 and 38066 in the address locations (might also explain the weird stall at idle issue today )
Reply
Old Nov 26, 2007 | 05:13 PM
  #10  
tephra's Avatar
EvoM Guru
15 Year Member
iTrader: (6)
 
Joined: Feb 2007
Posts: 9,486
Likes: 67
From: Melbourne, Australia
I prefer to use hex so just enter 0x895C inside 00 (leaving the leading 0xFFFF) and 0x895D inside 01 (leaving the leading 0xFFFF).

if in doubt take a screeny of the MUT table and post up.
Reply
Old Nov 26, 2007 | 06:23 PM
  #11  
Slo_crx1's Avatar
Thread Starter
Evolved Member
iTrader: (9)
 
Joined: Sep 2007
Posts: 821
Likes: 1
From: Simpson, PA
Ok, here's a quick shot of the MUT table...



I just wanted to double check that those first two cell values (MUT0x cell values 0 and 1) are the ones to use.
Reply
Old Nov 26, 2007 | 06:37 PM
  #12  
tephra's Avatar
EvoM Guru
15 Year Member
iTrader: (6)
 
Joined: Feb 2007
Posts: 9,486
Likes: 67
From: Melbourne, Australia
yup.,,
Reply
Old Nov 26, 2007 | 06:43 PM
  #13  
Slo_crx1's Avatar
Thread Starter
Evolved Member
iTrader: (9)
 
Joined: Sep 2007
Posts: 821
Likes: 1
From: Simpson, PA
Originally Posted by tephra
yup.,,
Ok, thanks for all your help! I think I'm getting the hang of this now lol.
Reply
Old Dec 26, 2007 | 05:59 PM
  #14  
nj1266's Avatar
Evolved Member
iTrader: (6)
 
Joined: Nov 2004
Posts: 3,254
Likes: 13
From: USA
Sorry to bring this back up, but what is the code to define the MUT table and 2 byte load for the rom in question?
Reply
Old Dec 28, 2007 | 05:42 PM
  #15  
Slo_crx1's Avatar
Thread Starter
Evolved Member
iTrader: (9)
 
Joined: Sep 2007
Posts: 821
Likes: 1
From: Simpson, PA
It is the same as is used for the 0008 xml file, just with these values listed above instead. I got your email btw, if you want I do believe I have the 0015.xml file on my other computer with both the 2 byte load coding and the code for the MUT table.

Jim
Reply




All times are GMT -7. The time now is 12:07 AM.