Notices
Evo General Discuss any generalized technical Evo related topics that may not fit into the other forums. Please do not post tech and rumor threads here.
Sponsored by: RavSpec - JDM Wheels Central

Problems with AEM UEGO with Serial Cable (Evoscan)

Thread Tools
 
Search this Thread
 
Old Apr 3, 2014 | 02:53 AM
  #1  
ehall20's Avatar
Thread Starter
Newbie
 
Joined: Oct 2013
Posts: 24
Likes: 0
From: Kansas City
Problems with AEM UEGO with Serial Cable (Evoscan)

Hey all, I originally posted this to the ECUFlash forum (https://www.evolutionm.net/forums/ec...e-evoscan.html), but didn't receive much response. Hoping someone on here can help me out:

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.
Reply
Old Apr 3, 2014 | 03:38 PM
  #2  
SW20Mike's Avatar
Evolving Member
Veteran: Air Force
iTrader: (6)
 
Joined: Jun 2006
Posts: 333
Likes: 13
From: AZ
I run Ver. 2.90023 and even I have this happen to my AEM wideband at times. What I do when I get the 0 reading, I change the SerialComPort and change around which USB I have the Wideband plugged into my laptop. It is annoying, but I find most of the time if I use the same USB port when using Evoscan, I don't get the 0 reading. Sorry I'm not much help, but I understand your frustration with this problem, happens to me at times.
Reply
Related Topics
Thread
Thread Starter
Forum
Replies
Last Post
UxC
Evo X Engine Management / Tuning Forums
2
Dec 19, 2016 08:43 AM
Dakota Evo
ECU Flash
10
Jul 25, 2016 05:15 PM
evo4mad
ECU Flash
1880
May 5, 2015 06:22 PM
erikm-x
Evo X Engine Management / Tuning Forums
2
Apr 20, 2014 12:29 AM
Eshark
ECU Flash
17
Aug 25, 2013 03:53 AM




All times are GMT -7. The time now is 05:33 PM.