Re: [wsjt-devel] TQSL's config.xml
Hi Dan, Yes, I understand. I stopped doing that sometime in the past, but couldn’t remember exactly “why”. Dave helped me understand it. I don’t make nearly as many QSO’s as I did when contesting “a lot”. Now, resubmitting a few QSO’s to LoTW isn’t that big of a deal. Back when I was making 1000’s of QSO’s per week/weekend, I wouldn’t not entertain the thought of going back and fishing out resubmissions. For now, I’m just waiting on LoTW to do their thing, then I’ll submit all the FT8 QSO’s. I did send a bunch to eQSL after somebody confirmed they were accepting them. 73’s Greg, KI7MT From: Dan Malcolm [mailto:dan.malcol...@gmail.com] Sent: Tuesday, July 18, 2017 4:28 PM To: 'WSJT software development' <wsjt-devel@lists.sourceforge.net> Subject: Re: [wsjt-devel] TQSL's config.xml Greg, My question was more for information than for a real intent. I have already done the FT8 mapping, and it is working quit well Dan-K4SHQ From: Greg Beam [mailto:ki7m...@gmail.com] Sent: Tuesday, July 18, 2017 12:00 PM To: 'WSJT software development' <wsjt-devel@lists.sourceforge.net <mailto:wsjt-devel@lists.sourceforge.net> > 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 From: Black Michael via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net] Sent: Tuesday, July 18, 2017 10:15 AM To: WSJT software development <wsjt-devel@lists.sourceforge.net <mailto:wsjt-devel@lists.sourceforge.net> > Cc: Black Michael <mdblac...@yahoo.com <mailto:mdblac...@yahoo.com> > 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 _ From: Dan Malcolm <dan.malcol...@gmail.com <mailto:dan.malcol...@gmail.com> > To: wsjtx-devel <wsjt-devel@lists.sourceforge.net <mailto:wsjt-devel@lists.sourceforge.net> > 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: “FT8” 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 wsjt-devel@lists.sourceforge.net <mailto: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
Re: [wsjt-devel] TQSL's config.xml
Thanks Dave, I was already aware of that and have done it. The question was more for information that real intent. Dan – K4SHQ From: Dave AA6YQ [mailto:aa...@ambersoft.com] Sent: Tuesday, July 18, 2017 12:21 PM To: 'WSJT software development' <wsjt-devel@lists.sourceforge.net> 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 From: Greg Beam [mailto:ki7m...@gmail.com] 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 From: Black Michael via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net] Sent: Tuesday, July 18, 2017 10:15 AM To: WSJT software development <wsjt-devel@lists.sourceforge.net <mailto:wsjt-devel@lists.sourceforge.net> > Cc: Black Michael <mdblac...@yahoo.com <mailto:mdblac...@yahoo.com> > 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 _ From: Dan Malcolm <dan.malcol...@gmail.com <mailto:dan.malcol...@gmail.com> > To: wsjtx-devel <wsjt-devel@lists.sourceforge.net <mailto:wsjt-devel@lists.sourceforge.net> > 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: “FT8” 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 wsjt-devel@lists.sourceforge.net <mailto: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
Re: [wsjt-devel] TQSL's config.xml
Greg, My question was more for information than for a real intent. I have already done the FT8 mapping, and it is working quit well Dan-K4SHQ From: Greg Beam [mailto:ki7m...@gmail.com] Sent: Tuesday, July 18, 2017 12:00 PM To: 'WSJT software development' <wsjt-devel@lists.sourceforge.net> 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 From: Black Michael via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net] Sent: Tuesday, July 18, 2017 10:15 AM To: WSJT software development <wsjt-devel@lists.sourceforge.net <mailto:wsjt-devel@lists.sourceforge.net> > Cc: Black Michael <mdblac...@yahoo.com <mailto:mdblac...@yahoo.com> > 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 _ From: Dan Malcolm <dan.malcol...@gmail.com <mailto:dan.malcol...@gmail.com> > To: wsjtx-devel <wsjt-devel@lists.sourceforge.net <mailto:wsjt-devel@lists.sourceforge.net> > 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: “FT8” 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 wsjt-devel@lists.sourceforge.net <mailto: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
Re: [wsjt-devel] TQSL's config.xml
Hi Dave, OK, thanks for clearing that up. I knew something wasn’t straight forward, but could not recall what it was. The resubmission part is what was missing. Thanks Greg From: Dave AA6YQ [mailto:aa...@ambersoft.com] Sent: Tuesday, July 18, 2017 2:01 PM To: 'WSJT software development' <wsjt-devel@lists.sourceforge.net> Subject: Re: [wsjt-devel] TQSL's config.xml >>>AA6YQ comments below From: Greg Beam [mailto:ki7m...@gmail.com] Sent: Tuesday, July 18, 2017 2:02 PM To: 'WSJT software development' Subject: Re: [wsjt-devel] TQSL's config.xml Hi 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. >>>That’s not correct. When LoTW accepts FT8 QSOs directly, you can remove the >>>automatic mapping to DATA from TQSL. At that point in time, it would be >>>polite to resubmit your FT8 QSOs to LoTW so that QSO partners pursuing an >>>FT8 WAS endorsement (if one is introduced) will get the “exact mode matches” >>>they need. 73, Dave, AA6YQ -- 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
Re: [wsjt-devel] TQSL's config.xml
>>>AA6YQ comments below From: Greg Beam [mailto:ki7m...@gmail.com] Sent: Tuesday, July 18, 2017 2:02 PM To: 'WSJT software development' Subject: Re: [wsjt-devel] TQSL's config.xml Hi 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. >>>That’s not correct. When LoTW accepts FT8 QSOs directly, you can remove the >>>automatic mapping to DATA from TQSL. At that point in time, it would be >>>polite to resubmit your FT8 QSOs to LoTW so that QSO partners pursuing an >>>FT8 WAS endorsement (if one is introduced) will get the “exact mode matches” >>>they need. 73, Dave, AA6YQ -- 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
Re: [wsjt-devel] TQSL's config.xml
YES eqsl uploades ft8 ok On 18 July 2017 at 19:20, Ryan Tourge <ryan.tou...@gmail.com> wrote: > 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. > > On Tue, Jul 18, 2017 at 2:02 PM, Greg Beam <ki7m...@gmail.com> wrote: > >> Hi 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 >> >> >> >> >> >> *From:* Dave AA6YQ [mailto:aa...@ambersoft.com] >> *Sent:* Tuesday, July 18, 2017 11:21 AM >> *To:* 'WSJT software development' <wsjt-devel@lists.sourceforge.net> >> *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 >> >> >> >> >> >> >> >> *From:* Greg Beam [mailto:ki7m...@gmail.com <ki7m...@gmail.com>] >> *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 >> >> >> >> *From:* Black Michael via wsjt-devel [mailto:wsjt-devel@lists.sourc >> eforge.net <wsjt-devel@lists.sourceforge.net>] >> *Sent:* Tuesday, July 18, 2017 10:15 AM >> *To:* WSJT software development <wsjt-devel@lists.sourceforge.net> >> *Cc:* Black Michael <mdblac...@yahoo.com> >> *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 >> >> >> >> >> -- >> >> *From:* Dan Malcolm <dan.malcol...@gmail.com> >> *To:* wsjtx-devel <wsjt-devel@lists.sourceforge.net> >> *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: “FT8” >> >> >> >> 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. >> >> · eQS
Re: [wsjt-devel] TQSL's config.xml
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. On Tue, Jul 18, 2017 at 2:02 PM, Greg Beam <ki7m...@gmail.com> wrote: > Hi 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 > > > > > > *From:* Dave AA6YQ [mailto:aa...@ambersoft.com] > *Sent:* Tuesday, July 18, 2017 11:21 AM > *To:* 'WSJT software development' <wsjt-devel@lists.sourceforge.net> > *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 > > > > > > > > *From:* Greg Beam [mailto:ki7m...@gmail.com <ki7m...@gmail.com>] > *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 > > > > *From:* Black Michael via wsjt-devel [mailto:wsjt-devel@lists. > sourceforge.net <wsjt-devel@lists.sourceforge.net>] > *Sent:* Tuesday, July 18, 2017 10:15 AM > *To:* WSJT software development <wsjt-devel@lists.sourceforge.net> > *Cc:* Black Michael <mdblac...@yahoo.com> > *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 > > > > > -- > > *From:* Dan Malcolm <dan.malcol...@gmail.com> > *To:* wsjtx-devel <wsjt-devel@lists.sourceforge.net> > *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: “FT8” > > > > 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 > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > > > -- > Check out the vibrant tech community
Re: [wsjt-devel] TQSL's config.xml
Hi 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 From: Dave AA6YQ [mailto:aa...@ambersoft.com] Sent: Tuesday, July 18, 2017 11:21 AM To: 'WSJT software development' <wsjt-devel@lists.sourceforge.net> 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 From: Greg Beam [mailto:ki7m...@gmail.com] 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 From: Black Michael via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net] Sent: Tuesday, July 18, 2017 10:15 AM To: WSJT software development <wsjt-devel@lists.sourceforge.net <mailto:wsjt-devel@lists.sourceforge.net> > Cc: Black Michael <mdblac...@yahoo.com <mailto:mdblac...@yahoo.com> > 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 _ From: Dan Malcolm <dan.malcol...@gmail.com <mailto:dan.malcol...@gmail.com> > To: wsjtx-devel <wsjt-devel@lists.sourceforge.net <mailto:wsjt-devel@lists.sourceforge.net> > 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: “FT8” 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 wsjt-devel@lists.sourceforge.net <mailto: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
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 From: Greg Beam [mailto:ki7m...@gmail.com] 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 From: Black Michael via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net] Sent: Tuesday, July 18, 2017 10:15 AM To: WSJT software development <wsjt-devel@lists.sourceforge.net> Cc: Black Michael <mdblac...@yahoo.com> 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 _ From: Dan Malcolm <dan.malcol...@gmail.com> To: wsjtx-devel <wsjt-devel@lists.sourceforge.net> 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: “FT8” 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 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
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 From: Black Michael via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net] Sent: Tuesday, July 18, 2017 10:15 AM To: WSJT software development <wsjt-devel@lists.sourceforge.net> Cc: Black Michael <mdblac...@yahoo.com> 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 _ From: Dan Malcolm <dan.malcol...@gmail.com <mailto:dan.malcol...@gmail.com> > To: wsjtx-devel <wsjt-devel@lists.sourceforge.net <mailto:wsjt-devel@lists.sourceforge.net> > 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: “FT8” 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 wsjt-devel@lists.sourceforge.net <mailto: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
Re: [wsjt-devel] TQSL's config.xml
Mike, I agree with that assessment. I did not realize that ADIF 3.0.6 was still draft, but since it is, that explains a lot. While changing my end is easy, that doesn’t make it the right thing to do. I will stay with what I have until ARRL makes the change. From: Black Michael via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net] Sent: Tuesday, July 18, 2017 11:15 AM To: WSJT software development <wsjt-devel@lists.sourceforge.net> Cc: Black Michael <mdblac...@yahoo.com> 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 _ From: Dan Malcolm <dan.malcol...@gmail.com <mailto:dan.malcol...@gmail.com> > To: wsjtx-devel <wsjt-devel@lists.sourceforge.net <mailto:wsjt-devel@lists.sourceforge.net> > 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: “FT8” 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 wsjt-devel@lists.sourceforge.net <mailto: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
Re: [wsjt-devel] TQSL's config.xml
Bill, I had that same thought, hence my query. While changing my end is easy, that doesn't make it the right thing to do. I will stay with what I have until ARRL makes the change. Thanks Dan - K4SHQ From: Bill Somerville [mailto:g4...@classdesign.com] Sent: Tuesday, July 18, 2017 11:08 AM To: wsjt-devel@lists.sourceforge.net Subject: Re: [wsjt-devel] TQSL's config.xml On 18/07/2017 17:02, Dan Malcolm wrote: 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: "FT8" Hi Dan, I doubt that will work as it probably has to match capability on the LotW server which will not be prepared to accept ADIF records from you specifying the mode as FT8. I would take the tQSL configuration file as private to the LotW developers and leave it alone. 73 Bill G4WJS. -- 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
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 From: Dan Malcolm <dan.malcol...@gmail.com> To: wsjtx-devel <wsjt-devel@lists.sourceforge.net> 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: “FT8” 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 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
Re: [wsjt-devel] TQSL's config.xml
On 18/07/2017 17:02, Dan Malcolm wrote: 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: “FT8” Hi Dan, I doubt that will work as it probably has to match capability on the LotW server which will not be prepared to accept ADIF records from you specifying the mode as FT8. I would take the tQSL configuration file as private to the LotW developers and leave it alone. 73 Bill G4WJS. -- 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
[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: "FT8" 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 wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
