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

D-VO · Aug 17, 2009, 10:10 AM

I'm not sure if this will make a difference, but I'm also using one of the first versions of the Tephra mod that has no load definition for the NLTS.

Z_Lancer_Man · Aug 17, 2009, 10:36 AM

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.

D-VO · Aug 17, 2009, 09:05 PM

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!

Raceghost · Sep 8, 2009, 05:44 PM

MFRED,

I am wanting to switch to the Tephra V7 rom and it is utilizing the new 96530006 / 96530706 as the base rom. Do you have settings already included in the new V7 for this? What would you recommend for utilizing the new V7 Tephra Rom with a Omni 4 bar?

fixem2 · Sep 8, 2009, 10:09 PM

Z_lancer_man, use your WGDC to bring the boost up closer to your target then use the correction to minimize the swings.

Z_Lancer_Man · Sep 9, 2009, 08:50 AM

Quote:

Originally Posted by fixem2

Z_lancer_man, use your WGDC to bring the boost up closer to your target then use the correction to minimize the swings.

Good advice - thanks! I've been able to get closer to my boost curve, but now I'm maxing out my WGDC and still my boost tapers. I'm currently in boost leak detection mode

05blue8 · Sep 11, 2009, 07:29 AM

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

whitey4d · Sep 12, 2009, 09:13 AM

Im really new to patching even tho Ive been using ECUFlash for years. My question is why do the 05 and 06 ROMs have a MAP Scaling table when the 04 and 03s Dont?

D-VO · Sep 12, 2009, 10:53 AM

Quote:

Originally Posted by 05blue8

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

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.

mrfred · Sep 12, 2009, 11:25 AM

Quote:

Originally Posted by D-VO

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.

Its not needed because my instructions have them disable the EGR test.

lan_evo_mr9 · Sep 12, 2009, 12:48 PM

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.

mrfred · Sep 12, 2009, 01:25 PM

Quote:

Originally Posted by lan_evo_mr9

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.

EDIT: I had the old periphery hex tables in the instructions. I have now updated the instructions to use the periphery bit tables. Please have another look at the instructions.

mrfred · Sep 12, 2009, 01:34 PM

Quote:

Originally Posted by whitey4d

Im really new to patching even tho Ive been using ECUFlash for years. My question is why do the 05 and 06 ROMs have a MAP Scaling table when the 04 and 03s Dont?

Because there is no MAP scaling table in the '03 and '04 ROMs.

mrfred · Sep 12, 2009, 01:49 PM

Quote:

Originally Posted by 05blue8

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

You didn't apply the settings properly. Its my fault and have updated the instructions. Please review the updated instructions in the first post.

lan_evo_mr9 · Sep 12, 2009, 02:43 PM

Thanks for the clarifications.