Re: RTTY RU Worked Before Problem - Fault Found


Joe Subich, W4TV
 

Without checking the N3FJP software ... it *should* record the QSO with
the mode that was used on the air and *export* FT4/FT8 QSOs as DG for
the Cabrillo file. ADIF exports should use <MODE:3>FT8 for FT8 and
<MODE:4>MFSK<SUBMODE:3>FT4 for LotW. In any case the log should have
the correct mode *NOT* DG/RY.

73,

... Joe, W4TV

On 2022-01-14 6:48 PM, Jeff Young wrote:
Will Cabrillo convert an FT4 to DG from a log that logged a QSO as FT4? If so, that's were I went wrong because I used the option in N3FJP'S RTTY RU to log contacts as DG immediately in the log during the contest.
Jeff KB3HF
-------- Original message --------
From: Jim Cooper <JTalert@jimcooper.org>
Date: 1/14/22 5:40 PM (GMT-06:00)
To: Support@HamApps.groups.io
Subject: Re: [HamApps] RTTY RU Worked Before Problem - Fault Found
On 15 Jan 2022 at 10:10, HamApps Support (VK3AMA)
wrote:

> Without any testing done yet, I have
> located the cause of the
> inconsistent B4 reporting. It is due
> to the mode logged as "DG" rather than
> "FT4". JTAlert would never find FT4
> worked B4 QSOs which are logged as
> "DG". That is not a mode JTAlert is
> looking for. I note that you have a
> mixture of "FT4" and "DG" logged for
> the contest.
FYI, I can note for you that the RU contest
Cabrillo file submission wants RY for RTTY
contacts and DG for all other digital contacts.
2.4 In the Cabrillo formatted log, RTTY contacts use RY and
all other digital modes use the DG
mode abbreviations.
I don't know if these get put into the ADIF log file,
but that's basically where the DG comes from.
w2jc

Join Support@HamApps.groups.io to automatically receive all group messages.