<table name="MAP Scaling" category="MAPSensor" address="5902" type="2D" level="1" scaling="uint8">
<table name="MAP Output" address="70F8" type="Y Axis" elements="9" scaling="Volts16"/>
</table>

that's what i have for 88570008 so far, direct boost stuff needs more work on it.
how do you find it, is 88570008 ok with our cars?

 

it seems mr fred's code for direct boost doesn't need a map subroutine since it reads map sensor readings from mut_38 directly. so we can probably enjoy direct boost on 88840017 even without the need to patch for the original mdp_here function.

it also looks like that only offsets now matter for 88840017.

in the meanwhile i have researched some tables for 88570008. could be incorrect since i can't currently test it, but it shouldn't be off by much. if someone is brave enough to try it, please let me know

variable for boost control
orig value: 6B18
should be: 6abc

shlr -> shll
orig value: 4A01
should be: 4a00

Boost Error RAM Address
orig value: 6996
should be: 6ea2

Boost Error RAM Address in Load Error Table
orig value: 6996
should be: 6ea2

MUT8A
should be 6ea3

MUT8B
should be 6ea9

<table name="Variable for Boost Control" category="Turbo" address="40892" type="1D" level="1" scaling="Hex16"/>
<table name="SHLR->SHLL for EBC" category="Turbo" address="405D2" type="1D" level="1" scaling="Hex16"/>
<table name="Boost Error RAM Address" category="Turbo" address="40882" type="1D" level="1" scaling="Hex16"/>
<table name="Boost Error RAM Address in Load Error Table" category="Turbo" address="62DC" type="1D" level="1" scaling="Hex16"/>
<table name="WGDC Correction Interval #1 (High Gear Range)" category="Turbo" address="1654" type="1D" level="1" scaling="uint16"/>
<table name="WGDC Correction Interval #2 (Low Gear Range)" category="Turbo" address="1656" type="1D" level="1" scaling="uint16"/>
<table name="Boost Adder" category="Turbo" address="1670" type="1D" level="1" scaling="psia16"/>
<table name="Boost Error Correction" category="Turbo" address="3894" type="2D" level="1" scaling="OffsetWGDC">
<table name="Boost Error" elements="17" type="Y Axis" address="62E0" elements="17" scaling="BoostErrorPsi"/>
</table>

 

Just to confirm explicitly and summarize what was said in this thread - logging works perfectly after everything is done according to the instructions here.

The car is 2007 EDM EvoIX with Tephra ROM 88580714 (initially it was running 88840016) without MAP-sensor in the intake manifold in stock.

Parts needed for the car:
1) OmniPower 4bar MAP-sensor (or any other suitable sensor of your choice)
2) Bosch parts for connector (1x 1284485112 (connector), 1x 1280703022 (plastic cover) and 3x 1987352119 (pin for the connector) - mentioned in post #18 of this thread, thanks GiGas)
3) few meters of wires of your choice
4) one EvoIX ECU pin (can be purchased from http://www.dsm-ezine.com/evo9pins.html - thanks Danieln for direction and Jack_of_Trades for availability of those)

Work needed:
1) drilling the intake manifold to place the sensor (can be done without removing the manifold)
2) wiring to the ECU (along with other wires going there from engine bay, just make sure everything is done nice and have no contact with hot parts)
3) soldering, wiring and adding one more pin to the ECU connector (signal - pin #1 of the sensor to pin #92 of the ECU (only this one is free and you should add the ECU pin there), ground - pin #2 of the sensor to pin #49 of the ECU (connect to the existing wire that go there) and 5V - pin #3 of the sensor to pin #42 of the ECU (connect to the existing wire that go there); as per recommendations of GiGas in post #21 of this thread, and not as pictured in post #31 of this thread)

Software modifications needed:
1) in Evoscan (I currently use v2.7.0090) just log request 38 with appropriate formula (I currently use 0.234*x-14.4+0.5 for readings in psig at my above the sea level (not perfect, but very close to what it should be), when evaluating your formula make sure your account for the altitude where you are)
2) if you want to log values in bar, the formula should be 0.016134*x-0.9928+0.0345
3) 14.4 and 0.9928 are offsets for the barometric pressure for your above the sea level - adjust them according to your altitude

Happy logging!

 

here are some direct boost tables for other roms, to be used with mr. fred's direct boost how-to.
i only have these roms with tephra's patches, but the tables should be the same within rom id. please check.

note that these tables require hardware modifications. use at your own risk.

------------------- for 88580714

Variable for Boost Control
orig value: 6b28 - change to: 6acc

SHLR->SHLL for EBC
orig value: 4a01 - change to: 4a00

Boost Error RAM Address
orig value: 69b2 - change to: 6ebe

Boost Error RAM Address in Load Error Table
orig value: 69b2 - change to: 6ebe

MUT8A (Use for Boost Error)
orig value: 6aad - change to: 6ebf

MUT8B (Use for WGDC Correction)
orig value: 6b21 - change to: 6ec5

<table name="Variable for Boost Control" category="Turbo" address="40882" type="1D" level="1" scaling="Hex16"/>
<table name="SHLR->SHLL for EBC" category="Turbo" address="405f4" type="1D" level="1" scaling="Hex16"/>
<table name="Boost Error RAM Address" category="Turbo" address="40876" type="1D" level="1" scaling="Hex16"/>
<table name="Boost Error RAM Address in Load Error Table" category="Turbo" address="735c" type="1D" level="1" scaling="Hex16"/>

<table name="MUT8A Use for Boost Error" category="MUT" address="375EE" type="1D" level="1" scaling="Hex16"/>
<table name="MUT8B Use for WGDC Correction" category="MUT" address="375F2" type="1D" level="1" scaling="Hex16"/>

------------------- for 88840017

Variable for Boost Control
orig value: 6b28 - change to: 6acc

SHLR->SHLL for EBC
orig value: 4a01 - change to: 4a00

Boost Error RAM Address
orig value: 69b2 - change to: 6ebe

Boost Error RAM Address in Load Error Table
orig value: 69b2 - change to: 6ebe

MUT8A (Use for Boost Error)
orig value: 6aad - change to: 6ebf

MUT8B (Use for WGDC Correction)
orig value: 6b21 - change to: 6ec5


<table name="Variable for Boost Control" category="Turbo" address="408B2" type="1D" level="1" scaling="Hex16"/>
<table name="SHLR->SHLL for EBC" category="Turbo" address="4060E" type="1D" level="1" scaling="Hex16"/>
<table name="Boost Error RAM Address" category="Turbo" address="408A6" type="1D" level="1" scaling="Hex16"/>
<table name="Boost Error RAM Address in Load Error Table" category="Turbo" address="735c" type="1D" level="1" scaling="Hex16"/>

<table name="MUT8A Use for Boost Error" category="MUT" address="37B6E" type="1D" level="1" scaling="Hex16"/>
<table name="MUT8B Use for WGDC Correction" category="MUT" address="37B72" type="1D" level="1" scaling="Hex16"/>


------------ naming --------------------
mr fred | tephra / colby
------- | --------------
Base Boost # | Boost Desired Engine Load
Boost Adder | Boost Control Load Offset
Boost Error Correction | Turbo Boost Error Correction
Boost Error | Boost Error

changes in scalings, to be done ONLY in boost-related tables (above):
Load8 -> psia8
Load16 -> psia16
LoadError -> BoostErrorPsi

--------------------------------------

 

Did you install the map sensor on your car already?

Cheers,

Daniel

 

not yet, but we're using vd's car as a testbed. however, i'm very close to get it done too

 

Yesterday I've flashed my Evo with 88580714 ROM augmented with direct boost mods according to the justastockevo's instructions. So far everything works perfectly.

Will keep posted once Grimmspeed 3-port BCS goes in.

 

Hello


I modifield the tephra 88580714 rom for direct boost control as justastockevo posted in the #49 + insert the scaling of JDM 3 map sensor posted MrFred in the how-to: ECU-based direct boost control topic.
Please someone would check it before I uploaded it ?

http://www.2shared.com/file/0UWVjgCI...TephraMod.html

http://www.2shared.com/document/s6_L...580714-v7.html

My car has JDM 3 bar map sensor from the factory. What should I do with the MAP Ve max min and like this table ?! Do I have to see them in the rom ? Or the ecu will read from mut 38 directly ?

 

I've looked through the ROM you posted - it appears to include proper values for direct boost control. 6 new 1D tables have their values quite spot on, same for the scalings. So to me it looks as ready to go. Values for WGDC and target boost are zeroed, so you're not expected to have any negative effects after flashing it into your car.

VE maps are not a part of direct boost control stuff, they are related to speed density. So you should not seek for them as for now.

As for MAP-sensor function you can easily check it through logging MUT38 request in Evoscan, if it shows correct values (after you put in correct evaluation formula) - you have another sign everything is right.

 

Thanks VD to check it. I have to try it Do you have speed density patch also for this rom ?

 

i probably can port it from 8859, but i'd need a car with MAP/IAT installed to do code tryout and a person who knows what to do.

 

Hi folks!.
So happy to see that this tread still live .

As I wrote in a early post, my acd/ayc pump went worn and I did fight so much the national import coperation (7 month) And I had to close down photo albums and activity in this forum.

My EVO are on the street again and you made me re-open public access to the photo album again, sorry fore the inconvient you may have had due to this.

I will deffently implement soon.

 

welcome back mate....

 

Hello,

Does some one know how to wire the GM 3 port in the Eu RS Evo 9 which has dual boost control solenoid ? where to plug the 3 port solenoid ?

 

I am shure that u can finde info on this forum - try to search.