Omni 4bar writeup
Thread Starter
Joined: Feb 2007
Posts: 9,486
Likes: 67
From: Melbourne, Australia
Omni 4bar writeup
Hi All,
Firstly - Big thanks do Dave (Murlo26) for suppling the MAP sensor used to validate this.
Secondly - Because of the variations between regions (USDM vs AUDM vs JDM) it is ESSENTIAL that you verify your tune is still correct AFTER the 4bar change - you can do this by logging Load AND AFR before and after, ensuring they are still good!
Thirdly - If OMNI are reading this, please supply fatter O-Rings with the MAP sensor so they seal better against the intake manifold...
Intro:
Because of how the EvoX uses the MAP sensor (as a mechanism to calculate load) we are REQUIRED to change some scalings in the ECU when changing to a 4bar map sensor - if you DONT you will run leaner that you are tuned for - which is really bad
Because of the complexities of altitude and psig vs psia we will convert all of our scalings to kPa, this scaling is altitude independent
Step 1: Add some new scaling defititions into your evo10base.xml:
These should be very accurate, the StockXMAP scaling was calculated from how the ECU converts the voltage into a OBD kPa value. The Omni4barMAP scaling was calculated from the Omni 4bar spec sheet.
Step 2: Modify your scalings:
To make things easier we are just modifying 1 of the 3xMAP tables at this stage:
- Modify your "MAP based Load Calc #1" table to use the "StockXMAP in kPa" scaling
- Modify your "MAP based Load Calc #2" table to use the "Omni4barMAP in kPa" scaling
Step 3: Open ECUFlash and copy the axis from "MAP based Load Calc #1" to "MAP based Load Calc #2"
In my picture I havn't YET copied the axis, once you have copied you will see the #2 axis look exactly like the original and the #1 axis will change to smaller values - this is ok.
Step 4: Save, and then edit the evo10base.xml again and update the scaling for the remaining 2 "MAP based Load Calc" maps to be "Omni4barMAP in kPa"
Step 5: Do the exact same but for the "Fuel Compensation MAT vs MAP" table, here is the XML for this table:
53040010:
526800xx:
Step 6: Realign the Omni4bar with other ECU parameters (DTC P0069, Logging kPa via CAN, etc)
53040010:
526800xx:
Step 7: Save and Flash
Step 8: CHECK YOUR TUNE
Again - if this information helped you out, please help me out by sending my some paypal - address in my signature
Cheers
D.
Firstly - Big thanks do Dave (Murlo26) for suppling the MAP sensor used to validate this.
Secondly - Because of the variations between regions (USDM vs AUDM vs JDM) it is ESSENTIAL that you verify your tune is still correct AFTER the 4bar change - you can do this by logging Load AND AFR before and after, ensuring they are still good!
Thirdly - If OMNI are reading this, please supply fatter O-Rings with the MAP sensor so they seal better against the intake manifold...
Intro:
Because of how the EvoX uses the MAP sensor (as a mechanism to calculate load) we are REQUIRED to change some scalings in the ECU when changing to a 4bar map sensor - if you DONT you will run leaner that you are tuned for - which is really bad
Because of the complexities of altitude and psig vs psia we will convert all of our scalings to kPa, this scaling is altitude independent
Step 1: Add some new scaling defititions into your evo10base.xml:
Code:
<scaling name="StockXMAP in kPa" units="StockXMAP in kPa" toexpr="((x * 2556 / 3800) + 0.5) / 2" frexpr="((x * 2) - 0.5) * 3800 / 2556" format="%.2f" min="0" max="350" inc="0.05" storagetype="uint16" endian="big"/> <scaling name="Omni4barMAP in kPa" units="Omni4barMAP in kPa" toexpr="((x / 4) * 1.6151) + 3.4779" frexpr="((x - 3.4779) / 1.6151) * 4" format="%.2f" min="0" max="400" inc="0.05" storagetype="uint16" endian="big"/> <scaling name="Percent_128_add_385_div_512" units="%" toexpr="((x+384)/512)*100" frexpr="((x/100)*512)-384" format="%.1f" min="0" max="100" inc="2" storagetype="uint8" endian="big"/>
Step 2: Modify your scalings:
To make things easier we are just modifying 1 of the 3xMAP tables at this stage:
- Modify your "MAP based Load Calc #1" table to use the "StockXMAP in kPa" scaling
- Modify your "MAP based Load Calc #2" table to use the "Omni4barMAP in kPa" scaling
Step 3: Open ECUFlash and copy the axis from "MAP based Load Calc #1" to "MAP based Load Calc #2"
In my picture I havn't YET copied the axis, once you have copied you will see the #2 axis look exactly like the original and the #1 axis will change to smaller values - this is ok.
Step 4: Save, and then edit the evo10base.xml again and update the scaling for the remaining 2 "MAP based Load Calc" maps to be "Omni4barMAP in kPa"
Step 5: Do the exact same but for the "Fuel Compensation MAT vs MAP" table, here is the XML for this table:
53040010:
Code:
<table name="Fuel Compensation MAT vs MAP - Stock3bar" category="Misc" address="60b89" type="3D" swapxy="true" scaling="Percent_128_add_385_div_512"> <table name="MAP" address="62af4" type="X Axis" elements="10" scaling="StockXMAP in kPa"/> <table name="MAT" address="62ae0" type="Y Axis" elements="7" scaling="Temp"/> </table> <table name="Fuel Compensation MAT vs MAP - Omni4bar" category="Misc" address="60b89" type="3D" swapxy="true" scaling="Percent_128_add_385_div_512"> <table name="MAP" address="62af4" type="X Axis" elements="10" scaling="Omni4barMAP in kPa"/> <table name="MAT" address="62ae0" type="Y Axis" elements="7" scaling="Temp"/> </table>
Code:
<table name="Fuel Compensation MAT vs MAP - Stock3bar" category="Misc" address="60b4d" type="3D" swapxy="true" scaling="Percent_128_add_385_div_512"> <table name="MAP" address="62ab6" type="X Axis" elements="10" scaling="StockXMAP in kPa"/> <table name="MAT" address="62aa2" type="Y Axis" elements="7" scaling="Temp"/> </table> <table name="Fuel Compensation MAT vs MAP - Omni4bar" category="Misc" address="60b4d" type="3D" swapxy="true" scaling="Percent_128_add_385_div_512"> <table name="MAP" address="62ab6" type="X Axis" elements="10" scaling="Omni4barMAP in kPa"/> <table name="MAT" address="62aa2" type="Y Axis" elements="7" scaling="Temp"/> </table>
53040010:
Code:
<table name="Omni4bar #1 0x03B6 -> 0x02FF" category="Misc" address="17b92" type="1D" scaling="Hex16"/> <table name="Omni4bar #2 0x0ED8 -> 0x0BFC" category="Misc" address="17bc2" type="1D" scaling="Hex16"/> <table name="Omni4bar #3 0x0ED8 -> 0x0BFC" category="Misc" address="17bd6" type="1D" scaling="Hex16"/>
Code:
<table name="Omni4bar #1 0x03B6 -> 0x02FF" category="Misc" address="17d76" type="1D" scaling="Hex16"/> <table name="Omni4bar #2 0x0ED8 -> 0x0BFC" category="Misc" address="17da6" type="1D" scaling="Hex16"/> <table name="Omni4bar #3 0x0ED8 -> 0x0BFC" category="Misc" address="17dba" type="1D" scaling="Hex16"/>
Step 8: CHECK YOUR TUNE
Again - if this information helped you out, please help me out by sending my some paypal - address in my signature
Cheers
D.
Last edited by tephra; Jun 9, 2016 at 06:31 AM.
Thread Starter
Joined: Feb 2007
Posts: 9,486
Likes: 67
From: Melbourne, Australia
At the moment the USDM changes haven't been fully tested - Murlo26 or scheides will report up when they are happy
Updating your logger:
EvoScan:
Eval="(x/4*0.2343)-14.196"
Tactrix:
scalingrpn=x,4,/,0.2343,*,14.196,-
It's 14.196 because I live at 14.5 psig - Whatever altitude you live at add 0.3psi
Updating your logger:
EvoScan:
Eval="(x/4*0.2343)-14.196"
Tactrix:
scalingrpn=x,4,/,0.2343,*,14.196,-
It's 14.196 because I live at 14.5 psig - Whatever altitude you live at add 0.3psi
Last edited by tephra; Sep 26, 2010 at 08:54 PM.
Confirmed working on USDM 2008 AFR, timing, idle, long and short term fuel trims are all working as they were before under all conditions I've tried; cold/warm start, cruising, playing, driving the wife, sitting in traffic, etc.
NOTE: when you log 'boost' in evoscan you will need to update your formula. This is in tephra's docs but don't be scurred, if you are all of a sudden running 18psi vs 26psi from before, but the car feels normal, this is why
AFR, timing, idle, long and short term fuel trims are all working as they were before under all conditions I've tried; cold/warm start, cruising, playing, driving the wife, sitting in traffic, etc. NOTE: when you log 'boost' in evoscan you will need to update your formula. This is in tephra's docs but don't be scurred, if you are all of a sudden running 18psi vs 26psi from before, but the car feels normal, this is why
Trending Topics
Evolved Member
Joined: Jun 2009
Posts: 653
Likes: 12
From: Houston, TX
Evolved Member
Joined: Jun 2009
Posts: 653
Likes: 12
From: Houston, TX
Evolved Member
Joined: Jun 2009
Posts: 653
Likes: 12
From: Houston, TX
Golden has done enough work to be able to ask that and have earned it. Anyone driving a 2010 USDM Evo thats tuned, odds are that Golden did the map definitions the tuner used. This doesn't even count the various other world market cars he has also defined for people.