Trying again to get a 7747 to connect to TPV5 again

jim_in_dorris · Post by **jim_in_dorris** » Thu Dec 29, 2011 1:54 pm

I spent a couple of hours yesterday sitting in the truck try to get TPV5 to connect. I can get V4 to run and winaldl to run, but V5 won't connect. I tried powering down the laptop, adding listen for silence and listen for packet to the adx with no joy. I did get it to change from just sitting at "DA: Connecting" to saying "DA: not connected" after 3`4 seconds of trying. I am running a homemade aldl connector with a usb/serial converter. I don't think it is the problem since V4 works fine, but I have been wrong before. I really like the added features of V5 , and would like to get this to work so I can use it on other vehicles as well.

jim_in_dorris · Post by **jim_in_dorris** » Sun Jan 01, 2012 3:05 pm

Okay, I don't know if this is a bug or what. When I have the TPV5 port selected the same as what I have it set in the device manager, and test the cable it says cable not found. If I change the port in TPV5 to something other than what is in the device manager, say the device manager is set to com 4 and I set TPV5 to com 3, then test the cable it returns cable found and tested good. What is going on?

jim_in_dorris · Post by **jim_in_dorris** » Wed Jan 04, 2012 3:35 pm

Well, I figured out why COM 3 responded with cable good. My built-in modem was set to com 3 and it responded. I changed it to com 2 and set the USB to serial adapter to com 3 and it didn't give me an error. However that did not solve my connection problem. TPV4 works fine at com 3, but TPV5 still will not connect. I tried adding a macro to listen for silence, then listen for packet, but that did no good. What else can I try? I am about to stuff my 8625 in just to see if it connects. If it does, then I have a large reason to finish gathering parts and make the swap. I will need to burn a bin for the truck after that as well.

Post by **Mangus** » Thu Jan 05, 2012 9:02 pm

7747 is 160 baud. You should directly import into v5 the working definition from v4. It should hook right up, provided the same COM port settings.

EagleMark · Post by **EagleMark** » Thu Jan 05, 2012 10:17 pm

I used to use WinALDL and TPV4. Switch back and forth. When I installed TPV5 it would never connect to cable although same com port. I uninstalled WinALDL, restarted computer and was connected to TPV5 many many times. Installed WinALDL and used it, never again could I get connected to TPV5. Uninstalled WinALDL, restarted computer and connected to TPV5.

Explain that? That makes no sense, but it has happened to many more people then me.

Then realized I had no use for WinALDL and never reinstalled it.

Can hook to DataMaster and WinFlash, same cable, then back to TPV5. But never with WinALDL installed and used could I ever get TPV5 connected? It was like a hostle takeover...

Post by **Mangus** » Fri Jan 06, 2012 6:30 am

Unexplainable.

EagleMark · Post by **EagleMark** » Fri Jan 06, 2012 7:02 am

Exactly. That is what I have told at least 20 people with same issue. 2 of which were near my town and came by with their laptops. We got rid of WinALDL and TPV5 connected! One, and mine I had to uninstall all USB from devive manager, do the driver uninstall, install FTDI drivers, restart.

Moates has three atricles on drivers and cables. Last case scenario, with warnings is FT Clean.

On another fourm same topic, I asked if anyone can run WinALDL and TPV5 back and forth. Only one person said they could and do. Only differance we could find was he has Windows XP and everyone else was higher version...

So maybe that info will help you as a software writer? Still makes no sense to me/us.

jim_in_dorris · Post by **jim_in_dorris** » Sat Jan 07, 2012 8:47 am

Ok, I tried TPV5 on my son's laptop which has never had WINALDL on it. Still no luck. I will try importing from V4 next.

EagleMark · Post by **EagleMark** » Sat Jan 07, 2012 2:00 pm

of course you seem to be having more trouble than most...