Omni 4 bar MAP sensor ROM compatibility settings for USDM Evo 8/9
#17
Evolved Member
iTrader: (115)
Over the weekend I installed the Omni 4 Bar and made the changes to my ROM as advised by this thread, as well as the ECU direct controlled boost thread and so far so good! I made a couple runs on my way into work this morning and so far everything seems to be working. Peak boost hit 15.3 PSI, load just under 200.
A question I had was why the ECU didn't get closer to my target boost level? For a starting baseline boost table, I used Mr. Fred's table. Will the Boost Error Correction table really make up that difference or are my WGDC values too conservative? If it makes a difference, both restrictor pills have been removed from my boost lines.
A question I had was why the ECU didn't get closer to my target boost level? For a starting baseline boost table, I used Mr. Fred's table. Will the Boost Error Correction table really make up that difference or are my WGDC values too conservative? If it makes a difference, both restrictor pills have been removed from my boost lines.
#18
Evolved Member
iTrader: (1)
Hey MrFred, I found that the settings for the "Airflow/Hz Raw Scaling" table were the cause for my lean conditions. I've had these values set this way for about two years and have never had a problem, so I just set them back to the factory settings. Thanks for your help!
#22
Evolved Member
iTrader: (28)
P0069 with Omni
Hey guys, any idea why I'm not throwing the P0069 code with the Omni? Here are my settings. Some of the exact values wouldn't go in so do you have to edit the formulas to get them exact? For instance the MAP output would round values vs what mrfred said to enter in the fields, is that ok?
Thanks
Thanks
#24
Evolved Member
iTrader: (1)
Hey guys, any idea why I'm not throwing the P0069 code with the Omni? Here are my settings. Some of the exact values wouldn't go in so do you have to edit the formulas to get them exact? For instance the MAP output would round values vs what mrfred said to enter in the fields, is that ok?
Thanks
Thanks
BTW: I noticed you don't have the definition for "EGR pressure diff":
<table name="EGR Pressure Diff" category="MAPSensor" address="1b68" type="1D" level="1" scaling="Volts16"/>
This should be set to .04.
Last edited by D-VO; Sep 12, 2009 at 09:56 AM.
#25
Hey blue, I had the same quirk with the 96940011. It ran well without the settings being spot on.
BTW: I noticed you don't have the definition for "EGR pressure diff":
<table name="EGR Pressure Diff" category="MAPSensor" address="1b68" type="1D" level="1" scaling="Volts16"/>
This should be set to .04.
BTW: I noticed you don't have the definition for "EGR pressure diff":
<table name="EGR Pressure Diff" category="MAPSensor" address="1b68" type="1D" level="1" scaling="Volts16"/>
This should be set to .04.
#26
Evolved Member
iTrader: (10)
When changing the FCA2 bits per instructions, how necessary is it to have that exact hex bit? Just wondering because it enables one of the p0300 tests/checks/codes. Is it OK to disable the one p0300 that gets enabled when running this map sensor? IE, bit 4 of FCA2.
Last edited by lan_evo_mr9; Sep 12, 2009 at 11:57 AM.
#29
Hey guys, any idea why I'm not throwing the P0069 code with the Omni? Here are my settings. Some of the exact values wouldn't go in so do you have to edit the formulas to get them exact? For instance the MAP output would round values vs what mrfred said to enter in the fields, is that ok?
...
Thanks
...
Thanks