It's my understanding that when FT8 is implemented you can upload as FT8
and it will then confirm FT8 QSOs and unconfirm the DATA QSOs. I might be
wrong.
Post by Greg BeamHi Dave,
Thanks. I recall--vaguely--there being some issue with using this method
before LoTW implements the mode. I donât recall what it was offhand.
Something to the affect that, once youâve created the map, you (or LoTW)
cannot go back and change it in the event the mapping we select locally
differs from the server-side implementation. Thus, for whatever reason at
the time, I chose to just wait for LoTW to implement the mode.
I think when JT9 came out, there was discussion about the use of mapping
to data. However, I canât recall exactly what the situation was. It may be
a moot point now. It may also I am confusing the RTTY to DATA debate, no
sure.
73âs
Greg, KI7MT
*Sent:* Tuesday, July 18, 2017 11:21 AM
*Subject:* Re: [wsjt-devel] TQSL's config.xml
You can configure TQSL to automatically âmapâ FT8 QSOs to DATA now, which
will enable LoTW to accept them. See
https://lotw.arrl.org/lotw-help/pref-adi/
73,
Dave, AA6YQ
*Sent:* Tuesday, July 18, 2017 1:00 PM
*To:* 'WSJT software development'
*Subject:* Re: [wsjt-devel] TQSL's config.xml
You could ask Rick M., Dave, or one of the other Trusted QSL developers,
but, I would think that adjustments to the client-side will have little to
no affectâother than mapping the mode to dataâuntil the server-side model
has been updated to accommodate the new mode.
Even if the ADIF spec is released today, the backend work would still need
to be done before correct mapping of FT8 QSOâs could be realized. I donât
know what the LoTW eng/test/production release process is, but I would
suspect work has already begun adding changes to the server model based on
the proposed ADIF changes.
I donât really understand the urgency here. All one must do is hold back
their FT8 QSOâs until the LoTW server is ready to accept them (as FT8 QSOâs
that is). This situation âis not newâ, it happens with every new mode /
sub-mode introduction.
73âs
Greg, KI7MT
*Sent:* Tuesday, July 18, 2017 10:15 AM
*Subject:* Re: [wsjt-devel] TQSL's config.xml
3.0.6 has not had finally approval yet.
eQSL is just implementing it early.
I doubt ARRL will ever touch a draft ADIF spec.
de Mike W9MDB
------------------------------
*Sent:* Tuesday, July 18, 2017 11:05 AM
*Subject:* [wsjt-devel] TQSL's config.xml
A question for smarter people than me.
TQSLâs config.xml contains all the modes acceptable to TQSL. Instead of
mapping FT8->DATA in TQSL, could I accomplish something similar but more
accurate by inserting a new XML coded line in config.xml?
Insert a line like: â<adifmode adif-mode="FT8" mode="FT8">FT8</adifmode>â
This might even be moot, since the new ADIF spec is out and includes FT8.
· LoTWâs website shows config.xmlâs latest iteration is v11.0.
No mention of which ADIF spec.
· ADIF.ORGâs website still shows v3.0.5 as the latest.
· eQSL says itâs using ADIF spec 3.0.6.
Itâs entirely possible that ARRL will update config.xml soon on its own.
Dan â 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
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
https://lists.sourceforge.net/lists/listinfo/wsjt-devel