Omni 4 bar values not chaning
#1
Newbie
Thread Starter
Join Date: Dec 2015
Location: Chicago
Posts: 34
Likes: 0
Received 0 Likes
on
0 Posts
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!
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.
#3
Newbie
Thread Starter
Join Date: Dec 2015
Location: Chicago
Posts: 34
Likes: 0
Received 0 Likes
on
0 Posts
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.
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.
#5
Newbie
Thread Starter
Join Date: Dec 2015
Location: Chicago
Posts: 34
Likes: 0
Received 0 Likes
on
0 Posts
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.
#6
Newbie
Thread Starter
Join Date: Dec 2015
Location: Chicago
Posts: 34
Likes: 0
Received 0 Likes
on
0 Posts
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!
Back to logging I go!
Trending Topics
#8
Evolved Member
iTrader: (41)
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
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
#9
Newbie
Thread Starter
Join Date: Dec 2015
Location: Chicago
Posts: 34
Likes: 0
Received 0 Likes
on
0 Posts
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.
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.
#10
Evolved Member
iTrader: (41)
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.
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.
Thread
Thread Starter
Forum
Replies
Last Post
johnnnyjeans
Cobb AccessPORT
3
Jun 4, 2012 09:30 AM