We often get inquiries about Thunderbolt UAD devices that just won’t connect to the host computer in question. The vast majority of these cases often boil down to a bad Thunderbolt cable.
What are some of the symptoms of a bad Thunderbolt cable?
- The UAD Meter & Control Panel displays the message “No Devices Found” even though your device is powered on and connected.
- You touch the Thunderbolt cable and a beeping sound comes out the speakers followed by the “no devices found” message.
- Your host computer shuts down the moment you connect your Thunderbolt cable.
- Your host computer randomly restarts or shuts down on its own without a visible cause.
- You get UAD error codes such as -38, -51 etc in your DAW environment.
- Unexplained CPU spikes in your DAW software.
- You get the spinning wheel of death when hovering your cursor over the UAD Meter & Control Panel.
- You see a “Connecting to Apollo” message when you thought you were already connected.
- You experience sluggish behavior on your host computer.
What can be done to resolve these symptoms?
Sometimes, all you need to do is remove the cable, shake it around, flip the directions and firmly re-seat it to restore your connection.
Often, however, you will need to replace your Thunderbolt cable with a brand new one. Please note however, that all of these symptoms can occur with a brand new cable right out of the box. Just because it is new does not mean that it isn’t bad.
All Thunderbolt 3 USB-C cables certified by Intel as Thunderbolt 3 compliant are compatible with Arrow. However, it's important to note that not all USB-C cables support Thunderbolt 3 - some USB-C cables can only be used for power or for other data protocols like USB 3. For details, see this article.
Another troubleshooting tip that may help you get a reliable connection are to blow out your Thunderbolts with dust off or compressed air just in case any particles are blocking the connection.
We have also seen PRAM / NVRAM resets and SMC resets help resolve issues with Thunderbolt UAD devices not being recognized by Mac computers: