[Dx4win] Importing FT4 QSO confirmations from the LoTW
Georg (DL5NO)
georg at dl5no.de
Sat Apr 17 15:29:49 EDT 2021
Hi Keith,
thanks for your email!
I downloaded a new lotwreport.adi with all QSOs, and after import also
the FT4 QSOs have a "Cnfm"->"Y", that solved my problem :-)
I can't understand how I got the old (apparently corrupt) lotwreport.
All others: Pse ignore my original mail.
73 and tnx,
Georg
> All of my imported FT4 QSO's from LOTW are confirmed. I use DX4WIN
> 9.09.1259 also.
>
> When importing the lotwreport.adi file into DX4WIN make sure the Options
> for duplicate QSOs window says: "imported QSO sets Lotw Confirmed flag"
>
> For example: I just imported a lotwreport.adi report today into DX4WIN
> and it set all recent FT4 QSOs to LOTW confirmed.
>
> The LOTW notation for each FT4 QSO is showing a "Y" under the Cnfm
> window block in DX4WIN.
>
> Keith W3KB
>
>
> ------------------------------------------------------------------------
> *From:* dx4win-bounces at mailman.qth.net <dx4win-bounces at mailman.qth.net>
> on behalf of Georg (DL5NO) <georg at dl5no.de>
> *Sent:* Saturday, April 17, 2021 1:23 PM
> *To:* dx4win at mailman.qth.net <dx4win at mailman.qth.net>
> *Subject:* [Dx4win] Importing FT4 QSO confirmations from the LoTW
> Hi,
>
> after importing the file of confirmed QSOs from the LoTW, I noticed that
> no confirmations of FT4-QSOs are shown in DX4WIN. Instead, all these
> FT4-QSOs are marked with the identifier "X" in the NOTFOUND file,
> despite the identical date, time and callsign in DX4WIN and LoTW.
>
> When I looked through the export and import files, I noticed the
> following: In DX4WIN as well as in the export to the LoTW the FT4-QSOs
> are marked as mode "MFSK" and submode "FT4". However, the ARRL web
> service for querying LoTW confirmations only returns the mode (MFSK),
> but not the submode. This is also specified in
> https://lotw.arrl.org/lotw-help/developer-query-qsos-qsls/
> <https://lotw.arrl.org/lotw-help/developer-query-qsos-qsls/>. It looks
> like the missing submode field leads to a negative QSOs match when
> importing the confirmed QSOs in DX4WIN.
>
> DX4WIN Version is 9.0.9.1259. Can other DX4WIN users confirm this behavior?
>
> I know that it is possible to set all FT4 QSOs manually to "LoTW
> confirmed" using the function "Check log against imported log", however
> with many FT4-QSOs this is time consuming, so any fix to the problem is
> appreciated. Possibly this behavior may also occur with other
> MFSK-submodes, which I have not yet checked.
>
> 73 de Georg, DL5NO
> ______________________________________________________________
> DX4WIN mailing list
> Home: http://mailman.qth.net/mailman/listinfo/dx4win
> <http://mailman.qth.net/mailman/listinfo/dx4win>
> Help: http://mailman.qth.net/mmfaq.htm <http://mailman.qth.net/mmfaq.htm>
> Post: mailto:DX4WIN at mailman.qth.net <mailto:DX4WIN at mailman.qth.net>
>
> This list hosted by: http://www.qsl.net <http://www.qsl.net>
> Please help support this email list: http://www.qsl.net/donate.html
> <http://www.qsl.net/donate.html>
More information about the DX4WIN
mailing list