LOG4OM V2 & JTDX problem.

General discussions V2
User avatar
sq9jxb
Advanced Class
Posts: 52
Joined: 14 Jan 2020, 16:00
Contact:

Re: LOG4OM V2 & JTDX problem.

Post by sq9jxb » 18 Jan 2020, 20:14

G4POP wrote:
16 Jan 2020, 17:28



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


How to set Log4OM 2 and JTDX to make it work?
  If it is possible step by step.

Regards
Log4OM 2.3 , JTDX 2.1.0.x64, Windows 10 x64
Yaesu FT-897D, Icom IC-735, Musb1017/Musb2232FK , ATU-150 , LDG-AT-200Pro
SGC PowerClear, EMU0202
.........................................
73!
Jan SQ9JXB

User avatar
W7DRM
Log4OM Alpha Team
Posts: 732
Joined: 19 Feb 2014, 19:44

Re: LOG4OM V2 & JTDX problem.

Post by W7DRM » 19 Jan 2020, 00:47

Instructions for logging from JTDX into Log4OM V2:
.
1. Log4OM V2 - open Program Configuration - ADIF Function tab.
2. Check Enable ADIF monitor
3. Click on folder icon and search for the wsjtx_log.adi file in the JTDX folder under User\<name>\App Data\Local\ folder. See below.
4. Click on the + tool.
5. Make sure you end up with the Enabled file path and file name as shown in the example below.
6. Click Save and apply at the top.

Note that the logging into V2 is not instant, as its a scheduled scan of the adif file. But it works fine for me.
.
ADIF_JTDX.PNG
ADIF_JTDX.PNG (48.79 KiB) Viewed 174 times
73,
Doug
W7DRM

User avatar
sq9jxb
Advanced Class
Posts: 52
Joined: 14 Jan 2020, 16:00
Contact:

Re: LOG4OM V2 & JTDX problem.

Post by sq9jxb » 19 Jan 2020, 08:08

Hello W7DRM

So I did and now Log4OM2 scans this .adi file for 20 minutes, and there are only 3900 QSO FT4 / FT8. The file has 2MB.
It takes long time.
I hope this works without a problem.

Regards

EDIT:

I did everything according to the description posted here on the Forum,
I did some QSOs and I don't write to Log4OM v2.
But I manage in a different way, the station sign appears in the Callsign window, the station details are completed, the rest I enter myself and log in after clicking the Save QSO icon.

Regards
Log4OM 2.3 , JTDX 2.1.0.x64, Windows 10 x64
Yaesu FT-897D, Icom IC-735, Musb1017/Musb2232FK , ATU-150 , LDG-AT-200Pro
SGC PowerClear, EMU0202
.........................................
73!
Jan SQ9JXB

User avatar
IW3HMH
Site Admin
Posts: 2542
Joined: 21 Jan 2013, 14:20
Location: Quarto d'Altino - Venezia (ITA)
Contact:

Re: LOG4OM V2 & JTDX problem.

Post by IW3HMH » 19 Jan 2020, 11:03

Unfortunately JTDX doesn't provide UDP messages like WSJT-X
I'm able to get UDP messages through JTAlert using JT Alert adif udp broadcast (not related to specific Log4OM options, but available in JTAlert for JTDX)
Daniele Pistollato - IW3HMH

User avatar
SP2L
Novice Class
Posts: 21
Joined: 29 Aug 2019, 13:33
Location: Gdynia, Poland
Contact:

Re: LOG4OM V2 & JTDX problem.

Post by SP2L » 22 Jan 2020, 18:00

Greetings Daniele et al.


This particular issue is a bit deeper than it look at first glance...

UDP protocol in JTDX is modified.
I think, getting in touch with Igor UA3DJY, JTDX team leader,
would be the best option in order to obtain detailed info.
Best regards.
Tom - SP2L
https://www.sp2l.ampr.org

Post Reply