EFILive Scan tool not connecting to vehicle?
10-24-2006, 11:28 PM
#1
EFILive Scan tool not connecting to vehicle? Ok, I haven't played with my tune for a while, so I though I do a little logging today and make some changes. Problem, Scan tool won't connect to the PCM. It will connect to the cable and the cable will black box log and can even flash in a new tune, but the laptop won't connect to the pcm with the scaner (The tuner connects just fine). I get this in the console.
20:00:51.126: EFILive V7 Version V7.3.2 (Build 416)
20:00:53.220: Ready.
20:01:32.886: Scanning for EFILive FlashScan Cable (USB)
20:01:32.902: Autodetect interface ...
20:01:33.089: Connection to [FSP] interface is OK
20:01:33.121: Autodetect OBD II protocol...
20:01:33.292: Vehicle not detected
20:01:33.324: Interface firmware model: FSP
20:01:33.339: Interface firmware version: 1.2.17
20:01:33.371: Interface firmware date: Jan 18, 2005
20:01:33.386: FlashScan serial number: 003542135579
20:01:33.699: Loaded customer details for Kyle B [] from file: 2GTEK19V811344010.cus
20:01:33.699: Initialising PIDs...
20:01:33.839: Initialising Modules...
20:01:33.839: Ready.
I am usually the last one to post stuff like this, but I have tried everything. Cig fuse is good. Got the lasted USB drivers, just installed the software on this computer a couple of weeks ago (Brand new Dell, worked then). Tried unplugging and replugging every thing back in, rebooted the laptop a couple of times. Held my tongue to the left AND the right, and still, nothing. Won't connect to the PCM. Other then that it works fine, lol. Any ideas??
20:00:51.126: EFILive V7 Version V7.3.2 (Build 416)
20:00:53.220: Ready.
20:01:32.886: Scanning for EFILive FlashScan Cable (USB)
20:01:32.902: Autodetect interface ...
20:01:33.089: Connection to [FSP] interface is OK
20:01:33.121: Autodetect OBD II protocol...
20:01:33.292: Vehicle not detected
20:01:33.324: Interface firmware model: FSP
20:01:33.339: Interface firmware version: 1.2.17
20:01:33.371: Interface firmware date: Jan 18, 2005
20:01:33.386: FlashScan serial number: 003542135579
20:01:33.699: Loaded customer details for Kyle B [] from file: 2GTEK19V811344010.cus
20:01:33.699: Initialising PIDs...
20:01:33.839: Initialising Modules...
20:01:33.839: Ready.
I am usually the last one to post stuff like this, but I have tried everything. Cig fuse is good. Got the lasted USB drivers, just installed the software on this computer a couple of weeks ago (Brand new Dell, worked then). Tried unplugging and replugging every thing back in, rebooted the laptop a couple of times. Held my tongue to the left AND the right, and still, nothing. Won't connect to the PCM. Other then that it works fine, lol. Any ideas??
10-25-2006, 12:28 PM
#4
12 Second Club
iTrader: (4)
Join Date: May 2003
Location: Midwest
Posts: 3,324
Likes: 0
Received 0 Likes
on
0 Posts
Im having the same problem with a friends car. The tuning tool will connect to his car, but the scan tool will not. The scan toold connects to my car and other cars fine. His is a 98 Z28.
10-25-2006, 07:44 PM
#7
Originally Posted by TAQuickness
Shouldn't need to re-install. Try checking the connection properties to verify the right connection type is specified.
. When in and recalled all property's and worked like a champ 
I knew it had to be something simple since everything else work fine. Thank you! Trending Topics
10-25-2006, 10:32 PM
#9
TECH Junkie
iTrader: (28)
Join Date: Jan 2004
Location: Houston
Posts: 3,250
Likes: 0
Received 0 Likes
on
0 Posts
Originally Posted by kbracing96
Gosh TA, your so smart .
.
Originally Posted by kbracing96
When in and recalled all property's and worked like a champ I knew it had to be something simple since everything else work fine. Thank you!
I knew it had to be something simple since everything else work fine. Thank you!
09-16-2009, 11:13 AM
#10
i'm having connection issues, but on my lt1. I'm suspecting some of it has to do with the USB to serial converter. I ordered a PCMCIA serial card on the recommendation from carputing. I'm going to get that in the next day or two and see what happens. i think some of the usb to serial adapters are not all the same.
09-17-2009, 04:15 PM
#12
LT1, carputing, you must be using LT1Edit. First, my condolences. I use it too, to my extreme shame and misfortune. Second, the cable is very sensitive to the chipset in the USB to serial cable. You need to keep trying a different brand until you find one that works. I have two that work, but there is no brand name on them anywhere. I have also tried a couple that did not work, I just kept trying until I found one that did work.
09-17-2009, 10:19 PM
#13
LT1, carputing, you must be using LT1Edit. First, my condolences. I use it too, to my extreme shame and misfortune. Second, the cable is very sensitive to the chipset in the USB to serial cable. You need to keep trying a different brand until you find one that works. I have two that work, but there is no brand name on them anywhere. I have also tried a couple that did not work, I just kept trying until I found one that did work.
09-18-2009, 07:14 AM
#14
There is also Jet Dynamic Spectrum Tuner (formerly Tunercat) but it is another $400, and LT1Edit has no resale value. I'm in the same boat, I bought LT1Edit on someone else's recommendation, and I'm stuck with it.
None the less, you just need to try another USB to Serial cable. There are some that work, some that don't. Also, go into Device Manager and make sure the port Windblows assigned matches the one you are setting in Autotap and LT1Edit. It should be between 1 and 4, LT1Edit does not see any port above that number.
None the less, you just need to try another USB to Serial cable. There are some that work, some that don't. Also, go into Device Manager and make sure the port Windblows assigned matches the one you are setting in Autotap and LT1Edit. It should be between 1 and 4, LT1Edit does not see any port above that number.
