Same here. TQSL can map FT8 to “Data,” which works fine. For the time being, I
am forgoing FT8 uploads to eQSL.
George J Molnar, KF2T
Nevada, USA
> On Jul 3, 2017, at 7:22 PM, Dan Malcolm <dan.malcol...@gmail.com> wrote:
>
> I suspect I am not the only one with logging problems to eQSL and LoTW.
> Thanks to a hint from another ham on this forum, I can now trick TQSL into
> uploading FT8 QSO’s. I just heard from an eQSL support volunteer, who in
> essence says that they are aware of the new mode, but are constrained by
> ADIF.ORG. I suspect LoTW has the same constraint but there is a workaround.
> QRZ seems to be handling all this in stride.
>
> What is the common practice now for eQSL? I have on a few occasions, changed
> the mode to SSB, but that brings issues too. One is that signal reports
> won’t match the mode. All this will get sorted out in time but has anyone
> come up with a better solution than mine? At the moment I am just holding
> off on sending FT8 QSO’s to eQSL.
>
> Dan Malcolm
> K4SHQ
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
