locked Requests for ADIF files


onaka@...
 

Hello
This is a request for JTAlert's ADIF file.

JTAlert does not have <qso_date_off: 8> in the ADIF file.
WSJT-X and JTDX include <qso_date_off: 8>.
Log linkage software JT_Linker does not work well without <qso_date_off: 8>.
Could you please add <qso_date_off: 8> to ADIF file?

Sample data for JTAlrt and WSJT-X ADIF files.
[JTAlert]
<CALL: 6> UA0JBY <QSO_DATE: 8> 20210716 <TIME_ON: 6> 043200 <TIME_OFF: 6> 043300 <FREQ: 9> 21.076356 <FREQ_RX: 9> 21.076356 <BAND: 3> 15m <BAND_RX: 3> 15m <MODE : 3> FT8 <DXCC: 2> 15 <COUNTRY: 14> Asiatic Russia <CQZ: 2> 19 <ITUZ: 2> 33 <CONT: 2> AS <RST_SENT: 3> -10 <RST_RCVD: 3> -05 < LOTW_QSL_SENT: 1> R <LOTW_QSL_RCVD: 1> R <EQSL_QSL_SENT: 1> R <EQSL_QSL_RCVD: 1> R <QSLMSG: 11> TNX FB QSO! <K_INDEX: 1> 2 <SFI: 2> 74 <COMMENT: 25> FT8 Sent: -10 Rcvd: -05 <NAME: 12> herman Lebed <QTH: 14> Asiatic Russia <PFX: 3> UA0 <MY_GRID SQUARE: 8 > PM54SA82 <MY_CQ_ZONE: 1> 0 <MY_ITU_ZONE: 1> 0 <STATION_CALLSIGN: 6> JA4JOE <QSO_COMPLETE: 1> Y <EOR>
 
[WSJT-X]
<call: 6> UA0JBY <gridsquare: 4> PO30 <mode: 3> FT8 <rst_sent: 3> -10 <rst_rcvd: 3> -05 <qso_date: 8> 20210716 <time_on: 6> 043200 <qso_date_off: 8> 20210716 <time_off: 6> 043300 <band: 3> 15m <freq: 9> 21.076356 <station_callsign: 6> JA4JOE <my_gridsquare: 8> PM54SA82 <comment: 25> FT8 Sent: -10 Rcvd: -05 <eor>


HamApps Support (VK3AMA)
 

On 16/07/2021 2:58 pm, onaka@... wrote:
This is a request for JTAlert's ADIF file.

JTAlert does not have <qso_date_off: 8> in the ADIF file.
WSJT-X and JTDX include <qso_date_off: 8>.
Log linkage software JT_Linker does not work well without <qso_date_off: 8>.
Could you please add <qso_date_off: 8> to ADIF file?

Sample data for JTAlrt and WSJT-X ADIF files.
[JTAlert]
<CALL: 6> UA0JBY <QSO_DATE: 8> 20210716 <TIME_ON: 6> 043200 <TIME_OFF: 6> 043300 <FREQ: 9> 21.076356 <FREQ_RX: 9> 21.076356 <BAND: 3> 15m <BAND_RX: 3> 15m <MODE : 3> FT8 <DXCC: 2> 15 <COUNTRY: 14> Asiatic Russia <CQZ: 2> 19 <ITUZ: 2> 33 <CONT: 2> AS <RST_SENT: 3> -10 <RST_RCVD: 3> -05 < LOTW_QSL_SENT: 1> R <LOTW_QSL_RCVD: 1> R <EQSL_QSL_SENT: 1> R <EQSL_QSL_RCVD: 1> R <QSLMSG: 11> TNX FB QSO! <K_INDEX: 1> 2 <SFI: 2> 74 <COMMENT: 25> FT8 Sent: -10 Rcvd: -05 <NAME: 12> herman Lebed <QTH: 14> Asiatic Russia <PFX: 3> UA0 <MY_GRID SQUARE: 8 > PM54SA82 <MY_CQ_ZONE: 1> 0 <MY_ITU_ZONE: 1> 0 <STATION_CALLSIGN: 6> JA4JOE <QSO_COMPLETE: 1> Y <EOR>
 

Hi OM,

I can confirm the missing QSO_DATE_OFF from the ADIF file (also DXKeeper, HRD5 and the lastqso.adi file).

This is due to the logging code for the affected loggers being written back when WSJT-X did not record Date & Time off data. Log4OM was not affected as the JTAlert code for it was written when WSJT-X was  providing the
Date & Time off data. I neglected to update the DXKeeper, ADIF & HRD5 logging code when WSJT-X changed to include the extra information. Note there have been no changes to the ACLog code as it does not support the QSO_DATE_OFF data in its logging API.

Please check your email inbox, I have sent a new build of JTAlert for you to test.

de Laurie VK3AMA


onaka@...
 

Laurie Thank you for your quick response.

I tested JTAlert.2.50.4.build.0002.Beta.Install.X64.exe.
QSO_DATE_OFF data is included in the ADIF file.

Thank you
Onaka JA4JOE


Willi Passmann
 

Am 17.07.2021 um 02:19 schrieb HamApps Support (VK3AMA):
This is due to the logging code for the affected loggers being written back when WSJT-X did not record Date & Time off data. Log4OM was not affected as the JTAlert code for it was written when WSJT-X was  providing the Date & Time off data.

Laurie,

I am using Log4OM v1.41.0.0 and this version does not get QSO_DATE_OFF data.

I noticed that some weeks ago and since then I started to add this data manually.

vy 73,
Willi,DJ6JZ


HamApps Support (VK3AMA)
 

On 17/07/2021 7:29 pm, Willi Passmann wrote:

Laurie,

I am using Log4OM v1.41.0.0 and this version does not get QSO_DATE_OFF data.

I noticed that some weeks ago and since then I started to add this data manually.

vy 73,
Willi,DJ6JZ


Willi,

I am unable to test Lo4OM v1, there is something wrong with my install. I did check Log4OM v2 and it correctly logged both the QSO_DATE and QSO_DATE_OFF.

What WSJT-X is logging.


What was logged by Log4OM v2.


In JTAlert the logging code for Log4 v1 and v2 is identical (just a copy and paste), it is simply ADIF encoded text. JTAlert is sending both QSO_DATE fields for Log4 v1 and v2. It looks to me like
the problem is with Log4 v1.

de Laurie VK3AMA


Willi Passmann
 

Willi,

I am unable to test Lo4OM v1, there is something wrong with my install. I did check Log4OM v2 and it correctly logged both the QSO_DATE and QSO_DATE_OFF.

What WSJT-X is logging.


What was logged by Log4OM v2.


Laurie,

here are screenshots of a log, from JTDX and Log4OM v1.41.0.0.
Note the missing check mark for QSO end date in Log4OM.

This is missing since an update some weeks ago, but I don't recall which one.

vy 73,
Willi, DJ6JZ


Willi Passmann
 

Am 19.07.2021 um 08:28 schrieb HamApps Support (VK3AMA):
You could try the latest JTAlert build, it has the QSO_DATE_OFF not logging fix for ADIF files, that fix may have affected the Log4 logging. Try it out.

64bit (x64) https://dnl.HamApps.com/Beta/JTAlert.2.50.4.build.0002.Beta.Install.X64.exe

This version is working fine with Log4OM v1: No more manual correction of my logs necessary :-)

Thank you, Laurie.

vy 73,
Willi, DJ6JZ