Page 1 of 3

LOG4OM V2 & JTDX problem.

Posted: 16 Jan 2020, 15:15
by F1NQP
Morning, everybody.

First of all, thank you for this version 2 that we have been waiting for impatiently.

I work mainly in FT8 with JTDX.
In Software integration/Connections, I have configured UDP INBOUND with port 2237, and I have checked in front of it.

In version 2 there is no more COMMUNICATOR to boot as on V1?

I made multiple tests, and nothing works. The qso made in FT8 on JTDX, when I click on "LOG QSO", they don't appear in LOG4OM2.
In JTDX I didn't touch anything, the address is 127.0.0.1, the port 2237, and I checked in Settings/reporting the boxes "Accept UDP requests" and "notify on accepted udp request".

I translated the V2 notice online to read it, but I couldn't find any information.

Who could give me more information?

73 to all and good afternoon.


:!: :!: :!: Message complement:
Following the message from Aldo VA3AG, below, I have made a test with WSJT-X, and the qso are well transmitted to LOG4OM v2 via UDP.

So why doesn't it work with JTDX ????

Re: LOG4OM V2 & JTDX problem.

Posted: 16 Jan 2020, 16:09
by VA3AG
F1NQP wrote:
16 Jan 2020, 15:15
Morning, everybody.

First of all, thank you for this version 2 that we have been waiting for impatiently.

I work mainly in FT8 with JTDX.
In Software integration/Connections, I have configured UDP INBOUND with port 2237, and I have checked in front of it.

In version 2 there is no more COMMUNICATOR to boot as on V1?

I made multiple tests, and nothing works. The qso made in FT8 on JTDX, when I click on "LOG QSO", they don't appear in LOG4OM2.
In JTDX I didn't touch anything, the address is 127.0.0.1, the port 2237, and I checked in Settings/reporting the boxes "Accept UDP requests" and "notify on accepted udp request".

I translated the V2 notice online to read it, but I couldn't find any information.



Who could give me more information?

73 to all and good afternoon.

Translated with www.DeepL.com/Translator (free version)
JTDX is not supported by Log4OM2 yet. WSJT-X is fine.

73 GL

Re: LOG4OM V2 & JTDX problem.

Posted: 16 Jan 2020, 16:22
by F1NQP
sorry i didn't post in the right place :oops:

Re: LOG4OM V2 & JTDX problem.

Posted: 16 Jan 2020, 16:27
by F1NQP
Hello Aldo.

It's a shame, I will not be able to use V2 because I am JTDX 200%.
Let's wait for V2.1 :evil:

Thank you.

Re: LOG4OM V2 & JTDX problem.

Posted: 16 Jan 2020, 16:38
by DF5WW
WSJT-X and JTDX using the same engine and the setups should be equivalent. That means
if WSJT-X works JTDX should do so to. Did you try direct logging from JTDX or did you use
JTalert for logging to Log4OM ? If so you have to wait a few days for a newer JTalert version
with Log4OM V2 support.

If you log directly from JTDX to Log4OM V2 and it did not work it´s not a shame for Log4OM.
If so the programmer of JTDX hasn´t implemented UDP Outbound and then it´s a shame for
JTDX ....

;) ;)

Re: LOG4OM V2 & JTDX problem.

Posted: 16 Jan 2020, 16:45
by F1NQP
Hello Juergen.

No, I don't use JTALERT.

With log4om v1, it worked perfectly through the UDP port, I've been doing FT8 since December 2017, and I total 15,000 qso that have passed through log4om via UDP.

YES it's curious that V2 doesn't work with JTDX, because it's the same kernel as WSJT-x. Especially since JTDX is well mentioned in the V2 documentation.

In short, let's wait for a precise answer from the team !!!

Many thanks 73.

Re: LOG4OM V2 & JTDX problem.

Posted: 16 Jan 2020, 17:24
by DF5WW
Have played a bit with JTDX in the last 30 minutes but not get it to work for direct logging to
the V2. Think the problem is the secondary UDP connection that WSJT-X can handle but JTDX
can not. JTDX has only the main UDP setup. In the manual i find out that the connection to
WSJT-X have one for Port 2237 as ADIF MESSAGE and one für Port 2333 on the secondary UDP
for JT_MESSAGE. Think there could be the problem and if so it´s simply a JTDX problem.

By the way, i have installed latest JTDX and there is no secondary UDP .... :cry: :cry:

Re: LOG4OM V2 & JTDX problem.

Posted: 16 Jan 2020, 17:28
by G4POP
F1NQP wrote:
16 Jan 2020, 16:27
Hello Aldo.

It's a shame, I will not be able to use V2 because I am JTDX 200%.
Let's wait for V2.1 :evil:

Thank you.
I just loaded and tested JTDX it requires a TCP port which we have not yet implemented - Soon!

TEMPORARY WORKAROUND
However I was able to log from JTDX to Log4OM V2 by using our ADIF inbound function, read the user guide about FLDigi ADIF use the same principle but direct path to the JTDX folder in AppData

Just logged a couple of QSO's without a problem using the above

Radio set up using Omnirig in JTDX just the same as WSJT

Re: LOG4OM V2 & JTDX problem.

Posted: 16 Jan 2020, 17:33
by F1NQP
Many thanks Juergen.

Many thanks Terry, I'm going to try this method, and I'll come back to this forum to say if it's OK.

Have a good night.

Re: LOG4OM V2 & JTDX problem.

Posted: 16 Jan 2020, 17:56
by F1NQP
It doesn't work through FLDIGI either.

I'm going back to the V1 until better days come.