Monday, July 14, 2025

(tr)uSDX headache

 I hope this post will help solving problems with the (tr)uSDX and connecting the computer with one USB cable for CAT and audio. It is also written for myself as reminder. Let's asume everything was working well. But for some reason, nothing works the next day. 


The above message was given loading the (tr)uSDX driver, which you should load before starting a digimode software program like WSJT-X or others. What is happening here, it was working yesterday? What should do? I removed all drivers, restarted the computer, installed the driver again. Still the same message. I even installed a new VB-cable version. Still the same. Suddenly it occured to me that the VB-cable could be in use by another program or device. And yes, it was. Right click on your soundsymbol reveals what source is used. In my case the VB-cable. It should be the normal internal soundcard.


Above is what it should look like. If the VB-cable is chosen the (tr)uSDX driver will not load correctly.


Above what you see when the everything is allright!

Next problem. VARA-HF which is used for Winlink and VarAC. Settings are correct. Both VB-cables are choosen in audiosettings. Transmit audio is correct (verified with another radio). But there is no RX audio. 


So far my solution is to plug in a microphone into the computer, in my case a headset. Then restart the (tr)uSDX driver and then start VARA-HF. It does receive now. After that I start VarAC which will try to start another instance of VARA-HF, ignore that. It is working now...
I guess it's the same problem with Windows assigning the VB-cable to be used by the computer instead of the (tr)uSDX driver just like with the soundcard problem I wrote above. I guess there is a better solution but my knowledge of Windows is just too limited.


No comments: