Re: [Dx4win] Importing FT4 QSO confirmations from the LoTW

For the record, Logbook does export the proper MODE/SUBMODE: K1MU K1MU K8SRB 40M 7.04907 MFSK FT4 DATA 20200610 2020-09-16 10:17:08 // QSO record inserted/modified at LoTW 011000 2020-06-10T01:10:00Z // QSO Date & Time; ISO-8601 Y 20200623 2020-06-23 02:57:13 // QSL record matched/modified at

Re: [Dx4win] Importing FT4 QSO confirmations from the LoTW

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,

Re: [Dx4win] Importing FT4 QSO confirmations from the LoTW

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

[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