Notices
ECU Flash

Problems logging with Evoscan

Thread Tools
 
Search this Thread
 
Old Aug 23, 2009 | 02:39 PM
  #1  
cableguy5752's Avatar
Thread Starter
Evolving Member
iTrader: (5)
 
Joined: Mar 2006
Posts: 216
Likes: 0
From: Rockford, IL
Problems logging with Evoscan

My old laptop completely crashed. I was using Evoscan .99 I think. Never had any problems with it.

I bought a new laptop and bought the new 2.6 beta 19 version. It won't connect. It gets to the "link engaged" and immediately disconnects with a error: can't connect to com port 1.

So I downloaded version 2.5 and get the same thing. I also downloaded Mitsulogger v1.6 beta 3 and that seems to work fine. I'd rather use Evoscan as I'm more comfortable with it.

Any help as to why I'm getting this error would be appreciated. Thanks
Reply
Old Aug 23, 2009 | 06:57 PM
  #2  
chmodlf's Avatar
Evolved Member
iTrader: (19)
 
Joined: Oct 2004
Posts: 885
Likes: 0
From: CT
I'm having problems too with a new netbook.
Reply
Old Aug 23, 2009 | 09:39 PM
  #3  
oldevodude's Avatar
Evolved Member
iTrader: (3)
 
Joined: Feb 2007
Posts: 579
Likes: 0
what OS and what usb to serial converter?
Reply
Old Aug 23, 2009 | 10:05 PM
  #4  
biggie5252's Avatar
Evolved Member
iTrader: (47)
 
Joined: Apr 2007
Posts: 1,320
Likes: 2
From: Kansas City
Are you trying to log an external wideband? The only time I get that error is when my laptop changes the comport on my wideband from whatever it used the last time it was hooked up. Evoscan tries to use the old comport. Basically I have to select the comport everytime I use evoscan (unless I plug the cable into the same usb port as last time).
Reply
Old Aug 24, 2009 | 11:13 AM
  #5  
cableguy5752's Avatar
Thread Starter
Evolving Member
iTrader: (5)
 
Joined: Mar 2006
Posts: 216
Likes: 0
From: Rockford, IL
Yes thats what I have too... a new HP netbook running XP. I'm using a radioshack usb to serial adapter. The drivers for it are up to date. My AEM wideband always logs on com port
4. It never changes. And i'm also using the 1.3 tactrix cable. It just keeps saying cannot connect to com port 1.
Reply
Old Aug 24, 2009 | 11:45 AM
  #6  
biggie5252's Avatar
Evolved Member
iTrader: (47)
 
Joined: Apr 2007
Posts: 1,320
Likes: 2
From: Kansas City
I use a 2 year old radio shack usb-serial converter. I've never had a problem with it? Have you checked to see that your computer is assigning comport 1 to the usb serial adapter?
Reply
Old Aug 25, 2009 | 02:30 PM
  #7  
Jimvr4's Avatar
Newbie
 
Joined: Apr 2009
Posts: 1
Likes: 0
From: San Jose, CA
I thought the 1.3 tactrix cable came with USB. If you need an external USB converter I believe it must use the FTDI chipset to work properly - not sure if the radioshack unit meets the requirements.
Reply
Old Aug 25, 2009 | 10:46 PM
  #8  
biggie5252's Avatar
Evolved Member
iTrader: (47)
 
Joined: Apr 2007
Posts: 1,320
Likes: 2
From: Kansas City
This is for the serial connection out of the Aem Uego. Not a tactrix cable.

FWIW, OP, I just upgraded to 2.6 and couldn't get my Uego to work either. It would connect, but wouldn't log the wideband. It would just pick a value and freeze. I had to go back to 2.5.
Reply
Old Aug 26, 2009 | 03:43 PM
  #9  
cableguy5752's Avatar
Thread Starter
Evolving Member
iTrader: (5)
 
Joined: Mar 2006
Posts: 216
Likes: 0
From: Rockford, IL
I can't even connect for 2 seconds on 2.5 or 2.6. Com port 4 is being used for the radio shack usb to serial adapter for the wideband. I don't know if the 1.3 tactrix is being used on port 1 or whats going on.
Reply
Old Aug 27, 2009 | 01:37 AM
  #10  
SoCal Rally's Avatar
Evolving Member
 
Joined: Feb 2008
Posts: 254
Likes: 1
From: SoCal
Originally Posted by biggie5252
This is for the serial connection out of the Aem Uego. Not a tactrix cable.

FWIW, OP, I just upgraded to 2.6 and couldn't get my Uego to work either. It would connect, but wouldn't log the wideband. It would just pick a value and freeze. I had to go back to 2.5.
There was an issue found with wideband logging from UEGO ... upgrade to v2.7 Beta2
Reply
Old Aug 27, 2009 | 01:43 AM
  #11  
SoCal Rally's Avatar
Evolving Member
 
Joined: Feb 2008
Posts: 254
Likes: 1
From: SoCal
Originally Posted by cableguy5752
It just keeps saying cannot connect to com port 1.
COM Port 1 is usually reserved for serial ports with a physical port present on the notebook i.e. not a virtual COM Port as used by EvoScan. I'm guessing your drivers aren't installed correctly. Visit http://www.limitless.co.nz/evoscan/ and look about 80% of the way down the page (just above the pics of the OBDII port & EvoScan plug) for more info.

Last edited by SoCal Rally; Aug 27, 2009 at 01:46 AM.
Reply
Old Aug 27, 2009 | 07:35 AM
  #12  
nic3boy's Avatar
Newbie
iTrader: (2)
 
Joined: Jan 2009
Posts: 11
Likes: 0
From: montreal
thanks
Reply
Old Aug 27, 2009 | 08:13 AM
  #13  
biggie5252's Avatar
Evolved Member
iTrader: (47)
 
Joined: Apr 2007
Posts: 1,320
Likes: 2
From: Kansas City
Originally Posted by SoCal Rally
There was an issue found with wideband logging from UEGO ... upgrade to v2.7 Beta2
Thanks!
Reply




All times are GMT -7. The time now is 05:09 AM.