I'm having problems getting my UEGO to work, and was wondering if anyone had ideas. First off, this is the AEM Inline UEGO, so no gauge is connected, it's just the standalone module.

I initially followed the install guide on EvoX forums. Basically I removed my secondary O2 sensor completely, flashed the ECU to disable it and P0139 and P0140, and then wired things as shown in the diagram below:



Note: The "green wire" below to my Serial to USB converter is the "SRX" line. The device itself is from here, recommended by another member on the board: http://www.acroname.com/robotics/par...SB-SERIAL.html

The Serial to USB device has LEDs for any transmit and receive activity, and I see nothing for receive data (even tried swapping the lines, i.e. TX and RX lines ot make sure I had not confused them). The receive LED does not light up at all. So this makes me think the AEM Inline UEGO is not sending any data at all!

I also tried logging the Wideband O2 data using my Tactrix standalone logger setup, which works fine otherwise. I got "0" values for what I thought was the address of the Secondary O2 sensor in the ECU with the following setup in my logcfg.txt:

I decided to try and simplify things and I cut the connection to both the "Brown" and "White" AEM UEGO wires. I still had no activity coming off of the RS232 ("gray wire") of the AEM Inline UEGO. I connect with Hyperterminal in Windows XP, and it connects to the correct COM port, and confirms it is connected, but I see nothing. And again, the receive LED on the Serial-to-USB controller never lights up to show it is receiving any data from the AEM Inline UEGO.

One thing I noted was that when I turn the car to ON, the AEM Inline UEGO controller only flashes the "Ready" light multiple times and then goes solid. The "Status" light never lights up or does anything. Not sure what this means, but the AEM installation manual indicates that the "Status" light should also flash during sensor warmup, but it definitely never does anything.

Oh, and in terms of power - I wired the 12V power for the AEM Inline UEGO to my cigarette lighter fuse using a 15A Expand-a-fuse. The Black ground wire is simply connected to a chassis bolt that is up in the area of the drivers side fuse box. The Expand-a-fuse I use also powers my auto-dimming mirror. I thought maybe this was causing an issue so I unplugged the auto-dimming mirror, and still same results as above - no data over the RS-232 of the AEM Inline UEGO.

So I am out of ideas...and frustrated. The only thing I can think at this point is that the AEM Inline UEGO is broken, and needs to be exchanged. I say this based on the fact that AEM's manual says both the Status and Ready lights should blink during sensor warmup, but only the Ready light blinks ever. So maybe the sensor is broken and not sending any data?

Ideas, thoughts, help?? I'm all out of anything I can think of even trying.

 

Are you only checking on your serial connection? I would take a look at the settings for the virtual com-port and make sure they are correct as well as check to make sure it is streaming data to hyperterminal (the instructions should walk you through this).

What usb->serial adapter are you using? Some of the cheaper ones won't work for some devices. The UEGO is pretty easy on comms, but this could also be a problem.

 

I just hooked up my uego today after months of head-banging misery. I ended up giving up on the serial cable idea and spliced into the rear o2 sensor (on my 9 MR) and it wasn't working because I connected the blue data wire from the guage to the sensor. The white wire off the sensor is the analog 0-5v output! I wired the white wire up and it's been logging beautifully all day through the tactrix on evoscan. I don't know if this is an option for you, but there is a specific how to to do it.
Hope that helps, I didn't read your whole post.

 

Thanks for the fast responses guys!

One clarification just so everyone is aware; this is the unit I have: http://www.aemelectronics.com/wideba...u6nfb1ef90aus6 (the standalone Wideband controller with sensor, as pictured there.)

Here is a screenshot from the manual of what each wire does. My understanding of the below is that I wire the "grey" AEM wire in to my Serial-to-USB controller's RX line; I also wire the "white" AEM UEGO line in to my Secondary O2 sensor wire that runs to the cars ECU to allow Tactrix standalone logging. Am I missing something here??



I had both white and grey wires connected as I describe above. The Serial-to-USB has little LEDs to indicate if any data is being received (whether valid, invalid, doesn't matter - any data, period), and it showed nothing coming from the AEM Uego controller. I confirmed I could send data out of the Serial-to-USB (the TX line) by simply typing and I saw the "green" LED for the TX line light up as I typed characters. So the PC was communicating with the device.

As for what serial-to-USB converter, see the link above in my original post. I put it there, and another guy had said he used the same on his X, so that is why I bought it. I ordered some additional ones just in case that is the culprit.

Also - I confirmed my Tactrix standalone logger was not logging any data via the "white" wire that outputs to the secondary O2 sensor. Unless I have the address wrong? See my original post for the setup I was using.

Any ideas? I'm tempted to just order another UEGO and see if I still have problems...

 

First, I would investigate why that status light is not doing what it is supposed to. Are you sure the sensor is connected to the unit?

Isn't the wire on the rear O2 harness yellow and green? Are you sure you got the right one?

It seems you have eliminated alot of options for the problem if that status light isn't the issue.... there is no data/(possibly no voltage) coming over your lines. I'd test the white wire with a multimeter while the car is running. If you have a fast enough multimeter you can also test the serial transmission line.

Then verify that you are connected to the right pin on serial and correct wire for rear 02.

 

Okay, updates galore!

1.) Got it logging via Tactrix standalone logger; I made a dumb error. My log is attached below with a picture of my readings while driving inbound I94 today in Chicago. How do the readings look?

2.) Serial data now comes in. Hyperterminal sucks. I used two other programs and I get data, but it is all jibberish! I had the setting for the serial port at 19200, 8-N-1, and it looks like all junk characters. The AEM Serial monitor also gives a status of "Packet size too big/small." I posted over at the AEM forums asking "WTF" basically :-)

XLS link: http://www.yourpicturehost.com/afr.xls