Page 1 of 3

JTalert: QSO to Log4OM (mySQL)

Posted: 31 Mar 2018, 18:50
by PA0AER
I got this message:
Failure: QSO not logged
Error Message: Log4OM MySQL: Unable tot confirm QSO logged
NOTE: The QSO is still saved to the WSJT-X Log File

The connection between Log4OM and WSJT-X is ok (tested in log4OM)

I think that I have tried everything possible, but nothing is logged. In the past there was no problem.
Thanks in advance,

Re: JTalert: QSO to Log4OM (mySQL)

Posted: 31 Mar 2018, 20:50
by G4POP
Probably an incorrect path set to the logbook in JTalert or the Log4om communicator incorrectly set up - UDP miss-match perhaps

Re: JTalert: QSO to Log4OM (mySQL)

Posted: 01 Apr 2018, 07:53
by PA0AER
Thanks Terry,

I found it, in the communicator settings > Inbound settings > Adif File polling was Enable File polling not checked.
Yhanks for the hint
Ger

Re: JTalert: QSO to Log4OM (mySQL)

Posted: 01 Apr 2018, 09:26
by G4POP
That's not how JTalert sends qso's to Log4om, it's not by polling the ADIF file, check the JTalert documentation for correct set up!

Re: JTalert: QSO to Log4OM (mySQL)

Posted: 01 Apr 2018, 09:44
by DF5WW
In the Log4OM communicator "Inbound Settings" UDP must be enabled and the UDP Port must be the
same as in JTAlert (normally 2236 for both). Logging to Log4OM must be enabled in JTalert. In JTalert
you have to set the correct path to your SQlite File.

comm.png
comm.png (9.08 KiB) Viewed 6171 times
JTalert.png
JTalert.png (38.61 KiB) Viewed 6171 times

Re: JTalert: QSO to Log4OM (mySQL)

Posted: 01 Apr 2018, 10:33
by PA0AER
Hello Jürgen, I'm not using SQlite but mySQL

Re: JTalert: QSO to Log4OM (mySQL)

Posted: 01 Apr 2018, 11:45
by G4POP
PA0AER wrote: 01 Apr 2018, 10:33 Hello Jürgen, I'm not using SQlite but mySQL
If you base that assumption on the JTalert message it's an error of JTalert fixed in yesterday's release.

If you really are using mySql then use the fields marked mySql in the screenshot provided by Juergen instead of the Sqlite ones

Re: JTalert: QSO to Log4OM (mySQL)

Posted: 01 Apr 2018, 13:15
by PA0AER
I have used that settings for MySQL, except de UDP port, in my case is that 2237 (and 2236 for communicator)

Re: JTalert: QSO to Log4OM (mySQL)

Posted: 01 Apr 2018, 17:00
by PA0AER
I see another issue, WCF Services satus = stopped. I see also no wcf status with the name log4om in services from Windows. Can I add that services in Windows?

I have seen a post from Lauri, VK3AM : I have just now successfully tested JTAlert logging to Log4OM while the WCF service was turned off, so it is clearly not needed by Communicator UDP. l I have no idea what purpose WCF serves.

So, it is not necessary, but why is it it still in the GUI?

Juergen says that the DIF filepolling is not needed, but when I uncheck that, log4om doesn't log anymore.

Is it maybe an idea that I made screenshots from all the settings?

Re: JTalert: QSO to Log4OM (mySQL)

Posted: 04 Apr 2018, 11:48
by PA0AER
I'm now back from my /A QTH and checked the settings on my home QTH. Juergen is right, here I do not use the adif polling.
BUT, wcf is running here. And the system need that, when I uncheck the service, i got no logging. The big question is now how can I get a WCF service up and running on mu /A QTH?