LOG4OM setup with wsjt-x jtalert

[K7ERD]

Been a happy user of V1 but am having trouble getting V2 set up. I am using the latest versions (as of this date) of LOG4OM, WSJT-X and JTAlert. Tried following the LOG4OM setup instructions/examples in the user manual but ran into a problem. The manual says to set up inbound and outbound udp connections, but the dialogue box to select them (as shown in the examples) is not populated and there is nothing to select.

Gave it a try anyway and got the following results. When attempting to log a FT8 qso I get an error message from JTAlert saying that it was unable to confirm logging in log4om. The qso information is populated in the log4om screen with callsign, freq, date/time info, etc. but does not write to the log file. However, if I manually send to the log file it is successful.

I'm stumped and need suggestions of what to do next.

Ed K7ERD

[G4POP]

There is not an outbound UDP connection required in Log4OM, please identify the user guide page where you read this so that I can edit it.

Are you sure that you set the path to the Log4OM sqlite file correctly in JTAlert?

[K7ERD]

Terry;
The log path in JTAlert is set correctly and test ok (passes)

Pages 161 and 162 show inbound and outbound items in the boxes that are to be checked. My boxes are empty, so no paths can be checked off. I wonder why I do not have any entries so I can set the paths.

[K7ERD]

Terry;
I just figured out that I'm supposed to add the JT Message info into the inbound window per page 186. Missed that one. I still can't get Log4OM to load into the log file. I'm reviewing WSJT-X and JTAlert UDP setups. May have made an error somewhere.

Thank you for the assistance.
Ed K7ERD

[G4POP]

Pages 161 and 162 show inbound and outbound items in the boxes that are to be checked. My boxes are empty, so no paths can be checked off. I wonder why I do not have any entries so I can set the paths.

Those pages are a general introduction to and explanation of how the UDP system functions and are not specific to your setup.

Page 190 onward details the SPECIFIC setup for JTAlert and WSJT-X/WSJT-Z/JTDX

If you follow the step by step instructions it will work, dont just emulate the screen shots because some of the other data refers to other setups and is not required in every instance - Read and do as instructed in the text of the user guide.

Outbound connections are NOT REQUIRED for what you are trying to achieve!

[G4POP]

Terry;
I just figured out that I'm supposed to add the JT Message info into the inbound window per page 186. Missed that one. I still can't get Log4OM to load into the log file. I'm reviewing WSJT-X and JTAlert UDP setups. May have made an error somewhere.

Thank you for the assistance.
Ed K7ERD

Please follow the step by step instructions on page 190 >>>>

[K7ERD]

Terry;
I am pleased to report that I've things working. It was a bad case of RTFM. Thank you for your assistance. I would like to suggest that those sections be put into a quick start user guide. The manual is quite comprehensive but is quite daunting.

Again thank you.

73 Ed K&ERD

[KI5IO]

Terry;
I am pleased to report that I've things working. It was a bad case of RTFM. Thank you for your assistance. I would like to suggest that those sections be put into a quick start user guide. The manual is quite comprehensive but is quite daunting.

Again thank you.

73 Ed K&ERD

Ed,

Pls keep updating the U.G. as Terry is always updating.

I download a new version almost every week (if not more). I save it as a PDF and that PDF is "searchable". That works very well for me.

Here is a link to my recommendations about the U.G. from some time ago.

https://forum.log4om.com/viewtopic.php?f=40&t=5117

[AB7R]

I am having a dickens of a time here. I finally have L4OM logging contacts from JTalert (JTA). but when I click on a call from jtdx it does not show up on the l4om log window. Only logs once the contact is completed. Also The square decodes on the callsigns #1 window. When clicking on one of those are they supposed to start a contact on jtdx? Seems like it should but not working here. Seems like a lack of communication between JTA and JTDX.