New WW IX MR
Yeah I would definitely keep the height where it is for now and see how the car handles. It certainly isnt slammed and you're not really DDing the car so I'd say leave well enough alone.
As for your codes hopefully they were a fluke and will never appear again. I hate electrical issues, its always something stupid. If you did indeed have an issue with your TPS and MAP sensor, I'd imagine the car would idle funky. What does it read in evoscan? IIRC mine says I think 12.9%
As for the wideband are you only having issues logging it? Does it show the correct values from the gauge face? If so I'd venture a guess that its an issue with the formula in evoscan. Have you updated the software recently by chance?
As for your codes hopefully they were a fluke and will never appear again. I hate electrical issues, its always something stupid. If you did indeed have an issue with your TPS and MAP sensor, I'd imagine the car would idle funky. What does it read in evoscan? IIRC mine says I think 12.9%
As for the wideband are you only having issues logging it? Does it show the correct values from the gauge face? If so I'd venture a guess that its an issue with the formula in evoscan. Have you updated the software recently by chance?
Yeah I would definitely keep the height where it is for now and see how the car handles. It certainly isnt slammed and you're not really DDing the car so I'd say leave well enough alone.
As for your codes hopefully they were a fluke and will never appear again. I hate electrical issues, its always something stupid. If you did indeed have an issue with your TPS and MAP sensor, I'd imagine the car would idle funky. What does it read in evoscan? IIRC mine says I think 12.9%
As for the wideband are you only having issues logging it? Does it show the correct values from the gauge face? If so I'd venture a guess that its an issue with the formula in evoscan. Have you updated the software recently by chance?
As for your codes hopefully they were a fluke and will never appear again. I hate electrical issues, its always something stupid. If you did indeed have an issue with your TPS and MAP sensor, I'd imagine the car would idle funky. What does it read in evoscan? IIRC mine says I think 12.9%
As for the wideband are you only having issues logging it? Does it show the correct values from the gauge face? If so I'd venture a guess that its an issue with the formula in evoscan. Have you updated the software recently by chance?
Yeah it shows the correct values from the gauge, etc. It's only when in evoscan that it doesn't show up right - formula was modified for the autometer back in 2009 or something and unchanged since then - and even so, it should still be fluctuating etc., just the wrong number coming out right? right now it just stays pretty much stagnant at 10.xxx in evoscan - no other changes outside of this wideband moving from one car to another. just strange.. hopefully i figure it out sometime
Well if the formula is wrong it wouldnt necessarily have to fluctuate. What if the formula was something simple like *=10. The value would always be 10, right? Do you have it wired into the ecu or are you using a serial cable? Maybe you have an issue with a connection?
10.00+(16.00-10.00)*x/204
so basically it's getting an x reading of almost 0 almost all the time
i'll have to ask the shop how the wideband was wired in... i think that might be the key there
Yeah well that would obvi be a silly equation I was just stating that for sake of discussion. If you know the formula hasnt changed then it must be an electrical/ mechanical issue, rather than a coding error.
When you used to log it, would you only need to hook up one USB cable to your computer aka your tactrix cable or was there another cable? If it was only one cable then it must be wired into your ecu.
I've been meaning to wire my wideband into my ecu but keep putting that off. I have a serial cable that was made years ago and just have that sitting in my glovebox. I think if you have it wired into your ecu though there is some code that needs to be flashed into your evu or additional XML files that need to be added to your laptop. I know there is a thread on it in the Ecuflash section that explains everything. Since I have yet to do it though I dont remember exactly what it entails.
When you used to log it, would you only need to hook up one USB cable to your computer aka your tactrix cable or was there another cable? If it was only one cable then it must be wired into your ecu.
I've been meaning to wire my wideband into my ecu but keep putting that off. I have a serial cable that was made years ago and just have that sitting in my glovebox. I think if you have it wired into your ecu though there is some code that needs to be flashed into your evu or additional XML files that need to be added to your laptop. I know there is a thread on it in the Ecuflash section that explains everything. Since I have yet to do it though I dont remember exactly what it entails.
Yeah well that would obvi be a silly equation I was just stating that for sake of discussion. If you know the formula hasnt changed then it must be an electrical/ mechanical issue, rather than a coding error.
When you used to log it, would you only need to hook up one USB cable to your computer aka your tactrix cable or was there another cable? If it was only one cable then it must be wired into your ecu.
I've been meaning to wire my wideband into my ecu but keep putting that off. I have a serial cable that was made years ago and just have that sitting in my glovebox. I think if you have it wired into your ecu though there is some code that needs to be flashed into your evu or additional XML files that need to be added to your laptop. I know there is a thread on it in the Ecuflash section that explains everything. Since I have yet to do it though I dont remember exactly what it entails.
When you used to log it, would you only need to hook up one USB cable to your computer aka your tactrix cable or was there another cable? If it was only one cable then it must be wired into your ecu.
I've been meaning to wire my wideband into my ecu but keep putting that off. I have a serial cable that was made years ago and just have that sitting in my glovebox. I think if you have it wired into your ecu though there is some code that needs to be flashed into your evu or additional XML files that need to be added to your laptop. I know there is a thread on it in the Ecuflash section that explains everything. Since I have yet to do it though I dont remember exactly what it entails.
Taking a closer look at this (and checking in the garage) I think the ride height on the passenger side is actually a good bit higher than on the driver's side... def will need to get this corner balanced or something
Last edited by kyoo; May 9, 2013 at 08:30 AM.
Anyway, the only issues for my car as it stands now are:
- P0069 Code keeps returning - this is the MAP sensor code. I've got an omni4 bar on the car that ran perfectly on my previous evo, so not sure what is causing the issue
- The O2 sensor needs to be wired to the ECU (not sure why it wasn't done in the first place), and the gauge position redone on the steering column
- Whiteline steering rack bushings installed
- There was a picture above of the exhaust that looks like the frame rail is dented - however, I went under the car the other day when I was doing the coilover protection, and it looks like those frame rails are shaped that way, not dented.
- P0069 Code keeps returning - this is the MAP sensor code. I've got an omni4 bar on the car that ran perfectly on my previous evo, so not sure what is causing the issue
- The O2 sensor needs to be wired to the ECU (not sure why it wasn't done in the first place), and the gauge position redone on the steering column
- Whiteline steering rack bushings installed
- There was a picture above of the exhaust that looks like the frame rail is dented - however, I went under the car the other day when I was doing the coilover protection, and it looks like those frame rails are shaped that way, not dented.