If you just splice in like that the ECU will be getting 2 seperate signals.

Just buy 3 pairs of bullet or spade connectors. Place male connector on wire 75 near ECU harness. Then place female connectors on wire to your wideband, and also on 75 wire going to rear 02 sensor.

 

Okay makes sense, I'll just do it that way. What I would like to know though is what power wire you guys used to power the UEGO?

I ask because my gauge was wired on the driver side and it was getting power from an unused fuse spot using a 5v fuse. I could keep it there and just run the blue wire out of the wire harness to the ECU.

 

I ran a 16awg wire directly to the battery with a 2.5A fuse holder. I run all my accessory wires through the factory grommet located behind the drivers fender (under the liner). Years like this with no issues.

 

Thank you very much. I did the spade connector suggestion and AFR seems to be logging correctly with the op's provided formula. I haven't logged using load yet but I will once I-15 clears up lol.

 

I'm running a 94170008 ECU, In order to complete step 7, can I just copy and paste the XML from TephraMod 94170715 for the Rear 02 tables and proceed that way or are the addresses going to be different?

Such as, can I just copy/paste this into my 94170008 ECU XML?
And then change the hex to 0x0009? and the enable to 0? Will this cause conflicts or do I need to modify the 94170008 XML more to use this part of Tephra?

 

I've used this post and the same formula. When my car is at idle my gauge is displaying 14.7 log with evo scan it logs in the 9's. When I give the car a bit of throttle the evoscan scaling is way off. Now I have seen people mention changing the setting on the gauge, removing the heater CEL patch, and changing the value of "9" to something else because "all cars are different". Which one is it?

 

So, I run just the value 'x' in evoscan and it ranges between 8 and 16. It is responsive to throttle but it's just too big of a swing, of course. So I suck at math but I started trying little calculations. I ended up with (I know it's wrong so somebody who is math-smart fix please) 0.5*x+8.75. It wasn't that far off but yes it was off. This was done logging 3C and not MUT 12. When I tried for MUT 12 all kinds of craziness happened.

The calculation 0.0397*x+10 or whatever is way far off in EvoScan 2.9 for the Evo 9.

I did use the complete delete patch https://www.evolutionm.net/forums/ec...8590015-a.html

Again, I hope this isn't screwing stuff up. There has to be somebody who has EvoScan 2.9, an Evo 9, and good logs.

 

I performed this mod and every signal I'm getting is around 9.3. Any ideas?

 

If you are using the AEM UEGO Wideband 02 (digital) make sure that you select it in the Wideband drop down menu and then select the COM port at the top of the same menu. This fixed my logging the constant 9 or 10 and it is accurate but I am still getting sudden drops down to 11 for like a second. It's weird.

 

I was actually just looking at that dropdown today wondering if I should change it .

I'll go change it and see what it does!

 

Still reads 9s. I'm assuming that the x value is reading as 0. Does anyone know why this would be? It's all plugged in correct. Do I use the white wire as it comes out of the gauge or off of the sensor? My car is untuned because of this..

 

Did you try just 'x' first? If you did that I did not get any values then I would have to ask what entry you edited in EvoScan. I used WB02 with Request ID 3c. I also put in just plain old 'x' to see if there was data and there was. I knew this wasn't the narrowband because I had deleted it with a patch. I got crazy flux values that seemed to change with throttle positions. I then tossed on the equation and got all 9s just like you did. Then I went and checked out the COM ports.

Try this, go and fire up EvoScan and don't plug in the flash cable just yet. Select the last UEGO entry (usb/wifi....) and then check and see what COM ports you see there without the cable plugged into the laptop. Then plug that badboy in and see what COM appears. That should be the one you select. Then give it a shot.

 

It won't let me select a COM port, as my remote is from 3C as entered in the "Data Items" section. I have the code entered on the first page.

 

If you cannot select a COM port on your computer then something is wrong with your USB ports or your computer did not properly load the driver for your flash cable. You have to have COM ports available or your flash cable would not work at all.

 

My UEGO is wired into the ECU, not into a USB. My flash cable flashes and works perfectly. I don't have to select a com port because the flash cable is the only thing running into my computer.