¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io
  1. Linuxham
  2. Topics

Importing ADIF file from DXKeeper

 

I was experimenting with merging data from the DXLab DXKeeper logbook app into fldigi's Logbook. ?The sample file used included the following LoTW-related ADIF fields, all of which were populated with valid data:
?
LOTW_QSL_SENT
LOTW_QSL_RCVD
LOTW_QSLSDATE
LOTW_QSLRDATE
?
In the resulting records in fldigi's Logbook, none of the merged records captured any LOTW data. ?On the Logbook's QSL tab the LOTW-rcvd and LOTW-sent fields were all empty. ?I assume that those two fields map to the LOTW_QSL_SENT and LOTW_QSL_RCVD adif fields (or perhaps LOTW_QSLSDATE and LOTW_QSLRDATE?).
?
Why is the data not making it into the fldigi Logbook?
?
Tnx.
?
Steve, N5EP
 

Hi Steve,

Fldigi does not store its logbook as ADIF, but in a list of data structures, so does not record all possible ADIF fields.

73 Phil GM3ZZA

Get

From:[email protected] <[email protected]> on behalf of swpub, N5EP via groups.io <swpub@...>
Sent:?Monday, May 12, 2025 11:18:55 PM
To:[email protected] <[email protected]>
Subject:?[linuxham] Importing ADIF file from DXKeeper

I was experimenting with merging data from the DXLab DXKeeper logbook app into fldigi's Logbook. ?The sample file used included the following LoTW-related ADIF fields, all of which were populated with valid data:
?
LOTW_QSL_SENT
LOTW_QSL_RCVD
LOTW_QSLSDATE
LOTW_QSLRDATE
?
In the resulting records in fldigi's Logbook, none of the merged records captured any LOTW data. ?On the Logbook's QSL tab the LOTW-rcvd and LOTW-sent fields were all empty. ?I assume that those two fields map to the LOTW_QSL_SENT and LOTW_QSL_RCVD adif fields (or perhaps LOTW_QSLSDATE and LOTW_QSLRDATE?).
?
Why is the data not making it into the fldigi Logbook?
?
Tnx.
?
Steve, N5EP
 

Thank you, Philip. ?I take it, then, that the LOTW-rcvd and LOTW-sent fields in the fldigi Logbook's QSL tab only get populated when interfacing with LoTW is done by fldigi invoking tqsl for an upload, and then matching with adit records downloaded from LoTW, as described in the fldigi documentation?
?
I was hoping that fldigi's Logbook might be suitable as a general purpose logbook that I could load my entire ham radio log history into, but clearly that will not work since I would lose a lot of information in a transfer from DXKeeper using adif files. ?Logging is the only ham radio function causing me to still keep one foot in the Windoze world, where I run DXKeeper in a VMWare Fusion virtual machine with Windows 11 for ARM on a Mac (M2 cpu). ?I have transitioned all the rest of my ham computer functions to macOS, and I also have Linux when needed.
?
73,
?
Steve, N5EP
 

¿ªÔÆÌåÓý

OK Steve,

I wrote my own logging software so I don't have that problem. I wrote it because I wasn't happy with the only free Windows logger I found 10 years ago.

I think there are Linux and/or MacOS logging apps available.

73 Phil GM3ZZA

From: [email protected] <[email protected]> on behalf of swpub, N5EP via groups.io <swpub@...>
Sent: 13 May 2025 9:08 PM
To: [email protected] <[email protected]>
Subject: Re: [linuxham] Importing ADIF file from DXKeeper
?
Thank you, Philip. ?I take it, then, that the LOTW-rcvd and LOTW-sent fields in the fldigi Logbook's QSL tab only get populated when interfacing with LoTW is done by fldigi invoking tqsl for an upload, and then matching with adit records downloaded from LoTW, as described in the fldigi documentation?
?
I was hoping that fldigi's Logbook might be suitable as a general purpose logbook that I could load my entire ham radio log history into, but clearly that will not work since I would lose a lot of information in a transfer from DXKeeper using adif files. ?Logging is the only ham radio function causing me to still keep one foot in the Windoze world, where I run DXKeeper in a VMWare Fusion virtual machine with Windows 11 for ARM on a Mac (M2 cpu). ?I have transitioned all the rest of my ham computer functions to macOS, and I also have Linux when needed.
?
73,
?
Steve, N5EP

1 - 4 of 4