ok, so i have hooked up the cable as we've discussed, and when i connect it to the laptop it pops up with the typical hardware found blah blah blah, then after about 10 seconds it says the devise is not recognized by windows....
when its first connected the rx and tx leds flash and then the led in the center stays lit while the rx and tx leds stay off.... have i done something wrong here?
You mean the power LED? The power LED should be on when ever there is power connected to the board.
Have you manually installed the FTDI drivers? Windows won't find the drivers for FTDI devices.
The man who says something is impossible, is usually interrupted by the man doing it.
yes the power led. the receive and transmit leds flash twice then stay off. no i have not installed driversand im none too computer savvy.... can i get a walk through? maybe?
1995 Chevrolet Monte Carlo LS 3100 + 4T60E
I follow those steps and i get to "updating driver" and my only options for drivers are "Communications port", im not given the 2.08.14 option as a driver
You will need to load a suitable driver for the usb chip. I used the file found in this link http://www.ftdichip.com/Drivers/VCP.htm.
Now with that said depending on the date of manufacture of your chip and your operating system version you may have to manually set up the device on your computer. Also in TunerPro you will have to initialize the device by selecting the appropriate com port.
open tunerpro, click tools tab, click preferences. Click the Data Acq./Emulation tab, under the Data Acquisition & Logging info it should see "use plug-in", Tunerpro data..., click on Configure Plug-in Component. Click test for valid interface....
At this point when u click on "test..." It will respond with either cable not found or not functioning. You must have the usb adapter connected to the laptop and the vehicle ALDL port for any of this to work.
I have found even though the cable test did not find my cable, it will still connect to the ecm and allow data. This is why you need everything hooked up so that you can test the "connect" function of the acquisition mode. As long as the "DA:Connected" indicator is blue and not yellow you should be transferring data.
Hope this helps
Buddrow
If it don't fit force it, if it don't force fit f&%@ it!
Followed this setup and I have a few questions,Originally Posted by RobertISaar
1st- when i setup the tunerpro side of the aldl connection, im only given the option for comm 4, is this normal? Can i only use comm 4 and therefore setup the cable in devise manager to be comm 4? But when i verify it in the acquisition setup, it is not found or connected?
2nd- is it a big deal or not that tunerpro, when choosing acquire data, that it is "not connected" in tunerpro?
Ok just tried again right after plugging in the cable to the computer and it came up good when doing the test for valid interface, but then tried again after a couple miniutes and back to failed...?
Last edited by rokcrawlin85; 01-08-2014 at 06:58 AM.
when in TP, if com4 is the only option showing up when the cable is plugged in(and driver setup), then that should be the COM port being created by the cable.
when doing the tests, is this with the cable plugged into the computer, but not the vehicle? because the test SHOULD fail while connected to a vehicle, but should pass when disconnected from the vehicle. it isn't always that cut and dry though, cables that fail that test can work flawlessly during actual scanning.
1995 Chevrolet Monte Carlo LS 3100 + 4T60E
The failed test is with the cable connected to the PC but NOT connected the the vehicle. The short time it clears the test on initial plug in is very odd to me.... could this be a driver issue? I had a hella time getting the drivers installed, ended up having to use the ftdi site for drivers which may cause issues from what I've been reading
Posting Permissions
Reply With Quote
Bookmarks