ECU boost control mods
#241
Evolved Member
iTrader: (3)
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.
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.
#242
Evolving Member
iTrader: (3)
yes i have checked the endians, but still no luck. Besides the endians in tephra's mods, are there any other endians to search for?
I did notice a difference in the code between 1.30 and 1.41. When you add Ecu boost control mods the category is specified differently. eg:1.41 uses "<---turbo--------->" to identify categories instead of eg: category="turbo".
are the categories supposed to be modified to be compatible with 1.41?
I did notice a difference in the code between 1.30 and 1.41. When you add Ecu boost control mods the category is specified differently. eg:1.41 uses "<---turbo--------->" to identify categories instead of eg: category="turbo".
are the categories supposed to be modified to be compatible with 1.41?
#243
Evolved Member
iTrader: (27)
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.
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.
#244
Evolving Member
iTrader: (3)
^are some of your tables highlighted blue? On mines, all of the knock sensor filter maps, OBD II Codes, Emissions EGR, Periphery, and MUT are blue for some reason. Everything else is black, which i'm guessing there's a problem with these remaining tables.
BTW i'm also using tephra mods V6. i previously had V5.10 which also had the same effect of blue table menus, when i loaded the xml files.
BTW i'm also using tephra mods V6. i previously had V5.10 which also had the same effect of blue table menus, when i loaded the xml files.
#245
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
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
other question: With Tephra V6-2 rom, Should I link Variable for Boost Control to the 1-Byte Load or not? If yes, what is the value to put?
#248
Evolving Member
Join Date: Sep 2009
Location: Creston, Iowa
Posts: 123
Likes: 0
Received 0 Likes
on
0 Posts
Since TephraV7 now has maf iat corrections, do you think this is still a better option for load based guys? Im running it with my iat corrections pretty much zeroed out.
#249
Evolved Member
iTrader: (17)
No matter what error correction system your using, 80% WGDC at 40* with make a lot more boost then 80% WGDC at 80*. So the MAF IAT comp table is very useful.
Last edited by Evo_Jay; Nov 23, 2009 at 10:33 PM.
#250
Evolved Member
iTrader: (1)
Join Date: Apr 2008
Location: EUROPE
Posts: 563
Likes: 0
Received 0 Likes
on
0 Posts
No I did not menage to find the right addresses for Mut 8A and Mut 8B for *17
I ask around but no luck for me.
Try to ask and maybe you will be more lucky than me.
Seems that MUT 8A and 8B for 88840016 is not the same with MUT 8A or 8B for 88840017 rom id.
#251
Evolving Member
Join Date: Sep 2009
Location: Creston, Iowa
Posts: 123
Likes: 0
Received 0 Likes
on
0 Posts
Agreed but this variable does not vary nearly as much. Pick your way I guess, this way with less correction(much less for me), or use the stock boost variable with more correction.
#252
Evolved Member
iTrader: (1)
Join Date: Apr 2008
Location: EUROPE
Posts: 563
Likes: 0
Received 0 Likes
on
0 Posts
I try to look over the MUT subroutine of 88840017 comparing with 88840016.
Since there is the same address for the MUT table the instructions given by mrfred for *16 should work also for 88840017.
I am looking for ECU-based direct boost control (PSI) for EDM cars with MAP sensor installed but I did not found nothing.
Seems that only load based is available for EDM IX roms.
Since there is the same address for the MUT table the instructions given by mrfred for *16 should work also for 88840017.
I am looking for ECU-based direct boost control (PSI) for EDM cars with MAP sensor installed but I did not found nothing.
Seems that only load based is available for EDM IX roms.
#253
Evolved Member
iTrader: (1)
Join Date: Apr 2008
Location: EUROPE
Posts: 563
Likes: 0
Received 0 Likes
on
0 Posts
When you will find time........ can you please look a bit over the correct address Mut 8A and 8B for 8817?
Most of the 8816 users jump to 8817 already in Europe....
Thanks a lot....
#254
Evolving Member
iTrader: (9)
Join Date: Oct 2006
Location: Raliegh, North Carolina
Posts: 145
Received 0 Likes
on
0 Posts
^are some of your tables highlighted blue? On mines, all of the knock sensor filter maps, OBD II Codes, Emissions EGR, Periphery, and MUT are blue for some reason. Everything else is black, which i'm guessing there's a problem with these remaining tables.
BTW i'm also using tephra mods V6. i previously had V5.10 which also had the same effect of blue table menus, when i loaded the xml files.
BTW i'm also using tephra mods V6. i previously had V5.10 which also had the same effect of blue table menus, when i loaded the xml files.
Thread
Thread Starter
Forum
Replies
Last Post
mrfred
ECU Flash
496
Sep 14, 2022 07:08 PM
mrfred
ECU Flash
78
Nov 22, 2014 02:39 PM