Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
What might be happening?
24-07-2026, 05:16 PM, (This post was last modified: 24-07-2026, 05:18 PM by EI4KF.)
#1
What might be happening?
Hello Jordi

Please see video at https://youtu.be/7UjtpWRsfxk

This is not an email for help as its not a Swisslog error I believe. I do wonder though if you have any idea why it happens. Its on every station called / worked on JTDX. The callsign comes to the Entry of QSOs window and then switches in and out. Nothing actually goes wrong, the callsign is logged.

Flex Radio SmartSDR software, due to the company's regressive policy toward its customers that now mean a subscription is required to get latest new features, has come under competition. A superb alternative has emerged called AetherSDR. All software that works with SmartSDR also works with AetherSDR. One of its features is that I can open a second panorama and connect to a KIWI SDR. So I can have Slice 1 locally on 21074 for example and be using JTDX and I have Slice 2 connected to a KIWI and use WSJTx to receive either same band or other band. 

Swisslog does not like this! My UDP link is only to JTDX (as far as I know) but somehow the WSJTx instance interferes. As soon as I close WSJTx or the second Slice, the problem stops. The UDP is solid and remains green.

It is not "end of the world" but I wonder if there might be a solution.

73 de Erik EI4KF
Reply
24-07-2026, 06:05 PM,
#2
RE: What might be happening?
Hello Erik,

You have set this video this video as private and I can't watch it.

Please send me screenshots of:

- Reports tab from JTDX and WSJT
- The WSJT-X UDP settings in Swisslog

I need to see the UDP routes and all settings to try to find out what's happening.

73
Jordi, EA3GCV
Current developer of Swisslog
Reply
24-07-2026, 08:51 PM, (This post was last modified: 24-07-2026, 08:53 PM by EI4KF.)
#3
RE: What might be happening?
Hello Jordi

OK silly me. The video is now Public.

JTDX
   

WSJTX
   

SWL
   


I think I know what you might say: both are using UDP Port 2239? I hadn't thought of that. Because they are on different Slices with different DAX audio channels, I thought they would be independent but I have a feeling you are going to say they are not. 

Erik
Reply
25-07-2026, 09:56 PM,
#4
RE: What might be happening?
Hi Erik,

Effectively the problem is because you are using the same UDP Port either in JTDX and WSJT-X. Swisslog is receiving all traffic from both programs at once and that's why you see the QSO Entry window chaging callsign all the time.

I suggest you to use your main FT8 program (I believe in JTDX) as the Main instance in Swisslog (port 2239) and set another port in WSJT-X (i.e. 2240) and set this in Swisslog as a Log QSO instance. This way when you save QSOs from WSJT-X will be saved in Swisslog. It's the best way to use both programs at once and don't miss any saved QSO.

73
Jordi, EA3GCV
Current developer of Swisslog
Reply
26-07-2026, 08:19 AM,
#5
RE: What might be happening?
(25-07-2026, 09:56 PM)EA3GCV Wrote: Hi Erik,

Effectively the problem is because you are using the same UDP Port either in JTDX and WSJT-X. Swisslog is receiving all traffic from both programs at once and that's why you see the QSO Entry window chaging callsign all the time.

I suggest you to use your main FT8 program (I believe in JTDX) as the Main instance in Swisslog (port 2239) and set another port in WSJT-X (i.e. 2240) and set this in Swisslog as a Log QSO instance. This way when you save QSOs from WSJT-X will be saved in Swisslog. It's the best way to use both programs at once and don't miss any saved QSO.

73

Yes thank you Jordi. I will do that. Its a bit annoying because with WSJTx it is only monitoring a KIWI RX and cannot make QSOs. Changing the port in this scenario means changing it back if I use it instead of JTDX. But still, a small price to pay to have total control of a KIWI RX and FT8 streaming in my SDR software and Flex Radio. 

Some software now overcome this by connecting to the Flex Radio Slice in the API

   

Not that I am advocating you should do this in Swisslog. I doubt there is any demand yet.

Thanks again, 73 de Erik.
Reply
28-07-2026, 09:44 AM,
#6
RE: What might be happening?
Just an idea... if you set another UDP Port to WSJT-X and selec it as a Log QSO instance, you could also use a WSJT-X Band Map in Swisslog to monitor only this instance for the statistics you want. You can select the data source (instance) on WSJT-X Band MAps. It's a very interesting way to monitor different instances within Swisslog.

73
Jordi, EA3GCV
Current developer of Swisslog
Reply
28-07-2026, 05:31 PM,
#7
RE: What might be happening?
(28-07-2026, 09:44 AM)EA3GCV Wrote: Just an idea... if you set another UDP Port to WSJT-X and selec it as a Log QSO instance, you could also use a WSJT-X Band Map in Swisslog to monitor only this instance for the statistics you want. You can select the data source (instance) on WSJT-X Band MAps. It's a very interesting way to monitor different instances within Swisslog.

73

I need another monitor. The three I have are not enough....
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)