Notices
ECU Flash

status of 2 byte load?

Thread Tools
 
Search this Thread
 
Old Mar 4, 2007 | 02:58 AM
  #91  
JoeBee's Avatar
Evolving Member
 
Joined: Sep 2006
Posts: 152
Likes: 0
From: Germany
@l2r99gst
First and second line are the same.
This gives an error in ecuflash.
Reply
Old Mar 4, 2007 | 03:49 AM
  #92  
JoeBee's Avatar
Evolving Member
 
Joined: Sep 2006
Posts: 152
Likes: 0
From: Germany
I like this table. Thanks to l2r99gst.

Here is it for the EVO 7, ID: 99860002
PHP Code:
    <table name="MUT table" category="Misc" address="0x302d8" type="3D" level="1" scaling="Hex16"> 
        <table name="X" type="Static X Axis" elements="16" scaling="Hex16"> 
            <data>8</data> 
            <data>A</data> 
            <data>C</data> 
            <data>E</data> 
            <data>10</data> 
            <data>12</data> 
            <data>14</data> 
            <data>16</data> 
            <data>18</data> 
            <data>1A</data> 
            <data>1C</data> 
            <data>1E</data> 
            <data>0</data> 
            <data>2</data>
            <data>4</data> 
            <data>6</data>  
        </table> 
        <table name="Y" type="Static Y Axis" elements="32"> 
            <data>302D8</data>
            <data>302F8</data>
            <data>30318</data>
            <data>30338</data>
            <data>30358</data>
            <data>30378</data>
            <data>30398</data>
            <data>303B8</data>
            <data>303D8</data>
            <data>303F8</data>
            <data>30418</data>
            <data>30438</data>
            <data>30458</data>
            <data>30478</data>
            <data>30498</data>
            <data>304B8</data>
            <data>304D8</data>
            <data>304F8</data>
            <data>30518</data>
            <data>30538</data>
            <data>30558</data>
            <data>30578</data>
            <data>30598</data>
            <data>305B8</data>
            <data>305D8</data>
            <data>305F8</data>
            <data>30618</data>
            <data>30638</data>
            <data>30658</data>
            <data>30678</data>
            <data>30698</data>
            <data>306B8</data>
        </table> 
    </table> 

Last edited by JoeBee; Mar 4, 2007 at 03:52 AM.
Reply
Old Mar 4, 2007 | 06:04 AM
  #93  
l2r99gst's Avatar
Evolved Member
iTrader: (2)
 
Joined: Mar 2004
Posts: 3,499
Likes: 4
From: CA
Originally Posted by JoeBee
@l2r99gst
First and second line are the same.
This gives an error in ecuflash.
Fixed. I went to make a correction and it looks like I messed up when I pasted it back in.

Also, the credit goes to Bez. He defined it in the ROM he was disassembling, so I just found it in mine and defined it. If you look at his definition file, there are also many more tables, like for rear 02, etc, that I have also found in my ROM.


Eric
Reply
Old Mar 4, 2007 | 07:42 AM
  #94  
fixem2's Avatar
Evolved Member
iTrader: (30)
 
Joined: Dec 2003
Posts: 929
Likes: 0
From: USA
l2r99gst, is that what the MUT table looks like for the 96940011 ROM after patching the correct address with FFFF899A and FFFF899B?

Did you add these lines to EvoScan:

<DataListItem DataLog="Y" Display="Load0" LogReference="Load0" RequestID="00" Eval="x" Unit="steps" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="255" ChartMin="0" ChartMax="255" Notes="" />
<DataListItem DataLog="Y" Display="Load1" LogReference="Load1" RequestID="01" Eval="x" Unit="steps" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="255" ChartMin="0" ChartMax="255" Notes="" />
<DataListItem DataLog="Y" Display="2byteLoad" LogReference="2byteLoad" RequestID="FF" Eval="((256*[Load0])+[Load1])*0.3125" Unit="load" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="500" ChartMin="0" ChartMax="500" Notes="2 byte load read from ECU" />
Attached Thumbnails status of 2 byte load?-mut_table.jpg  

Last edited by fixem2; Mar 4, 2007 at 07:44 AM.
Reply
Old Mar 4, 2007 | 08:37 AM
  #95  
JoeBee's Avatar
Evolving Member
 
Joined: Sep 2006
Posts: 152
Likes: 0
From: Germany
Originally Posted by l2r99gst
...Also, the credit goes to Bez. He defined it in the ROM he was disassembling, so I just found it in mine and defined it. If you look at his definition file, there are also many more tables, like for rear 02, etc, that I have also found in my ROM.
Sure, althoug thanks to Bez and jcsbanks.
I have done the same. Dissassemble my file and try to find the similar code positions.
Reply
Old Mar 4, 2007 | 08:53 AM
  #96  
l2r99gst's Avatar
Evolved Member
iTrader: (2)
 
Joined: Mar 2004
Posts: 3,499
Likes: 4
From: CA
Originally Posted by fixem2
l2r99gst, is that what the MUT table looks like for the 96940011 ROM after patching the correct address with FFFF899A and FFFF899B?

Did you add these lines to EvoScan:

<DataListItem DataLog="Y" Display="Load0" LogReference="Load0" RequestID="00" Eval="x" Unit="steps" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="255" ChartMin="0" ChartMax="255" Notes="" />
<DataListItem DataLog="Y" Display="Load1" LogReference="Load1" RequestID="01" Eval="x" Unit="steps" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="255" ChartMin="0" ChartMax="255" Notes="" />
<DataListItem DataLog="Y" Display="2byteLoad" LogReference="2byteLoad" RequestID="FF" Eval="((256*[Load0])+[Load1])*0.3125" Unit="load" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="500" ChartMin="0" ChartMax="500" Notes="2 byte load read from ECU" />
Yes, that is what it would look like when patching for 2-byte load.

As far as logging, I use LogWorks, but what you wrote for EvoScan looks ok to me.


Eric
Reply
Old Mar 6, 2007 | 08:20 PM
  #97  
nj1266's Avatar
Evolved Member
iTrader: (6)
 
Joined: Nov 2004
Posts: 3,254
Likes: 13
From: USA
Originally Posted by l2r99gst
Yes, that is what it would look like when patching for 2-byte load.

As far as logging, I use LogWorks, but what you wrote for EvoScan looks ok to me.


Eric
Eric,

Care to share the logworks formula that you use? Is there anything else that I will need besides the formula to log the 2 byte load?
Reply
Old Mar 6, 2007 | 08:58 PM
  #98  
chrisw's Avatar
Evolved Member
iTrader: (2)
 
Joined: Mar 2003
Posts: 2,217
Likes: 0
From: Santa Cruz
Originally Posted by nj1266
Eric,

Care to share the logworks formula that you use? Is there anything else that I will need besides the formula to log the 2 byte load?
try looking at these posts

https://www.evolutionm.net/forums/sh...4&postcount=62

https://www.evolutionm.net/forums/sh...5&postcount=65

it's pretty straight forward if you have done this in mitsulogger or evoscan
Reply
Old Mar 6, 2007 | 11:29 PM
  #99  
mchuang's Avatar
Evolved Member
iTrader: (11)
 
Joined: Sep 2005
Posts: 2,180
Likes: 1
From: h town
Originally Posted by nj1266
Eric,

Care to share the logworks formula that you use? Is there anything else that I will need besides the formula to log the 2 byte load?

I think something needs to be added to the data file for your rom in ecu flash, but what you type I think is rom specific.
Reply
Old Mar 7, 2007 | 06:35 AM
  #100  
l2r99gst's Avatar
Evolved Member
iTrader: (2)
 
Joined: Mar 2004
Posts: 3,499
Likes: 4
From: CA
Originally Posted by nj1266
Eric,

Care to share the logworks formula that you use? Is there anything else that I will need besides the formula to log the 2 byte load?
NJ,

First, you need to modfy your ROM for 2-byte load logging. You change the first two variables in the MUT table (for requests 00 and 01) to be the high and low byte of real load. The location of your MUT table and your load variable is going to be different from ROM to ROM. JCSBanks posted the locations for a few ROMs in this thread and I have posted the location of the MUT table and gave the definition for it for the 05 ROM. Then, I gave the address of the MSB and LSB for load, which I'm pretty sure is FFFF899A and FFFF899B. I have logged it and it looked correct, but to be 100% sure, maybe someone like JCS should verify.

When that is complete, you can use these formulas (posted by jfitzpat, post #69 in this thread), then chart it with a calculation * 10/32:

For protocols.xml
<datachannel id="#00" name="loadmsb" selected="0" units="load" min="0" max="255" expr="x" type="0"/>
<datachannel id="#01" name="loadlsb" selected="0" units="load" min="0" max="255" expr="x" type="0"/>

Formula:
MC(ECU_Load;%;0;350) = ((loadmsb * 256) + loadlsb)*10/32


The newer version of LogWorks should be able to do the combination in one step by logging request 01000000, but I have simply used what is above.


Eric

Last edited by l2r99gst; Mar 7, 2007 at 06:38 AM.
Reply
Old Mar 10, 2007 | 08:20 AM
  #101  
JoeBee's Avatar
Evolving Member
 
Joined: Sep 2006
Posts: 152
Likes: 0
From: Germany
---------------- NOT VERIFIED ! ----------------

2 Byte Load for EVO VII, ID: 98640014

MUT Table starts at 0x02E9E0
2 Byte Load stand at 0xFFFF885C (high Byte) and 0xFFFF885D (low Byte)

So you can patch:
0x02E9E2 to 0x885C for Load High Byte at MUT ID 00
0x02E9E6 to 0x885D for Load Low Byte at MUT ID 01

---------------- NOT VERIFIED ! ----------------
Reply
Old Mar 10, 2007 | 02:20 PM
  #102  
fbikawi's Avatar
Evolving Member
iTrader: (1)
 
Joined: Sep 2004
Posts: 119
Likes: 0
From: Abu Dhabi, UAE
joebee,

my EVO VII rom is 98640014

i want to log 2 byte load using LogWorks 2. what i could understand after reading is:

1- add two line to 98640014.xml file

<table name="00" address="0x885C" type="ID" level="1" scaling="unit16" />
<table name="01" address="0x885D" type="ID" level="1" scaling="unit16" />

2- add two lines to protocol.xlm of the LogWork:

<datachannel id="#00" name="loadmsb" selected="0" units="load" min="0" max="255" expr="x" type="0" />
<datachannel id="#01" name="loadlsb" selected="0" units="load" min="0" max="255" expr="x" type="0" />

3- using the formula:
MC(ECU_Load;%;0;350) = (loadmsb * 256) + loadlsb

please confirm if at least the first step is correct?? because i did not totally understand what do u mean by patch.

sorry but i am dieing to log the load accurately.
Reply
Old Mar 10, 2007 | 03:37 PM
  #103  
l2r99gst's Avatar
Evolved Member
iTrader: (2)
 
Joined: Mar 2004
Posts: 3,499
Likes: 4
From: CA
Originally Posted by fbikawi
3- using the formula:
MC(ECU_Load;%;0;350) = (loadmsb * 256) + loadlsb
The formula would be:

MC(ECU_Load;%;0;350) = ((loadmsb * 256) + loadlsb)*10/32


Eric
Reply
Old Mar 10, 2007 | 05:19 PM
  #104  
tephra's Avatar
EvoM Guru
15 Year Member
iTrader: (6)
 
Joined: Feb 2007
Posts: 9,486
Likes: 67
From: Melbourne, Australia
Originally Posted by fbikawi
<table name="00" address="0x885C" type="ID" level="1" scaling="unit16" />
<table name="01" address="0x885D" type="ID" level="1" scaling="unit16" />
more like:
<table name="00" address="0x2E9E2" type="ID" level="1" scaling="unit16" />
<table name="01" address="0x2E9E6" type="ID" level="1" scaling="unit16" />

Then in ECU flash you set 00 = 0x885C, and 01 = 0x885D

Cheers
David
Reply
Old Mar 11, 2007 | 01:54 AM
  #105  
tephra's Avatar
EvoM Guru
15 Year Member
iTrader: (6)
 
Joined: Feb 2007
Posts: 9,486
Likes: 67
From: Melbourne, Australia
yippie, I worked out the audm evoix's - and it appears to work...

great mod for AFR tuning thou Although AFRMAP's still don't match up correctly??!?!

It seems to be correct so here goes :

88580013/88580014
2 Byte Load= 0xFFFF6B22
MUT R0 = 0x373C4
MUT R1 = 0x373C8

ie set 0x373C6 = 0x6B22, and 0x373CA = 0x6B23

Last edited by tephra; Mar 11, 2007 at 06:33 AM. Reason: update info
Reply



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