Notices
ECU Flash

ECU boost control mods

Thread Tools
 
Search this Thread
 
Old Mar 8, 2009 | 03:51 PM
  #226  
GST Motorsports's Avatar
Account Disabled
iTrader: (8)
 
Joined: Sep 2007
Posts: 3,366
Likes: 2
From: Hayward
Originally Posted by tephra
Bryan - This should work:

AUDM Evo IX 88580013/14

Add the following lines to your ROM file:

----- (don't add the "-----")
<table name="Variable for Boost Control" category="Turbo" address="40882" type="1D" level="1" scaling="Hex16"/>

<table name="WGDC Correction update delay #1" category="Turbo" address="1654" type="1D" level="1" scaling="uint16"/>

<table name="WGDC Correction update delay #2" category="Turbo" address="1656" type="1D" level="1" scaling="uint16"/>

<table name="Load Error RAM Address" category="Turbo" address="40876" type="1D" level="1" scaling="Hex16"/>

<table name="Load Error RAM Address in Load Error Table" category="Turbo" address="735c" type="1D" level="1" scaling="Hex16"/>

<table name="MUT8A" category="MUT" address="375ee" type="1D" level="1" scaling="Hex16"/>

<table name="MUT8B" category="MUT" address="375f2" type="1D" level="1" scaling="Hex16"/>
-----

Instructions for ECUFlash

Variable for boost control: Stock will read 6B28. Change it to 6B22. The table is in hex format, so you will have to enter it as 0x6B22

WGDC Correction update delay: Use table #1. Table #2 is for when the vehicle speed exceeds the boost limiting speed. Set the value anywhere from 1 to 10. Each unit is approx 0.08 to 0.1 sec.

The "Load Error RAM Address" and "Load Error RAM Address in Load Error Table" will both read: 69B2. Change both to 6ECE (again, you'll need to enter it as 0x....)

Change MUT8A will read 6AAD. Change it to 6ECF (again enter it as 0x....)

Change MUT8B will read 6B21. Change it to 6EC5 (enter it as 0x....)

Save the ROM file and upload it to your ECU. Then go to the instructions below for setting up EvoScan.
Hey Tephra,

Looks like this is incorrect. Logging -20 when BDEL + Offset = target load.
Reply
Old Mar 8, 2009 | 04:48 PM
  #227  
tephra's Avatar
EvoM Guru
15 Year Member
iTrader: (6)
 
Joined: Feb 2007
Posts: 9,486
Likes: 67
From: Melbourne, Australia
which is -20? mut8a or 8b?
Reply
Old Mar 8, 2009 | 04:57 PM
  #228  
GST Motorsports's Avatar
Account Disabled
iTrader: (8)
 
Joined: Sep 2007
Posts: 3,366
Likes: 2
From: Hayward
Originally Posted by tephra
which is -20? mut8a or 8b?
Sorry, LoadError
Reply
Old Mar 8, 2009 | 05:23 PM
  #229  
tephra's Avatar
EvoM Guru
15 Year Member
iTrader: (6)
 
Joined: Feb 2007
Posts: 9,486
Likes: 67
From: Melbourne, Australia
quick Q:

where the 'before' values all correct?
Reply
Old Mar 8, 2009 | 05:28 PM
  #230  
GST Motorsports's Avatar
Account Disabled
iTrader: (8)
 
Joined: Sep 2007
Posts: 3,366
Likes: 2
From: Hayward
Originally Posted by tephra
quick Q:

where the 'before' values all correct?
yup!
Reply
Old Mar 11, 2009 | 05:11 PM
  #231  
tephra's Avatar
EvoM Guru
15 Year Member
iTrader: (6)
 
Joined: Feb 2007
Posts: 9,486
Likes: 67
From: Melbourne, Australia
hrmm it should work fine then.

can you shoot me the rom so I can check it out?

cheers!
Reply
Old Mar 11, 2009 | 05:38 PM
  #232  
GST Motorsports's Avatar
Account Disabled
iTrader: (8)
 
Joined: Sep 2007
Posts: 3,366
Likes: 2
From: Hayward
Originally Posted by tephra
hrmm it should work fine then.

can you shoot me the rom so I can check it out?

cheers!
Just sent via email, thanks!
Reply
Old Mar 11, 2009 | 05:56 PM
  #233  
tephra's Avatar
EvoM Guru
15 Year Member
iTrader: (6)
 
Joined: Feb 2007
Posts: 9,486
Likes: 67
From: Melbourne, Australia
Oops - 6EBE/F not 6ECE/F

Bryan - This should work:

AUDM Evo IX 88580013/14

Add the following lines to your ROM file:

----- (don't add the "-----")
<table name="Variable for Boost Control" category="Turbo" address="40882" type="1D" level="1" scaling="Hex16"/>

<table name="WGDC Correction update delay #1" category="Turbo" address="1654" type="1D" level="1" scaling="uint16"/>

<table name="WGDC Correction update delay #2" category="Turbo" address="1656" type="1D" level="1" scaling="uint16"/>

<table name="Load Error RAM Address" category="Turbo" address="40876" type="1D" level="1" scaling="Hex16"/>

<table name="Load Error RAM Address in Load Error Table" category="Turbo" address="735c" type="1D" level="1" scaling="Hex16"/>

<table name="MUT8A" category="MUT" address="375ee" type="1D" level="1" scaling="Hex16"/>

<table name="MUT8B" category="MUT" address="375f2" type="1D" level="1" scaling="Hex16"/>
-----

Instructions for ECUFlash

Variable for boost control: Stock will read 6B28. Change it to 6B22. The table is in hex format, so you will have to enter it as 0x6B22

WGDC Correction update delay: Use table #1. Table #2 is for when the vehicle speed exceeds the boost limiting speed. Set the value anywhere from 1 to 10. Each unit is approx 0.08 to 0.1 sec.

The "Load Error RAM Address" and "Load Error RAM Address in Load Error Table" will both read: 69B2. Change both to 6EBE (again, you'll need to enter it as 0x....)

Change MUT8A will read 6AAD. Change it to 6EBF (again enter it as 0x....)

Change MUT8B will read 6B21. Change it to 6EC5 (enter it as 0x....)

Save the ROM file and upload it to your ECU. Then go to the instructions below for setting up EvoScan.
Reply
Old Mar 11, 2009 | 07:09 PM
  #234  
GST Motorsports's Avatar
Account Disabled
iTrader: (8)
 
Joined: Sep 2007
Posts: 3,366
Likes: 2
From: Hayward
Originally Posted by tephra
Oops - 6EBE/F not 6ECE/F

Bryan - This should work:

AUDM Evo IX 88580013/14

Add the following lines to your ROM file:

----- (don't add the "-----")
<table name="Variable for Boost Control" category="Turbo" address="40882" type="1D" level="1" scaling="Hex16"/>

<table name="WGDC Correction update delay #1" category="Turbo" address="1654" type="1D" level="1" scaling="uint16"/>

<table name="WGDC Correction update delay #2" category="Turbo" address="1656" type="1D" level="1" scaling="uint16"/>

<table name="Load Error RAM Address" category="Turbo" address="40876" type="1D" level="1" scaling="Hex16"/>

<table name="Load Error RAM Address in Load Error Table" category="Turbo" address="735c" type="1D" level="1" scaling="Hex16"/>

<table name="MUT8A" category="MUT" address="375ee" type="1D" level="1" scaling="Hex16"/>

<table name="MUT8B" category="MUT" address="375f2" type="1D" level="1" scaling="Hex16"/>
-----

Instructions for ECUFlash

Variable for boost control: Stock will read 6B28. Change it to 6B22. The table is in hex format, so you will have to enter it as 0x6B22

WGDC Correction update delay: Use table #1. Table #2 is for when the vehicle speed exceeds the boost limiting speed. Set the value anywhere from 1 to 10. Each unit is approx 0.08 to 0.1 sec.

The "Load Error RAM Address" and "Load Error RAM Address in Load Error Table" will both read: 69B2. Change both to 6EBE (again, you'll need to enter it as 0x....)

Change MUT8A will read 6AAD. Change it to 6EBF (again enter it as 0x....)

Change MUT8B will read 6B21. Change it to 6EC5 (enter it as 0x....)

Save the ROM file and upload it to your ECU. Then go to the instructions below for setting up EvoScan.
Thank you! I'll try it out.
Reply
Old Mar 16, 2009 | 08:37 AM
  #235  
Danieln's Avatar
Evolved Member
iTrader: (1)
 
Joined: Apr 2008
Posts: 563
Likes: 0
From: EUROPE
Hi Guys,

I run 88840017 and I followed the same steps to update my xml file for Ecuflash 88840017.xml file by ussing 88840016 explained mod knowing that are the same.

After "88840016", I took the example and I added the following lines into my ROM file:

<table name="Variable for Boost Control" category="Turbo" address="408B2" type="1D" level="1" scaling="Hex16"/>

<table name="WGDC Correction update delay #1" category="Turbo" address="1654" type="1D" level="1" scaling="uint16"/>

<table name="WGDC Correction update delay #2" category="Turbo" address="1656" type="1D" level="1" scaling="uint16"/>

<table name="Load Error RAM Address" category="Turbo" address="408A6" type="1D" level="1" scaling="Hex16"/>

<table name="Load Error RAM Address in Load Error Table" category="Turbo" address="735C" type="1D" level="1" scaling="Hex16"/>

<table name="MUT8A" category="MUT" address="37A22" type="1D" level="1" scaling="Hex16"/>

<table name="MUT8B" category="MUT" address="37A26" type="1D" level="1" scaling="Hex16"/>


I change "Variable for boost control" from 6B28 in to 6B22

WGDC Correction update delay - Use table #1. Table #2 value is set to 10

For "Load Error RAM Address" and "Load Error RAM Address in Load Error Table" I set the value from 69B2 into 6ECE.

But value of MUT8A is "60AF" not "6AAD"

Same for MUT8B, value is "6A..." not "6B21"

Can I use the same values for MUT8A and MUT8B??? (6ECF for MUT8A and 6EC5 for MUT8B)

Please tell me if I must put different values into those cells.

Thanks
Reply
Old Mar 16, 2009 | 03:40 PM
  #236  
tephra's Avatar
EvoM Guru
15 Year Member
iTrader: (6)
 
Joined: Feb 2007
Posts: 9,486
Likes: 67
From: Melbourne, Australia
Dan - 88840017 probably has a slightly different MUT table location than 88840016...

I will look this up when I get to work..
Reply
Old Mar 17, 2009 | 12:29 AM
  #237  
Danieln's Avatar
Evolved Member
iTrader: (1)
 
Joined: Apr 2008
Posts: 563
Likes: 0
From: EUROPE
Cheers Dave,

I was thinking about this also.

Than I will wait for some updates and I will see.

Seems that this ROM version is not so popular around.

My older map version was 88840013 usdm and I switch to 88840017 two month ago.

Maybe it`s better to switch to 88840016 version?? What do U say?

Take care Dave

Have a perfect Day!

Dan
Reply
Old Jun 25, 2009 | 12:18 AM
  #238  
kaj's Avatar
kaj
EvoM Community Team Leader
20 Year Member
Liked
Loved
Community Favorite
iTrader: (60)
 
Joined: Mar 2006
Posts: 13,634
Likes: 824
From: Fresno, CA
just bumped into this thread and have a quick question.. as i continue reading through it.. i see the same type of coding over and over, but with changes.. so is the OP edited to have the latest info, or do i get it from the last post?

sorry if it's a dumb question. i should be sleeping and am having trouble finding time to read all these threads, due to work.
i'm just trying to get a grip on all this stuff while working 80hrs/week. ..
Reply
Old Jun 25, 2009 | 06:12 AM
  #239  
evo8426's Avatar
Evolved Member
iTrader: (27)
 
Joined: Jan 2006
Posts: 4,248
Likes: 9
From: Charlotte, North Carolina
the coding in the first post is what i use and my runs like its supposed to, make sure you get the right coding for your rom
Reply
Old Jun 25, 2009 | 01:43 PM
  #240  
ixbreaker's Avatar
Evolving Member
iTrader: (3)
 
Joined: Apr 2006
Posts: 146
Likes: 0
From: so cal
The first page still states that the mods work for ecuflash 1.3 and below. Has anyone tested these mods with 1.41?

I tryed upgrading to 1.41 recently and have been having problems not starting ocassionally. I believe the issue may be related to using 1.41. I could be wrong if people have been using the mods with success, but it would help me a great deal to know. Thankyou all in advance.
Reply



All times are GMT -7. The time now is 06:46 PM.