Virtual serial ports are on their way out!
Today I went all-in on setting up my commonly used app's to use TCP/IP. Anything with Hamlib works great. You just have to know the secret squirrel stuff, which is to type into the port setting box IP:port, e.g. "127.0.0.1:1800", or whatever you've got Thetis set to. So right where it says "COM10" or the like, just type right over the top of it.
So far I have tested this with:
- Fldigi (you do have to select Hamlib as the method)
- WSJT-X
- JS8Call
Of course N1MM has TCP/IP now as a normal method, and I know DXLabs will have it soon.
The one disappointment so far is Winlink Express.
Examples (Thetis is running on the same PC so IP is "localhost", i.e. 127.0.0.1, and I've set my port to 1881 in Thetis):
Hamlib enabled app's can now use TCP/IP (WSJT-X, Fldigi & others)
- Tony EI7BMB
- Posts: 652
- Joined: Sun Apr 09, 2017 2:31 pm
- Location: Dublin
- Contact:
Re: Hamlib enabled app's can now use TCP/IP (WSJT-X, Fldigi & others)
Thanks Scott. Just set this up on JTDX . Your screenshot made me realise there is now a specific entry for our radio. I've been using Kenwood TS2000 for years.
Last edited by Tony EI7BMB on Thu Jun 23, 2022 5:15 pm, edited 1 time in total.
Re: Hamlib enabled app's can now use TCP/IP (WSJT-X, Fldigi & others)
Good to know that it works with JTDX, Tony, thanks!
Re: Hamlib enabled app's can now use TCP/IP (WSJT-X, Fldigi & others)
Hey,
just tried it in JTDX (2.2.160-rc1) with no luck (see screenshot below).
Any ideas?
73 Ernst
just tried it in JTDX (2.2.160-rc1) with no luck (see screenshot below).
Any ideas?
73 Ernst
Re: Hamlib enabled app's can now use TCP/IP (WSJT-X, Fldigi & others)
Try using 127.0.0.1 instead of 10.0.0.5
Mike W9MDB
Re: Hamlib enabled app's can now use TCP/IP (WSJT-X, Fldigi & others)
That does not work for me unless I set this also in Thetis.
I need 10.0.0.5 because I am accessing Thetis also from other PCs in the network.
73 Ernst
I need 10.0.0.5 because I am accessing Thetis also from other PCs in the network.
73 Ernst
Re: Hamlib enabled app's can now use TCP/IP (WSJT-X, Fldigi & others)
I just installed JTDX 2.2.159 64 bit (16 bit audio) on Windows 10.
It worked fine with both 127.0.0.1 and 192.168.1.xx addresses, depending on how I had Thetis set up.
Ernst: perhaps take a look at the firewall settings on all of the involved PCs.
It worked fine with both 127.0.0.1 and 192.168.1.xx addresses, depending on how I had Thetis set up.
Ernst: perhaps take a look at the firewall settings on all of the involved PCs.
Re: Hamlib enabled app's can now use TCP/IP (WSJT-X, Fldigi & others)
Very strange. Just tested 127.0.0.1 (127.0.0.1:13013 in Thetis and jtdx) => same error msg
Tests without success so far:
EDIT:
Selecting TS2000 instead of Flexradio/Anan-PowerSDR/Thetis has done the trick
73 Ernst
Tests without success so far:
- reverting back to jtdx-2.2.159-win64
starting jtdx with an empty data-dir
EDIT:
Selecting TS2000 instead of Flexradio/Anan-PowerSDR/Thetis has done the trick
![Smile :)](./images/smilies/icon_e_smile.gif)
73 Ernst
Re: Hamlib enabled app's can now use TCP/IP (WSJT-X, Fldigi & others)
That's not making a lot of sense. My tests were with the Flex/Anan/Thetis rig type.oe3ide wrote:Very strange. Just tested 127.0.0.1 (127.0.0.1:13013 in Thetis and jtdx) => same error msg
Tests without success so far:reverting back to jtdx-2.2.159-win64
starting jtdx with an empty data-dir
EDIT:
Selecting TS2000 instead of Flexradio/Anan-PowerSDR/Thetis has done the trick![]()
73 Ernst
Are you certain you are running with TCP/IP? It's easy to accidentally run with COM ports. The only way to be sure is to disable them in Thetis.
Re: Hamlib enabled app's can now use TCP/IP (WSJT-X, Fldigi & others)
Yes, I know it makes no sense
But these are the settings in the ini:
As soon as I stop the TCP/IP-Cat server in Thetis, I get the cat-error msg in JTDX. So its definitive connected via TCP/IP-CAT.
It works with TS-2000 and TS-480. But does not work with Flexradio6xxx or Flexsdr 1000 or Flexradio/Anan powersdr/Thetis
![Shocked :shock:](./images/smilies/icon_eek.gif)
But these are the settings in the ini:
Code: Select all
Rig=Kenwood TS-2000
CATTCIPort=
CATNetworkPort=10.0.0.5:13013
CATUSBPort=
CATSerialPort=10.0.0.5:13013
CATSerialRate=115200
As soon as I stop the TCP/IP-Cat server in Thetis, I get the cat-error msg in JTDX. So its definitive connected via TCP/IP-CAT.
It works with TS-2000 and TS-480. But does not work with Flexradio6xxx or Flexsdr 1000 or Flexradio/Anan powersdr/Thetis
Re: Hamlib enabled app's can now use TCP/IP (WSJT-X, Fldigi & others)
There is a setting to turn off the startup message. I’ll check when I get home.
Mike W9MDB
Re: Hamlib enabled app's can now use TCP/IP (WSJT-X, Fldigi & others)
Turn off the "Send version on client connect".
Mike W9MDB
Re: Hamlib enabled app's can now use TCP/IP (WSJT-X, Fldigi & others)
I have FT8 and FLDIGI working but on both I can't listen to the audio either input o output.
I am probably missing something very simple, but can't figure out what it is.
MON is selected but as soon as I check SETUP>AUDIO>VAC1 . Auto Enable: Enable for digital modes. Disable for all others, I lose being able to hear the audio. as he VAC1 Enable gets unchecked. In digital modes I am using the Voicemeter Virtual audio cables .In there a way to listen to the Voicementer audio?
Anybody have any ideas on what I am missing?
I am probably missing something very simple, but can't figure out what it is.
MON is selected but as soon as I check SETUP>AUDIO>VAC1 . Auto Enable: Enable for digital modes. Disable for all others, I lose being able to hear the audio. as he VAC1 Enable gets unchecked. In digital modes I am using the Voicemeter Virtual audio cables .In there a way to listen to the Voicementer audio?
Anybody have any ideas on what I am missing?
Re: Hamlib enabled app's can now use TCP/IP (WSJT-X, Fldigi & others)
Your issues are audio related and don't belong in this topic.
Please start a new topic in the virtual audio sub-forum.
Please start a new topic in the virtual audio sub-forum.