Although somewhat questionable, I therefore propose DXKeeper
considers MFSK without submode and FT4 as the same mode for eQSL
confirmations.
Absolutely not! MFSK without a sub-mode can be any of number of
"modes" including MFSK8, MFSK16, and JS8 each of which are
recognized for various award programs.
Accepting MFSK as equivalent to MFSK(FT4) is equivalent to accepting
PSK as equivalent to PSK(PSK31) or PSK(PSK63) or PSK(PSK125), etc.
The proper solution is to get the station that uploaded the QSO with
MODE=MFSK SUBMODE=<none> to fix his/her upload as either MODE=FT4
(not ADIF compliant) or as MODE=MFSK SUBMODE=FT4 (correct).
eQSL *should* refuse to accept QSOs with MODE=MFSK SUBMOD=<none>
or treat them as "data only".
73,
... Joe, W4TV
On 2020-06-13 4:03 PM, Bj?rn Ekelund, SM7IUN wrote:
Yes.
But logging into eqsl.cc shows that eQSL considers them a match and thereby
represents a confirmed QSO.
Although somewhat questionable, I therefore propose DXKeeper considers MFSK without?submode
and FT4 as the same mode for eQSL confirmations.
Bj?rn
Den l?r 13 juni 2020 kl 21:57 skrev Bernd - KB7AK <bernd1peters@... <mailto:bernd1peters@...>>:
He might be referring to the fact that some QSO's in eQSL come
through as just MFSK, while the majority comes through as MFSK(FT4).
If a QSO is logged as MFSK in eQSL it cannot be matched to a QSO
that is logged as FT4 in DXKeeper, I usually have one of 2 each week.
