Notices
ECU Flash

Omni 4 bar MAP sensor ROM compatibility settings for USDM Evo 8/9

Thread Tools
 
Search this Thread
 
Old Jun 15, 2011 | 08:59 PM
  #181  
Nashou66's Avatar
Evolving Member
 
Joined: Apr 2011
Posts: 125
Likes: 0
From: West Seneca NY
Ahh your right Hornstar. I wasn't thinking.


So all is good with mine then as well!!

Athanasios
Reply
Old Jun 21, 2011 | 10:00 PM
  #182  
gunhaha's Avatar
Evolving Member
iTrader: (5)
 
Joined: Mar 2007
Posts: 206
Likes: 0
From: Kansas
Originally Posted by HornstarBU
I just installed mine this evening, it's pretty dead on.

At boost I show 6.5 psi, gauge shows 6 ish...not an accurate guage though
At idle, evoscan shows -11 psi (also known as 22 in /Hg) and my guage shows 22in/Hg

I noticed a lot of people say vacuum is wrong on theirs, it's just that the map sensor shows starting at absolute 0, and always in PSI, but most boost gauges show in/Hg and then switch to PSI at 0 atmospheric, or 14.7 absolute..

I think...whatever, -11 is the same as your boost gauge showing -22.
1 psi is equal to 1.9 inHg
Reply
Old Jun 22, 2011 | 12:22 AM
  #183  
And's Avatar
And
Evolving Member
20 Year Member
 
Joined: Dec 2005
Posts: 419
Likes: 0
From: Bristol, England
I log with x*1.6334 and it gives you kPa then which is easy to convert in to bar etc as 100 = atmos 200 = 1bar and 300 = 2bar
Reply
Old Dec 18, 2011 | 08:47 PM
  #184  
sabrinaEvo's Avatar
Evolving Member
iTrader: (2)
 
Joined: Jun 2011
Posts: 138
Likes: 1
From: San Jose
Just did this today.

Do these numbers look right for an Evo IX with only an open air filter and turbo back exhaust?

3rd gear pull from 2-6k rpm (needed more space for the last 1k but didn't have it):

Max boost = 19.18 psi @ 3500 rpm
Tapers to ~ 16.33 psi before lifting

Reply
Old Dec 23, 2011 | 11:47 PM
  #185  
crckheadjed's Avatar
Evolving Member
15 Year Member
iTrader: (4)
 
Joined: Aug 2008
Posts: 246
Likes: 1
From: Connecticut
Is it okay if i try to change my values to the specified ones but cannot make them exact per ecuflash rounding up or down?

0.51 25
0.90 49
1.29 70
1.68 96
2.07 120
2.46 144
2.85 170
3.24 195
3.63 255


Mine-

0.51 25
0.90 49
1.29 70
1.69 96
2.08 120
2.45 144
2.84 170
3.24 195
3.63 255
Reply
Old Dec 24, 2011 | 09:13 AM
  #186  
sabrinaEvo's Avatar
Evolving Member
iTrader: (2)
 
Joined: Jun 2011
Posts: 138
Likes: 1
From: San Jose
Originally Posted by crckheadjed
Is it okay if i try to change my values to the specified ones but cannot make them exact per ecuflash rounding up or down?

0.51 25
0.90 49
1.29 70
1.68 96
2.07 120
2.46 144
2.85 170
3.24 195
3.63 255


Mine-

0.51 25
0.90 49
1.29 70
1.69 96
2.08 120
2.45 144
2.84 170
3.24 195
3.63 255
I had the same thing happen to me. It would round or display 0.01 difference after entering it into EcuFlash. I think it should be fine. The chart above was using settings similar to yours (i.e. not exactly the same as the chart from the OP), and people told me the chart looks right for a stock turbo & boost.

Also, my starting values in the chart were also a bit different from the table in the OP.

Try it out and log and compare to mine if you're running stock boost.
Reply
Old Dec 24, 2011 | 05:09 PM
  #187  
crckheadjed's Avatar
Evolving Member
15 Year Member
iTrader: (4)
 
Joined: Aug 2008
Posts: 246
Likes: 1
From: Connecticut
well it ran as it did with stock, so im assuming its alright. logs comparable to the stock map/settings
Reply
Old Apr 10, 2012 | 12:09 PM
  #188  
06Black's Avatar
Evolving Member
 
Joined: Mar 2008
Posts: 142
Likes: 0
From: The mitten
mrfred, is it ok to use the code you listed for the Evo9 ROM's with 88591715?
Reply
Old Apr 30, 2012 | 11:28 AM
  #189  
05blue8's Avatar
Evolved Member
iTrader: (28)
 
Joined: Mar 2007
Posts: 843
Likes: 5
From: Austin, TX
Hey guys, I'm running 96530706 and had been logging boost fine until my motor went boom. I got my car back a week ago and now boost isn't logging. It's stuck at 34.5383. I have the formula right in EvoScan so is there anything else I can check to see what could be going on? I know the symptoms of a bad map sensor (car runs bad, bogs, barely drivable) and my car runs good, my aem gauge works fine, it was tuned using the Zeitronix set-up and worked fine there but mine stopped.

Thanks!
Matt
Reply
Old Apr 30, 2012 | 12:38 PM
  #190  
Z_Lancer_Man's Avatar
Evolved Member
iTrader: (115)
 
Joined: Dec 2003
Posts: 2,295
Likes: 4
From: Albuquerque, NM
Originally Posted by 05blue8
Hey guys, I'm running 96530706 and had been logging boost fine until my motor went boom. I got my car back a week ago and now boost isn't logging. It's stuck at 34.5383. I have the formula right in EvoScan so is there anything else I can check to see what could be going on? I know the symptoms of a bad map sensor (car runs bad, bogs, barely drivable) and my car runs good, my aem gauge works fine, it was tuned using the Zeitronix set-up and worked fine there but mine stopped.

Thanks!
Matt
Sounds like your sensor/sender has gone bad. I assume you've made sure everything is still hooked up correctly (power, signal, etc.). You could put a DMM on the signal output wire and ground and see I the voltage fluctuates with the engine running.
Reply
Old Apr 30, 2012 | 12:47 PM
  #191  
05blue8's Avatar
Evolved Member
iTrader: (28)
 
Joined: Mar 2007
Posts: 843
Likes: 5
From: Austin, TX
Thanks for the tip, the wires are wrapped so I need to cut back the wiring to make sure just in case something happened.

If the sensor was bad wouldn't the car run like crap? I've had a sensor go bad and the car wasn't drivable at all.
Reply
Old Jun 15, 2012 | 10:09 PM
  #192  
Eisen7's Avatar
Evolving Member
 
Joined: Jul 2007
Posts: 172
Likes: 1
From: Australia
Just wanted to check what the "EGR Pressure Diff" should be set to if running an Omni 4 bar sensor, as it's not really mentioned here.

At the moment my "EGR Pressure Diff" is set to 0.12. Is that correct?

Note that this is on a JDM 7 running 90550701. Thanks!
Reply
Old Jul 11, 2012 | 03:19 PM
  #193  
Raceghost's Avatar
Evolved Member
iTrader: (4)
 
Joined: Dec 2001
Posts: 1,034
Likes: 21
From: Out West
MFRED,

I came across this thread again when I was double checking for the 1000'th time why MAPsensor settings are not available in the 96530706 ROM.

Either way, just a heads up on the settings for the 94170715 ROM. All other roms you have the Mid VE set to 4.90v from the stock 4.2 or something. With this 94170715 ROM you have them set the MAP Test 1: Mid VE High Voltage Test -- Change from 4.61 volts to 4.80 volts. Curiosity asks if this is a typo, for my readings are still off a bit. I recently changed to 4.90 v and have not gone out and got a reading. Will you double check your results if you have them from 3 years ago, and see if you made a typo on the Mid VE voltage?

Thanks in advance.

Last edited by Raceghost; Jul 11, 2012 at 03:22 PM.
Reply
Old Jan 8, 2013 | 04:09 PM
  #194  
black_beauty's Avatar
Evolved Member
15 Year Member
iTrader: (19)
 
Joined: Feb 2010
Posts: 854
Likes: 1
From: Clarksville, TN
Did this and Evoscan shows -14.4 all the time? What could I have done wrong?
Reply
Old Feb 10, 2013 | 12:25 AM
  #195  
Dynotech Tuning's Avatar
Former Sponsor
iTrader: (12)
 
Joined: Jan 2011
Posts: 1,312
Likes: 9
From: Seekonk, MA
***UPDATED 2/10/2013 after finding a math error of mine which made MrFreds original formulas correct anyhow***
I will keep this here to avoid further confusion, my bad.

I came across the actual formulas from OMNI the other day and created the actual formulas we should be using for kpa and PSIg:

OMNI 4 BAR MAP KPA
Code:
<DataListItem DataLog="N" Color="" Display="OMNI 4 bar kPA" LogReference="OMNI4barKPA" RequestID="38" Eval=" x*1.63345239" Unit="kpa" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="400" ChartMin="0" ChartMax="400" ScalingFactor="1" Notes="" Priority="1" Visible="False" LogHide="false" />





OMNI 4 BAR MAP PSIg

To accurately log PSIg, the formula is:

x*0.23691218-B


where B is the local atmospheric pressure. The local atmospheric pressure is 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

x*0.23691218-14.3


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


<DataListItem DataLog="N" Color="" Display="OMNI 4 bar PSIg" LogReference="OMNI4barPSIg" RequestID="38" Eval="FORMULA HERE" Unit="kpa" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="43.5" ChartMin="0" ChartMax="43.5" ScalingFactor="1" Notes="" Priority="1" Visible="False" LogHide="false" />


TIP:

I find the best way to find the accurate local atmospheric pressure is to set the B value to the number zero and have the engine ice cold at ambient outside temperature. Turn the key ON but do not start the vehicle. Log the Omni 4 bar PSI in evoscan. Replace the B value with whatever reading you datalogged.

example: If you logged 14.65, replace the zero you placed in the formula with 14.65

Relog the PSI and now it should roughly read 0 PSI.


-Jamie

Last edited by Dynotech Tuning; Feb 10, 2013 at 02:01 PM.
Reply



All times are GMT -7. The time now is 01:13 PM.