Log4OM - JTAlertX - WSJT-X intercommunication

General discussions about Log4OM features
Post Reply
hammarby
Novice Class
Posts: 3
Joined: 03 Oct 2018, 09:34

Log4OM - JTAlertX - WSJT-X intercommunication

Post by hammarby » 03 Oct 2018, 09:50

Hello! I'm using Log4OM, JTAlertX and WSJT-X together and it works great on Win10.

I have one thing though that I haven't figured out how to solve though.

Let me explain. When working with Log4OM alone, I can click a callsign in the spots window and Log4OM will provide me with a lot of information about that call sign. (Even though I'm not currently having a QSO with that station) It also updates the Grey Line Map. It's really useful.

However, when using the "Log4OM - JTAlertX - WSJT-X"-combo, I would like Log4OM to show the same info for any ongoing QSO in WSJT-X. That would be both useful and really cool. (I do recall I had that functionality in another logging program together with WSJT-X).

So my question for you guys is if that's possible to set up.

Cheers!

hammarby
Novice Class
Posts: 3
Joined: 03 Oct 2018, 09:34

Re: Log4OM - JTAlertX - WSJT-X intercommunication

Post by hammarby » 10 Oct 2018, 17:11

Hello! I'm currently trying to figure out why my question hasn't been answered.

Maybe it's a difficult question or maybe it's an odd request.

I tried to set up Log4OM with WSJT-X without JTAlertX. Logging works but, same in this setup, Log4OM doesn't show me any info about the call sign for any ongoing QSOs.

Please, if you have any idea about how to set it up, share it with me.

Cheers!

hammarby
Novice Class
Posts: 3
Joined: 03 Oct 2018, 09:34

Re: Log4OM - JTAlertX - WSJT-X intercommunication

Post by hammarby » 12 Oct 2018, 11:44

I've tried today using wireshark and npcap to trace the intercommunication on localhost adapter but i failed to catch them for some reason. I might give it another try later.

My configuration
  • WSJT-X is set up to accept UDP requests on port 2237
  • Log4OM UPD Server is listening at port 2236 (127.0.0.1) (Inbound for Log4OM communicator)
  • JTAlertX is transmitting ADIF UDP packets on port 2333. JTAlertX can be set up to rebroadcast WSJT-X UDP Packets but it's not activated.
There is a lot of intercommunication set up. I try to get some better understanding of it.

Some assumptions. Please feel free to correct me if I'm wrong.
  • JTAlertX connects to WSJT-X on port 2237. JTAlertX gets information both about ongoing QSO and logging requests. I don't believe that WSJT-X is making any connections. (JTAlertX shows ongoing QSOs, the info must come from somewhere...)
  • JTAlertX connects to Log4OM at port 2236 for logging purposes only. Question is though if there is any information sent about ongoing QSO or not.
Cheers!

User avatar
G4POP
Moderator
Posts: 5011
Joined: 21 Jan 2013, 15:55
Location: Burnham on Crouch, Essex UK

Re: Log4OM - JTAlertX - WSJT-X intercommunication

Post by G4POP » 12 Oct 2018, 12:26

hammarby wrote:
03 Oct 2018, 09:50
However, when using the "Log4OM - JTAlertX - WSJT-X"-combo, I would like Log4OM to show the same info for any ongoing QSO in WSJT-X.

So my question for you guys is if that's possible to set up.

No that is not how it works Log4OM receievs the data sent by JTAlert on port 2236 and records it directly to the logbook, there is a setting in our latest release that will analyse the inbound qso and improve the data quality but thats all.
73 Terry G4POP

User avatar
G4POP
Moderator
Posts: 5011
Joined: 21 Jan 2013, 15:55
Location: Burnham on Crouch, Essex UK

Re: Log4OM - JTAlertX - WSJT-X intercommunication

Post by G4POP » 12 Oct 2018, 12:28

You might receive more responses if users could see your call sign and know your location as a result. Thats why we request that you use your call sign as your user name
73 Terry G4POP

Post Reply