Since wsjt-x communicates with jtalert and dxlab via udp, is it supported configuration to run wsjt-x on a linux machine communicating with jtalert and dxlab running on a windows machine?

This would be on a local, reliable, high speed network.

On 30/05/2021 20:15, Jim Pennino via groups.io wrote:

Since wsjt-x communicates with jtalert and dxlab via udp, is it supported configuration to run wsjt-x on a linux machine communicating with jtalert and dxlab running on a windows machine?

This would be on a local, reliable, high speed network.

Hi Jim,

as far as I know there is no issue with interoperation with DX Lab Suite across the Internet, specifically with SpotCollector, all you should need to do is open the server port in your firewall (usually 2237) for incoming UDP on the machine running SpotCollector, and specify that machine's IP address in the WSJT-X "Settings->Reporting->UDP Server" field.

With JTAlert I don't think it is possible as JTAlert does several things that require access to WSJT-X files and processes of the machine it is running on.

73
Bill
G4WJS.

I run WSJT-X in Linux connected to DXLab on a Windoze box to do my needs highlighting in WSJT-X. It works well. I've tried JTalert a couple of times over the years but this has not been supported. Maybe that's changed. Not a big fan anyway. I've tried AlarmeJT in Linux but it was just too much clutter....

73

-Jim
NU0C

On Sun, 30 May 2021 12:15:39 -0700
"Jim Pennino via groups.io" <penninojim@...> wrote:

Since wsjt-x communicates with jtalert and dxlab via udp, is it supported configuration to run wsjt-x on a linux machine communicating with jtalert and dxlab running on a windows machine?

This would be on a local, reliable, high speed network.

That is almost my exact configuration.   Each "machine" has to have a static IP.   On Linux you will want to build and install samplicator to split the UDP traffic among two different IP's and ports.   That way you can still use CQRLog's features such as the CQ Monitor and logging, while sending the UDP traffic off to windows as well.

 I use a old copy of Windows 7 on Virtualbox to run Log4OM.  You can just as well use any other program such as the DXLab suite.  As long as you can tell it what IP address and UDP port to listen to.  I do this out of pure laziness.  Someday, I will get around to fixing CQRLog so that it uploads to QRZ.   Then I can eliminate this weird stuff all together.   For now, it works.

There has been a long standing problem with JTAlert in that you can not set the IP address for JTAlert.   So it will always be hanging out listening on 127.0.0.1.  It simply won't work.   Not to mention it has to detect WSJT-X running before launch.   It's better to toss it and use a native Linux tool such as AlarmeJT or CQRLog.  Both have source available so you can make it yours.

Samplicator:
http://kb6ibb-15.ham-radio-op.net/Ham-Radio/Using%20WSJT-X%20in%20Linux%20with%20CQRLOG%20and%20AlarmeJTx8x.net.pdf

Samplicator Source:
http://kb6ibb-15.ham-radio-op.net/Ham-Radio/Source-Code/samplicator-master/