Seems like alot of people have trouble trying to get the UEGO to work with Evoscan... I don't think it is the program's fault

 

I have the uego with evoscan 2.5. It works fine. What I have read though, is that people are having trouble with 2.6. Some of those people downgrade to 2.5 and everything works fine. There is a perfect example of this situation a couple posts above mine.

There are a number of people who can't get it to work at all and you can contribute that to possibly installer error.

 

i had the same issue with 2.6, installed the latest 2.7b4 and everything seems to be logging just fine now.

 

The fix is = download the newest version of evoscan, and then download the beta2.7 version. That will fix all AEM WB issues.

 

^^^worked for me.

i was previously running 2.5 to log with the AEM

 

How do I download the Beta version? Do you have a link?

Also, can someone tell my how to test my recently wired AEM Uego. I'm brand new to Evoscan. I believe I have the correct com port selected, but when I select the external AFR setting, nothing seems to register (no change in that reading/s).

 

How are you trying to log your AFRs? Are you logging through the D-sub, serial connector or did you replace your O2 sensor with this and wired it up through your ECU?

 

Used a DB9 serial cable (brown wire for signal, yellow wire for ground - checked with a Volt Meter). These connected directly to the AEM Ueog as per the many threads with instructions (blue wire from wideband providing the signal). Did the wideband config in Evoscan - believe I have the correct COM port selected - also selected "AEM Uego" from the available choices. With the DataLogger ON, I checked on "External AFR" and was expected to see changes in the readings for the row - did not see anything. Had the car idling - revved it a few times - values remained zero. Am I going about the right way to see if the wideband connection/readings work?

 

What COM port are you logging from on your PC? And are you using an USB-Serial adapter cable or plugging it straight into a serial port on your older laptop? I believe EVOScan can only log from COM ports 1 - 4. You can check/set the COM port in the Device manager.

Another check to make sure at least the Wideband is communicating properly is to open Hyper Terminal and see if you see the outputs. If not, then the problem is outside of EVOScan. Check the installation instructions of the UEGO for how to use it in Hyper Terminal.

 

I have currently hooked to COM4 via a USB-Serial adapter cable.

I just checked the manual and explains how to use Hyperterminal to check the data stream. Thanks Lancer_Man, let me check that when I get home (Evo it's my wife's DD).

 

Good luck! And my wife wishes my EVO were her DD

 

How do you get 2.7?

 

The Hyperterminal thing worked great. Got perfect wideband readings from COM6. Assigned that port in Evoscan2.6 (wideband settings) and it seemed to work for a second or so and then the readings froze. Log map showed the same thing - got AFR readings for sec and then it froze at that number.

Uninstalled version 2.6 and installed 2.5 - will check again tonight.

 

The 2.7beta version download is located in the "Evoscan/GPS review" thread, page 65, post 968.

 

Yup 2.6 had the issues stated however it was quickly spotted and the following betas had a new code written by Hamish and since then the UEGO has been logging fine. So download the beta 2.7 and you should be set.