I expect the next JTAlert public release will correctly log the WSJT-X Contest exchanges to all the supported Loggers. I am currently extending JTAlert to utilise the new Logging and Status UDP data. Having said the above, I am now in possession of a pre-release build of WSJT-X that includes the Contest Exchanges in the logged QSO UDP packet. Not logging of Contest exchanges was due to the exchange information not being available to JTAlert via the WSJT-X UDP interface over which the logging data is transmitted by WSJT-X. I would appreciate your assistance in finding out my error in setting up JTAlert for this RTTY Log. I could not use the RTTY log for a correct record of contacts.
However, the wsjx.log did contain these contacts but without a state or grid square of the contact. After hitting the ok button, I checked the RTTY log and again there was no state for the contact and the qso was not automatically submitted. Here I filled into the summary the following: report sent, the report received, the exchange sent, and the exchange received. To understand what might be happening, I filled in the summary of a qso for an "imaginary" contact ( i.e. However, there was no state for the contact and the qso was not automatically submitted. The RTTY log showed the station call in the appropriate entryīox and the RST report of the contact and also the RST report that I sent. On 2:53 wrote: However, after I made a qso, the summary of it in the WSJT-X program did not include the exchange that I sent (i.e., 599 DE). Necessary data from the WSJT-X exchange depending on the Contest STX_STRING and SRX_STRING data so I will need to extract the Loggers will take some work as they don't accept standard ADIF WSJT-X Contest exchanges to all the supported Loggers. I expect the next JTAlert public release will correctly log the
I am currently extending JTAlert to utilise the Having said the above, I am now in possession of a pre-releaseīuild of WSJT-X that includes the Contest Exchanges in the logged Interface over which the logging data is transmitted by WSJT-X. Information not being available to JTAlert via the WSJT-X UDP Not logging of Contest exchanges was due to the exchange I would appreciate your assistance in finding out my error in However, the wsjx.log did contain theseĬontacts but without a state or grid square of the contact.Ĭlearly I could not use the RTTY log for a correct record of After hitting the ok button, I checked the RTTY logĪnd again there was no state for the contact and the qso was notĪutomatically submitted. The summary the following: report sent, the report received, theĮxchange sent, and the exchange received. To understand what might be happening, I filled in the summary ofĪ qso for an "imaginary" contact ( i.e. However, there was no state for the contact and the qso was not Report of the contact and also the RST report that I sent. Showed the station call in the appropriate entry box and the RST Include the exchange that I sent (i.e., 599 DE). Made a qso, the summary of it in the WSJT-X program did not Clearly I could not use the RTTY log for a correct record of contacts.
The RTTY log showed the station call in the appropriate entry box and the RST report of the contact and also the RST report that I sent. However, after I made a qso, the summary of it in the WSJT-X program did not include the exchange that I sent (i.e., 599 DE). After looking up the details for using JTAlert with the N3FJP ACLog, I followed the directions in the ATAlert help section to direct input to the N3FJP RTTY log. I was unable to log contacts using N3FJP Roundup Log.