Log4OM

There's an error with the MySQL dll file that they say should be fixed in the next version. Info and workaround here: https://hamapps.groups.io/g/Support/top ... 3976#27581

Well I upgraded JTalert and Log4OM today and I have had limited success.

Using Log4OM version 1, everything works as it is supposed to with WSJT-X and JTalert 2.15, no issues.

Using Log4OM version 2, I get an error that the QSO did not log, then some time later, it actually shows up in Log4OM, but the contact doesn't show as B4 in JTalert.

I guess because it actually logs in version 2, this is an issue somewhere else, but I have been at this for a couple hours, been over every setting a dozen times, and for the life of me cannot figure it out.

Any suggestions would be appreciated, but in the meantime, I am going back to version 1.

In JTAlert, there is a setting to up the time for checking that the log has been updated. Try setting this to 20 or 30 seconds.

Wow, you are going back to V1 because of an error message? Tough crowd...

73,

Doug - W7DRM

lol, no it's not like that

I was just getting frustrated and was more in the mood to play radio than play software, so I just switched for that. I figured after my brain cooled down in a day or so, I would take a fresh look at it.

Thanks for the tip, I will give that a shot.

Mike

ETA: That worked, thanks again!

Now on to the next part of the learning curve.

VK3AMA wrote: 22 Jan 2020, 05:14

KI5IO wrote: 22 Jan 2020, 04:08
When you get the prompt to save the QSO (if you use that option) do you then get an error or warning message indicating that JTAlert can't confirm being able to log to the Log4OM2 SQLite file?

And then a moment or two later the QSO does appear in the F7 Recent QSOs Tab.

Log4OM V2 is slower in writing the QSO to the SQlite log file compared to V1 (based on my testing).
Since the QSO is correctly being written to the log file, you just need to increase the wait time in JTAlert before it checks the file for the new record and confirms the logging was successful. See the Logging section of the JTAlert Settings.

de Laurie, VK3AMA

I can only set the delay up to 20 seconds, the qso is taking around 34 seconds to be logged and thus always get the error message from JTalert.

2020-02-06 11:05:35.6881 INFO: [#=z7WMJzEjdrDmRepoUt9VP4_8=] : Begin ADIF import
2020-02-06 11:05:35.8311 INFO: [#=zDn_tT$ILUnksrAcHc9SUWfOf4TOJ] : Performing QSO search on callsign TA1BX
2020-02-06 11:05:35.9031 INFO: * [#=zDn_tT$ILUnksrAcHc9SUWfOf4TOJ][72 ms] : QSO search on callsign TA1BX completed
2020-02-06 11:05:35.9301 INFO: [#=zePm5BYI3IUChubTgVw==] : Award Management - Parse log started on 1 items
2020-02-06 11:05:35.9331 INFO: [AwardsDatabase] : Loading Awards list from database
2020-02-06 11:05:36.4291 INFO: [#=zSz745mHoIlC8y9gOpD7OsgU=] : ???? WSJT-X / FT8 -9 FT8 EA7KIP IM76IF KN41 ???? ???????? Default
2020-02-06 11:05:36.6701 INFO: [#=zSz745mHoIlC8y9gOpD7OsgU=] : ???? WSJT-X / FT8 -9 FT8 EA7KIP IM76IF???? ???? ???????? Default
2020-02-06 11:05:39.7233 INFO: [#=zSz745mHoIlC8y9gOpD7OsgU=] : ???? WSJT-X 2.1.1 9c3311
2020-02-06 11:05:40.3943 WARN: [FwDateTime][StringToDate] : ConvertDate: cannot convert the input string 10101
2020-02-06 11:05:43.7245 INFO: [#=zSz745mHoIlC8y9gOpD7OsgU=] : ???? WSJT-X / FT8 -9 FT8 EA7KIP IM76IF???? ???? ???????? Default
2020-02-06 11:05:54.7191 INFO: [#=zSz745mHoIlC8y9gOpD7OsgU=] : ???? WSJT-X 2.1.1 9c3311
2020-02-06 11:05:55.2712 WARN: [FwDateTime][StringToDate] : ConvertDate: cannot convert the input string 10101
2020-02-06 11:05:59.6369 INFO: [#=zSz745mHoIlC8y9gOpD7OsgU=] : ???? WSJT-X / FT8 -9 FT8 EA7KIP IM76IF???? ???? ???????? Default
2020-02-06 11:06:00.1699 INFO: [#=zSz745mHoIlC8y9gOpD7OsgU=] : ???? WSJT-Xa?(????????? ` ~ R6AK <HB0/HB9LCW> -05
2020-02-06 11:06:00.8330 INFO: [#=zSz745mHoIlC8y9gOpD7OsgU=] : ???? WSJT-X / FT8 -9 FT8 EA7KIP IM76IF???? ???? ???????? Default
2020-02-06 11:06:07.0593 INFO: * [AwardsDatabase][31126 ms] : Awards list retrieved from database
2020-02-06 11:06:07.1153 INFO: * [#=zePm5BYI3IUChubTgVw==][31184 ms] : Award Management - Parse log terminated
2020-02-06 11:06:07.1183 INFO: * [#=z7WMJzEjdrDmRepoUt9VP4_8=][31430 ms] : End of ADIF import
2020-02-06 11:06:07.1213 INFO: [#=zh4$C0MA9NszexTnsaNr$FjBlSHBX] : {d35d083f-305a-45fb-b726-083303b7d171} received 1 QSO
2020-02-06 11:06:07.1463 INFO: [#=zgJve__65v5ySrIbpcg==] : ############### ADD QSO Callsign: TA1BX Date: 06/02/2020 11:04:15 Band: 17m Mode: FT8
2020-02-06 11:06:07.9444 INFO: [#=zDn_tT$ILUnksrAcHc9SUWfOf4TOJ] : Performing QSO search on callsign TA1BX
2020-02-06 11:06:08.1364 INFO: [#=zvLagAAg9f2ZJVKJJqg==] : [HAMQTH] Search start on TA1BX (originally TA1BX)
2020-02-06 11:06:08.8158 INFO: [#=zvLagAAg9f2ZJVKJJqg==] : [HAMQTH] Search completed
2020-02-06 11:06:08.8198 INFO: * [#=zDn_tT$ILUnksrAcHc9SUWfOf4TOJ][875 ms] : QSO search on callsign TA1BX completed
2020-02-06 11:06:09.0938 INFO: [#=zgJve__65v5ySrIbpcg==] : QSO Callsign: TA1BX Date: 06/02/2020 11:04:15 Band: 17m Mode: FT8 Saved

From the log it looks like it is taking 32 seconds to retrieve the Awards list.

Is there anyway to speed this up?

the new version of jtdx allows logging into LOG4OM without using JTalert

Hmm. older versions have allowed this too. The problem was the DX_Call send to the Log4OM V2
engine. Reason ... JTDX havn´t had a second UDP facility. And as i can see in your sreener we have
only the primary one in JTDX.

it wasn't there

JTDX-2.1.0-rc148-win64

Thank´s for info. Think it will be checked out. Not longer time this eve but will spot in the
A-Team network. Thank´s for reporting.

SQ5TDZ wrote: 21 Feb 2020, 19:23 the new version of jtdx allows logging into LOG4OM without using JTalert

Hello Andrew

Log4OM version 2.2 or 2.3?