Re: TQSL 2.5 Release candidate (2.5-rc1) available for testing

Rick Murphy

The frequency ranges are specified in the LoTW configuration file and
cover the full extent of the bands worldwide.
TQSL doesn't complain, for example, if the frequency is not valid for
the US as long as it's in range.
60 meters, for example:
<band high="5450" low="5250" spectrum="HF">60M</band>

So, anything between 5250 and 5450 is acceptable, TQSL doesn't care
about the fixed frequencies used, etc.

More detail:
QSOs must have a Band. If you don't supply a BAND with your log, but
supply a FREQ, TQSL will infer the band from the frequency.
Say, 14200 - BAND is set to 20M. In this case, both BAND and FREQ are
uploaded to Logbook.

If you only provide a BAND, that's OK.

If you provide both, and the FREQ is out of range for the BAND, TQSL
used to reject the log; it now ignores that FREQ.

If you provide neither, TQSL will reject the QSO.

On Mon, Sep 30, 2019 at 3:47 PM Gary Hinson <Gary@...> wrote:

Thanks for all your hard work Rick.

I'm curious about the band/frequency checking aspect: does it handle the different frequency ranges permitted in various countries (e.g. on 60m)?

Gary ZL2iFB

-----Original Message-----
From: ARRL-LoTW@... <ARRL-LoTW@...> On Behalf Of Rick Murphy
Sent: 01 October 2019 08:32
Subject: [ARRL-LoTW] TQSL 2.5 Release candidate (2.5-rc1) available for testing

I'm getting ready to release the next version of TQSL, pending translation updates which I'm going to be sending out shortly.

Here's the list of major changes in TQSL 2.5:

- If a QSO provides a Band and a Frequency, and that frequency is out of range for the given band, then the frequency is ignored.

- Callsign Certificate requests for US hams use the ULS database for verifying the callsign and for providing address information. This also includes validation for 1x1 callsigns.

- When creating a callsign certificate, the first question is now for what kind of call. Personal, former, club, etc. This makes the rest of the process easier as defaults can be applied.

- When displaying the list of DXCC entities for a callsign certificate, the deleted entities are now pushed to the end of the list. The word "DELETED" in their names can now be localized so it's easier for non-english speakers to understand.

- When loading a callsign certificate, TQSL no longer asks for a password for that certificate. This can be re-enabled by a preference setting.

- The TQSL ADIF editor now emits proper MODE/SUBMODE for modes that require that.

- TQSL checks for operating as an elevated ("As Administrator") account on Windows and complains. A user is allowed to permanently bypass that check.

- References to "Duplicate" QSOs were changed to "previously uploaded".

- When editing a Station Location, do not override the existing data with ARRL or ULS address data. Those are now only used when station locations are initially created.

Lots of changes, especially around the callsign certificate processes, so testing here would be much appreciated.

OSX 32-bit:
Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA

Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA

Join to automatically receive all group messages.