Problems AEM UEGO via Serial Cable (Evoscan)
Problems AEM UEGO via Serial Cable (Evoscan)
I'm still pretty new to this, so please bear with me. After fussing around with every aspect of this thing for the past 4-5 hours, I'm just about at my wits' end. I just installed an AEM UEGO wideband O2 sensor and gauge, and soldered up a serial connector from the serial output of the gauge. This should allow me to log AFR's on Evoscan with a serial to USB converter. When I try to do so, however, all I get is a reading of 0, and a message at the bottom of Evoscan Reading AEM Error: Port Closed. I selected the AEM UEGO 9600 in Evoscan's dropdown, and also selected ComPort 3 (which is the same ComPort the cable is configured as under the windows 7 device manager).
I grabbed a multimeter and checked the DC coming out of pin 2, getting about 2.5v at idle. So I know I soldered the connections correctly.
I opened the link in Hyperterminal, and was able to log the AFR's that way. Likewise, I was able to use the AEM Log feature on Mitsulogger to pull up the AFR's on my computer. So I know the cable is making a connection with my Laptop. I assume this also rules out my problem being a driver issue (correct me if I'm wrong).
I tried installing old versions of Evoscan, with no luck. So far I've tried 2.9, 2.8, and 2.7. I found a similar thread on here where a guy said he unticked a box in the device manager labeled "enable FIFO buffers," but I was unable to find that box in my device manager. So, I went into my registry and changed the value of "ForceFifoEnable" from 1 to 0; still no luck. Any idea where to go from here?
EDIT: Also, I forgot to add that if I change the request field for external wideband in Evoscan from "WDB" to anything else, it gets rid of the error, but I just get random readings. I'm not really familiar enough with Evoscan yet to know if this is significant.
I grabbed a multimeter and checked the DC coming out of pin 2, getting about 2.5v at idle. So I know I soldered the connections correctly.
I opened the link in Hyperterminal, and was able to log the AFR's that way. Likewise, I was able to use the AEM Log feature on Mitsulogger to pull up the AFR's on my computer. So I know the cable is making a connection with my Laptop. I assume this also rules out my problem being a driver issue (correct me if I'm wrong).
I tried installing old versions of Evoscan, with no luck. So far I've tried 2.9, 2.8, and 2.7. I found a similar thread on here where a guy said he unticked a box in the device manager labeled "enable FIFO buffers," but I was unable to find that box in my device manager. So, I went into my registry and changed the value of "ForceFifoEnable" from 1 to 0; still no luck. Any idea where to go from here?
EDIT: Also, I forgot to add that if I change the request field for external wideband in Evoscan from "WDB" to anything else, it gets rid of the error, but I just get random readings. I'm not really familiar enough with Evoscan yet to know if this is significant.
Last edited by ehall20; Apr 2, 2014 at 01:58 AM.
Are you checking the com port setting of the AFR cable when the flash cable is also plugged in? I would ensure they are both plugged in and check the com port at that point in time and then set ECUFlash to be the port that you see at that point in time.
Throughout all this, I've only had the serial to USB cable plugged in. I left the Tactrix cable disconnected so I wouldn't have one more variable to worry about.
Also, I'm currently using this serial to USB cable ( ). This is the AEM unit I'm using (http://www.streettunedmotorsports.com/parts/aem_uego.htm)
Also, I'm currently using this serial to USB cable ( ). This is the AEM unit I'm using (http://www.streettunedmotorsports.com/parts/aem_uego.htm)
In order for evoscan (at least version 2.7) to correctly log wdb you need to change decimal separator in windows regional settings. I don't remember which one is right, but if you have comma change it to dot and vice versa.
Maybe that wil help.
Maybe that wil help.
Thanks, I'll give that a shot today. Although it was working fine for logging when I had just the Tactrix cable plugged in (logged TPS, knock sum, etc. fine), so I'm inclined to say that's not the issue.
Problem solved! For anyone reading this thread in the future, the problem ended up being that I needed to plug the Tactrix cable in at the same time as the serial cable coming from my wideband. Thanks for the help.
Last edited by ehall20; Apr 4, 2014 at 08:14 AM.
I according to xPRimNT tutorial (http://www.evoxforums.com/forums/showthread.php?t=21747)
Use hyperterminal communications test everything is normal.
Check on EVOSCAN match COM.
But when use EVOSCAN record AFR to 0.
This is the reason why.
You can use images express the way you solve this problem? Thank you very much!
Trending Topics
That blue cable you are using sucks. I used one for a month and it died. I went to microcenter and bought a highend RS232(DB9) to usb adapter and if works like a charm now. Measure the voltage at the RS232 before the usb and see if its seeing voltage. If so its that cheap blue usb adapter you're using. It was my issue.
I'm showing the same error "AEM error: the port is closed". Now I have a 9-pin from best buy (not sure the series) wired to my gauge and have tried plugging them in at the same time with "4-1 USB adding thingy. I have the uego 9600 selected but also in that window is where my main problem is. The drop down Menu to select the serial comport leads nowhere, there are no options such as the comport 3, I'm truly hoping to get my tune done in the next week or 2 so please help thank you.
I'm showing the same error "AEM error: the port is closed". Now I have a 9-pin from best buy (not sure the series) wired to my gauge and have tried plugging them in at the same time with "4-1 USB adding thingy. I have the uego 9600 selected but also in that window is where my main problem is. The drop down Menu to select the serial comport leads nowhere, there are no options such as the comport 3, I'm truly hoping to get my tune done in the next week or 2 so please help thank you.
Make sure you installed the driver for the USB-Serial adapter they normally require one. You won't read anything without it. You can test with Hyper terminal as mentioned above. You can check to make sure it installed properly by going to Device manager and looking under Com ports. You should see something listed there.
Thread
Thread Starter
Forum
Replies
Last Post







