On Mon, Sep 30, 2019 at 5:15 PM Phil Cooper via Groups.Arrl.Org
No, this was purely a defect in the ADIF Editor built in to TQSL. It
was saving any QSO that should have been stored as MODE/SUBMODE as
just MODE (<MODE:3>FT4). Yes, the behavior of TQSL was wrong in the
same way as some logging programs.
2. Is there some way of making sure that folk enter the correct CQ and ITU zones? Just recently, when syncing my logging program with LoTW, I am seeing more than a few where I get QSO Partner has not specified a CQ Zone (or ITU Zone), which means that I could potentially lost out on a credit somewhere.If there's address data for the call, TQSL will pre-fill the zones. If
not, it's up to the user to know and fill them in. I've fixed the
problem cases where the zones are reversed, and Logbook fixes the
issues where the zones are incorrect for the entity. Forcing people to
enter a zone is not going to happen for reasons already hashed out.
3. Like Gary ZL2IFB. I am concerned about the wording of the first line, about frequency. Can you explain what this means please?Already explained (I hope).
-Rick (MU/K1MU in April, possibly)
Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA