ROM disassembly as raw text file
I put Richard's new tables up on my site.
Roms updated so far:
53610010
5557000x (for me)
5559000x (for Bryan)
Tables added:
IAT to switch Load from Baro+Temp to Baro
Reactive Solenoid Max WGDC vs CTS
OBTR (Over-Boost Timing Retard) Load
OBTR (Over-Boost Timing Retard)
OBTR Variable for Boost Control 0xC78A -> 0xC72E (+ other values)
OBTR SHLR->SHLR2 0x5201 -> 0x5202
OBTR Boost Error RAM Address 0xC5A4 -> 0xC5A2 (+ other values)
OBTR Boost Error RAM Address in Load Error Table 0xC5A4 -> 0xC5A2 (+ other values)
And the Direct Boost tables for 53610010
All thanks goes to Richard. I just added the tables to my site and found the addresses for my rom by copying his work.
Roms updated so far:
53610010
5557000x (for me)
5559000x (for Bryan)
Tables added:
IAT to switch Load from Baro+Temp to Baro
Reactive Solenoid Max WGDC vs CTS
OBTR (Over-Boost Timing Retard) Load
OBTR (Over-Boost Timing Retard)
OBTR Variable for Boost Control 0xC78A -> 0xC72E (+ other values)
OBTR SHLR->SHLR2 0x5201 -> 0x5202
OBTR Boost Error RAM Address 0xC5A4 -> 0xC5A2 (+ other values)
OBTR Boost Error RAM Address in Load Error Table 0xC5A4 -> 0xC5A2 (+ other values)
And the Direct Boost tables for 53610010
All thanks goes to Richard. I just added the tables to my site and found the addresses for my rom by copying his work.
Need to add the 52680015-22 to this...
Thread Starter
Evolved Member
Joined: Oct 2010
Posts: 2,447
Likes: 14
From: Australia
Hi Clipse3GT.
Here's the grab-bag of stuff for 52680015 - 22 :
As usual with these things, double-check the "before" data is sensible, check logs for correct operation, blah blah blah. 
Hope it's useful!
Rich
Here's the grab-bag of stuff for 52680015 - 22 :
Code:
<table name="IAT to switch Load from Baro+Temp to Baro" category="Timing" address="53544" type="1D" scaling="Temp"/>
<table name="Reactive Solenoid Max WGDC vs CTS" category="Turbo" address="5a208" type="2D" scaling="WGDuty">
<table name="Coolant Temp" address="5d2ee" type="Y Axis" elements="8" scaling="Temp"/>
</table>
<table name="OBTR (Over-Boost Timing Retard) Load" category="Load Boost" address="58c70" type="2D" swapxy="true" scaling="Timing">
<table name="Load Error" address="625e0" type="Y Axis" elements="9" scaling="LoadError"/>
</table>
<table name="OBTR (Over-Boost Timing Retard)" category="Direct Boost" address="58c70" type="2D" swapxy="true" scaling="Timing">
<table name="Boost Error" address="625e0" type="Y Axis" elements="9" scaling="BoostErrorPsi"/>
</table>
<table name="OBTR Variable for Boost Control 0xC774 -> 0xC71A" category="Direct Boost" address="21f52" type="1D" scaling="Hex16"/>
<table name="OBTR SHLR->SHLR2 0x5201 -> 0x5202" category="Direct Boost" address="21f54" type="1D" scaling="Hex16"/>
<table name="OBTR Boost Error RAM Address 0xC590 -> 0xC58E" category="Direct Boost" address="21f6a" type="1D" scaling="Hex16"/>
<table name="OBTR Boost Error RAM Address in Load Error Table 0xC590 -> 0xC58E" category="Direct Boost" address="625dc" type="1D" scaling="Hex16"/>
Hope it's useful!
Rich
Thread Starter
Evolved Member
Joined: Oct 2010
Posts: 2,447
Likes: 14
From: Australia
Naff-all, I reckon. 
It was just something I found as I wandered through the timing "load choice" code. I'd heard everyone talking about how the ECU chose this load over 25C, and that load under 25C... and then came across the place were the magic "25C" was stored.
Being pretty new to it all, I slapped it into EcuFlash so I could check out its majesty. And now it's loose in the world like a virus.
I guess it could be useful if someone doesn't want their chosen load changing at 25C. I mean, it could be used to force the ECU to always use "Baro+Temp", same as the fuel maps... by setting it really high.
But that's looking for a "problem" that could be solved by this number! :P
Rich
It was just something I found as I wandered through the timing "load choice" code. I'd heard everyone talking about how the ECU chose this load over 25C, and that load under 25C... and then came across the place were the magic "25C" was stored.
Being pretty new to it all, I slapped it into EcuFlash so I could check out its majesty. And now it's loose in the world like a virus.
I guess it could be useful if someone doesn't want their chosen load changing at 25C. I mean, it could be used to force the ECU to always use "Baro+Temp", same as the fuel maps... by setting it really high.
But that's looking for a "problem" that could be solved by this number! :P
Rich
Added to Goldenevo.com
Hi Clipse3GT.
Here's the grab-bag of stuff for 52680015 - 22 :
As usual with these things, double-check the "before" data is sensible, check logs for correct operation, blah blah blah.
Hope it's useful!
Rich
Here's the grab-bag of stuff for 52680015 - 22 :
Code:
<table name="IAT to switch Load from Baro+Temp to Baro" category="Timing" address="53544" type="1D" scaling="Temp"/>
<table name="Reactive Solenoid Max WGDC vs CTS" category="Turbo" address="5a208" type="2D" scaling="WGDuty">
<table name="Coolant Temp" address="5d2ee" type="Y Axis" elements="8" scaling="Temp"/>
</table>
<table name="OBTR (Over-Boost Timing Retard) Load" category="Load Boost" address="58c70" type="2D" swapxy="true" scaling="Timing">
<table name="Load Error" address="625e0" type="Y Axis" elements="9" scaling="LoadError"/>
</table>
<table name="OBTR (Over-Boost Timing Retard)" category="Direct Boost" address="58c70" type="2D" swapxy="true" scaling="Timing">
<table name="Boost Error" address="625e0" type="Y Axis" elements="9" scaling="BoostErrorPsi"/>
</table>
<table name="OBTR Variable for Boost Control 0xC774 -> 0xC71A" category="Direct Boost" address="21f52" type="1D" scaling="Hex16"/>
<table name="OBTR SHLR->SHLR2 0x5201 -> 0x5202" category="Direct Boost" address="21f54" type="1D" scaling="Hex16"/>
<table name="OBTR Boost Error RAM Address 0xC590 -> 0xC58E" category="Direct Boost" address="21f6a" type="1D" scaling="Hex16"/>
<table name="OBTR Boost Error RAM Address in Load Error Table 0xC590 -> 0xC58E" category="Direct Boost" address="625dc" type="1D" scaling="Hex16"/>
Hope it's useful!
Rich
Thread Starter
Evolved Member
Joined: Oct 2010
Posts: 2,447
Likes: 14
From: Australia
Hi Clipse3GT.
Here's the grab-bag of stuff for 52680015 - 22 :
As usual with these things, double-check the "before" data is sensible, check logs for correct operation, blah blah blah.
Hope it's useful!
Rich
Here's the grab-bag of stuff for 52680015 - 22 :
Code:
<table name="IAT to switch Load from Baro+Temp to Baro" category="Timing" address="53544" type="1D" scaling="Temp"/>
<table name="Reactive Solenoid Max WGDC vs CTS" category="Turbo" address="5a208" type="2D" scaling="WGDuty">
<table name="Coolant Temp" address="5d2ee" type="Y Axis" elements="8" scaling="Temp"/>
</table>
<table name="OBTR (Over-Boost Timing Retard) Load" category="Load Boost" address="58c70" type="2D" swapxy="true" scaling="Timing">
<table name="Load Error" address="625e0" type="Y Axis" elements="9" scaling="LoadError"/>
</table>
<table name="OBTR (Over-Boost Timing Retard)" category="Direct Boost" address="58c70" type="2D" swapxy="true" scaling="Timing">
<table name="Boost Error" address="625e0" type="Y Axis" elements="9" scaling="BoostErrorPsi"/>
</table>
<table name="OBTR Variable for Boost Control 0xC774 -> 0xC71A" category="Direct Boost" address="21f52" type="1D" scaling="Hex16"/>
<table name="OBTR SHLR->SHLR2 0x5201 -> 0x5202" category="Direct Boost" address="21f54" type="1D" scaling="Hex16"/>
<table name="OBTR Boost Error RAM Address 0xC590 -> 0xC58E" category="Direct Boost" address="21f6a" type="1D" scaling="Hex16"/>
<table name="OBTR Boost Error RAM Address in Load Error Table 0xC590 -> 0xC58E" category="Direct Boost" address="625dc" type="1D" scaling="Hex16"/>
Hope it's useful!
Rich
Thank you Rich!!!!
Rich,
Is the "Reactive Solenoid Max WGDC vs CTS" used to limit the wastegate until a certain coolant temperature? Sounds like a feature I would use to keep the wifey from getting into boost to soon. She is a start and run type of driver
Got the address handy for that on 56890010?
Is the "Reactive Solenoid Max WGDC vs CTS" used to limit the wastegate until a certain coolant temperature? Sounds like a feature I would use to keep the wifey from getting into boost to soon. She is a start and run type of driver
Got the address handy for that on 56890010?
Thread Starter
Evolved Member
Joined: Oct 2010
Posts: 2,447
Likes: 14
From: Australia
Yeah, that seems to be exactly what it does. For 56890009, should be:
Personally, I think a 3250rpm "cold" rev limiter would be an awesome idea!
Rich
Code:
<table name="Reactive Solenoid Max WGDC vs CTS" address="5a500" category="Turbo" type="2D" scaling="WGDuty">
<table name="Coolant Temp" address="5d628" type="Y Axis" elements="8" scaling="Temp"/>
</table>
Rich
Yeah, that seems to be exactly what it does. For 56890009, should be:
Personally, I think a 3250rpm "cold" rev limiter would be an awesome idea!
Rich
Code:
<table name="Reactive Solenoid Max WGDC vs CTS" address="5a500" category="Turbo" type="2D" scaling="WGDuty">
<table name="Coolant Temp" address="5d628" type="Y Axis" elements="8" scaling="Temp"/>
</table>
Rich
Actually it wouldnt be to bad of one... ever watch an oil pressure gauge while a car is still cold? Even in the summer heat of Florida its sky high for a while even though the coolant temperature is up to operating temperature... It takes a few minutes longer for the oil to get to operating temperature for pressure to come down to some sane levels.
Thread Starter
Evolved Member
Joined: Oct 2010
Posts: 2,447
Likes: 14
From: Australia
I fitted an oil temp gauge to my last car, and was pretty amazed to see how long it actually took to get to 40C/50C in the morning... nearly 15 minutes.
Very useful on track too...
Rich
Very useful on track too...
Rich
