Official 2 byte thread!
#316
Evolved Member
iTrader: (14)
I was recently tuning an Ev08, with 94170015, at some considerable altitude and discovered that the 2-byte load address (895C,895D) was incorrect.
Or more likley, an un-compensated 2-byte load address.
The Load_IAT_BARO_16 address is at 8960, 8961.
Perhaps someone in Colorado might like to test this also and confirm/refute the result.
This got me wondering if any other addresses as listed in Jacks first post may in fact be un-compensated 2-byte.
Or more likley, an un-compensated 2-byte load address.
The Load_IAT_BARO_16 address is at 8960, 8961.
Perhaps someone in Colorado might like to test this also and confirm/refute the result.
This got me wondering if any other addresses as listed in Jacks first post may in fact be un-compensated 2-byte.
#318
#319
Newbie
Seeking help logging 2 byte load, driving me crazy, any help appeciated
I have an Australian market delivered Evo IX with internal ID 88580014 which inherits 88580013
I've edited the 88580013 rom to have the following code to enable 2byte load
<table name="2 byte load high bit" address="373C6" category="Misc" type="1D" level="1" scaling="uint16" />
<table name="2 byte load low bit" address="373CA" category="Misc" type="1D" level="1" scaling="uint16" />
..and in ECUFlash (v 1.42 and 1.43) I've edited the MUT table MUT00 from 0x6A09 to 0x6B22 and MUT01 from 0x6A08 to 0x6B23
Prior to changing the MUT codes the 373C6 value is at 27145 and the 373CA value is at 27144. After I enter the new MUT00/01 values I get 27426 and 27427
In EvoScan (using Navigator version to log) I have edited the Data.xml to include the following
<DataListItem DataLog="Y" Color="" Display="Load MUT 2Byte Mod" LogReference="Load2" RequestID="00" RequestID2="01" Eval="0.3125*x" Unit="load" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="500" ChartMin="0" ChartMax="500" ScalingFactor="1" Priority="1" Visible="False" />
Previously I've logged over 140 runs and used LoadCalc with no probs, but everyone is saying 2 byte load is more accurate. I've attached an image of the log file data I'm getting with the above set-up, generally zero's but under load, values up to 0.91
Ideas and suggestions welcomed.
I have an Australian market delivered Evo IX with internal ID 88580014 which inherits 88580013
I've edited the 88580013 rom to have the following code to enable 2byte load
<table name="2 byte load high bit" address="373C6" category="Misc" type="1D" level="1" scaling="uint16" />
<table name="2 byte load low bit" address="373CA" category="Misc" type="1D" level="1" scaling="uint16" />
..and in ECUFlash (v 1.42 and 1.43) I've edited the MUT table MUT00 from 0x6A09 to 0x6B22 and MUT01 from 0x6A08 to 0x6B23
Prior to changing the MUT codes the 373C6 value is at 27145 and the 373CA value is at 27144. After I enter the new MUT00/01 values I get 27426 and 27427
In EvoScan (using Navigator version to log) I have edited the Data.xml to include the following
<DataListItem DataLog="Y" Color="" Display="Load MUT 2Byte Mod" LogReference="Load2" RequestID="00" RequestID2="01" Eval="0.3125*x" Unit="load" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="500" ChartMin="0" ChartMax="500" ScalingFactor="1" Priority="1" Visible="False" />
Previously I've logged over 140 runs and used LoadCalc with no probs, but everyone is saying 2 byte load is more accurate. I've attached an image of the log file data I'm getting with the above set-up, generally zero's but under load, values up to 0.91
Ideas and suggestions welcomed.
#320
Evolved Member
The Evoscan part is correct, but you have a few things wrong there:
<table name="2 byte load Hi_byte" address="373C6" category="Misc" type="1D" scaling="Hex16" />
<table name="2 byte load Lo_byte" address="373CA" category="Misc" type="1D" scaling="Hex16" />
and set the data:
6B24
6B25
<table name="2 byte load Hi_byte" address="373C6" category="Misc" type="1D" scaling="Hex16" />
<table name="2 byte load Lo_byte" address="373CA" category="Misc" type="1D" scaling="Hex16" />
and set the data:
6B24
6B25
Last edited by merlin.oz; Jul 27, 2011 at 10:16 PM.
#321
Newbie
Thanks for the reply Merlin.
I made the suggested changes and note that 373C4 for hi_byte puts me in the MUT0- (FFFF or 65535 decimal) field. MUT00 is definitely 373C6 and MUT01 is 373CA, so I think it should be...
<table name="2 byte load Hi_byte" address="373C6" category="Misc" type="1D" scaling="uint16" />
<table name="2 byte load Lo_byte" address="373CA" category="Misc" type="1D" scaling="uint16" />
...and now I've tried it with 6B24 (27428 decimal) and 6B25 (27429 decimal), both swapped for low and high as well, but still not sending the right signal through. any other address suggestions for MUT00 and MUT01?
Regards,
Gavin
I made the suggested changes and note that 373C4 for hi_byte puts me in the MUT0- (FFFF or 65535 decimal) field. MUT00 is definitely 373C6 and MUT01 is 373CA, so I think it should be...
<table name="2 byte load Hi_byte" address="373C6" category="Misc" type="1D" scaling="uint16" />
<table name="2 byte load Lo_byte" address="373CA" category="Misc" type="1D" scaling="uint16" />
...and now I've tried it with 6B24 (27428 decimal) and 6B25 (27429 decimal), both swapped for low and high as well, but still not sending the right signal through. any other address suggestions for MUT00 and MUT01?
Regards,
Gavin
The Evoscan part is correct, but you have a few things wrong there:
<table name="2 byte load Hi_byte" address="373C4" category="Misc" type="1D" scaling="uint16" />
<table name="2 byte load Lo_byte" address="373C6" category="Misc" type="1D" scaling="uint16" />
and set the data:
6B24
6B25
<table name="2 byte load Hi_byte" address="373C4" category="Misc" type="1D" scaling="uint16" />
<table name="2 byte load Lo_byte" address="373C6" category="Misc" type="1D" scaling="uint16" />
and set the data:
6B24
6B25
#323
Newbie
Thanks again for the reply, still not working.
I changed the code as follows in my 88580013.xml file as follows
<table name="2 byte load high bit" address="373C4" category="Misc" type="1D" level="1" scaling="uint16" />
<table name="2 byte load low bit" address="373C6" category="Misc" type="1D" level="1" scaling="uint16" />
I get the result shown in attachment Table Changes.jpg
Then when I adjust the values of 2 byte high load and low load to 27428 and 27429 respectively, I get the result shown in Table Change01.jpg
You're saying this is correct?
Regards,
Gavin
I changed the code as follows in my 88580013.xml file as follows
<table name="2 byte load high bit" address="373C4" category="Misc" type="1D" level="1" scaling="uint16" />
<table name="2 byte load low bit" address="373C6" category="Misc" type="1D" level="1" scaling="uint16" />
I get the result shown in attachment Table Changes.jpg
Then when I adjust the values of 2 byte high load and low load to 27428 and 27429 respectively, I get the result shown in Table Change01.jpg
You're saying this is correct?
Regards,
Gavin
#324
Evolved Member
Sorry, I see your problem now, add this scrap to your def for the MUT, then fix MUT00 and 01.
I was forgetting about those pesky FFFF's which the scaling shown below eliminates.
My previous posts now have ammended addresses and scaling. The scaling should have been Hex16, not uint16.
<scaling name="RamAddress" units="hex" toexpr="x-4294901760" frexpr="x+4294901760" format="%04x" min="0" max="65535" inc="1" storagetype="uint32" endian="big"/>
<table name="MUT Table" address="373c4" category="MUT" type="3D" scaling="RamAddress">
<table name="X" type="Static X Axis" elements="16">
<data>0</data>
<data>1</data>
<data>2</data>
<data>3</data>
<data>4</data>
<data>5</data>
<data>6</data>
<data>7</data>
<data>8</data>
<data>9</data>
<data>A</data>
<data>B</data>
<data>C</data>
<data>D</data>
<data>E</data>
<data>F</data>
</table>
<table name="Y" type="Static Y Axis" elements="30">
<data>MUT0X</data>
<data>MUT1X</data>
<data>MUT2X</data>
<data>MUT3X</data>
<data>MUT4X</data>
<data>MUT5X</data>
<data>MUT6X</data>
<data>MUT7X</data>
<data>MUT8X</data>
<data>MUT9X</data>
<data>MUTAX</data>
<data>MUTBX</data>
<data>MUTCX</data>
<data>MUTDX</data>
<data>MUTEX</data>
<data>MUTFX</data>
<data>MUT10X</data>
<data>MUT11X</data>
<data>MUT12X</data>
<data>MUT13X</data>
<data>MUT14X</data>
<data>MUT15X</data>
<data>MUT16X</data>
<data>MUT17X</data>
<data>MUT18X</data>
<data>MUT19X</data>
<data>MUT1AX</data>
<data>MUT1BX</data>
<data>MUT1CX</data>
<data>MUT1DX</data>
</table>
</table>
I was forgetting about those pesky FFFF's which the scaling shown below eliminates.
My previous posts now have ammended addresses and scaling. The scaling should have been Hex16, not uint16.
<scaling name="RamAddress" units="hex" toexpr="x-4294901760" frexpr="x+4294901760" format="%04x" min="0" max="65535" inc="1" storagetype="uint32" endian="big"/>
<table name="MUT Table" address="373c4" category="MUT" type="3D" scaling="RamAddress">
<table name="X" type="Static X Axis" elements="16">
<data>0</data>
<data>1</data>
<data>2</data>
<data>3</data>
<data>4</data>
<data>5</data>
<data>6</data>
<data>7</data>
<data>8</data>
<data>9</data>
<data>A</data>
<data>B</data>
<data>C</data>
<data>D</data>
<data>E</data>
<data>F</data>
</table>
<table name="Y" type="Static Y Axis" elements="30">
<data>MUT0X</data>
<data>MUT1X</data>
<data>MUT2X</data>
<data>MUT3X</data>
<data>MUT4X</data>
<data>MUT5X</data>
<data>MUT6X</data>
<data>MUT7X</data>
<data>MUT8X</data>
<data>MUT9X</data>
<data>MUTAX</data>
<data>MUTBX</data>
<data>MUTCX</data>
<data>MUTDX</data>
<data>MUTEX</data>
<data>MUTFX</data>
<data>MUT10X</data>
<data>MUT11X</data>
<data>MUT12X</data>
<data>MUT13X</data>
<data>MUT14X</data>
<data>MUT15X</data>
<data>MUT16X</data>
<data>MUT17X</data>
<data>MUT18X</data>
<data>MUT19X</data>
<data>MUT1AX</data>
<data>MUT1BX</data>
<data>MUT1CX</data>
<data>MUT1DX</data>
</table>
</table>
Last edited by merlin.oz; Jul 27, 2011 at 10:20 PM.
#325
Newbie
combined your code and while I was at it transitioned to Tephra Mod V7, took a while to adjust all the maps with the added resolution in fuel and timing...and skipped straight to Load1Byte. Hope this now isn't off topic. I've posted the results of a log comparing LoadCalc and Load1Byte
Thanks again Merlin for sharing your knowledge
Thanks again Merlin for sharing your knowledge
#328
Evolving Member
Join Date: Mar 2008
Location: The mitten
Posts: 142
Likes: 0
Received 0 Likes
on
0 Posts
+1 to this, the link for the MUT table is broken. can some one re-host it somewhere?