2qsos.docx- (202.73 KiB) Downloaded 270 times
QSO Doubling in Log
QSO Doubling in Log
When I log a QSO using WSJTX it is logging twice in log! Anyone else seeing this? N9LJY
Re: QSO Doubling in Log
Are you perhaps also using JTAlert, which is then logging the QSO again?
Re: QSO Doubling in Log
Tom,
It could also be that you have enable reading an ADIF file from WSJT-x or JTAlert.
That will also cause the double-logging.
It could also be that you have enable reading an ADIF file from WSJT-x or JTAlert.
That will also cause the double-logging.
73 - Nolan Kienitz - KI5IO
Plano, TX
Plano, TX
Re: QSO Doubling in Log
Thanks All, Just going by the help file in the connection section. Will uncheck the ADIF and see.. Tom
Re: QSO Doubling in Log
Gentlemen, when I turned off port 2333 it didn't log contact, but then I turned off 2237 and turned on port 2333 it double logged again. Tom.
Re: QSO Doubling in Log
yes I am.. Tom.
Last edited by N9LJY on 22 Jan 2020, 22:57, edited 1 time in total.
Re: QSO Doubling in Log
FROM HAMAPPS GROUP:
This is the latest build of JTAlert with Log4OMV2 support.
https://dnl.HamApps.com/Beta/JTAlert.2. ... .Setup.exe
This build works in getting the WSJT-X "DX Call" to Log4OM for any number of WSJT-X instances as it sends the instruction direct to Log4OM and doesn't rely on Log4OM monitoring the JTAlert UDP rebroadcast. Monitoring the UDP rebroadcast has a defect in that it cannot handle WSJT-X instances started with a -rig parameter. Note, this is a Log4OMV2 defect, not a JTAlert defect.
The setup of Log4OMV2 and JTAlert is now simplified due to the above changes.
Setup Instructions:
Enable the Remote Control port in Log4OMV2.
Create an ADIF_MESSAGE inbound connection in Log4OMV2.
Enable the sending of the DX Call in JTAlert.
Set the Control port in JTAlert to match the port used in Log4OMV2 (Step 1.)
Set the ADIF_MESSAGE port in JTAlert to match the port used in Log4OMV2 (Step 2.)
Note: If you previously created a JT_MESSAGE inbound connection in Log4OMV2, that can be disabled or removed.
Note: If you previously enabled the UDP rebroadcast in JTAlert that can be disabled.
de Laurie VK3AMA
This is the latest build of JTAlert with Log4OMV2 support.
https://dnl.HamApps.com/Beta/JTAlert.2. ... .Setup.exe
This build works in getting the WSJT-X "DX Call" to Log4OM for any number of WSJT-X instances as it sends the instruction direct to Log4OM and doesn't rely on Log4OM monitoring the JTAlert UDP rebroadcast. Monitoring the UDP rebroadcast has a defect in that it cannot handle WSJT-X instances started with a -rig parameter. Note, this is a Log4OMV2 defect, not a JTAlert defect.
The setup of Log4OMV2 and JTAlert is now simplified due to the above changes.
Setup Instructions:
Enable the Remote Control port in Log4OMV2.
Create an ADIF_MESSAGE inbound connection in Log4OMV2.
Enable the sending of the DX Call in JTAlert.
Set the Control port in JTAlert to match the port used in Log4OMV2 (Step 1.)
Set the ADIF_MESSAGE port in JTAlert to match the port used in Log4OMV2 (Step 2.)
Note: If you previously created a JT_MESSAGE inbound connection in Log4OMV2, that can be disabled or removed.
Note: If you previously enabled the UDP rebroadcast in JTAlert that can be disabled.
de Laurie VK3AMA
Re: QSO Doubling in Log
Laurie, Thank You, will try..73s Tom
Re: QSO Doubling in Log
The pictures associated with this message from Laurie did not copy above. Please visit the Hamapps group to view the entire detailed message. Make sure you find the latest current one as above. There have been many more earlier instructions before landing on this one. It works great. Good Luck, Herb, WB8ASI
