Omni 4 bar values not chaning - EvolutionM - Mitsubishi Lancer and Lancer Evolution Community



Omni 4 bar values not chaning

Reply
 
 
 
Thread Tools Search this Thread
Old Nov 29, 2016, 04:15 PM   #1
Newbie
Thread Starter
 
mr.k's Avatar
 
Join Date: Dec 2015
Location: Chicago
Posts: 29
Thanks: 0
Thanked 0 Times in 0 Posts

Drives: 2005 SSL

Question Omni 4 bar values not changing

I've ran into a problem trying to log boost in evoscan. I added in the omni 4 bar sensor formula a little while back and it seemed that I got everything calibrated with atmospheric pressure. My formula is 0.2369*x-14.2 with the request ID of 38 and everything else set up as it should (according to the install writeup). Anyways, so the other day I open up excel to read some logs and notice that the value is stuck at -14.2 for boost. The only other thing I did was add in some xml. files to ecu flash in order to read my rom, which I cannot see effecting evoscan.
Has anyone ran into this problem before? Any solutions? I know the sensor isn't bad because the car still runs
I can post pics of what I have in evoscan if that would help.

Help a newbie out!

Last edited by mr.k; Nov 29, 2016 at 05:40 PM.
Offline
 
Reply With Quote
Old Nov 29, 2016, 04:50 PM   #2
Evolving Member
iTrader: (17)
 
Join Date: Nov 2014
Location: Honolulu, HI
Posts: 455
Thanked 26 Times in 26 Posts

Drives: 06 Evo IX MR SE and a Snowboard

If you followed all the instructions in the Omni 4 bar thread correctly there should be no reason you can't log boost pressure. Try going over everything once more just to be sure.
Offline
 
Reply With Quote
Old Nov 29, 2016, 05:10 PM   #3
Newbie
Thread Starter
 
mr.k's Avatar
 
Join Date: Dec 2015
Location: Chicago
Posts: 29
Thanks: 0
Thanked 0 Times in 0 Posts

Drives: 2005 SSL

Here is a screen cap of the entry, looks like I actually used 14.1 for the atmospheric pressure.




The ecu has been patched to support the omni 4 bar by the previous owner.
Only other thing I can think is that maybe the pin died/has no power on the OBD port for the Tactrix cable? since the "x" value would be reading 0 all the time, hence the -14 value all the time.
Offline
 
Reply With Quote
Old Nov 30, 2016, 12:02 PM   #4
Evolving Member
iTrader: (17)
 
Join Date: Nov 2014
Location: Honolulu, HI
Posts: 455
Thanked 26 Times in 26 Posts

Drives: 06 Evo IX MR SE and a Snowboard

Did you use an existing parameter in the list or did you make a new one? In your "EvoScan Edit Data Settings" list, try adding a new item and use the same settings you posted. See if that works. Everything in your screenshot looks good.
Offline
 
Reply With Quote
Old Nov 30, 2016, 12:38 PM   #5
Newbie
Thread Starter
 
mr.k's Avatar
 
Join Date: Dec 2015
Location: Chicago
Posts: 29
Thanks: 0
Thanked 0 Times in 0 Posts

Drives: 2005 SSL

Quote:
Originally Posted by Klaiceps View Post
Did you use an existing parameter in the list or did you make a new one? In your "EvoScan Edit Data Settings" list, try adding a new item and use the same settings you posted. See if that works. Everything in your screenshot looks good.
I believe I wrote over the exsisting MAP or JDM MAP sensor.. whatever one the write up said to do. I'll try to do that and keep you guys updated.
Offline
 
Reply With Quote
Old Dec 1, 2016, 08:59 AM   #6
Newbie
Thread Starter
 
mr.k's Avatar
 
Join Date: Dec 2015
Location: Chicago
Posts: 29
Thanks: 0
Thanked 0 Times in 0 Posts

Drives: 2005 SSL

Looks like it fixed itself! I re-wrote the new formula in and then both started to work again. Couldn't tell anyone why but I'm not complaining

Back to logging I go!
Offline
 
Reply With Quote
Old Dec 1, 2016, 11:19 AM   #7
Evolving Member
iTrader: (17)
 
Join Date: Nov 2014
Location: Honolulu, HI
Posts: 455
Thanked 26 Times in 26 Posts

Drives: 06 Evo IX MR SE and a Snowboard

Good to hear you got it figured out. Evos do some strange things sometimes.
Offline
 
Reply With Quote
Old May 16, 2017, 07:59 AM   #8
EvoM Super Moderator
iTrader: (41)
 
heel2toe's Avatar
 
Join Date: Jul 2007
Location: Massachusetts
Posts: 3,475
Thanks: 0
Thanked 23 Times in 22 Posts

Drives: 05 Evo SSL

Bumping this back up as I went to do some tuning last night and I couldn't get my OMNI to log. The equation is setup correct in Evoscan and I even tried adding it again like the OP to see if it changed anything and the value is stuck at -14.6.

Im wondering if my sensor has crapped out but at the same time Im not sure my car would be able to run without it?

I saw this thread so it makes me think mine might be subject to the same result but I question if thats plausible given the fact that other than not being able to log boost my car runs great.
https://www.evolutionm.net/forums/ec...-teardown.html
Offline
 
Reply With Quote
Old May 16, 2017, 08:44 AM   #9
Newbie
Thread Starter
 
mr.k's Avatar
 
Join Date: Dec 2015
Location: Chicago
Posts: 29
Thanks: 0
Thanked 0 Times in 0 Posts

Drives: 2005 SSL

heel2toe, my issue seemed to work itself out. I attribute it to an Evoscan issue though. Currently, I am running into an issue where everything "x" is being read as 0. I'll be going back to Evoscan 2.7 to see if everything is working right.

I would think that if the MAP sensor was failing, then we would have issues with the engine running correctly? I am no expert, but that is why I narrowed it down to Evoscan because the car is/was running fine. Correct me if I am wrong though.
Offline
 
Reply With Quote
Old May 16, 2017, 11:30 AM   #10
EvoM Super Moderator
iTrader: (41)
 
heel2toe's Avatar
 
Join Date: Jul 2007
Location: Massachusetts
Posts: 3,475
Thanks: 0
Thanked 23 Times in 22 Posts

Drives: 05 Evo SSL

Thanks for the feedback. I tried reinstalling Evoscan last night but that didnt change anything either. Everything else is logging fine; its just the MAP that doesnt want to play nicely.

I guess to help narrow it down I can try logging a buddies car to see if its a MAP sensor issue or a logging issue.

What is strange is that yours worked itself out. But electronics are sorta funky at times so it could be that they are prone to heat and work at times and other times not so much which is just early signs of failure. Who knows...was just hoping you figured out what it was that caused your issue other than it randomly starting to work again.
Offline
 
Reply With Quote
Old May 16, 2017, 02:09 PM   #11
Newbie
Thread Starter
 
mr.k's Avatar
 
Join Date: Dec 2015
Location: Chicago
Posts: 29
Thanks: 0
Thanked 0 Times in 0 Posts

Drives: 2005 SSL

Hah I wish I could help: I am still trying to figure out why my evoscan is not logging at all nothing has been working
Offline
 
Reply With Quote
 
 
Reply

Related Topics
Thread Thread Starter Forum Replies Last Post
HowTo: Logging Wideband AFR via Rear O2 ECU ADC Input (Logging AFR without serial) xPRimNT Evo X Engine Management / Tuning Forums 154 Feb 24, 2017 09:35 PM
Omni 4 bar MAP sensor ROM compatibility settings for USDM Evo 8/9 mrfred EcuFlash 258 Feb 19, 2017 11:23 AM
Omni 4bar readings Vs Boost guage readings. 4b11slayer EcuFlash 4 Sep 30, 2016 07:26 AM
Setting up Evoscan for SD mines5 EcuFlash 1 Aug 6, 2016 11:46 AM
JDM Evo 8 | EvoScan | Omni Power 4 Bar EvoIIIAj EcuFlash 10 Nov 14, 2013 12:59 PM


Tags
error, evoscan, fix, map, omni

Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are Off
Pingbacks are Off
Refbacks are Off



All times are GMT -7. The time now is 01:56 AM.


 
  • Ask a Question
    Get answers from community experts
What's your question?
Send