Notices
ECU Flash

Evoscan and UEGO problem

Thread Tools
 
Search this Thread
 
Old May 11, 2008, 01:05 PM
  #1  
Newbie
Thread Starter
 
Flump's Avatar
 
Join Date: Apr 2008
Location: Centerville, OH
Posts: 11
Likes: 0
Received 0 Likes on 0 Posts
Evoscan and UEGO problem

I just installed the UEGO and bought the evoscan software. The software logs fine, and I made the serial connection and bought a USB to serial converter.

I tested the UEGO connection in the hyperterminal, and it works just fine. Evoscan will not read the UEGO. The device manager informs me that it is using comport 11. This isn't even an option in evoscan.

I have read that v2.2 (what i downloaded) doesn't have wideband support or something from some of the posts, and it has been suggested to just get v2.0. How do I do this? The only thing I can find on his site is where I registered to download this. I can't even figure out how to redownload v2.2 if I needed to do so.

What should I do?
Old May 11, 2008, 01:29 PM
  #2  
Evolved Member
iTrader: (4)
 
3gturbo's Avatar
 
Join Date: Dec 2005
Location: Charlotte
Posts: 571
Received 8 Likes on 8 Posts
For some reason he decided it was a good idea to remove wideband support completely from the evoscan 2.2 just download 2.1 good luck with fixing all the errors in the .xml
Old May 11, 2008, 03:30 PM
  #3  
Evolved Member
iTrader: (16)
 
RedLanEVO's Avatar
 
Join Date: Apr 2006
Location: Twin Cities, MN
Posts: 888
Likes: 0
Received 0 Likes on 0 Posts
hmm wierd. whenever i start logging with the aem using evoscan, it makes my car RPMS jump and hold at 3k. i've tried it 5-6 times it does the same thing. maybe its that 2.2 version?
Old May 11, 2008, 04:40 PM
  #4  
Newbie
Thread Starter
 
Flump's Avatar
 
Join Date: Apr 2008
Location: Centerville, OH
Posts: 11
Likes: 0
Received 0 Likes on 0 Posts
Well I found out how to download evoscan v2.0, but I still cannot log the UEGO. I'm pretty sure the problem is that when I check which com port the UEGO is in the device manager it says its com11. The only options in evoscan are coms 1-4. Is there any way to change which com port it uses?
Old May 11, 2008, 05:42 PM
  #5  
Newbie
Thread Starter
 
Flump's Avatar
 
Join Date: Apr 2008
Location: Centerville, OH
Posts: 11
Likes: 0
Received 0 Likes on 0 Posts
Originally Posted by RedLanEVO
hmm wierd. whenever i start logging with the aem using evoscan, it makes my car RPMS jump and hold at 3k. i've tried it 5-6 times it does the same thing. maybe its that 2.2 version?

I just tried the v2.0 with the car running and it did this exact same thing with my car. I wasn't even trying to log the wideband this time. Does this program ever work?
Old May 11, 2008, 07:28 PM
  #6  
Newbie
Thread Starter
 
Flump's Avatar
 
Join Date: Apr 2008
Location: Centerville, OH
Posts: 11
Likes: 0
Received 0 Likes on 0 Posts
Alright, here's a list of things i've done to troubleshoot the problem which has not been solved.

1. Checked connection in hyperterminal. Everything is good. I'm getting data from the UEGO

2. DL'd EvoScan v2.0 because of the supposed issues with wideband support. I had the problem where when i tried to connect to the car the idle went to 2.5k or so.

3. Uninstalled and reinstalled the drivers for both the serial/usb cable and the tactrix cable. This got rid of the idle problem with the connection. Rechecked the connection in hyperterminal and everything was fine.

4. Tried evoscan v2.0 with UEGO still does not work.

In hyperterminal its COM11 that the uego is recognized on as well as in the device manager. When I plug it into the usb port while evoscan is running (not connected to car) com1 is an option. I choose this and start the log. I then check the external WB, and it immediately stops the log. I officially have no idea what to do now.
Old May 11, 2008, 08:27 PM
  #7  
Evolved Member
iTrader: (38)
 
recompile's Avatar
 
Join Date: Nov 2006
Location: New Hampshire, USA
Posts: 1,745
Likes: 0
Received 8 Likes on 5 Posts
Yet another reason EvoScan v0.99 is the best
Old May 12, 2008, 06:16 AM
  #8  
Newbie
Thread Starter
 
Flump's Avatar
 
Join Date: Apr 2008
Location: Centerville, OH
Posts: 11
Likes: 0
Received 0 Likes on 0 Posts
Originally Posted by Shameless Tuning
Yet another reason EvoScan v0.99 is the best

I just downloaded this, and so I'm gonna see what happens tonight after work. Sorry for posting so much, but I just wanted to keep this updated as I moved along so someone with similar problems can find almost all the answers in one place.

O, and there is a thread titled Where can i download evoscan v2.1 for anyone looking to download an older version because their newer one will not work with their wideband.
Old May 12, 2008, 03:35 PM
  #9  
Newbie
Thread Starter
 
Flump's Avatar
 
Join Date: Apr 2008
Location: Centerville, OH
Posts: 11
Likes: 0
Received 0 Likes on 0 Posts
I finally got the damn thing working. V2.2 DOES NOT support the AEM UEGO...at least the one I got. I'm sure some people know this, but I know for sure now. V2.0 works just fine.

I was having a problem with my computer assigning the serial to usb device to com port 11. The problem here is that evoscan v2.0 can only read com ports 1-4. v0.99 can only read up to com9 so i still had a problem.

Here is how you CHANGE THE PORT for XP users.

Go to:
1) control panel
2) system
3) hardware tab
4) click on device manager
5) click on ports
6) right click on the port that is the usb serial device
7) Go to properties
8) Go to details tab
9) Click advanced
10) There will be a drop down list and you can pick the com port here. (Choose 1-4)

This ended up being my problem. That and the fact that v2.2 doesn't support the uego.

Finally I get to tune my car. Hopefully someone finds this helpful.
Old Jun 4, 2008, 09:30 PM
  #10  
Newbie
 
dawnduran's Avatar
 
Join Date: Jan 2007
Location: Germany
Posts: 88
Likes: 0
Received 0 Likes on 0 Posts
Sorry for hijacking this thread...

My AEM UEGO in every Evoscan version shows the O2-Data *10.
For example at 14,7 at my UEGO, Evoscan shows 147.

I did change the evoscanformula to "x/10", but nothing changed.
Any ideas?
Old Jun 5, 2008, 10:58 AM
  #11  
Evolved Member
 
EvoBroMA's Avatar
 
Join Date: Feb 2006
Location: MA
Posts: 1,345
Likes: 0
Received 1 Like on 1 Post
Originally Posted by dawnduran
Sorry for hijacking this thread...

My AEM UEGO in every Evoscan version shows the O2-Data *10.
For example at 14,7 at my UEGO, Evoscan shows 147.

I did change the evoscanformula to "x/10", but nothing changed.
Any ideas?
can you try "x/10.0"
Old Jun 17, 2008, 12:15 PM
  #12  
Newbie
 
dawnduran's Avatar
 
Join Date: Jan 2007
Location: Germany
Posts: 88
Likes: 0
Received 0 Likes on 0 Posts
Originally Posted by dexmix
can you try "x/10.0"
I tried it, but it doesn't work.
Still AFR * 10.
Old Jun 17, 2008, 12:17 PM
  #13  
Evolved Member
iTrader: (2)
 
TouringBubble's Avatar
 
Join Date: Jul 2006
Location: Chelsea, AL
Posts: 2,639
Likes: 0
Received 3 Likes on 3 Posts
Try "x*0.1" maybe?
Old Jun 17, 2008, 12:19 PM
  #14  
Evolved Member
iTrader: (25)
 
sabastian458's Avatar
 
Join Date: Feb 2005
Location: Upstate, SC
Posts: 1,607
Likes: 0
Received 0 Likes on 0 Posts
you need to change the com port for the USB adapter on the device manager of window to com 3 or 4. I had the same issue at 1 time.
Old Jun 17, 2008, 01:06 PM
  #15  
Evolved Member
iTrader: (5)
 
Mr. Evo IX's Avatar
 
Join Date: Nov 2005
Location: Plano, TX
Posts: 1,910
Received 1 Like on 1 Post
Check the selector switch on the back of the Uego, it may have moved from P00 AFR. Mine used to flip over to Lambda and read 1.0 at 14.7. I use COM6 for my Uego.

I'm running EvoScan 2.1 and previously .99.

Last edited by Mr. Evo IX; Jun 17, 2008 at 01:28 PM.




All times are GMT -7. The time now is 04:39 PM.