2 Byte RPM for IX - 88590015?
pd1 pm'd me today asking about this so I thought I would post here as well:
2byte RPM was easy - BUT i think there might be something wrong with it.
find your high octane map, then look up the rpm axis andd find that in the ROM
the previous 2 bytes should be 00 0F, the previous 4 bytes to that will be FF FF XX YY.
Thats the memory address for RPM that the ECU uses when looking up MAPS...
BUT when I log that and normal RPM, 2byte RPM seems to LAG behind normal RPM by 1 request if you know what I mean...
let me know how you get on!
cheers
d.
2byte RPM was easy - BUT i think there might be something wrong with it.
find your high octane map, then look up the rpm axis andd find that in the ROM
the previous 2 bytes should be 00 0F, the previous 4 bytes to that will be FF FF XX YY.
Thats the memory address for RPM that the ECU uses when looking up MAPS...
BUT when I log that and normal RPM, 2byte RPM seems to LAG behind normal RPM by 1 request if you know what I mean...
let me know how you get on!
cheers
d.
Does anyone understand this or has tried it? Has it worked?
ok girls(:P) - since you are soo bloody slack 
Hehe
Two byte load for 88590015 is 0xFFFF6B42
This means you need to put 0xFFFF6B42 into MUT02 and 0xFFFF6B43 into MUT03 - if you don't understand this go and read the other thread !
Hehe
Two byte load for 88590015 is 0xFFFF6B42
This means you need to put 0xFFFF6B42 into MUT02 and 0xFFFF6B43 into MUT03 - if you don't understand this go and read the other thread !
Newbie
Joined: Jan 2007
Posts: 16
Likes: 0
Evolving Member
Joined: May 2007
Posts: 178
Likes: 0
From: Italy
88840016
For 88840016 owners here it is the 2-byte RPM:
EcuFlash: add this lines to 88840016.xml just before </rom>
<table name="MUT02 2-byte RPM MSB" category="MUT" address="37802" type="1D" level="1" scaling="Hex16"/>
<table name="MUT03 2-byte RPM LSB" category="MUT" address="37806" type="1D" level="1" scaling="Hex16"/>
Values:
MUT02 from 6A11 to 6AFE (hex: enter 0x6AFE)
MUT03 from 6A10 to 6AFF (hex: enter 0x6AFF)
EvoScan: modify your Data.xml line from
<DataListItem DataLog="N" Color="" Display="RPM MUT 2Byte Mod" LogReference="RPMMUT2Byte" RequestID="02" RequestID2="03" Eval="31.25x" Unit="units" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="8000" ChartMin="0" ChartMax="8000" ScalingFactor="0.1" Notes=""/>
to
<DataListItem DataLog="N" Color="" Display="RPM MUT 2Byte Mod" LogReference="RPMMUT2Byte" RequestID="02" RequestID2="03" Eval="1000x/256" Unit="units" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="8000" ChartMin="0" ChartMax="8000" ScalingFactor="0.1" Notes=""/>
The new scaling is 1000x/256 (0x0100 is 1000 rpm).
Enjoy
EcuFlash: add this lines to 88840016.xml just before </rom>
<table name="MUT02 2-byte RPM MSB" category="MUT" address="37802" type="1D" level="1" scaling="Hex16"/>
<table name="MUT03 2-byte RPM LSB" category="MUT" address="37806" type="1D" level="1" scaling="Hex16"/>
Values:
MUT02 from 6A11 to 6AFE (hex: enter 0x6AFE)
MUT03 from 6A10 to 6AFF (hex: enter 0x6AFF)
EvoScan: modify your Data.xml line from
<DataListItem DataLog="N" Color="" Display="RPM MUT 2Byte Mod" LogReference="RPMMUT2Byte" RequestID="02" RequestID2="03" Eval="31.25x" Unit="units" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="8000" ChartMin="0" ChartMax="8000" ScalingFactor="0.1" Notes=""/>
to
<DataListItem DataLog="N" Color="" Display="RPM MUT 2Byte Mod" LogReference="RPMMUT2Byte" RequestID="02" RequestID2="03" Eval="1000x/256" Unit="units" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="8000" ChartMin="0" ChartMax="8000" ScalingFactor="0.1" Notes=""/>
The new scaling is 1000x/256 (0x0100 is 1000 rpm).
Enjoy
Evolving Member
Joined: May 2007
Posts: 178
Likes: 0
From: Italy
No, different map. MUT addresses are different, tephra wrote the values to insert a few posts ago.
You can try this in 88590015.xml:
<table name="MUT02 2-byte RPM MSB" category="MUT" address="3EE8E" type="1D" level="1" scaling="Hex16"/>
<table name="MUT03 2-byte RPM LSB" category="MUT" address="3EE92" type="1D" level="1" scaling="Hex16"/>
Values:
MUT02 from 6A29 to 6B1E (hex: enter 0x6B1E)
MUT03 from 6A28 to 6B1F (hex: enter 0x6B1F)
Don't know about Evoscan scaling for USDM.
You can try this in 88590015.xml:
<table name="MUT02 2-byte RPM MSB" category="MUT" address="3EE8E" type="1D" level="1" scaling="Hex16"/>
<table name="MUT03 2-byte RPM LSB" category="MUT" address="3EE92" type="1D" level="1" scaling="Hex16"/>
Values:
MUT02 from 6A29 to 6B1E (hex: enter 0x6B1E)
MUT03 from 6A28 to 6B1F (hex: enter 0x6B1F)
Don't know about Evoscan scaling for USDM.
v99 there is no scaling. The above was for adding to the ECUflash ROM type xml. For the type 15 I have this:
<table name="2 byte load high bit" category="Misc" address="3ee86" type="1D" level="1" scaling="uint16"/>
<table name="2 byte load low bit" category="Misc" address="3ee8a" type="1D" level="1" scaling="uint16"/>
then change the values to:
27459 and 27550 respectively. Just type in them in no having to use the 0x then hex (though those values are probably the same actually).
<table name="2 byte load high bit" category="Misc" address="3ee86" type="1D" level="1" scaling="uint16"/>
<table name="2 byte load low bit" category="Misc" address="3ee8a" type="1D" level="1" scaling="uint16"/>
then change the values to:
27459 and 27550 respectively. Just type in them in no having to use the 0x then hex (though those values are probably the same actually).
2byte RPM
MUT 02 = 6B1E
MUT 03 = 6B1F
Here is the new eval for your RPM Eval="1000*x/256" to add to the data.xml in EvoScan.
If you are using the MUT table you can put them at any MUT request you want (assuming it doesnt overwrite one that you need). According to tephra (and I have noticed this as well) the 4x line in the MUT isnt used by anything.
MUT 02 = 6B1E
MUT 03 = 6B1F
Here is the new eval for your RPM Eval="1000*x/256" to add to the data.xml in EvoScan.
If you are using the MUT table you can put them at any MUT request you want (assuming it doesnt overwrite one that you need). According to tephra (and I have noticed this as well) the 4x line in the MUT isnt used by anything.
