Omni 4bar map sensor Plug and Play
EvoM Guru
iTrader: (50)
Joined: Mar 2006
Posts: 9,675
Likes: 132
From: Tri-Cities, WA // Portland, OR
Wouldn't the 4bar just need different scalings for the boost control tables?
25 psi of boost would be roughly a raw bit count of 214 using the JDM 3bar. So your desired boost table is 25 psi, which is 214 raw.
That same 214 bit count would correspond to ~36 PSI on the 4bar. Thus, the ECU would try to reach the raw bit count of 214, giving you 36 psi instead of 25 PSI that is reflected using the 3 bar scaling.
The ECU just looks at the raw bit count, it has no idea if you have a 3 bar or 4bar. The ECU tables just need to be scaled to reflect the 4bar.
But honestly, I haven't tuned closed loop boost at all (I use a manual controller) so I could be completely wrong.
25 psi of boost would be roughly a raw bit count of 214 using the JDM 3bar. So your desired boost table is 25 psi, which is 214 raw.
That same 214 bit count would correspond to ~36 PSI on the 4bar. Thus, the ECU would try to reach the raw bit count of 214, giving you 36 psi instead of 25 PSI that is reflected using the 3 bar scaling.
The ECU just looks at the raw bit count, it has no idea if you have a 3 bar or 4bar. The ECU tables just need to be scaled to reflect the 4bar.
But honestly, I haven't tuned closed loop boost at all (I use a manual controller) so I could be completely wrong.
Wouldn't the 4bar just need different scalings for the boost control tables?
25 psi of boost would be roughly a raw bit count of 214 using the JDM 3bar. So your desired boost table is 25 psi, which is 214 raw.
That same 214 bit count would correspond to ~36 PSI on the 4bar. Thus, the ECU would try to reach the raw bit count of 214, giving you 36 psi instead of 25 PSI that is reflected using the 3 bar scaling.
The ECU just looks at the raw bit count, it has no idea if you have a 3 bar or 4bar. The ECU tables just need to be scaled to reflect the 4bar.
But honestly, I haven't tuned closed loop boost at all (I use a manual controller) so I could be completely wrong.
25 psi of boost would be roughly a raw bit count of 214 using the JDM 3bar. So your desired boost table is 25 psi, which is 214 raw.
That same 214 bit count would correspond to ~36 PSI on the 4bar. Thus, the ECU would try to reach the raw bit count of 214, giving you 36 psi instead of 25 PSI that is reflected using the 3 bar scaling.
The ECU just looks at the raw bit count, it has no idea if you have a 3 bar or 4bar. The ECU tables just need to be scaled to reflect the 4bar.
But honestly, I haven't tuned closed loop boost at all (I use a manual controller) so I could be completely wrong.
Any settings reference, or location to look for?
Hey guys. After installing the omni 4 bar, I've noticed a lean spike of over 18.4 (aem wideband) when slightly lifting off the throttle after boosting. Has anyone else experienced this? Any ideas?
D-VO, I am seeing similiar. If I lift I go flat line on my AEM Wideband. Of ourse I am also experiencing stutter, hesitation and misfire when I push the throttle over 25% at about 3k - 5k. I also just installed my 272's at the same time though...
By chance do you have the scalings for ECUFlash and EVO scan on the Omni 4 Bar, I don't hink mine is reading right. My boost guage says higher than Evo Scan does...
Any help on this would be tremendous. Thanks
By chance do you have the scalings for ECUFlash and EVO scan on the Omni 4 Bar, I don't hink mine is reading right. My boost guage says higher than Evo Scan does...
Any help on this would be tremendous. Thanks
D-VO, I am seeing similiar. If I lift I go flat line on my AEM Wideband. Of ourse I am also experiencing stutter, hesitation and misfire when I push the throttle over 25% at about 3k - 5k. I also just installed my 272's at the same time though...
By chance do you have the scalings for ECUFlash and EVO scan on the Omni 4 Bar, I don't hink mine is reading right. My boost guage says higher than Evo Scan does...
Any help on this would be tremendous. Thanks
By chance do you have the scalings for ECUFlash and EVO scan on the Omni 4 Bar, I don't hink mine is reading right. My boost guage says higher than Evo Scan does...
Any help on this would be tremendous. Thanks

*Now that I'm looking at this, shouldn't the map scaling table go upto 5 volts and not 3.63? I thought the omni map sensors read from 0 - 5 volts. Could that be whats causing the lean spike? Does anyone else have this problem?
For EVOScan: What I did was copied the "JDMMap" code in the xml to create a second one and named it "Omni 4 bar", then changed the formula to 0.238683*x-(add your atmospheric pressure here), so in case I need to log JDMMap on someone elses car I'll still have the correct formula for the 3 bar.
BTW: I've noticed this stuttering issue coming up again in recent posts. Didn't this have something to do with the P0300 code or blown head gasket or something. I used to have this problem too, but my memory is a bit spotty on the answer.
Last edited by D-VO; Aug 8, 2009 at 01:18 PM. Reason: oops
96940011:
<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="EGR MAP offset #1" category="MAPSensor" address="44fa" type="2D" level="1" scaling="uint8">
<table name="RPM" address="623c" type="Y Axis" elements="9" scaling="RPM"/>
</table>
<table name="EGR MAP offset #2" category="MAPSensor" address="450a" type="2D" level="1" scaling="uint8">
<table name="RPM" address="623c" type="Y Axis" elements="9" scaling="RPM"/>
</table>
<table name="EGR Pressure Diff" category="MAPSensor" address="1b68" type="1D" level="1" scaling="Volts16"/>
<table name="MAP Comparison" category="MAPSensor" address="27fe" type="1D" level="1" scaling="Volts16"/>
The rest are here: https://www.evolutionm.net/forums/ec...tructions.html
<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="EGR MAP offset #1" category="MAPSensor" address="44fa" type="2D" level="1" scaling="uint8">
<table name="RPM" address="623c" type="Y Axis" elements="9" scaling="RPM"/>
</table>
<table name="EGR MAP offset #2" category="MAPSensor" address="450a" type="2D" level="1" scaling="uint8">
<table name="RPM" address="623c" type="Y Axis" elements="9" scaling="RPM"/>
</table>
<table name="EGR Pressure Diff" category="MAPSensor" address="1b68" type="1D" level="1" scaling="Volts16"/>
<table name="MAP Comparison" category="MAPSensor" address="27fe" type="1D" level="1" scaling="Volts16"/>
The rest are here: https://www.evolutionm.net/forums/ec...tructions.html
Omni Power 4 & 7 Bar MAP Sensors ($100 shipped): http://www.stikiller.com/product.php...age=1&featured


