open port 2.0 issues
Thread Starter
Joined: Feb 2005
Posts: 554
Likes: 3
From: Fort Worth, TX
open port 2.0 issues
evoscan will not recognize open port 2.0 for me.
is this a problem for anyone else?
i just bought open port 2.0 cable from tactrix and i have the latest version of evoscan downloaded.
when i click start logging, it says "USB cable device not responding"
any help or direction would be greatly appreciated.
is this a problem for anyone else?
i just bought open port 2.0 cable from tactrix and i have the latest version of evoscan downloaded.
when i click start logging, it says "USB cable device not responding"
any help or direction would be greatly appreciated.
Evolved Member
Joined: Mar 2008
Posts: 730
Likes: 3
From: Lattitude 48.38°, Longitude 17.58°, Altitude 146m = Slovakia, for common dude
Maybe you can use MutMonitor
Thread Starter
Joined: Feb 2005
Posts: 554
Likes: 3
From: Fort Worth, TX
okay well...
im using my bud's 1.3 cable but it doesnt have the reflash connector (i dont know what its called)
to my understanding, i need that connector also to reflash the ECU but do i also need it to log?
and...am i reading right when i hear people having no issues with ecuFlash and 2.0 cable?
im using my bud's 1.3 cable but it doesnt have the reflash connector (i dont know what its called)
to my understanding, i need that connector also to reflash the ECU but do i also need it to log?
and...am i reading right when i hear people having no issues with ecuFlash and 2.0 cable?
The OP2.0 cable works fine when using it with ECUFlash to read and flash the ecu rom; just not when trying to log with any logging software at least on the VIII's and IX's.
okay well...
im using my bud's 1.3 cable but it doesnt have the reflash connector (i dont know what its called)
to my understanding, i need that connector also to reflash the ECU but do i also need it to log?
and...am i reading right when i hear people having no issues with ecuFlash and 2.0 cable?
im using my bud's 1.3 cable but it doesnt have the reflash connector (i dont know what its called)
to my understanding, i need that connector also to reflash the ECU but do i also need it to log?
and...am i reading right when i hear people having no issues with ecuFlash and 2.0 cable?
Trending Topics
[22:15:49.902] reading firmware
[22:15:49.918] flash file version is 1.05.2463
[22:15:50.464] main code version : 1.03.2380
[22:15:50.777] waiting for bootloader (may be installing drivers)... press any key to abort
[22:15:54.199] connecting to bootloader on COM3
[22:15:54.840] no bootloader response []
[22:15:55.136] no bootloader response []
[22:15:55.449] no bootloader response []
[22:15:58.230] J2534 error [device not responding].
[22:15:58.230] unable to connect to vehicle interface.
[22:15:49.918] flash file version is 1.05.2463
[22:15:50.464] main code version : 1.03.2380
[22:15:50.777] waiting for bootloader (may be installing drivers)... press any key to abort
[22:15:54.199] connecting to bootloader on COM3
[22:15:54.840] no bootloader response []
[22:15:55.136] no bootloader response []
[22:15:55.449] no bootloader response []
[22:15:58.230] J2534 error [device not responding].
[22:15:58.230] unable to connect to vehicle interface.
Evolving Member
Joined: May 2007
Posts: 208
Likes: 0
From: Europe
Has anybody resolved it?
Last edited by dolphin888; Mar 18, 2009 at 07:19 AM.
Evolving Member
Joined: May 2007
Posts: 208
Likes: 0
From: Europe
