Log4OM

Greetings.


My setup is as follows:
- Windows 8.1 64 bit
- SunSDR2Pro
- JTDX-2.0.2-rc140_17
- Log4OM v1.39.00

Previously as logging software I used Logger32.
QSO logging from JTDX to Logger32 worked O.K on UDP port 2237.

When I changed Logger32 to Log4OM the only way to log new QSO's
is by monitoring appropriate JTDX file, which is wsjtx_log.adi
(see attached picture).

It is working but I would prefer to log by means of UDP messages,
at least for one reason: to have logged also Frequency RX.

Went over Log4OM User Guide updated 12/08/2019 6:02 PM
but did not found working solution, apparently.
Unless, I overlooked something obvious...

Will appreciate all suggestions and help to solve this matter.


Best regards.
Tom - SP2L

You have not enabled the inbound port at bottom of your image to 2236 and set JTalert to 2236

Page 193 of the user guide

Hello Terry.


Thank you very much for prompt response.

In addition, SunSDR2Pro and JTDX do not employ
any external rig control software.
JTDX uses built-in emulation of Kenwood TS-480 commands.

Picture shows WORKING setup.
Previously I _HAD_ checked UDP Inbound box,
but it wasn't working, at least not for me.
That's why now I monitor wsjtx_log.adi file.

I do not use JTalert, so far...
Do I need to use it in order to have QSO's logged to Log4OM?

sp2l wrote: ↑02 Oct 2019, 21:17 I do not use JTalert, so far...
Do I need to use it in order to have QSO's logged to Log4OM?

With version 1 of Log4OM yes but version 2 will work direct with WSJT if you need to


Set the logging in JTAlert to the Log4OM sqlite file path, full details in our user guide page 193 - Dont use ADIF monitoring

Hello Terry.


Let me repeat once more:
I do not use JTalert...

Attached picture shows setup according to User Guide.
Now logging doesn't work, apparently...

What else I'm missing, please?

sp2l wrote: ↑02 Oct 2019, 21:55 Let me repeat once more:
I do not use JTalert...

My appologies I missread your first posting!

Assuming JTDX is the same as WSJT regarding UDP broadcast Log4OM Version 1 does not communicate directly with those programs but requireds JTAlert to interface correctly.

Log4OM version 2, which will hopefully be released very soon, will interface directly with WSJT and presumably also with JTDX if they use the same structure.

Meanwhile if you dont want to use JTAlert you will need to rely on the ADIF connection

Good morning Terry.


Again, I appreciate very much your prompt response.

Now eveything's plain and simple, Hi!

So, I'll wil wait impatiently for version 2 to be released,
mainly because I'm committed proponent of Log4OM!