Ok, I feel better after watching this video. I was having issues with the driver dropping out intermittently, and I see it did it to you to here at 11:45 and 13:13, before returning back to normal operation a handful of seconds later. This has been unresponsive to my attempts at troubleshooting and RF mitigation. I know a lot of people say they're not having issues, so I exchanged my TruSDX to Amazon just in case I got a faulty one, but if the new one does this same thing I think I'll just use a Digirig until the issue is potentially fixed in future firmware or driver updates. I know currently Manuel has said his workload is really high, so he's not going to offer support for the micro USB-only interface at the moment. It's still a great radio and I can't wait to see where it goes in the future!
I tried the settings that you gave (WSJT-X) with a Digirig and the lead they sell for the (tr) uSDX, but unfortunately, I kept on receiving error messages.
Thank you for the comment. In my case, I didn’t use the digirig add-on module so I’m not sure what the issue could be; however, I’d suggest joining the (tr)uSDX forum online & posting your configuration, settings, and error message. A lot of experienced & sharp folks post there, so good troubleshooting goes on in the forum threads. That would be my suggestion to find the root cause. Hope it helps & 73!
I appreciate this is an old video so I don't necessarily expect a response/ I have your exact same settings on windows 7 machine. I have tried many different usb cables/hubs/vb audio cable/voicmeeter/virtual port drivers/ferrite beads and rings etc. but keep running in to the same issue. Rx works fine ft8 coming in great. As soon as I hit Tx everything breaks and have to restart trusdx driver. Any tios or ideas please? Thanks for the great video.
Thank you for the comment/question. I have read that the truSDX on FT8 is very finicky as far as operating with the single USB cable and Guido's driver program for the PC. I have also found it to be only OK for FT8; for example, it sometimes looses sync with my PC and I have reset the truSDX. In your case, I'd say Windows 7 is quite an old OS since it was released ˜2009 and that may be part of the issue. You see, my setup used Windows 11. Now, as far as Rx getting the FT8 signal, that's a milestone. I mean it's quite good that you're getting that working since it implies that many of your settings are correct. When you Tx things go belly up to me speaks to the many variables in the setup, e.g. the single USB cable, Guido's driver program, the Windows OS, and perhaps most importantly the trUSDX itself. Don't get me wrong, I still think that the truSDX is a great little rig that sips current and works great. Heck I took it to England and did a POTA activation there where I got a Michigan station. However, Manuel and Guido clearly state that the truSDX is an experimenter's rig and should not be expected to work flawlessly like an ICOM or YAESU. I tend to agree. Love the radio but... it has compromises in its design to make it affordable. I still have the truSDX in my portable pack that I take as a backup in my car. I think highly of it and use if for CW but not really for FT8 anymore. Best of luck and 73!
@@quantumradio Thank you very much for your comprehensive response. You confirmed much of what I thought. I am looking to get a more serious rig soon but I also like experimenting which is why I decided to get my foundation licence for HAM here in England. Wull let you know if I get it working. All the best. 73s
I get no audio on transmit at all. Any thoughts? Seem to be getting audio just fine js8call, no signal is transmitted however. It switches to transmit and recieve ptt no issues, chsnges frequencies, etc.. thought?
Thanks for the comment. Audio coming into the JS8Call would seem to mean that the Settings>Audio tab>Input is set correctly to "Cable Output (VB-Audio Virtual Cable)", but maybe the Output is not set correctly to "Cable Input (VB-Audio Virtual Cable)". Other things to quickly check would be: Firmware version, menu option 9.7 F/W, must be 2.00u. Audio volume, menu option 1.1, was +4 in my video but I've increased it up to 7, 8, and even up to 10 in other tests with positive results, so you may want to vary that. Also, I'd concentrate on getting WSJT-X>FT8 to work since we always seem to have FT8 signals and WSJT-X is pretty solid software. The idea being that if the settings are correct for FT8, and the problem persists, then it would seem that the problem is hardware related. Heads up that Manuel DL2MAN mentioned in one of his videos that he tried about 4 different USB cables before finding one, a short length one, that worked. Other than that, I'd methodically check the different settings for FT8 and get that to work. Then proceed to JS8Call. Hope that helps. 73!
I have this same setup between my PC and the tr usdx.. but my input is showing red. Lowering the virtual mic setting does not lower the input and it stays red. I can "mute" it but cannot lower it. Is this an issue?
It sounds like you're talking about the needle on the signal meter at the bottom left of the VARA window showing red and not coming down to yellow or green. I'd suggest lowering the volume in the (tr)uSDX to 4 or 5. 73.
I’ve got the all setup and getting contacts on ft8 and js8call. However when I start up WinLink vara hf I keep getting an error message saying the com port is in use. I’m not too computer savvy, how do I fix this?
Thank you for the comment. It may be that Winlink has a COM port other than COM8 selected. I'd check the Winlink>Open Session (Vara HF Winlink)>Settings>Radio Setup & ensure tht Radio Control Port>Serial Port To Use = COM8. 73!
@@quantumradio thanks! That’s what I try to do, is to use com port 8. Every attempt results in com port in use. When I select a different com port it allows it, but of course there’s no connection between the two. Then go back to com port 8 and get the same in use message
@@tjs2909 Yes, the TRUSDX Driver uses COM8 & CABLE audio devices in WSJT-X or any other HAM radio program. So I don't believe that it will work on another port. When I run Winlink I first run FT8 with the configurations shown in the video, then exit FT8 (do not exit/restart the TRUSDX Driver or unplug cables), next I launch Winlink with the configurations shown in the video, and COM8 is then successfully used by Winlink. If you're doing this sequence, then it sounds like COM8 is not being "released" by Windows prior to running Winlink. That's interesting. For further troubleshooting, I’d suggest joining the (tr)uSDX forum online & posting your configuration, settings, and error message. This way the issue is shown to the (tr)uSDX user community. They're sharp folks in that forum & they may have the solution. Hope it helps & 73!
Hi I've Test now and it's working... i don't understand that I've need to start a truSDX Driverv and don't closed Driver, Tnx best 73 de IW6CAE@@quantumradio
Thanks for the comment. My setup didn't require the Digirig, just a sinigle USB cable from (tr)uSDX to the Windows laptop. I have heard of folks having good luck with the Digirig. It may be that the Digirig connection is more reliable than the single USB cable I've used; however, I don't have first hand experience of the Digirig connection to compare. Best of luck and 73!
Mine Acts weird on ft8. It decodes fine but when I tx it transmits but then after finishing it shows the red lines on the waterfall and stops receiving Audio. Psk reporter showed I transmitted. I think its the driver.
May be the length of the USB cable. DL2MAN did say that he went through 4 USB cables before finding one that worked for him. I believe that he ended up using a short USB cable for best results.
Thanks for the comment. The Winlink & VARA software & service is free though I paid for the "VARA license" & can in theory send/receive at faster transmission rates than w/the free version. As far as Winlink is concerned, I believe that you do have to have a callsign & signup to use Winlink, though I could be wrong. I have a Winlink account but not sure if it's required. Good news is that you can send/receive your emails to/from any email address, e.g. wxyz@gmail.com, abcd@outlook.com, etc. Hope that helps, 73!
Ok, I feel better after watching this video. I was having issues with the driver dropping out intermittently, and I see it did it to you to here at 11:45 and 13:13, before returning back to normal operation a handful of seconds later. This has been unresponsive to my attempts at troubleshooting and RF mitigation. I know a lot of people say they're not having issues, so I exchanged my TruSDX to Amazon just in case I got a faulty one, but if the new one does this same thing I think I'll just use a Digirig until the issue is potentially fixed in future firmware or driver updates. I know currently Manuel has said his workload is really high, so he's not going to offer support for the micro USB-only interface at the moment. It's still a great radio and I can't wait to see where it goes in the future!
Your video helped me to configure digital modes operation on my tr usdx. Thank you very much 73`s
Thank you for the comment & I’m glad it helped. Best of luck with your (tr)uSDX & 73!
Is firmware 2.00x a newer version? Wsjtx is working for me with the 2.00x firmware.
Thanks for the comment. Yes, I'm running 2.00x now and WSJT-X worked fine with it. Best of luck & 73!
I tried the settings that you gave (WSJT-X) with a Digirig and the lead they sell for the (tr) uSDX, but unfortunately, I kept on receiving error messages.
Thank you for the comment. In my case, I didn’t use the digirig add-on module so I’m not sure what the issue could be; however, I’d suggest joining the (tr)uSDX forum online & posting your configuration, settings, and error message. A lot of experienced & sharp folks post there, so good troubleshooting goes on in the forum threads. That would be my suggestion to find the root cause. Hope it helps & 73!
I appreciate this is an old video so I don't necessarily expect a response/ I have your exact same settings on windows 7 machine. I have tried many different usb cables/hubs/vb audio cable/voicmeeter/virtual port drivers/ferrite beads and rings etc. but keep running in to the same issue. Rx works fine ft8 coming in great. As soon as I hit Tx everything breaks and have to restart trusdx driver. Any tios or ideas please? Thanks for the great video.
Thank you for the comment/question. I have read that the truSDX on FT8 is very finicky as far as operating with the single USB cable and Guido's driver program for the PC. I have also found it to be only OK for FT8; for example, it sometimes looses sync with my PC and I have reset the truSDX. In your case, I'd say Windows 7 is quite an old OS since it was released ˜2009 and that may be part of the issue. You see, my setup used Windows 11.
Now, as far as Rx getting the FT8 signal, that's a milestone. I mean it's quite good that you're getting that working since it implies that many of your settings are correct. When you Tx things go belly up to me speaks to the many variables in the setup, e.g. the single USB cable, Guido's driver program, the Windows OS, and perhaps most importantly the trUSDX itself.
Don't get me wrong, I still think that the truSDX is a great little rig that sips current and works great. Heck I took it to England and did a POTA activation there where I got a Michigan station. However, Manuel and Guido clearly state that the truSDX is an experimenter's rig and should not be expected to work flawlessly like an ICOM or YAESU. I tend to agree. Love the radio but... it has compromises in its design to make it affordable.
I still have the truSDX in my portable pack that I take as a backup in my car. I think highly of it and use if for CW but not really for FT8 anymore. Best of luck and 73!
@@quantumradio Thank you very much for your comprehensive response. You confirmed much of what I thought. I am looking to get a more serious rig soon but I also like experimenting which is why I decided to get my foundation licence for HAM here in England. Wull let you know if I get it working. All the best. 73s
Thank you.
Thanks for sharing the settings! 73 - AA4K
Thank you for the comment. 73!
I can't get it to work.
I get no audio on transmit at all. Any thoughts? Seem to be getting audio just fine js8call, no signal is transmitted however. It switches to transmit and recieve ptt no issues, chsnges frequencies, etc.. thought?
Thanks for the comment. Audio coming into the JS8Call would seem to mean that the Settings>Audio tab>Input is set correctly to "Cable Output (VB-Audio Virtual Cable)", but maybe the Output is not set correctly to "Cable Input (VB-Audio Virtual Cable)". Other things to quickly check would be: Firmware version, menu option 9.7 F/W, must be 2.00u. Audio volume, menu option 1.1, was +4 in my video but I've increased it up to 7, 8, and even up to 10 in other tests with positive results, so you may want to vary that.
Also, I'd concentrate on getting WSJT-X>FT8 to work since we always seem to have FT8 signals and WSJT-X is pretty solid software. The idea being that if the settings are correct for FT8, and the problem persists, then it would seem that the problem is hardware related. Heads up that Manuel DL2MAN mentioned in one of his videos that he tried about 4 different USB cables before finding one, a short length one, that worked.
Other than that, I'd methodically check the different settings for FT8 and get that to work. Then proceed to JS8Call. Hope that helps. 73!
I have this same setup between my PC and the tr usdx.. but my input is showing red. Lowering the virtual mic setting does not lower the input and it stays red. I can "mute" it but cannot lower it. Is this an issue?
It sounds like you're talking about the needle on the signal meter at the bottom left of the VARA window showing red and not coming down to yellow or green. I'd suggest lowering the volume in the (tr)uSDX to 4 or 5. 73.
I’ve got the all setup and getting contacts on ft8 and js8call. However when I start up WinLink vara hf I keep getting an error message saying the com port is in use. I’m not too computer savvy, how do I fix this?
Thank you for the comment. It may be that Winlink has a COM port other than COM8 selected. I'd check the Winlink>Open Session (Vara HF Winlink)>Settings>Radio Setup & ensure tht Radio Control Port>Serial Port To Use = COM8. 73!
@@quantumradio thanks! That’s what I try to do, is to use com port 8. Every attempt results in com port in use. When I select a different com port it allows it, but of course there’s no connection between the two. Then go back to com port 8 and get the same in use message
@@tjs2909 Yes, the TRUSDX Driver uses COM8 & CABLE audio devices in WSJT-X or any other HAM radio program. So I don't believe that it will work on another port. When I run Winlink I first run FT8 with the configurations shown in the video, then exit FT8 (do not exit/restart the TRUSDX Driver or unplug cables), next I launch Winlink with the configurations shown in the video, and COM8 is then successfully used by Winlink. If you're doing this sequence, then it sounds like COM8 is not being "released" by Windows prior to running Winlink. That's interesting. For further troubleshooting, I’d suggest joining the (tr)uSDX forum online & posting your configuration, settings, and error message. This way the issue is shown to the (tr)uSDX user community. They're sharp folks in that forum & they may have the solution. Hope it helps & 73!
Thanks for video, i want to try with my (tr)uSDX🔝
Thank you for the comment. 73!
I've tested but I've a problem with audio in RX and TX... 😞@@quantumradio
Hi I've Test now and it's working... i don't understand that I've need to start a truSDX Driverv and don't closed Driver, Tnx best 73 de IW6CAE@@quantumradio
Sorry, new to all this.
No DigiRig?
Thanks for the comment. My setup didn't require the Digirig, just a sinigle USB cable from (tr)uSDX to the Windows laptop. I have heard of folks having good luck with the Digirig. It may be that the Digirig connection is more reliable than the single USB cable I've used; however, I don't have first hand experience of the Digirig connection to compare. Best of luck and 73!
Mine Acts weird on ft8. It decodes fine but when I tx it transmits but then after finishing it shows the red lines on the waterfall and stops receiving Audio. Psk reporter showed I transmitted. I think its the driver.
May be the length of the USB cable. DL2MAN did say that he went through 4 USB cables before finding one that worked for him. I believe that he ended up using a short USB cable for best results.
@@quantumradioWill try. Also turned off semi qsk and will try later.
@@quantumradio it works now
Can you send to any email address, and receive replies from any using winlink? Do I need to sign up for the service?
Thanks for the comment. The Winlink & VARA software & service is free though I paid for the "VARA license" & can in theory send/receive at faster transmission rates than w/the free version. As far as Winlink is concerned, I believe that you do have to have a callsign & signup to use Winlink, though I could be wrong. I have a Winlink account but not sure if it's required. Good news is that you can send/receive your emails to/from any email address, e.g. wxyz@gmail.com, abcd@outlook.com, etc. Hope that helps, 73!
@@quantumradio I got it working. Pretty cool stuff! Thanks
I dont have a hb+ack button
You're referring to JS8Call from what I can tell. I'd say get the latest version of that SW and see if that fixes it. Best of luck & 73.
@@quantumradio yes I was, I installed it this morning. Pretty sure it's the latest
@@justawfulgamer7738 JS8Call version 2.2.0. Try clicking on Menu>Mode>Enable HB & Enable ACK. That should do it.
E
When I'm using js8, it's TXing at .01W. How can I get it to TX at 4 or 5 W?
NM...LDO..I had the js8 slider all the way lowered.