Notices
ECU Flash

Omni 7 BAR Scalings

Thread Tools
 
Search this Thread
 
Old Apr 14, 2010 | 01:17 AM
  #1  
RoadSpike's Avatar
Thread Starter
Evolved Member
iTrader: (5)
 
Joined: Oct 2006
Posts: 3,805
Likes: 2
From: Sacramento, CA
Omni 7 BAR Scalings

Update
Found out my 16 bit scaling had an issue with the unit type so thats fixed now

Well out of boredom I decided to calculate the omni 7 bar scalings.

I have a pretty handy spread sheet to help me out.

Results
PHP Code:
    <scaling name="BoostErrorPsi OMNI7barMAP" units="psi" toexpr="(x-128)*0.049625" frexpr="(x/0.049625)+128" format="%.1f" min="-15" max="15" inc="0.1" storagetype="uint16" endian="big"/>
    <
scaling name="PSIa16 OMNI7barMAP" units="PSIa" toexpr="x*0.1985-1.81" frexpr="(x+1.81)/0.1985" format="%.1f" min="0" max="90" inc="0.3" storagetype="uint16" endian="big"/>
    <
scaling name="PSIa8 OMNI7barMAP" units="PSIa" toexpr="x*0.1985-1.81" frexpr="(x+1.81)/0.1985" format="%.1f" min="0" max="48" inc="0.3" storagetype="uint8" endian="big"/>
    <
scaling name="kPa OMNI7barMAP" units="kPa" toexpr="x*0.7009" frexpr="x/0.7009" format="%.1f" min="0" max="750" inc="0.7009" storagetype="uint16" endian="big"/> 

Important how to calculate them yourself notes:

kPa Scaling:
This scaling is based on the idea of a 10bit system so X will be between 0 and 1023 for the Volts being 0-5volts where 0 is 0volts and 1023 being 5 volts. Since the 7 bar is a 0 to 5 volt sensor there is no offset to compensate for the sensors range like the kavlico

PSIa 8 bit and 16 bit scalings:

These are both really 8 bit scalings with a weird twist. I think the best way to get the multiplier and offset is to use the 10bit scaling method with 0-1023 for 0-5volts and then mutiply the result by 2 for the multiplier. The offset is squashed by a factor of 8, don't really know why. The chart does this for you in the 10 bit scaling sheet.


Boost Error:
Easiest one of all but requires you know the PSIa8 bit scaling multiplier. Just take the 8 bit multiplier and divide it by 4 and you know what it is. You only need the multiplier in the boost error table since its all about change in X not really X meaning a value like volts.
Attached Files
File Type: zip
Scaling Chart.zip (3.3 KB, 0 views)

Last edited by RoadSpike; Apr 14, 2010 at 02:15 PM.
Old Apr 14, 2010 | 01:28 AM
  #2  
RoadSpike's Avatar
Thread Starter
Evolved Member
iTrader: (5)
 
Joined: Oct 2006
Posts: 3,805
Likes: 2
From: Sacramento, CA
4.14.2010, first post, formatting and original info borrowed/stolen from mrfred's post here:
https://www.evolutionm.net/forums/ec...evo-8-9-a.html

I lifted most of this content from scheides post here:
https://www.evolutionm.net/forums/ec...sdm-8-9-a.html

Contents of this Post

This post describes how to adapt an Omni 7-bar MAP sensor to a USDM Evo ECU and use the sensor to log boost with EvoScan or Mitsulogger. If you also want to use the sensor to for direct boost control, then you'll also need to do the mods in this thread.


Intro

This sensor is insane able to correctly read boost to a minimum of 87psi. Even Brent Rau would be satisfied with this sensor, at least for now

Special Note:
I've been informed that the omni style sensors have o-ring seal problems please do a boost leak check when installing and/or upgrade the o-ring with a thicker unit availiable at your local auto parts store.

ROMs currently covered
Evo 8s: 94170008, 94170014, 94170015, 96420007, 96420008, 96940011
Evo 9s: 88590013, 88590014, 88590015

To see which ROM you have, open it in ECUFlash, and expand on the "ROM Info" section. You'll see your ROM version there.


Where to get the MAP sensor

http://www.omnipowerusa.com/

MAP Sensor Swap

Here is a picture of the MAP sensor location (right on top of the intake manifold):



To remove the electrical plug, slide a thin blade screw driver under the metal retainer clip, and it will easily pry up. It is spring loaded, so it will go flying if you don't keep your hand on it when removing it.

After you swap in the Omni sensor, you'll need to perform some ROM mods. If the ROM mods are not done at the same time, the car will either not run or throw a CEL.

The next sections describe what mods need to be done to each of the different USDM Evo ROMs. The final section describes how to setup EvoScan or Mitsulogger to log boost.


ROM Mods for USDM Evo 9 ROMs 88590013, 88590014, 88590015

First is to add some definitions to your ECUFlash ROM XML definition file found in:

C:\Program Files\OpenECU\EcuFlash\rommetadata\mitsubishi\evo

Open the 885900XX.xml file with the text editor of your choice. Scroll down to the bottom of the file. Add the following lines just before the </rom> tag (copy everything *between* the ----):

----
<table name="MAP Scaling" category="MAPSensor" address="670c" type="2D" level="1" scaling="uint8">
<table name="MAP Output" address="800e" type="Y Axis" elements="9" scaling="Volts16"/>
</table>

<table name="MAP Fault Trig: Mid VE Max #1" category="MAPSensor" address="29d6" type="1D" level="1" scaling="Volts16"/>

<table name="MAP Fault Trig: Mid VE Min #1" category="MAPSensor" address="29b6" type="1D" level="1" scaling="Volts16"/>

<table name="MAP Fault Trig High VE #1" category="MAPSensor" address="29bc" type="1D" level="1" scaling="Volts16"/>

<table name="MAP vs Baro" category="MAPSensor" address="283c" type="1D" level="1" scaling="uint16"/>

<table name="MAP Comparison" category="MAPSensor" address="2838" type="1D" level="1" scaling="Volts16"/>
----

After modifying and saving the ROM xml file, launch ECUFlash, open your ROM, and find the new entries. Note that they have their own category. It may be necessary to set ECUFlash to "Developer" mode in the ECUFlash options (and relaunch ECUFlash) to be able to see the tables. Here is what needs to be changed in ECUFlash:

0.84 11
1.37 20
1.89 31
2.42 40
2.95 48
3.48 57
4.00 67
4.53 80
4.98 255

Change the values to:
Not Verified yet
0.23 25
0.46 49
0.66 70
0.91 96
1.13 120
1.36 144
1.61 170
1.85 195
2.42 255

Change the "MAP Fault Trig: Mid VE Max #1" value from 4.80 to 4.90.

Change the "MAP Fault Trig: Mid VE Min #1" value from 0.20 to 0.10.

Change the "MAP Fault Trig High VE #1" value from 1.80 to 0.51.

Change the "MAP vs Baro" parameter from 162 to 44. Testing Needed

Change the "MAP Comparison" value from 4.00 to 0.702. Needs to be tested

In ECUFlash, find the "Periphery4 (FEA) Bits" table. Change bit.14 from 1 to 0. This can be done by using the "minus" key on your computer. This disables the P0069 test.

Now find the "Periphery2 (FCA) Bits" table. Change bit.9 from 1 to 0. Use the "minus" key. This disables the P0401 (EGR) test.

Save the ROM file, and flash your ECU with it. That's it for the Evo 9 ROM mods. Now skip down to the end of this post to see instructions for setting up EvoScan/Mitsulogger to log boost.


ROM Mods for 2005 USDM Evo 8 ROM 96940011

First is to add some definitions to your ECUFlash ROM XML definition file found in:

C:\Program Files\OpenECU\EcuFlash\rommetadata\mitsubishi\evo

Open the 96940011.xml file with the text/XML editor of your choice. Scroll down to the bottom of the file. Add the following lines just before the </rom> tag (copy everything *between* the ----):

----
<table name="MAP Scaling" category="MAPSensor" address="57D2" type="2D" level="1" scaling="uint8">
<table name="MAP Output" address="6ED4" type="Y Axis" elements="9" scaling="Volts16"/>
</table>

<table name="MAP Fault Trig: Mid VE Max #1" category="MAPSensor" address="28B4" type="1D" level="1" scaling="Volts16"/>

<table name="MAP Fault Trig: Mid VE Min #1" category="MAPSensor" address="2894" type="1D" level="1" scaling="Volts16"/>

<table name="MAP Fault Trig High VE #1" category="MAPSensor" address="289A" type="1D" level="1" scaling="Volts16"/>

<table name="MAP vs MAF Baro" category="MAPSensor" address="2802" type="1D" level="1" scaling="uint16"/>

<table name="MAP Comparison" category="MAPSensor" address="27FE" type="1D" level="1" scaling="Volts16"/>
----

After modifying and saving the ROM xml file, launch ECUFlash, open your ROM, and find the new entries. Note that they have their own category. It may be necessary to set ECUFlash to "Developer" mode in the ECUFlash options (and relaunch ECUFlash) to be able to see the tables. Here is what needs to be changed in ECUFlash:

0.84 11
1.37 20
1.89 31
2.42 40
2.95 48
3.48 57
4.00 67
4.53 800.0204
4.98 255

Change the values to:
Not Verified yet
0.23 25
0.46 49
0.66 70
0.91 96
1.13 120
1.36 144
1.61 170
1.85 195
2.42 255

Change the "MAP Fault Trig: Mid VE Max #1" value from 4.80 to 4.90.

Change the "MAP Fault Trig: Mid VE Min #1" value from 0.20 to 0.10.

Change the "MAP Fault Trig High VE #1" value from 1.80 to 0.51.

Change the "MAP vs Baro" parameter from 162 to 44. Testing Needed

Change the "MAP Comparison" value from 4.00 to 0.702. Needs to be tested

In ECUFlash, find the "Periphery4 (FEA) Bits" table. Change bit.14 from 1 to 0. This can be done by using the "minus" key on your computer. This disables the P0069 test.

Now find the "Periphery2 (FCA) Bits" table. Change bit.9 from 1 to 0. Use the "minus" key. This disables the PO401 (EGR) test.

Save the ROM file, and flash your ECU with it. That's it for the Evo 9 ROM mods. Now skip down to the end of this post to see instructions for setting up EvoScan/Mitsulogger to log boost.


ROM Mods for 2004 USDM Evo 8 ROMs 96420007, 96420008

First is to add some definitions to your ECUFlash ROM XML definition file found in:

C:\Program Files\OpenECU\EcuFlash\rommetadata\mitsubishi\evo

Open the 96420007.xml file with the text/XML editor of your choice. Scroll down to the bottom of the file. Add the following lines just before the </rom> tag (copy everything *between* the ----):

----
<table name="MAP Test 1: Mid VE Max Voltage" category="MAPSensor" address="2048" type="1D" level="1" scaling="Volts16"/>

<table name="MAP Test 1: Mid VE Min Voltage" category="MAPSensor" address="2046" type="1D" level="1" scaling="Volts16"/>

<table name="MAP Test 2: Low VE Max Voltage" category="MAPSensor" address="204C" type="1D" level="1" scaling="Volts16"/>

<table name="MAP Test 3: High VE Min Voltage" category="MAPSensor" address="2050" type="1D" level="1" scaling="Volts16"/>

<table name="MAP Test 4: Max Minus Min" category="MAPSensor" address="2054" type="1D" level="1" scaling="Volts16"/>

<table name="MAP Scaling for Baro" category="MAPSensor" address="12059" type="1D" level="1" scaling="uint8"/>
----

After modifying and saving the ROM xml file, launch ECUFlash, open your ROM, and find the new entries. Note that they have their own category. It may be necessary to set ECUFlash to "Developer" mode in the ECUFlash options (and relaunch ECUFlash) to be able to see the tables. Here is what needs to be changed in ECUFlash:

MAP Test 1: Mid VE High Voltage Test -- Change from 4.61 volts to 4.90 volts.

MAP Test 1: Mid VE Low Voltage Test -- Change from 0.10 volts to 0.06 volts.

MAP Test 3: High VE Voltage Test -- Change from 1.80 volts to 0.51 volts.

MAP Test 4: Max Minus Min -- Change from 1.80 volts to 0.51 volts.

Change the "MAP Scaling for Baro" from 50 to 350

In ECUFlash, find the "Periphery2 (FCA) Bits" table. Change bit.9 from 1 to 0. Use the "minus" key on the keyboard. This disables the P0401 (EGR) test.

Save the ROM file, and flash your ECU with it. That's it for the ROM mods. Now skip down to the end of this post to see instructions for setting up EvoScan/Mitsulogger to log boost.


ROM Mods for 2004 USDM Evo 8 ROMs 94170014, 94170015

First is to add some definitions to your ECUFlash ROM XML definition file found in:

C:\Program Files\OpenECU\EcuFlash\rommetadata\mitsubishi\evo

Open the 94170014.xml or 94170015.xml file with the text/XML editor of your choice. Scroll down to the bottom of the file. Add the following lines just before the </rom> tag (copy everything *between* the ----):

----
<table name="MAP Test 1: Mid VE Max Voltage" category="MAPSensor" address="2048" type="1D" level="1" scaling="Volts16"/>

<table name="MAP Test 1: Mid VE Min Voltage" category="MAPSensor" address="2046" type="1D" level="1" scaling="Volts16"/>

<table name="MAP Test 2: Low VE Max Voltage" category="MAPSensor" address="204C" type="1D" level="1" scaling="Volts16"/>

<table name="MAP Test 3: High VE Min Voltage" category="MAPSensor" address="2050" type="1D" level="1" scaling="Volts16"/>
----

After modifying and saving the ROM xml file, launch ECUFlash, open your ROM, and find the new entries. Note that they have their own category. It may be necessary to set ECUFlash to "Developer" mode in the ECUFlash options (and relaunch ECUFlash) to be able to see the tables. Here is what needs to be changed in ECUFlash:

MAP Test 1: Mid VE High Voltage Test -- Change from 4.61 volts to 4.80 volts.

MAP Test 1: Mid VE Low Voltage Test -- Change from 0.10 volts to 0.06 volts.

MAP Test 3: High VE Voltage Test -- Change from 1.8 volts to 0.5 volts.

In ECUFlash, find the "Periphery2 (FCA) Bits" table. Change bit.9 from 1 to 0. Use the "minus" key on the keyboard. This disables the P0401 (EGR) test.

Save the ROM file, and flash your ECU with it. That's it for the ROM mods. Now skip down to the end of this post to see instructions for setting up EvoScan/Mitsulogger to log boost.


ROM Mods for 2003 USDM Evo 8 ROM 94170008

First is to add some definitions to your ECUFlash ROM XML definition file found in:

C:\Program Files\OpenECU\EcuFlash\rommetadata\mitsubishi\evo

Open the 94170008.xml file with the text/XML editor of your choice. Scroll down to the bottom of the file. Add the following lines just before the </rom> tag (copy everything *between* the ----):

----
<table name="MAP Test 1: Mid VE Max Voltage" category="MAPSensor" address="2048" type="1D" level="1" scaling="Volts16"/>

<table name="MAP Test 1: Mid VE Min Voltage" category="MAPSensor" address="2046" type="1D" level="1" scaling="Volts16"/>

<table name="MAP Test 2: Low VE Max Voltage" category="MAPSensor" address="204C" type="1D" level="1" scaling="Volts16"/>

<table name="MAP Test 3: High VE Min Voltage" category="MAPSensor" address="2050" type="1D" level="1" scaling="Volts16"/>
----

After modifying and saving the ROM xml file, launch ECUFlash, open your ROM, and find the new entries. Note that they have their own category. It may be necessary to set ECUFlash to "Developer" mode in the ECUFlash options (and relaunch ECUFlash) to be able to see the tables. Here is what needs to be changed in ECUFlash:

MAP Test 1: Mid VE High Voltage Test -- Change from 4.61 volts to 4.90 volts.

MAP Test 1: Mid VE Low Voltage Test -- Change from 0.10 volts to 0.06 volts.

MAP Test 3: High VE Voltage Test -- Change from 1.80 volts to 0.51 volts.

In ECUFlash, find the "Periphery2 (FCA) Bits" table. Change bit.9 from 1 to 0. Use the "minus" key on the keyboard. This disables the P0401 (EGR) test.

Save the ROM file, and flash your ECU with it. That's it for the ROM mods. Now skip down to the end of this post to see instructions for setting up EvoScan/Mitsulogger to log boost.


Logging Boost in EvoScan or Mitsulogger

MAP sensors do not know the local atmospheric pressure. To log boost in psig (what all boost gauges show and what people always use to discuss boost values), the conversion formula for the logging program needs to have an offset for your local atmospheric pressure. The general formula for the Omni 7 bar MAP sensor is:

0.4078*x-b

where b is the local atmospheric pressure. The local atmospheric pressure is affected strongly affected by altitude. For example the pressure at sea level is 14.7 psi, but at 5000 ft, the pressure is 12.2 psi. That's a big difference when you want to log boost. Use this table of altitude vs pressure to determine the offset pressure for your formula:

altitude (ft) local atmospheric pressure (psi)
0 14.7
500 14.4
1000 14.2
1500 13.9
2000 13.7
2500 13.4
3000 13.2
3500 12.9
4000 12.7
4500 12.5
5000 12.2
6000 11.8
7000 11.3
8000 10.9

*For example*, if you are living at 750 ft, then you'd want to use 14.3 psi as your offset, and the formula would be

0.4078*x-14.3

For kPa use this formula (no offsets with kPa)
2.8118*x

In the following instructions, please use your formula in place of the words FORMULA HERE.

For EvoScan 0.99+, the MAP logging definition in the Data.xml file should be changed to:

<DataListItem DataLog="Y" Color="" Display="OMNI7 MAP" LogReference="AEM5MAP" RequestID="38" Eval="FORMULA HERE" Unit="psig" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="-15" GaugeMax="100" ChartMin="-15" ChartMax="100" ScalingFactor="1" Notes=""/>

To log boost in psi in Mitsulogger, the MAP logging definition should be changed to:

<Request LogReference="OMNI7MAP" RequestID="38" Eval="FORMULA HERE" Unit="psig" Logged="y" Response="2"/>

Last edited by RoadSpike; Apr 14, 2010 at 12:39 PM.
Old Apr 14, 2010 | 02:23 AM
  #3  
tscompusa2's Avatar
Former Sponsor
iTrader: (22)
 
Joined: Oct 2005
Posts: 5,375
Likes: 8
From: pa
7bar .... damn ...... you might want to note in these posts that when you swap the sensor with a omni map sensor it creates a boost leak until you upgrade the rubber oring with something thicker.
Old Apr 14, 2010 | 02:43 AM
  #4  
RoadSpike's Avatar
Thread Starter
Evolved Member
iTrader: (5)
 
Joined: Oct 2006
Posts: 3,805
Likes: 2
From: Sacramento, CA
Originally Posted by tscompusa
7bar .... damn ...... you might want to note in these posts that when you swap the sensor with a omni map sensor it creates a boost leak until you upgrade the rubber oring with something thicker.
Noted in the intro now

Yeah I can't imagine doing 87psi of boost but there are a few moving past 44psi so I thought I would give them another option besides the 5 bar.
Old Apr 14, 2010 | 04:45 AM
  #5  
MR Turco's Avatar
EvoM Staff Alumni
iTrader: (16)
 
Joined: May 2007
Posts: 3,233
Likes: 3
From: Massachusetts
Wow 7 bar?! wouldn't this kill resolution?
Old Apr 14, 2010 | 10:06 AM
  #6  
RoadSpike's Avatar
Thread Starter
Evolved Member
iTrader: (5)
 
Joined: Oct 2006
Posts: 3,805
Likes: 2
From: Sacramento, CA
Originally Posted by MR Turco
Wow 7 bar?! wouldn't this kill resolution?
Its not really that bad the ADC is 10 bit so you get 1023 x for 5 volts

A single movement in x is related to 0.0992 PSI or 0.6843 kPa. I think around 10 BAR we would get into real trouble.

Last edited by RoadSpike; Apr 14, 2010 at 10:19 AM.
Old Apr 14, 2010 | 11:51 AM
  #7  
JohnBradley's Avatar
Evolved Member
iTrader: (30)
 
Joined: Jan 2004
Posts: 11,400
Likes: 75
From: Northwest
Awesome, good job
Old Apr 14, 2010 | 11:58 AM
  #8  
RoadSpike's Avatar
Thread Starter
Evolved Member
iTrader: (5)
 
Joined: Oct 2006
Posts: 3,805
Likes: 2
From: Sacramento, CA
Originally Posted by JohnBradley
Awesome, good job
hehe well don't congrads me just yet i can't even test most of this

I just wanted to get this ball rolling
Old Apr 14, 2010 | 02:16 PM
  #9  
RoadSpike's Avatar
Thread Starter
Evolved Member
iTrader: (5)
 
Joined: Oct 2006
Posts: 3,805
Likes: 2
From: Sacramento, CA
Blah realized when I looked this afternoon I goofed on the 16bit psi scaling for the boost adder. I didn't put in the right unit type so thats fixed.
Old May 16, 2011 | 02:28 AM
  #10  
kiwiracer's Avatar
Newbie
 
Joined: Mar 2010
Posts: 24
Likes: 0
From: new zealand
how would you set up a omni 7 bar sensor in a evo 8 ecu with tv7 mod 96531706?
Old May 16, 2011 | 02:38 AM
  #11  
RoadSpike's Avatar
Thread Starter
Evolved Member
iTrader: (5)
 
Joined: Oct 2006
Posts: 3,805
Likes: 2
From: Sacramento, CA
Originally Posted by kiwiracer
how would you set up a omni 7 bar sensor in a evo 8 ecu with tv7 mod 96531706?
The 9653 variant requires no settings.

Since the EDM cars didn't come with MDP sensors attached there are no settings to enable their use or stop CEL lights from appearing. You just simply plug in the sensor and start logging it with the formula provided.
Old May 16, 2011 | 08:19 PM
  #12  
kiwiracer's Avatar
Newbie
 
Joined: Mar 2010
Posts: 24
Likes: 0
From: new zealand
Originally Posted by RoadSpike
The 9653 variant requires no settings.

Since the EDM cars didn't come with MDP sensors attached there are no settings to enable their use or stop CEL lights from appearing. You just simply plug in the sensor and start logging it with the formula provided.
ok so i have a evo 6.5 car/ loom but going to use a evo 8 ecu. so im adding new wiring to my loom and attching a map sensor to pin 73 and doind the sd conversion.

im reflashing the ecu with 9653 v7 mod, and running a omni 7 bar sensor...

so dont I need to change the matching xlm rometa file that matchs to suit the omni 7 bar?
Old May 16, 2011 | 08:23 PM
  #13  
RoadSpike's Avatar
Thread Starter
Evolved Member
iTrader: (5)
 
Joined: Oct 2006
Posts: 3,805
Likes: 2
From: Sacramento, CA
Originally Posted by kiwiracer
ok so i have a evo 6.5 car/ loom but going to use a evo 8 ecu. so im adding new wiring to my loom and attching a map sensor to pin 73 and doind the sd conversion.

im reflashing the ecu with 9653 v7 mod, and running a omni 7 bar sensor...

so dont I need to change the matching xlm rometa file that matchs to suit the omni 7 bar?
I think your confused to what the xml does.

It does not change anything that your car is capable of it only highlights and defines areas for you to edit in your rom. Since the 9653 variant requires no settings no xml is required to edit parameters in order to prevent error codes.
Old May 16, 2011 | 08:47 PM
  #14  
kiwiracer's Avatar
Newbie
 
Joined: Mar 2010
Posts: 24
Likes: 0
From: new zealand
Originally Posted by RoadSpike
I think your confused to what the xml does.

It does not change anything that your car is capable of it only highlights and defines areas for you to edit in your rom. Since the 9653 variant requires no settings no xml is required to edit parameters in order to prevent error codes.
ok so i just have to enter the scalings for the omni 7 bar in the rom?. sorry im kinda new to this im going from a autronic to factory
Old May 16, 2011 | 09:16 PM
  #15  
RoadSpike's Avatar
Thread Starter
Evolved Member
iTrader: (5)
 
Joined: Oct 2006
Posts: 3,805
Likes: 2
From: Sacramento, CA
Originally Posted by kiwiracer
ok so i just have to enter the scalings for the omni 7 bar in the rom?. sorry im kinda new to this im going from a autronic to factory
Nope nothing to enter. You will need to add an entry in evoscan though to log the correct psi. All evoscan does is logs voltage we apply a formula to it in order to convert it to psi or kpa.


Quick Reply: Omni 7 BAR Scalings



All times are GMT -7. The time now is 08:07 PM.