Longer USB Cable Issue

[simonntw]

Hi All,

 

So I just recently got my Pod Go and due to the way my office is oriented, my PC is over the other side of the room to where my amps, cabs and other audio goodies are, including the Pod Go.  I happen to have a 10m long USB A to USB B cable, it's braided and has gold plated connectors, so I thought i'd give it a try and it doesn't really work, unfortunately.  It detects something and starts the "connecting" process in pod go edit, but ultimately fails with "connection interupted" and even crashes the software in some cases.

 

I don't have another 10m long usb cable to test, but I can confirm the short cable that came in the box does work fine.

 

So, before I waste any money on another long USB cable to test, are any of you aware of any inherant reasons why long usb cables don't work in general with pod go?

 

I'm using pod go edit 1.40 and firmware 1.40.

 

Thanks,

 

Simon

[phil_m]

The max length for USB 2.0 is typically listed as 5M, or about 16ft. You might be able to push that to 20ft, but, yeah, im not surprised you’re having issues with a 10M cable. There are ways you can extend it - active extender cables or bridges - but I’m not sure those would even work with the POD Go.

[simonntw]

On 10/11/2022 at 12:29 AM, phil_m said:

The max length for USB 2.0 is typically listed as 5M, or about 16ft. You might be able to push that to 20ft, but, yeah, im not surprised you’re having issues with a 10M cable. There are ways you can extend it - active extender cables or bridges - but I’m not sure those would even work with the POD Go.

 

Thanks for the reply, I appreciate it.  I'll shelve the idea of using a 10m cable come up with a different solution I think.

[voxman55]

On 10/11/2022 at 8:21 AM, simonntw said:

 

Thanks for the reply, I appreciate it.  I'll shelve the idea of using a 10m cable come up with a different solution I think.

One thing to try is to use the rear USB port of your PC, not front USB port. On many PCs the rear USB signal is stronger. Had this problem on my PC and using the rear USB port fixed the problem.