Integration with JTDX not working

Post Reply
VE3AND
Novice Class
Posts: 11
Joined: 04 Feb 2018, 15:18

Integration with JTDX not working

Post by VE3AND »

Log4OM 2.9.0.0, JTDX 2.2.0-rc152, not using JTAlert

Configured integration according to instruction on page 186 of manual version 29/10/2020 7:19 PM, but log entries are not being received in Log4OM.

How can I troubleshoot this?
User avatar
G4POP
Log4OM Alpha Team
Posts: 10748
Joined: 21 Jan 2013, 14:55
Location: Burnham on Crouch, Essex UK

Re: Integration with JTDX not working

Post by G4POP »

Did you set the 'Import QSO from JT Message #12' as on page 185 of the user guide

Log4OM Program config/applications/WSJT-x/JTDX
73 Terry G4POP
VE3AND
Novice Class
Posts: 11
Joined: 04 Feb 2018, 15:18

Re: Integration with JTDX not working

Post by VE3AND »

No, I assumed that only applied to WSTJ-X. I'll try it out next operating session.
VE3AND
Novice Class
Posts: 11
Joined: 04 Feb 2018, 15:18

Re: Integration with JTDX not working

Post by VE3AND »

G4POP wrote: 01 Nov 2020, 22:59 Did you set the 'Import QSO from JT Message #12' as on page 185 of the user guide

Log4OM Program config/applications/WSJT-x/JTDX
Nope, that did not work either.
User avatar
G4POP
Log4OM Alpha Team
Posts: 10748
Joined: 21 Jan 2013, 14:55
Location: Burnham on Crouch, Essex UK

Re: Integration with JTDX not working

Post by G4POP »

Are the primary UDP port in JTDX and also the UDP inbound port in Log4OM both set to 2237?
73 Terry G4POP
OE6CLD
Log4OM Alpha Team
Posts: 207
Joined: 04 Jun 2013, 08:54
Location: Nuremberg
Contact:

Re: Integration with JTDX not working

Post by OE6CLD »

Hi Andrew,

Please find attached my JTDX configuration with Log4OM v2. This has been working for many months without any problems. Please cross-check with your configuration. Please note that I'm NOT using JTAlert. For connecting Log4OM direct to JTDX, you will find a complete to-do list on page 186 in the 2.9.0.0. handbook. Both port 2333 an 2237 are default ports. If these ports are used by other applicartions, you can use any other free ports. Just make sure that the Primary UDP Server port (default 2237) and the JT_MESSAGE WSJT_DIRECT port are the same, and that the 2nd UDP Server port (2333) and the JT_MESSAGE JTDX DX CALL port are the same! In Log4OM don't forget to clock on "Save and apply" after doing any changes!

Log4OM Configuration -> Connections:
Log4OM Connections - JTDX.jpg
Log4OM Connections - JTDX.jpg (244.68 KiB) Viewed 4167 times

Log4OM Configuration -> WSJT-x / JTDX
Log4OM JTDX - JTDX.jpg
Log4OM JTDX - JTDX.jpg (151.65 KiB) Viewed 4167 times

JTDX Settings -> Reporting
JTDX Reporting Configuration.jpg
JTDX Reporting Configuration.jpg (215.53 KiB) Viewed 4167 times

Please let us know if this worked.

73
Claus
Claus, OE6CLD/DJ0DX/EI7JZ
VE3AND
Novice Class
Posts: 11
Joined: 04 Feb 2018, 15:18

Re: Integration with JTDX not working

Post by VE3AND »

Hi Claus;

Thanks very much. It turned out I had used 2337 instead 2237. I blame old age - of the computer screen, not me. :)

Just a note though - the setting for "import QSO from JT Message #12" is on page 185 of the manual, before the section on integrating JTDX. It's not clear that this setting is required just by reading page 186. Is there a place to submit corrections to the documentation?

73,

Andrew
User avatar
KI5IO
Log4OM Alpha Team
Posts: 1798
Joined: 16 Aug 2015, 16:30
Location: Plano, TX

Re: Integration with JTDX not working

Post by KI5IO »

VE3AND wrote: 03 Nov 2020, 23:24 Hi Claus;

Thanks very much. It turned out I had used 2337 instead 2237. I blame old age - of the computer screen, not me. :)

Just a note though - the setting for "import QSO from JT Message #12" is on page 185 of the manual, before the section on integrating JTDX. It's not clear that this setting is required just by reading page 186. Is there a place to submit corrections to the documentation?

73,

Andrew
Andrew,

The JT Message #12 only works with WSJTx. I have usually always tic'd it OFF when using JTDX, but have also run JTDX with it ON, but (as noted) it doesn't come into play with JTDX as that APP doesn't deal with JT Message #12 like WSJTx does.
73 - Nolan Kienitz - KI5IO
Plano, TX
M0TNX
Novice Class
Posts: 18
Joined: 04 May 2021, 20:01

Re: Integration with JTDX not working

Post by M0TNX »

Claus.
Many thanks for your advice and clear screenshots.

They have helped me get JTDX working with Log4OM flawlessly in a matter of minutes.

Again, Thank you.

Kev
M0TNX
py9dm
New user
Posts: 2
Joined: 24 Sep 2022, 11:02

Re: Integration with JTDX not working

Post by py9dm »

OE6CLD wrote: 02 Nov 2020, 11:02 Hi Andrew,

Please find attached my JTDX configuration with Log4OM v2. This has been working for many months without any problems. Please cross-check with your configuration. Please note that I'm NOT using JTAlert. For connecting Log4OM direct to JTDX, you will find a complete to-do list on page 186 in the 2.9.0.0. handbook. Both port 2333 an 2237 are default ports. If these ports are used by other applicartions, you can use any other free ports. Just make sure that the Primary UDP Server port (default 2237) and the JT_MESSAGE WSJT_DIRECT port are the same, and that the 2nd UDP Server port (2333) and the JT_MESSAGE JTDX DX CALL port are the same! In Log4OM don't forget to clock on "Save and apply" after doing any changes!

Log4OM Configuration -> Connections:

Log4OM Connections - JTDX.jpg


Log4OM Configuration -> WSJT-x / JTDX

Log4OM JTDX - JTDX.jpg


JTDX Settings -> Reporting

JTDX Reporting Configuration.jpg


Please let us know if this worked.

73
Claus
Olá a todos , sou um usuário feliz com o Log4OM 2 , uso também a v2.9.0e JTDX , sem o JT Alert . Gostaria de perguntar se há alguma diferença em sincronizar o Log4OM com o JTDX somente pela porta 2237 ou tem que usar a 2333 também?Pergunto pois uso somente a 2237 e para mim parece tudo normal . 73 a todos
Post Reply