ROM disassembly as raw text file

Reply Subscribe

Thread Tools

Search this Thread

Sep 1, 2011 | 03:23 PM

#106

merlin.oz

Evolved Member

Joined: Jun 2008

Posts: 824

Likes: 24

From: Sydney

That error correction thing is a really nice tweak Richard.

Sep 1, 2011 | 04:47 PM

#107

richardjh

Thread Starter

Evolved Member

Joined: Oct 2010

Posts: 2,447

Likes: 14

From: Australia

Quote:

Originally Posted by Golden

Also, I understand the need for clearing out the old positive correction, but you can fix that by having better boost targets in the upper RPM range.

Yeah, you'd think.

But without this patch, you can carry zero or negative EC correction into an SST WOT upshift and still see sub-optimal boost control...

Here's a log from a few days before I applied it:

Boost error was -0.7psi right before the shift.

Then, the ECU gets all excited comparing RPM, boost targets, "actual" boost, etc. 0.2 seconds into the upshift, it reckons WTF, BOOST IS 2PSI TOO LOW!

0.2 seconds after that, OH NOES, BOOST IS TOO HIGH!

My little patch shuts down the ECU's first (pointless) response. While there may still be some upward pressure on boost in the second half of the shift, at least there won't be more fuel on the fire from the WGDC error correction system...

Rich

Attached Thumbnails

ROM disassembly as raw text file-2011.09.02_upward1.png

Sep 1, 2011 | 08:51 PM

#108

Golden

Evolved Member

iTrader: (1)

Joined: Nov 2009

Posts: 1,456

Likes: 0

From: Omaha, NE

You SST guys are always trying to maintain boost. Just vent it like the rest of us.

(Sarcasm)

Sep 1, 2011 | 09:11 PM

#109

richardjh

Thread Starter

Evolved Member

Joined: Oct 2010

Posts: 2,447

Likes: 14

From: Australia

My next patch will be "SST Lift-To-Shift"!!! lol

Rich

Sep 2, 2011 | 12:24 AM

#110

RS200Z

Evolving Member

Joined: Jan 2009

Posts: 150

Likes: 0

From: Singapore

Quote:

Originally Posted by richardjh

Sure thing - as soon as I'm done playing with boost error correction code!

And heeeeere's some I prepared earlier!...

Rich

This boost control during upshifting for SST is just what I need on my SST! What does it take to implement this on the 53050009 ROM?

Last edited by RS200Z; Sep 2, 2011 at 12:32 AM.

Sep 2, 2011 | 12:33 AM

#111

richardjh

Thread Starter

Evolved Member

Joined: Oct 2010

Posts: 2,447

Likes: 14

From: Australia

Edited to keep up with your edit!

I'll dig out the OBTR EcuFlash defs you want for 53050009... hopefully tonight.

As for the boost tweak, that's a whole different story. There are good, manageable ways of doing it, and really s**tty ways of doing it. Let me think about that and get back to you.

Rich

Last edited by richardjh; Sep 2, 2011 at 12:51 AM.

Sep 2, 2011 | 05:40 AM

#112

richardjh

Thread Starter

Evolved Member

Joined: Oct 2010

Posts: 2,447

Likes: 14

From: Australia

Various defs for 53050009...

Code:

  <table name="Reactive Solenoid Max WGDC vs CTS" category="Turbo" address="5a228" type="2D" scaling="WGDuty">
    <table name="Coolant Temp" address="5d32a" type="Y Axis" elements="8" scaling="Temp"/>
  </table>
 
  <table name="OBTR (Over-Boost Timing Retard)" category="Direct Boost" address="58c74" type="2D" swapxy="true" scaling="Timing">
    <table name="Boost Error" address="6261e" type="Y Axis" elements="9" scaling="BoostErrorPsi"/>
  </table>
  <table name="OBTR Variable for Boost Control 0xC76C -> 0xC712" category="Direct Boost" address="21cc6" type="1D" scaling="Hex16"/>
  <table name="OBTR SHLR->SHLR2 0x5201 -> 0x5202" category="Direct Boost" address="21cc8" type="1D" scaling="Hex16"/>
  <table name="OBTR Boost Error RAM Address 0xC588 -> 0xC586" category="Direct Boost" address="21cde" type="1D" scaling="Hex16"/>
  <table name="OBTR Boost Error RAM Address in Load Error Table 0xC588 -> 0xC586" category="Direct Boost" address="6261a" type="1D" scaling="Hex16"/>
 
 
  <table name="OBTR (Over-Boost Timing Retard) Load" category="Load Boost" address="58c74" type="2D" swapxy="true" scaling="Timing">
    <table name="Load Error" address="6261e" type="Y Axis" elements="9" scaling="LoadError"/>
  </table>

As usual, please apply with all due care. Test and log.

I'll send these to Golden...

Rich

Sep 2, 2011 | 08:28 AM

#113

Golden

Evolved Member

iTrader: (1)

Joined: Nov 2009

Posts: 1,456

Likes: 0

From: Omaha, NE

Rich is funny...

He has been editing GoldenEvo.com with these definitions. I gave him access. So you all can thank him for adding them to the site.

Sep 2, 2011 | 08:34 AM

#114

itzwolf

Evolved Member

iTrader: (9)

Joined: Mar 2005

Posts: 1,193

Likes: 2

From: Florida

Rich,

Since you've become one of our beloved ROM experts

Golden's 56890009.xml is missing some of the Omni 4 Bar definitions. It appears the MAP tables and a few other things for rescaling are already there. I put together what is missing by duplicating the Load Boost stuff and grabbed the missing scaling factors from the Omni thread but there looks like there are 3 addresses that are needed still for ECU parameters etc.

The addresses in question from the 52680015.xml are:

Code:

  <table name="Omni4bar #1 0x03B6 -> 0x02FF" address="17d76" category="Omni 4 Bar Boost" type="1D" scaling="Hex16" /> 
  <table name="Omni4bar #2 0x0ED8 -> 0x0BFC" address="17da6" category="Omni 4 Bar Boost" type="1D" scaling="Hex16" /> 
  <table name="Omni4bar #3 0x0ED8 -> 0x0BFC" address="17dba" category="Omni 4 Bar Boost" type="1D" scaling="Hex16" />

Also I noticed the address is wrong for this particular definition:

Code:

<table name="Minimum IPW Code Path modifier #1 (0x7f09 -> 0x7f06)" address="30648" category="Fuel" type="1D" level="2" scaling="Hex16" />

Which reports "0x5141" instead of "0x7f09".

When you're poking around again do you think you could look these up?

Many thanks in advance!!

Sep 2, 2011 | 08:41 AM

#115

richardjh

Thread Starter

Evolved Member

Joined: Oct 2010

Posts: 2,447

Likes: 14

From: Australia

Quote:

Originally Posted by Golden

Rich is funny...

He has been editing GoldenEvo.com with these definitions. I gave him access. So you all can thank him for adding them to the site.

Damn, now everyone's gonna know who to blame when your site asplodes!

Rich

Sep 2, 2011 | 09:17 AM

#116

richardjh

Thread Starter

Evolved Member

Joined: Oct 2010

Posts: 2,447

Likes: 14

From: Australia

For Omni4bar, I reckon it's as follows for 56890009/10....

Code:

  <table name="Omni4bar #1 0x03B6 -> 0x02FF" address="1a2ee" category="Omni 4 Bar Boost" type="1D" scaling="Hex16" /> 
  <table name="Omni4bar #2 0x0ED8 -> 0x0BFC" address="1a31e" category="Omni 4 Bar Boost" type="1D" scaling="Hex16" /> 
  <table name="Omni4bar #3 0x0ED8 -> 0x0BFC" address="1a332" category="Omni 4 Bar Boost" type="1D" scaling="Hex16" />

Please note: I wouldn't know an actual Omni4bar if it fell on me!

Also for 56890009/10....

The IPW problem looks one digit should have been a 9 instead of 6. Of course, the wrong one digit can blow up an Ariane 5 rocket. Or your 4B11! Let's fix it...

Code:

<table name="Minimum IPW Code Path modifier #1 (0x7f09 -> 0x7f06)" address="30948" category="Fuel" type="1D" level="2" scaling="Hex16" />

And make no mistake, XMLs appear on Golden's site thanks to magic. Pay no attention to the chimpanzee behind the curtain, banging his fists on the keyboard.....

Rich

Sep 2, 2011 | 09:30 AM

#117

itzwolf

Evolved Member

iTrader: (9)

Joined: Mar 2005

Posts: 1,193

Likes: 2

From: Florida

Quote:

Originally Posted by richardjh

For Omni4bar, I reckon it's as follows for 56890009/10....

Code:

  <table name="Omni4bar #1 0x03B6 -> 0x02FF" address="1a2ee" category="Omni 4 Bar Boost" type="1D" scaling="Hex16" /> 
  <table name="Omni4bar #2 0x0ED8 -> 0x0BFC" address="1a31e" category="Omni 4 Bar Boost" type="1D" scaling="Hex16" /> 
  <table name="Omni4bar #3 0x0ED8 -> 0x0BFC" address="1a332" category="Omni 4 Bar Boost" type="1D" scaling="Hex16" />

Code:

<table name="Minimum IPW Code Path modifier #1 (0x7f09 -> 0x7f06)" address="30948" category="Fuel" type="1D" level="2" scaling="Hex16" />

And make no mistake, XMLs appear on Golden's site thanks to magic. Pay no attention to the chimpanzee behind the curtain, banging his fists on the keyboard.....

Rich

Sweet thanks!

I just noticed you updated the xml so I guess since your the mad scientist behind various XML updates the other 2011 owners would benefit from an Omni section. Here are the other parts if you feel like tossing them in the XML on the site to keep them unitform with Golden's other XML's.

Missing Omni 4 Bar specific scalings:

Code:

<scaling name="Omni4barBoostErrorPsi" units="psi" toexpr="(x-128)*0.2343/4" frexpr="(x*4/0.2343)+128" format="%.1f" min="-6.1" max="6.1" inc="0.1" storagetype="uint16" endian="big" /> 
<scaling name="Omni4barpsia16" units="psia" toexpr="x*0.2343" frexpr="x/0.2343" format="%.1f" min="0" max="49.5" inc="0.1" storagetype="uint16" endian="big" /> 
<scaling name="Omni4barpsia8" units="psia" toexpr="x*0.2343" frexpr="x/0.2343" format="%.1f" min="0" max="49.5" inc="0.1" storagetype="uint8" endian="big" />

Omni 4 Bar spcific section:

Code:

<table name="Atmospheric Boost (Omni4bar)" address="53488" category="Omni 4 Bar Boost" type="1D" scaling="Omni4barpsia16" /> 
<table name="Boost Target #1A (High Gear Range) (Omni4bar)" address="58ef1" category="Omni 4 Bar Boost" type="3D" swapxy="true" scaling="Omni4barpsia8">
<table name="Throttle" address="63020" type="X Axis" elements="9" scaling="Throttle_Main - Stored Minimum Throttle %" /> 
<table name="RPM" address="62f9e" type="Y Axis" elements="18" scaling="RPM" /> 
</table>
<table name="Boost Target #1B (High Gear Range) (Omni4bar)" address="58f9b" category="Omni 4 Bar Boost" type="3D" swapxy="true" scaling="Omni4barpsia8">
<table name="Throttle" address="63020" type="X Axis" elements="9" scaling="Throttle_Main - Stored Minimum Throttle %" /> 
<table name="RPM" address="62f9e" type="Y Axis" elements="18" scaling="RPM" /> 
</table>
<table name="Boost Target #2 (Low Gear Range) (Omni4bar)" address="57465" category="Omni 4 Bar Boost" type="3D" swapxy="true" scaling="Omni4barpsia8">
<table name="Throttle" address="63020" type="X Axis" elements="9" scaling="Throttle_Main - Stored Minimum Throttle %" /> 
<table name="RPM" address="62f9e" type="Y Axis" elements="18" scaling="RPM" /> 
</table>
<table name="Target Boost Error Correction (Omni4bar)" address="58d84" category="Omni 4 Bar Boost" type="2D" scaling="OffsetWGDC">
<table name="Boost Error" address="62fc8" type="Y Axis" elements="17" scaling="Omni4barBoostErrorPsi" /> 
</table>
<table name="Omni4bar #1 0x03B6 -> 0x02FF" address="1a2ee" category="Omni 4 Bar Boost" type="1D" scaling="Hex16" /> 
<table name="Omni4bar #2 0x0ED8 -> 0x0BFC" address="1a31e" category="Omni 4 Bar Boost" type="1D" scaling="Hex16" /> 
<table name="Omni4bar #3 0x0ED8 -> 0x0BFC" address="1a332" category="Omni 4 Bar Boost" type="1D" scaling="Hex16" />
<table name="OBTR (Over-Boost Timing Retard) (Omni4bar)" address="58d20" category="Omni 4 Bar Boost" type="2D" level="3" swapxy="true" scaling="Timing">
<table name="Load Error" address="62ff0" type="Y Axis" elements="9" scaling="Omni4barBoostErrorPsi" /> 
</table>

Sep 2, 2011 | 10:27 AM

#118

RazorLab

EvoM Guru

iTrader: (8)

Joined: Aug 2003

Posts: 14,094

Likes: 1,092

From: Mid-Hudson, NY

Cool stuff Richard!

Sep 2, 2011 | 01:54 PM

#119

Golden

Evolved Member

iTrader: (1)

Joined: Nov 2009

Posts: 1,456

Likes: 0

From: Omaha, NE

6... 9... what's the difference? lol I must have typo'd that one.

Sep 2, 2011 | 06:27 PM

#120

richardjh

Thread Starter

Evolved Member

Joined: Oct 2010

Posts: 2,447

Likes: 14

From: Australia

Quote:

Originally Posted by itzwolf

I just noticed you updated the xml so I guess since your the mad scientist behind various XML updates the other 2011 owners would benefit from an Omni section. Here are the other parts if you feel like tossing them in the XML on the site to keep them unitform with Golden's other XML's.

Main table defs now added for 56890009/10. I noted that the "patch" addresses were already in there.

And I've avoided the "Omni" OBTR stuff for now, as the "base" OBTR stuff still isn't there. All in good time...

Rich

Thread Tools

Search this Thread

Show Printable Version

Email this Page

Reply Share

First
Prev
8 / 17
Next
Last