Notices
Evo Engine / Turbo / Drivetrain Everything from engine management to the best clutch and flywheel.

p0106 code after installing Omni 4 bar

Thread Tools
 
Search this Thread
 
Old May 23, 2011 | 04:26 PM
  #1  
Hi Im Vinh's Avatar
Thread Starter
Evolving Member
15 Year Member
iTrader: (12)
 
Joined: Mar 2009
Posts: 363
Likes: 0
From: Houston,Tx
p0106 code after installing Omni 4 bar

Yesterday I installed and had the car's ecu properly setup to run the Omni 4 bar, all was good until today when I left the gym and noticed the CEL was on. Turns out the code is p0106( manifold absolute pressure sensor), does anybody know how I can go about fixing this? Yes, I searched before posting this thread but found no answer. The sensor is brand new and I did not drop it, any help would be greatly appreciated.
Reply
Old May 23, 2011 | 04:31 PM
  #2  
JohnBradley's Avatar
Evolved Member
Shutterbug
Liked
Loved
Community Favorite
iTrader: (30)
 
Joined: Jan 2004
Posts: 11,406
Likes: 78
From: Northwest
You changed the periphery 4 to B980?
Reply
Old May 23, 2011 | 04:36 PM
  #3  
Hi Im Vinh's Avatar
Thread Starter
Evolving Member
15 Year Member
iTrader: (12)
 
Joined: Mar 2009
Posts: 363
Likes: 0
From: Houston,Tx
Originally Posted by JohnBradley
You changed the periphery 4 to B980?
JB to save the day, I was not the actual person doing the ecu work but a friend was. I will be sure to ask him tonight when he gets back to me. THanks for the quick reply
Reply
Old May 29, 2011 | 11:56 AM
  #4  
Hi Im Vinh's Avatar
Thread Starter
Evolving Member
15 Year Member
iTrader: (12)
 
Joined: Mar 2009
Posts: 363
Likes: 0
From: Houston,Tx
bump for any help, the periphery 4 is changed to B980 JB
Reply
Old May 29, 2011 | 12:00 PM
  #5  
8UpUrV8's Avatar
Evolved Member
iTrader: (9)
 
Joined: Jul 2006
Posts: 553
Likes: 0
From: Houston
I did the flashing for the sensor. Logged fine after installing. Per4 was already at B980.

Have not tried logging after cel.
Reply
Old May 30, 2011 | 08:16 AM
  #6  
Hi Im Vinh's Avatar
Thread Starter
Evolving Member
15 Year Member
iTrader: (12)
 
Joined: Mar 2009
Posts: 363
Likes: 0
From: Houston,Tx
bump for any suggestions
Reply
Old May 30, 2011 | 11:59 AM
  #7  
Evoryder's Avatar
Evolved Member
iTrader: (55)
 
Joined: Apr 2004
Posts: 7,383
Likes: 10
From: ☼ Florida ☼
following MrFreds instructions should result in no codes. I'm sure something was not updated properly. Happens all the time.


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:

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

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 77.

Change the "MAP Comparison" value from 4.00 to 1.23.

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.
Reply
Old May 31, 2011 | 10:18 PM
  #8  
Hi Im Vinh's Avatar
Thread Starter
Evolving Member
15 Year Member
iTrader: (12)
 
Joined: Mar 2009
Posts: 363
Likes: 0
From: Houston,Tx
Thanks for the suggestion Evoryder, we will give that a try next time
Reply
Old Jul 18, 2011 | 08:41 AM
  #9  
Hi Im Vinh's Avatar
Thread Starter
Evolving Member
15 Year Member
iTrader: (12)
 
Joined: Mar 2009
Posts: 363
Likes: 0
From: Houston,Tx
I had the code erased at Advanced Auto and it stay off for 188 miles and yesterday night it came back on , I thought it was gone for good after passing the 150 mi. mark. Bump for anyone's input/suggestions/opinions
Reply
Old Jul 18, 2011 | 06:10 PM
  #10  
Evoryder's Avatar
Evolved Member
iTrader: (55)
 
Joined: Apr 2004
Posts: 7,383
Likes: 10
From: ☼ Florida ☼
Does it measure boost correctly? Other than a faulty sensor i can't see why it would not work. If the code is correct you should be fine.
Reply
Old Jul 19, 2011 | 09:04 AM
  #11  
Hi Im Vinh's Avatar
Thread Starter
Evolving Member
15 Year Member
iTrader: (12)
 
Joined: Mar 2009
Posts: 363
Likes: 0
From: Houston,Tx
Originally Posted by Evoryder
Does it measure boost correctly? Other than a faulty sensor i can't see why it would not work. If the code is correct you should be fine.
Before the CEL came up the sensor did measure boost correctly, It could possibly be faulty . But for now I shouldn't I have problems driving the car hard if the code is for a faulty map sensor correct?
Reply
Old Jul 19, 2011 | 09:11 AM
  #12  
05blue8's Avatar
Evolved Member
iTrader: (28)
 
Joined: Mar 2007
Posts: 843
Likes: 5
From: Austin, TX
If the map sensor was bad you'd know it, your car would run like ****, I've had two omni's fail on me and you know it the first time you try to build boost. Your issue isn't a bad sensor, something in the ROM isn't right is my guess. If you can boost past 5psi without the car feeling like it's about to fall apart, your sensor is good
Reply
Old Jul 19, 2011 | 04:55 PM
  #13  
Hi Im Vinh's Avatar
Thread Starter
Evolving Member
15 Year Member
iTrader: (12)
 
Joined: Mar 2009
Posts: 363
Likes: 0
From: Houston,Tx
Originally Posted by 05blue8
If the map sensor was bad you'd know it, your car would run like ****, I've had two omni's fail on me and you know it the first time you try to build boost. Your issue isn't a bad sensor, something in the ROM isn't right is my guess. If you can boost past 5psi without the car feeling like it's about to fall apart, your sensor is good
That's a good sigh of relief, yes car hits 25psi fine . Hopefully I can get this issue fixed soon, I'm about 80% set that it has to do with the ROM as well.
Reply
Old Jul 19, 2011 | 05:04 PM
  #14  
EvoVIII03's Avatar
Evolving Member
iTrader: (11)
 
Joined: Dec 2008
Posts: 111
Likes: 0
From: Michigan
Follow the instructions that Evoryder posted above and I bet that will fix your problem.
Reply
Old Jul 19, 2011 | 05:12 PM
  #15  
JohnBradley's Avatar
Evolved Member
Shutterbug
Liked
Loved
Community Favorite
iTrader: (30)
 
Joined: Jan 2004
Posts: 11,406
Likes: 78
From: Northwest
Just saw this thread again...sorry about the delay in getting back to you.

SO i am looking at it right now to see what the issue is.

aaron
Reply



All times are GMT -7. The time now is 06:39 PM.