: the UTC date of the QSO in YYYYMMDD format (without hyphens). Specifies that the QSO qualifies for the CW, PHONE orĭATA DXCC awards (as well as, potentially, the MIXED, single band and other DXCCs). This field is replaced by APP_LoTW_MODE containing the claimed mode.
The standard modes listed in the ADIF standard. MODE : the amateur mode (modulation type/protocol) for the QSO, specifically one of.: my receiver frequency for the QSO, in other words my QSO partner’sĪs in split or cross-band operation), in MHz with My transmitter frequency for the QSO (if specified), in MHz with 10 Hz resolution (with an SI non-compliant capital M, as per the ADIF specification). The wavelength of the band on which our QSO was made, in metres e.g. The callsign of the station I contacted, my QSO partner. STATION_CALLSIGN : the callsign I used on-air when making the QSOs.Hence is redundant: it is deprecated, included at present for backwards compatibility with
Tags and data fields - mostly as specified in the ADIF standard plus some APP_LoTW_ fields options ticked, the ADIF records contain these basic QSO QSOs made with any one of our callsigns, or all of them (the -Any- selection). Selecting from the drop-down list offered at Your Call Sign lets us extract confirmations for I believe LoTW uses UTC dates throughout, including here.
Enter the date numerically with hyphen separators as shown (an ISO 8601 format). The QSLs received since date lets us download confirmations recently received in order to Ticked, comparing the same confirmed QSO records between the ADIF files. To figure out what they really mean, I generated reports with and without each of the options There are a few poorly-worded and confusing options when generating confirmations from LoTW
It is a work-in-progress that in places refers to Logger32 simply because that’s the logging software I use.
I’ve created this unofficial user guide for ARRL’s Logbook of The World to supplement the helpĪvailable from the LoTW site.