Hb55047

I recently installed an omni 3 bar map sensor. The first time I tried logging it read 19psi but I realized my boost gauge was reading the same because my mbc was turned down. I turned it up to 23 and it was still only showing 19 in evoscan. I am running tephra v7 941715. I attached a screenshot of my rom settings for the map sensor. I have tried playing around with the formula in evoscan as well. My current formula is (0.17886*x)+ 0.161-y. With each formula I would adjust my local atmosphere pressure with the engine off until I get a reading of 0.0. The map reading seems pretty accurate, just that it wont go past 19psi. Any help would greatly be appreciated.

criptballer

iTrader: (3)

just did my omni 4 bar conversion and it all works fine for me. i'm still tuning my 4088r so i haven't gone past 15 psi. i just followed the tutorial found here though. wish i could help out more. maybe i'll run into the same problem

Raptord

iTrader: (10)

I'm using the same Evoscan formula so we know that atleast your formula is good. What MUT address is your OMNI logging from? Do you have a MAP scaling table? I have one but it doesn't seem like you do, may have something to do with that.

Hb55047

Thanks cript, good luck with your tuning. I hope you dont have the same problem.

Hi raptord I have been searching around the forums and it seems the 03 ecu doesnt have the scaling table. I actually got the formula from your thread but I was also getting the same results using the formula from the guide by mrfred. I am still learning my way around ecuflash. I can view the MUT table but how can I tell which address its using?

Raptord

iTrader: (10)

Open your copy of evoscan and check the "requestID" for your OMNI3Bar. That will tell you what address in the MUT table it is getting it's value from. After that check your MUT table to see which address it's logging.

For example, my requestID in evoscan is 38. So I go check my MUT table to see what value is at MUT38 and see that it is 6AED:



Once you know both your requestID and the MUT table address it corresponds to :

1- Confirm that the MUT table address is the correct one. Comparing with a stock rom will answer that question.

2- Confirm that the requestID is the same as the Boost (MDP) and JDMMAP entries in evoscan. Since evoscan isn't rom-specific, they should all be the same as mine (38).

If both of those things check out correctly, then I'm not really sure what the problem could be, sorry! Hopefully someone else will chime in with more advice.

Hb55047

Thanks for the info raptord. I tried to add the mut table entry to my stock rom' s xml but it didnt show up. I originally had my car tuned with the 96530706 rom before switching to my current rom so that the ics spray button wouldnt activate my evap solenoid. The MUT address is different in both for request 38. When I get a chance today I am going to try and switch it and test.

Hb55047

I tried changing the address, but it appeared it was for something other than the map sensor. It broke the formula and the reading I was getting wasnt changing with boost. I am starting to think maybe my sensor is defective.