96940011 05 EVOVIII ROM: Known Patches
Jun 8, 2007, 04:54 PM
#33
Newbie
Join Date: Jan 2005
Posts: 62
Likes: 0
Received 0 Likes
on
0 Posts
MUT Baud rate Patch for ROM ID 96940011
To increase the baudrate being logged in evoscan or mitsulogger
Add the following in 96940011.xml in ecuflash
In ecuflash, edit the entry BAUDRATE2_MUT and change it to 62500
Change your baudrate in either evoscan or mitsulogger to 62500
Enjoy slightly more data.
Add the following in 96940011.xml in ecuflash
PHP Code:
<scaling name="BAUDRATE" units="units" toexpr="500000/(x+1)" frexpr="500000/x-1" format="%.0d" min="0" max="500000" inc="1" storagetype="uint8" endian="big"/>
<table name="BAUDRATE1_OBD" address="cf81" type="1D" level="1" scaling="BAUDRATE"/>
<table name="BAUDRATE2_MUT" address="cfb1" type="1D" level="1" scaling="BAUDRATE"/>
<table name="BAUDRATE3_unknown" address="cfc1" type="1D" level="1" scaling="BAUDRATE"/>
Change your baudrate in either evoscan or mitsulogger to 62500
Enjoy slightly more data.
Last edited by turbotiger; Jun 8, 2007 at 04:57 PM.
Jul 1, 2007, 11:21 AM
#34
Newbie
Join Date: Jan 2005
Posts: 62
Likes: 0
Received 0 Likes
on
0 Posts
2 byte airflow mod
The following adds the 2byte airflow mod. This will allow the evoscan / mitsulogger to log airflow past the 1600hz clipping point. It also adds a finer degree of accuracy to the airflow.
If you've done the 2 byte load, you'll have the ecuflash definitions already loaded.
Change the following values in MUT Table
on the first row (3f314), column E = 89F6
on the first row (3f314), column 12 = 89F7
In evoscan's data.xml, find the section
<Mode2 name="Mode2" type="Data List Items">
Then add the following single line at the end of the section. This is all one line.
In Mitsulogger, add the following to requestid.xml under the section <ECUItems>
In DataLogLab, you can edit the definition file and add this in
If you've done the 2 byte load, you'll have the ecuflash definitions already loaded.
Change the following values in MUT Table
on the first row (3f314), column E = 89F6
on the first row (3f314), column 12 = 89F7
In evoscan's data.xml, find the section
<Mode2 name="Mode2" type="Data List Items">
Then add the following single line at the end of the section. This is all one line.
Code:
<DataListItem DataLog="Y" Color="" Display="Airflow MUT 2Byte Mod" LogReference="Airflow2Byte" RequestID="02" RequestID2="03" Eval="0.09828125x" Unit="Hz" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="2500" ChartMin="0" ChartMax="2500" ScalingFactor=" 0.1" Notes=""/>
Code:
<Request LogReference="AirflowB00" RequestID="02" Eval="x" Unit="INT" Logged="y" Response="2"/> <Request LogReference="AirflowB01" RequestID="03" Eval="x" Unit="INT" Logged="y" Response="2"/> <Request LogReference="Airflow2Byte" RequestID="FF" Eval="6.29/64*((256*AirflowB00)+AirflowB01)" Unit="Int" Logged="y" Response="2"/>
Code:
[Column] Name=AirFlow2byte Description=Air Flow ColumnTitle=AirFlow2Byte DataItemID=82 Type=1 ColumnDecimalPlaces=4 DisplayDecimalPlaces=2
Last edited by turbotiger; Jul 1, 2007 at 11:23 AM.
. Maybe I will add the last two and play with them later this week 
Jul 17, 2007, 09:06 AM
#37
Evolving Member
iTrader: (1)
Join Date: Mar 2007
Location: Coastal Maine
Posts: 315
Likes: 0
Received 0 Likes
on
0 Posts
https://www.evolutionm.net/forums/sh...jdm+map+sensor
Does this in fact work with the 96940011 rom, as it states?
CB
Jul 17, 2007, 06:48 PM
#38
https://www.evolutionm.net/forums/sh...jdm+map+sensor
Does this in fact work with the 96940011 rom, as it states?
CB
Does this in fact work with the 96940011 rom, as it states?
CB
Jul 27, 2007, 03:51 AM
#40
Evolving Member
iTrader: (8)
Join Date: Nov 2005
Location: Seattle, Washington
Posts: 155
Likes: 0
Received 0 Likes
on
0 Posts
I just wanted to chime in for those that may be following this thread...
It looks like most all the patches I have are already posted above. All the ones I have listed below are confirmed working (at least for me
). Below is all the patches copied directly from my ROM and a couple of instructions for setup and Evoscan.
below gives you:
MUT 2 byte load
MUT 2 byte Airflow
Lean Spool Enable/Disable
62500 baud rate
Perephery, Perephery 1, Perephery 2, Perephery 3
log WGDC in evoscan (patch for evoscan)
Paste at bottom of 96940011.xml (Just before </ROM>)
Lean spool Enable/Disable
Change both Lean Spool tables in ECUflash to 1500 to DISABLE
MUT Baud rate Patch
In ECUflash, change value in BAUDRATE2_MUT to 62500.
In Evoscan or Mitsulogger, change baud rate to 62500.
MUT 2 byte Load
Change values in MUT table:
on the first row (3f314), column 6 = 899A
on the first row (3f314), column A = 899B
(Must type 0x before value, 0x899A)
to log in Evoscan, select MUT 2 byte load
MUT 2 byte airflow
Change the values in MUT Table:
on the first row (3f314), column E = 89F6
on the first row (3f314), column 12 = 89F7
To log in Evoscan, add the following to Data.xml
Perephery, Perephery 1, Perephery 2, Perephery 3,
You can add these tables but for now leave all settings here alone. Work still in progress. HUGE DISCOVERY! Should be able to soon disable rear o2 CEL among many other changes.
Perephery 0 rear o2 sensor, change from 1 to 0 THREAD TO USE THIS HERE
ECU_PEREPHERY1 bit0 ENABLES/DISABLES LEAN SPOOL?
Perephery 2 ECU_PEREPHERY2 BIT 9 = ENABLE MAP SENSOR TEST.
To disable it set it to 0, The last 2 bits on the High byte are interesting, bit0 disables/enables OBD-II altogether, Bit1 enables/disables the EGR test, bit1 specifically controls the EGR test? Is it only the EGR test?
ECU_PEREPHERY2 BIT 10 also used in some checks in wich MDP present
Ecu_perephery3 seems to be a bit_coded obd checks and tests
Periphery 3 control the OBD2 readiness checks?
ECU_PEREPHERY4 FOUND!!!!!!! 0xFEA . APPEARED IN EVO9
ECU_PEREPHERY4 bit 14 controlls that test. (MDP-BARO compare to 1abc value) disabling bit 14 alone does stop the CEL.
Log WGDC in Evoscan
add to data.xml
Anyway, these patches are all confirmed working...
-Scott
It looks like most all the patches I have are already posted above. All the ones I have listed below are confirmed working (at least for me
). Below is all the patches copied directly from my ROM and a couple of instructions for setup and Evoscan. below gives you:
MUT 2 byte load
MUT 2 byte Airflow
Lean Spool Enable/Disable
62500 baud rate
Perephery, Perephery 1, Perephery 2, Perephery 3
log WGDC in evoscan (patch for evoscan)
Paste at bottom of 96940011.xml (Just before </ROM>)
PHP Code:
<table name="MUT table" address="3f314" type="3D" level="1" scaling="Hex16">
<table name="X" type="Static X Axis" elements="16" scaling="Hex16">
<data>4</data>
<data>6</data>
<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>
</table>
<table name="Y" type="Static Y Axis" elements="32">
<data>3f314</data>
<data>3f334</data>
<data>3f354</data>
<data>3f374</data>
<data>3f394</data>
<data>3f3B4</data>
<data>3f3D4</data>
<data>3f3F4</data>
<data>3f414</data>
<data>3f434</data>
<data>3f444</data>
<data>3f474</data>
<data>3f494</data>
<data>3f4B4</data>
<data>3f4D4</data>
<data>3f4F4</data>
<data>3f514</data>
<data>3f534</data>
<data>3f554</data>
<data>3f574</data>
<data>3f594</data>
<data>3f5B4</data>
<data>3f5D4</data>
<data>3f5F4</data>
<data>3f614</data>
<data>3f634</data>
<data>3f654</data>
<data>3f674</data>
<data>3f694</data>
<data>3f6B4</data>
<data>3f6D4</data>
<data>3f6F4</data>
<data>3f714</data>
</table>
</table>
<scaling name="BAUDRATE" units="units" toexpr="500000/(x+1)" frexpr="500000/x-1" format="%.0d" min="0" max="500000" inc="1" storagetype="uint8" endian="big"/>
<table name="BAUDRATE1_OBD" address="cf81" type="1D" level="1" scaling="BAUDRATE"/>
<table name="BAUDRATE2_MUT" address="cfb1" type="1D" level="1" scaling="BAUDRATE"/>
<table name="BAUDRATE3_unknown" address="cfc1" type="1D" level="1" scaling="BAUDRATE"/>
<table name="LeanSpoolEnable" category="Misc" address="1280" type="1D" level="1" scaling="RPMStatLimit"/>
<table name="LeanSpoolDisable" category="Misc" address="1284" type="1D" level="1" scaling="RPMStatLimit"/>
<table name="ECU_PEREPHERY" category="Misc" address="faa" type="1D" level="4" scaling="Hex16"/>
<table name="ECU_PEREPHERY1" category="Misc" address="fba" type="1D" level="4" scaling="Hex16"/>
<table name="ECU_PEREPHERY2" category="Misc" address="fca" type="1D" level="4" scaling="Hex16"/>
<table name="ECU_PEREPHERY3" category="Misc" address="fda" type="1D" level="4" scaling="Hex16"/>
Change both Lean Spool tables in ECUflash to 1500 to DISABLE
MUT Baud rate Patch
In ECUflash, change value in BAUDRATE2_MUT to 62500.
In Evoscan or Mitsulogger, change baud rate to 62500.
MUT 2 byte Load
Change values in MUT table:
on the first row (3f314), column 6 = 899A
on the first row (3f314), column A = 899B
(Must type 0x before value, 0x899A)
to log in Evoscan, select MUT 2 byte load
MUT 2 byte airflow
Change the values in MUT Table:
on the first row (3f314), column E = 89F6
on the first row (3f314), column 12 = 89F7
To log in Evoscan, add the following to Data.xml
PHP Code:
<DataListItem DataLog="Y" Color="" Display="Airflow MUT 2Byte Mod" LogReference="Airflow2Byte" RequestID="02" RequestID2="03" Eval="0.09828125x" Unit="Hz" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="2500" ChartMin="0" ChartMax="2500" ScalingFactor=" 0.1" Notes=""/>
You can add these tables but for now leave all settings here alone. Work still in progress. HUGE DISCOVERY! Should be able to soon disable rear o2 CEL among many other changes.
Perephery 0 rear o2 sensor, change from 1 to 0 THREAD TO USE THIS HERE
ECU_PEREPHERY1 bit0 ENABLES/DISABLES LEAN SPOOL?
Perephery 2 ECU_PEREPHERY2 BIT 9 = ENABLE MAP SENSOR TEST.
To disable it set it to 0, The last 2 bits on the High byte are interesting, bit0 disables/enables OBD-II altogether, Bit1 enables/disables the EGR test, bit1 specifically controls the EGR test? Is it only the EGR test?
ECU_PEREPHERY2 BIT 10 also used in some checks in wich MDP present
Ecu_perephery3 seems to be a bit_coded obd checks and tests
Periphery 3 control the OBD2 readiness checks?
ECU_PEREPHERY4 FOUND!!!!!!! 0xFEA . APPEARED IN EVO9
ECU_PEREPHERY4 bit 14 controlls that test. (MDP-BARO compare to 1abc value) disabling bit 14 alone does stop the CEL.
Log WGDC in Evoscan
add to data.xml
PHP Code:
<DataListItem DataLog="Y" Display="WGDC" LogReference="WGDC" RequestID="86" Eval="x/2" Unit="%" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="100" ChartMin="0" ChartMax="100"/>
Anyway, these patches are all confirmed working...
-Scott
Last edited by WTF_LOL; Jul 28, 2007 at 11:11 AM.
Jul 27, 2007, 09:46 PM
#43
Evolving Member
iTrader: (8)
Join Date: Nov 2005
Location: Seattle, Washington
Posts: 155
Likes: 0
Received 0 Likes
on
0 Posts
Thank you for your help today! however, it does not apear FFFF8976 is correct or there is something I did incorrectly. I put 8976 in 02 and 8977 in 03 and selected RPM 2 byte in evoscan. 2 byte RPM was logging in incorrect values. The wierd thing is, the log followed engine RPMs basic curves but, it was really exagerated. The spikes and dips happened at the same time but there was not the same difference between the two. I do not have access to the log right now but as an example, when engine RPM was at 906.25, 2byte RPM was at 7093.75. Then when Engine RPM is at 1312.5, 2 byte RPM is at 10593.75.
Anyway, if anybody has any advice on this I would appreciate it.
Thanks!
-Scott
Jul 28, 2007, 12:39 AM
#45
Evolving Member
iTrader: (8)
Join Date: Nov 2005
Location: Seattle, Washington
Posts: 155
Likes: 0
Received 0 Likes
on
0 Posts
Those two points I showed where not spikes, those where just two random points I had written down to help express the fact that they both followed similar curves but, that they where not always an equal difference. With the FFFF8976, 2 byte RPM was constantley in like the ~10k ~50k ranges and it was not always an exact difference between engine rpm and 2 byte rpm. However, I did just realize that the difference between those two points I listed are nearly the same percentage, so maybe that is the right variable for the MUT table but the calculation formula is incorrect?
I will post a log tomorrow to better express what I saw.
Anybody have any input?