Problems logging with Evoscan
Aug 23, 2009, 02:39 PM
#1
Evolving Member
Thread Starter
iTrader: (5)
Join Date: Mar 2006
Location: Rockford, IL
Posts: 216
Likes: 0
Received 0 Likes
on
0 Posts
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
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
Aug 23, 2009, 10:05 PM
#4
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).
Aug 24, 2009, 11:13 AM
#5
Evolving Member
Thread Starter
iTrader: (5)
Join Date: Mar 2006
Location: Rockford, IL
Posts: 216
Likes: 0
Received 0 Likes
on
0 Posts
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.
4. It never changes. And i'm also using the 1.3 tactrix cable. It just keeps saying cannot connect to com port 1.
Aug 25, 2009, 02:30 PM
#7
Newbie
Join Date: Apr 2009
Location: San Jose, CA
Posts: 1
Likes: 0
Received 0 Likes
on
0 Posts
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.
Trending Topics
Aug 25, 2009, 10:46 PM
#8
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.
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.
Aug 26, 2009, 03:43 PM
#9
Evolving Member
Thread Starter
iTrader: (5)
Join Date: Mar 2006
Location: Rockford, IL
Posts: 216
Likes: 0
Received 0 Likes
on
0 Posts
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.
Aug 27, 2009, 01:37 AM
#10
Aug 27, 2009, 01:43 AM
#11
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.
