doesn't matter.

 

Can somebody share the XML definitions for the MAP & scaling tables in ecuflash for 885900XX? The bug with evoM.net is messing with the code pasted in the OP and I need this information asap

 

It's not working, so use this, but you need to put a < in front of each line that has table in it.

Easiest thing to do is to go to the first page and hit quote and look in the reply to thread section and it will show the code.

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"/>

 

Thanks!! And thanks for the quote tip, that works perfectly

 

Has anyone had a Omni map go bad? if so what symptoms did you have?
Thanks

 

So I installed the omni 4 bar sensor tonight, set up the MAP scaling per this thread for the correct ROM ID, and took it for a test drive.

For some reason I'm now building boost slowly now. I used to peak at 250 load @3750rpm. and taper to about 220/225 at redline. Now I'm peaking at 225 load @ 5500rpm and it's tapering to 220 at redline.

If I assume that the scalings are correct and the evoscan output formula is correct (I triple checked these), I'm gradually increasing to a peak of 17psi at 5500 and tapering to 16 psi at redline.

Evoscan reports the WGDC is at 100% for the entire pull, suggesting to me that the ECU isn't actively trying to cut boost. What else could account for my crummy load curve? If I had a boost leak, I'd be running rich (I'm not: 11.1), right?


I can post logs tomorrow, just wondering if anyone had any ideas off the top of their head.

 

I was also in need of this and found something interesting to add. My firefox will not load the code when within the reply to section, but my IE did load the code. This is on Windows 10 if that makes any difference as well.

 

A little late but I just recently had a brand new Omni 4 bar unit go bad after a couple months. My AFRs were as rich as could be at like 10.0s and below when you were in the throttle. Even at idle it would hang around 12-13s. Thought the 91 map might have gotten switched to E85 by accident at first but that was definitely not the case.

 

Sorry for bringing the thread back from the dead! Can you please provide me with the "2004 USDM Evo 8 ROMs 94170014, 94170015" xml definition?? it dosn't show on my computer -.- thanks in advance!

 

cant you just grab a tephra map?

 

Bumping this back up. Did you buy another Omni 4 bar map sensor or did you replace it with a different one? If you used a different one, which one did you use?

 

Thanks to this thread everything went perfect. Someone also mentioned here when setting up Evoscan to add the formula but leave your local pressure out, do a log with the engine off and whatever it logs add that to the formula. Im amazed that my Prosport boost gauge was pretty damn accurate.

 

I bought another Omni 4 bar. There was apparently a bad batch of them recently where the pins on the connector would come lose and have no connection. Knew of at least 3 people at my tuners shop that purchased them at the same time and theirs also failed.

 

can some one tell me what the pinouts are for this sensor? ie pin 1 = 5V pin 2 = sig and pin 3 = ground? I drive evo 5 JDM on Evo 8 ECU 96530706 ROM need to wire mine up for boost log.

 

Pin 1 = ground
Pin 2 = signal
Pin 3 = Vcc 5V