Posts: 3,533 Threads: 265 Likes Received: 2,610 in 1,545 posts Likes Given: 3,893 Joined: Feb 2018 Reputation: 78 I hooked up my VTX a couple weeks ago to TBS Agent X and set the VTX up. Today Agent X won't recognize the VTX. When I plug in the cable, the VTX goes through its normal start-up routine correctly, but nothing on TBS Agent X. Any ideas what the problem might be?. • Posts: 21,213 Threads: 583 Likes Received: 8,946 in 6,620 posts Likes Given: 1,425 Joined: Jun 2018 Reputation: 786 I assume that you've tried a different USB cable in case you inadvertently grabbed a charge-only USB cable. Make sure you are definitely using a data cable. If you're 100% sure the cable is fine then do you see anything appear in Device Manager when you plug in the VTX (assuming of course that you're using a Windows computer)? • Posts: 3,533 Threads: 265 Likes Received: 2,610 in 1,545 posts Likes Given: 3,893 Joined: Feb 2018 Reputation: 78 (08-Feb-2021, 01:46 AM)SnowLeopardFPV Wrote: I assume that you've tried a different USB cable in case you inadvertently grabbed a charge-only USB cable. Make sure you are definitely using a data cable. If you're 100% sure the cable is fine then do you see anything appear in Device Manager when you plug in the VTX (assuming of course that you're using a Windows computer)? Yes, a good cable, and no it doesn't appear in DM. But clearly it did previously. With that said, I did get a dreaded Windows Update, so maybe that was the culprit. • Posts: 21,213 Threads: 583 Likes Received: 8,946 in 6,620 posts Likes Given: 1,425 Joined: Jun 2018 Reputation: 786 When you have the TBS Unify Pro32 HV connected to the computer via USB, check in Windows Device Manager under "Human Interface Devices" to see if one of the "USB Input Device" entries is for the Unify Pro32 VTX. You can check this by right-clicking each USB Input Device in turn then going to Properties -> Details and selecting "Bus reported device description" from the dropdown. I'm not entirely sure what description the Unify Pro32 HV will have but I would expect it to have "TBS" in the name like their other USB connectable products.. For instance, the Crossfire module has a description of "TBS CROSSFIRE". • Posts: 3,533 Threads: 265 Likes Received: 2,610 in 1,545 posts Likes Given: 3,893 Joined: Feb 2018 Reputation: 78 (08-Feb-2021, 03:23 PM)SnowLeopardFPV Wrote: When you have the TBS Unify Pro32 HV connected to the computer via USB, check in Windows Device Manager under "Human Interface Devices" to see if one of the "USB Input Device" entries is for the Unify Pro32 VTX. You can check this by right-clicking each USB Input Device in turn then going to Properties -> Details and selecting "Bus reported device description" from the dropdown. I'm not entirely sure what description the Unify Pro32 HV will have but I would expect it to have "TBS" in the name like their other USB connectable products.. For instance, the Crossfire module has a description of "TBS CROSSFIRE". Nothing on any of them that would be associated with the VTX, no Crossfire, no TBS, etc. • Posts: 21,213 Threads: 583 Likes Received: 8,946 in 6,620 posts Likes Given: 1,425 Joined: Jun 2018 Reputation: 786 It could be a driver issue but the TBS hardware generally just identifies itself as a standard Human Interface Device so if it was a driver issue then you would likely also have problems with other HID hardware connected to your computer. So maybe it's a hardware issue with the Unify Pro32 HV itself, or maybe the USB connector socket on the Unify Pro32 HV has a bad connection. Carefully inspect the pins with a magnifying glass for cracked or dry solder joints. Do you have another computer you can try it on? If you do then it would be worth trying that. Posts: 3,533 Threads: 265 Likes Received: 2,610 in 1,545 posts Likes Given: 3,893 Joined: Feb 2018 Reputation: 78 Thanks Snow I'll let you know. • Posts: 3,533 Threads: 265 Likes Received: 2,610 in 1,545 posts Likes Given: 3,893 Joined: Feb 2018 Reputation: 78 I hooked it to the wife's laptop, Same problem. And tried another cable just in case it had a broken wire, etc. All of it no worky, so it must be the VTX. I just wanted to turn down the power while working on it. I guess I will use the button old school. My first TBS component failure. This Pro32 HV VTX has been a pain from the beginning. Many of the LR crew are using other VTXs with good success....I may do the same. Thanks again for the help • Posts: 288 Threads: 56 Likes Received: 47 in 43 posts Likes Given: 13 Joined: Sep 2020 Reputation: 2 (09-Feb-2021, 05:43 AM)Krohsis Wrote: I hooked it to the wife's laptop, Same problem. And tried another cable just in case it had a broken wire, etc. All of it no worky, so it must be the VTX. I just wanted to turn down the power while working on it. I guess I will use the button old school. My first TBS component failure. This Pro32 HV VTX has been a pain from the beginning. Many of the LR crew are using other VTXs with good success....I may do the same. Thanks again for the help send it to me -- i'll fiddle w/it and then send it back to ya • Posts: 21,213 Threads: 583 Likes Received: 8,946 in 6,620 posts Likes Given: 1,425 Joined: Jun 2018 Reputation: 786 09-Feb-2021, 05:12 PM (This post was last modified: 09-Feb-2021, 05:14 PM by SnowLeopardFPV.) (09-Feb-2021, 05:43 AM)Krohsis Wrote: My first TBS component failure. This Pro32 HV VTX has been a pain from the beginning. Many of the LR crew are using other VTXs with good success....I may do the same. You could replace it with one of these... https://intofpv.com/t-rushfpv-rush-tank-solo-1600mw-vtx • |