Issues with Satellite (SAT) Template – ADIF Export and Missing Fields

Hi!

I would like to report several issues with the current implementation of the SAT (satellite) logging template in the World Radio League web log. As it stands, it is unfortunately not suitable for proper satellite QSO logging, especially for LoTW submissions (via the ADIF export).

1. Incorrect Frequency Handling

The Frequency field is automatically populated with the downlink frequency, whereas for logging purposes (and ADIF/LoTW compatibility), the uplink frequency should be used or at least both uplink and downlink should be clearly supported (e.g., via separate fields like FREQ and FREQ_RX).

2. Missing RST Fields

There are no input fields for RST_SENT and RST_RCVD, which are standard logging elements and commonly required for satellite QSOs.

3. Missing Satellite in List

The satellite QO-100 (Es’hail-2) is not available in the satellite selection list. This is a significant omission, as QO-100 is currently one of the most widely used satellites, especially in Europe.

4. Invalid ADIF Export for Satellite QSOs

When exporting QSOs in ADIF format for QSOs from the SAT log, the following mandatory satellite fields are missing:

  • <PROP_MODE:3>SAT

  • <SAT_NAME:x>xxx

Without these fields, the exported ADIF file cannot be uploaded to LoTW for satellite QSOs, making the export function effectively unusable for this purpose.

Due to the issues above, the current SAT template does not produce LoTW-compatible logs and is not suitable for serious satellite operation logging. I kindly suggest addressing these points to improve usability and standards compliance.

73 Andrej, S51BW

1 Like

@S51BW Hey Andrej

We’ll take a look at this. I’ve added this as a ticket in our system and we’ll do some testing on this and potentially push some fixes.

I’ll update this thread once we’ve had a chance to dig into this a bit.

Thanks & 73
Brad K4AZE

1 Like

Thanks Brad, much appreciated!

73

Andrej, S51BW

1 Like