Page 1 of 1
Integration with JTDX not working
Posted: 01 Nov 2020, 21:03
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?
Re: Integration with JTDX not working
Posted: 01 Nov 2020, 22:59
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
Re: Integration with JTDX not working
Posted: 01 Nov 2020, 23:34
by VE3AND
No, I assumed that only applied to WSTJ-X. I'll try it out next operating session.
Re: Integration with JTDX not working
Posted: 02 Nov 2020, 01:15
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.
Re: Integration with JTDX not working
Posted: 02 Nov 2020, 07:57
by G4POP
Are the primary UDP port in JTDX and also the UDP inbound port in Log4OM both set to 2237?
Re: Integration with JTDX not working
Posted: 02 Nov 2020, 11:02
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 (244.68 KiB) Viewed 4311 times
Log4OM Configuration -> WSJT-x / JTDX
- Log4OM JTDX - JTDX.jpg (151.65 KiB) Viewed 4311 times
JTDX Settings -> Reporting
- JTDX Reporting Configuration.jpg (215.53 KiB) Viewed 4311 times
Please let us know if this worked.
73
Claus
Re: Integration with JTDX not working
Posted: 03 Nov 2020, 23:24
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
Re: Integration with JTDX not working
Posted: 03 Nov 2020, 23:36
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.
Re: Integration with JTDX not working
Posted: 27 Oct 2021, 20:12
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
Re: Integration with JTDX not working
Posted: 24 Sep 2022, 12:19
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