Duplicate QSO with Log4OM+JTAlert+JTDX
Posted: 22 Apr 2021, 15:23
Both Michael/VE3TKI and I are experiencing the issue of duplicate QSO entries when using Log4OM, JTAlert and JTDX.
We have searched the forum for similar issues and found a number but none of them help resolve our issue.
We are using JTAlert v2.16.17, JTDX v2.2.0-rc155, and Windows 10 Pro.
All our program settings are as per the Log4OM manual updated 2021-04-21, pages 201 and 205 to 208. Also all programs are running as administrator per pages 13 and 14.
Note 1: With all the settings as per the manual, call signs do not populate the JTAlert call sign matrix. However, if we change the JTDX UDP Primary Server from 2235 (as per the manual) to 2233, the call signs are populated.
Note 2: We get duplicate log entries in Log4OM even though the ADIF Monitor in Log4OM is disabled (Log4OM settings/ADIF Functions) as per page 207 of the manual.
Since we are both experiencing the same issue in two different environments, I suspect we have “something” misconfigured. Other than the duplicate QSO entry all appears to be working fine.
Any guidance would be appreciated.
Cheers es 73,
Daniel VE3NI
We have searched the forum for similar issues and found a number but none of them help resolve our issue.
We are using JTAlert v2.16.17, JTDX v2.2.0-rc155, and Windows 10 Pro.
All our program settings are as per the Log4OM manual updated 2021-04-21, pages 201 and 205 to 208. Also all programs are running as administrator per pages 13 and 14.
Note 1: With all the settings as per the manual, call signs do not populate the JTAlert call sign matrix. However, if we change the JTDX UDP Primary Server from 2235 (as per the manual) to 2233, the call signs are populated.
Note 2: We get duplicate log entries in Log4OM even though the ADIF Monitor in Log4OM is disabled (Log4OM settings/ADIF Functions) as per page 207 of the manual.
Since we are both experiencing the same issue in two different environments, I suspect we have “something” misconfigured. Other than the duplicate QSO entry all appears to be working fine.
Any guidance would be appreciated.
Cheers es 73,
Daniel VE3NI