Date   
Re: FT4 not showing up in LoTW WAS Account Status and others

Dave AA6YQ
 

+ AA6YQ comments below

Several days ago I received my first LoTW confirmation on an FT4 QSO. I thought that it would show up in my WAS Awards Account.

+ What led you to that conclusion?


NOT SO ! ! !

FT4 needs to be added to the WAS Accounts Status and to the Account Credits under the ALL CREDITS and also under the Pending Credits.

+ That would only be appropriate if the ARRL had announced an FT4 endorsement for WAS. It has not done so.


Why does it take so long for LoTW to respond to new and accepted modes like FT4 into their WAS Accounts ? ? ?

+ Since the ARRL has not announced an FT4 endorsement for WAS, it's inappropriate to criticize the LoTW staff not implementing it.

73,

Dave, AA6YQ

Re: FT4 not showing up in LoTW WAS Account Status and others

Jim - N4ST
 

Who knows?
There are many digital modes that are not individually recognized for WAS, just grouped as Data.
And then there are modes that were recognized and now are "obsolete" because they have been superseded by superior modes.
I have WAS with JT9 and JT65 and now those are barely in use.
I doubt I will ever finish PSK125, ISCAT, FSK144, or HELL

____________
73,
Jim - N4ST

From: ARRL-LoTW@groups.io <ARRL-LoTW@groups.io> On Behalf Of NE8S ~ Doc
Sent: Saturday, July 20, 2019 10:36
To: ARRL-LoTW@groups.io
Subject: [ARRL-LoTW] FT4 not showing up in LoTW WAS Account Status and others

Several days ago I received my first LoTW confirmation on an FT4 QSO. I thought that it would show up in my WAS Awards Account. NOT SO ! ! !

FT4 needs to be added to the WAS Accounts Status and to the Account Credits under the ALL CREDITS and also under the Pending Credits.

Why does it take so long for LoTW to respond to new and accepted modes like FT4 into their WAS Accounts ? ? ?

FT4 not showing up in LoTW WAS Account Status and others

NE8S ~ Doc
 

Several days ago I received my first LoTW confirmation on an FT4 QSO. I thought that it would show up in my WAS Awards Account. NOT SO ! ! !

FT4 needs to be added to the WAS Accounts Status and to the Account Credits under the ALL CREDITS and also under the Pending Credits.

Why does it take so long for LoTW to respond to new and accepted modes like FT4 into their WAS Accounts ? ? ?

Re: Downloaded FT4 QSOs not Verified.

Jim - N4ST
 

Al,
Make sure that in your HRD Logbook you have configured the mode FT4 to map to FT4.
If you have it mapped to MFSK, then LoTW will log it as DATA.

___________
73,
Jim – N4ST


From: ARRL-LoTW@groups.io <ARRL-LoTW@groups.io> On Behalf Of Alfred Reeves
Sent: Friday, July 19, 2019 11:54
To: ARRL-LoTW@groups.io
Subject: Re: [ARRL-LoTW] Downloaded FT4 QSOs not Verified.

Both unconfirmed and confirmed. What logging program do you upload from? I'm using the latest ver of Ham Radio Deluxe.

TNX
Al
W1JHU

Re: Downloaded FT4 QSOs not Verified.

Rick Murphy
 

On Fri, Jul 19, 2019 at 5:48 PM Joe Subich, W4TV <lists@...> wrote:

HRD *MUST* export an FT4 QSO with <MODE:4>MFSK <SUBMODE:3>FT4 in
order for tQSL to recognize it correctly. 

If I may, a slight correction.
TQSL will happily accept <MODE:3>FT4 and treat it the same as the MODE/SUBMODE pair.

Perhaps removing this FT4 to MFSK configuration in HRD will make uploaded QSOs appear correctly.

Postel's Robustness Principle: "Be conservative in what you send, be liberal in what you accept."
That "<MODE:3>FT4" is strictly incorrect, but TQSL will allow it.
73,
    -Rick
--
Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA

Re: Downloaded FT4 QSOs not Verified.

Joe Subich, W4TV
 

Your HRD Logbook -> Configure -> Modes file maps FT4 to MFSK with
*NO SUBMODE*. tQSL treats MFSK without a submode (line 76 of the
<adifmap> section of config.xml (version 8.11)) as DATA.

HRD *MUST* export an FT4 QSO with <MODE:4>MFSK <SUBMODE:3>FT4 in
order for tQSL to recognize it correctly. The Developers of
HRD must absolutely fix their software to export the correct
MODE AND SUBMODE. That is not the case in version 6.6.0.236 -
the HRD LOG IS BUGGY.

You *MAY* be able to work around the bug in HRD by trying the
following:

1) Change the HRD Modes file from FT4 -> MFSK to FT4 -> FT4

The author of tQSL reported that the current version of tQSL has
a bug that permits accepting "MODE:3>FT4" but he has fixed the
bug in the next release of tQSL.

Again, what change did you make on or about 7/16 to trigger this
"new" (?) behavior?

73,

... Joe, W4TV

On 2019-07-19 5:09 PM, Alfred Reeves wrote:
On 7/19/2019 4:58 PM, Joe Subich, W4TV wrote:

When I log a FT4 QSO the mode displayed in my HRD log shows FT4. Then
when I upload that FT4 QSO to LOTW and view the uploaded QSO (Most
Recent QSOs) the mode is displayed as "DATA".
1) Where (what screen/display) are you seeing "DATA" - please post a
screen capture here.
Capture:


2) Please post a screen capture of  tQSL -> File -> Display or Modify
Preferences -> ADIF Modes here
Capture:


I might add that this situation only began around 7/16. Prior
to the 16th all my FT4 QSOs that I uploaded were displayed as FT4 on
LOTW.*//* So it appears that something changed around the 16th.
What changes did you make to your computer/software around 7/16?

What values are in your HRD Logbook -> Configure -> Modes file for FT4?
Have you consulted HRD Support for the correct way to handle MODE/SUBMODE - I do not see that capability yet in HRD 6.6.0.236.
Capture HRD Mapping:
Capture:

73,

   ... Joe, W4TV

Re: Downloaded FT4 QSOs not Verified.

Alfred Reeves
 



On 7/19/2019 4:58 PM, Joe Subich, W4TV wrote:

When I log a FT4 QSO the mode displayed in my HRD log shows FT4. Then
when I upload that FT4 QSO to LOTW and view the uploaded QSO (Most
Recent QSOs) the mode is displayed as "DATA".
1) Where (what screen/display) are you seeing "DATA" - please post a
screen capture here.
Capture:


2) Please post a screen capture of  tQSL -> File -> Display or Modify
Preferences -> ADIF Modes here
Capture:


> I might add that this situation only began around 7/16. Prior
> to the 16th all my FT4 QSOs that I uploaded were displayed as FT4 on
> LOTW.*//* So it appears that something changed around the 16th.

What changes did you make to your computer/software around 7/16?

What values are in your HRD Logbook -> Configure -> Modes file for FT4?
Have you consulted HRD Support for the correct way to handle MODE/SUBMODE - I do not see that capability yet in HRD 6.6.0.236.
Capture HRD Mapping:

Capture:

73,

   ... Joe, W4TV


On 2019-07-19 2:29 PM, Alfred Reeves wrote:
Dave:

Thank you your reply.  To answer your question: */Let's start with "what leads you conclude that the Mode of your submitted QSOs is being changed from FT4 to DATA"? Please be as specific as you can.
/*Answer: First of all, I'm using the latest version of Ham Radio Deluxe (HRD) for logging as well as uploading and downloading QSO to LOTW.*//*I have been using it for over 15 years with no issues.  When I log a FT4 QSO the mode displayed in my HRD log shows FT4. Then when I upload that FT4 QSO to LOTW and view the uploaded QSO (Most Recent QSOs) the mode is displayed as "DATA".  A change from the FT4 mode in my HRD log that I uploaded.  I might add that this situation only began around 7/16. Prior to the 16th all my FT4 QSOs that I uploaded were displayed as FT4 on LOTW.*//* So it appears that something changed around the 16th.  I can confirm that no changes were made here with HRD. */

/*Hope this make my situation clearer.  I appreciate any help yo can render to resolve the issue.

TNX
Al
W1JHU*/
/*




On 7/19/2019 1:55 PM, Dave AA6YQ wrote:
+ AA6YQ comments below:

Thanks for your reply.  I am running the 11.8 config.xml and latest TQSL.  All was OK until ARRL began changing the FT4 QSOs as "DATA" and not FT4 as was uploaded.

+ The ARRL has never done that.

When they were tagging them FT4 all was OK.  Only when they changed the tag to DATA did things go to pot.  There is no "DATA" mode stated in the latest ADIF Spec. so why is ARRL changing them to "DATA"?  Seems to me it's an ARRL issue.

+ Let's start with "what leads you conclude that the Mode of your submitted QSOs is being changed from FT4 to DATA"? Please be as specific as you can.

+ Just to be clear, I'm not seeking to argue with you, I am seeking to help you.

             73,

                 Dave, AA6YQ







Re: Downloaded FT4 QSOs not Verified.

Joe Subich, W4TV
 

When I log a FT4 QSO the mode displayed in my HRD log shows FT4. Then
when I upload that FT4 QSO to LOTW and view the uploaded QSO (Most
Recent QSOs) the mode is displayed as "DATA".
1) Where (what screen/display) are you seeing "DATA" - please post a
screen capture here.

2) Please post a screen capture of tQSL -> File -> Display or Modify
Preferences -> ADIF Modes here

I might add that this situation only began around 7/16. Prior
to the 16th all my FT4 QSOs that I uploaded were displayed as FT4 on
LOTW.*//* So it appears that something changed around the 16th.
What changes did you make to your computer/software around 7/16?

What values are in your HRD Logbook -> Configure -> Modes file for FT4?
Have you consulted HRD Support for the correct way to handle MODE/SUBMODE - I do not see that capability yet in HRD 6.6.0.236.

73,

... Joe, W4TV


On 2019-07-19 2:29 PM, Alfred Reeves wrote:
Dave:
Thank you your reply.  To answer your question: */Let's start with "what leads you conclude that the Mode of your submitted QSOs is being changed from FT4 to DATA"? Please be as specific as you can.
/*Answer: First of all, I'm using the latest version of Ham Radio Deluxe (HRD) for logging as well as uploading and downloading QSO to LOTW.*//*I have been using it for over 15 years with no issues.  When I log a FT4 QSO the mode displayed in my HRD log shows FT4. Then when I upload that FT4 QSO to LOTW and view the uploaded QSO (Most Recent QSOs) the mode is displayed as "DATA".  A change from the FT4 mode in my HRD log that I uploaded.  I might add that this situation only began around 7/16. Prior to the 16th all my FT4 QSOs that I uploaded were displayed as FT4 on LOTW.*//* So it appears that something changed around the 16th.  I can confirm that no changes were made here with HRD. */
/*Hope this make my situation clearer.  I appreciate any help yo can render to resolve the issue.
TNX
Al
W1JHU*/
/*
On 7/19/2019 1:55 PM, Dave AA6YQ wrote:
+ AA6YQ comments below:

Thanks for your reply.  I am running the 11.8 config.xml and latest TQSL.  All was OK until ARRL began changing the FT4 QSOs as "DATA" and not FT4 as was uploaded.

+ The ARRL has never done that.

When they were tagging them FT4 all was OK.  Only when they changed the tag to DATA did things go to pot.  There is no "DATA" mode stated in the latest ADIF Spec. so why is ARRL changing them to "DATA"? Seems to me it's an ARRL issue.

+ Let's start with "what leads you conclude that the Mode of your submitted QSOs is being changed from FT4 to DATA"? Please be as specific as you can.

+ Just to be clear, I'm not seeking to argue with you, I am seeking to help you.

             73,

                 Dave, AA6YQ

Re: Downloaded FT4 QSOs not Verified.

Dave AA6YQ
 

+ AA6YQ comments below

I do not believe people are creating mappings for modes in TQSL.

+ I did back in early May -- not because I was impatient, but to check out the mechanism to be sure everything worked correctly.

I was not, and did not know that ability even existed until this email chain. For me TQSL is a small utility piece of software that I must interact with very infrequently. HRD lets me select log entries and upload them to LOTW by running TQSL in the background

Sure we can all resubmit the QSO when everything is defined in the future, but the issue I see is why even allow QSO to be submitted with an improper mode defined. These QSO's will not count for anything!

+ That's not correct. If you submitted an FT4 QSO back in early May before LoTW accepted FT4 QSOs (because ADIF hadn't standardized the mode representation yet) and submitted it to LoTW by configuring TQSL to map FT4 to DATA, and if your QSO partners did the same thing, then the LoTW confirmations created were valid for DXCC, VUCC, WAS, WAZ, and WPX -- mixed, by band, and in digital mode. These confirmations were only "deficient" in that they would not count for an FT4 WAS endorsement, if the ARRL ever offered one. After ADIF and ARRL acted, that deficiency could be removed by removing the "FT4>DATA" mode map from TQSL and resubmitting your FT4 QSOs to LoTW; after your QSO partners did the same thing, your confirmed FT4 QSOs would be valid for a WAS FT4 endorsement.

All this does is to create a lot of zombies in LOTW.

+ That's false, as described above. LoTW confirmations of QSOs whose mode is DATA are valid for all ARRL and CQ awards except WAS FT4 endorsements.


Since FT4 software has been released there will be more and more hams using it and this just compound the problem. There will eventually be a cost for the zombies in LOTW.

+ The cost of mass storage continues to decline. Hopefully LoTW will someday be extended to permit users to hide their "zombie QSOs", but there is no compelling economic reason to delete them, and the economic incentive will continue to decrease.


There is another cost of the hams spending time in this email chain too.

+ Is there anyone having difficulty with FT4 QSOs in LoTW that is using a logging application other than HRD?

73,

Dave, AA6YQ

Re: Downloaded FT4 QSOs not Verified.

chuck.gooden
 

Dave,

I do not believe people are creating mappings for modes in TQSL. I was not, and did not know that ability even existed until this email chain.  For me TQSL is a small utility piece of software that I must interact with very infrequently.  HRD lets me select log entries and upload them to LOTW by running TQSL in the background

Sure we can all resubmit the QSO when everything is defined in the future, but the issue I see is why even allow QSO to be submitted with an improper mode defined.  These QSO's will not count for anything!  All this does is to create a lot of zombies in LOTW.    Since FT4 software has been released there will be more and more hams using it and this just compound the problem. There will eventually be a cost for the zombies in LOTW.  There is another cost of the hams spending time in this email chain too.

I will probably go back to using FT8, SSB, and FSK until the issues get worked out with FT4.  This is the end of discussion for me.  I have better things to do!!

Chuck K9LC

On 7/19/2019 1:14 PM, Dave AA6YQ wrote:
+ AA6YQ comments below

In my opinion, this should of never happened until the FT4 requirements are defined and implemented. Skipping steps, and allowing developers to chose their implementation leads to chaos. The confirmations could of waited until the ADIF requirements were determined and implemented. Once this was done then the logs could of been uploaded and processed by LOTW for confirmations.

+ No one was required to create an FT4=>DATA mapping in TQSL so they could immediately submit FT4 QSOs to LoTW. Users were free to patiently wait a few weeks until ADIF approved an FT4 mode representation for FT4 and the ARRL released an updated Config.xml file, and then submitted all of their FT4 QSOs made to date.

+ Anyone who did create an FT4=>DATA mapping in TQSL so they could immediately submit FT4 QSOs to LoTW could -- after ADIF and the ARRL acted -- remove that mapping, and then resubmit all of their FT4 QSOs.

+ Is it unreasonable to expect users who created an FT4=>DATA mapping in TQSL to remember that they did so?

+ Since one can remove the FT4=>DATA mapping and resubmit one's FT4 QSOs, there's no actual penalty for forgetting.

73,

Dave, AA6YQ




Re: Downloaded FT4 QSOs not Verified.

Dave AA6YQ
 

+ AA6YQ comments below

My understanding is that, when FT4 first appeared and the ADIF standard was not yet set, logging programs were using DATA as a default.

+ Some logging applications may have done so, but that action was unnecessary. The recommended way to support impatient users of a new digital mode whose "representation" has not yet been approved by ADIF is for those users to add a mapping to DATA in TQSL, as described in

<https://lotw.arrl.org/lotw-help/pref-adi/>

+ After ADIF approves the new mode's representation and the ARRL releases a Config.xml file for that new representation, those users who added a mapping to DATA in TQSL should remove that mapping, and resubmit their logged QSOs made in the new digital mode.

+ There are no users of DXLab reporting that FT4 QSOs are not being correctly submitted to LoTW.

73,

Dave, AA6YQ

Re: Downloaded FT4 QSOs not Verified.

Dave AA6YQ
 

+ AA6YQ comments below

I do not know what caused persons to create a mapping of FT4 to data, but apparently there was something that caused this, and now its effecting nearly everyone using FT4.

+ Only you (via TQSL) or your logging application can map FT4 to DATA in the QSOs you submit to LoTW.

73,

Dave, AA6YQ

Re: Downloaded FT4 QSOs not Verified.

Dave AA6YQ
 

+ AA6YQ comments below

Thank you your reply. To answer your question: Let's start with "what leads you conclude that the Mode of your submitted QSOs is being changed from FT4 to DATA"? Please be as specific as you can.

Answer: First of all, I'm using the latest version of Ham Radio Deluxe (HRD) for logging as well as uploading and downloading QSO to LOTW. I have been using it for over 15 years with no issues. When I log a FT4 QSO the mode displayed in my HRD log shows FT4. Then when I upload that FT4 QSO to LOTW and view the uploaded QSO (Most Recent QSOs) the mode is displayed as "DATA".

+ If the "Most Recent QSOs" displays of DATA, then I can see only two possibilities:

1. you have TQSL configured to "map" FT4 QSOs to DATA

2. HRD is sending your FT4 QSOs to LoTW with a mode of DATA

+ To determine whether you have TQSL configured to "map" FT4 QSOs to DATA, see

< https://lotw.arrl.org/lotw-help/pref-adi/>

+ Please post your findings.

73,

Dave, AA6YQ

Re: Downloaded FT4 QSOs not Verified.

Rick Murphy
 

Oh, and in the process of testing this, I found a defect in the embedded ADIF editor in TQSL.

When you enter a FT4 QSO while creating an ADIF file, it was saving this as "<MODE:3>FT4".  That's not valid.
TQSL will actually accept that and upload as a FT4 QSO. It also, of course, accepts the valid "<MODE:4>MFSK<SUBMODE:3>FT4" 

I've fixed this for the next TQSL release.
73,
    -Rick

On Fri, Jul 19, 2019 at 2:35 PM Rick Murphy via Groups.Io <k1mu.nospam=gmail.com@groups.io> wrote:
Alfred,
No logging program, using a bare ADIF file.

LoTW isn't your problem.  I presume that it's something with HRD emitting the QSOs as DATA. Please reach out to them for help.
73,
    -Rick

On Fri, Jul 19, 2019 at 2:29 PM Alfred Reeves <areeves18@...> wrote:
Dave:

Thank you your reply.  To answer your question:
Let's start with "what leads you conclude that the Mode of your submitted QSOs is being changed from FT4 to DATA"? Please be as specific as you can.
Answer: First of all, I'm using the latest version of Ham Radio Deluxe (HRD) for logging as well as uploading and downloading QSO to LOTW.  I have been using it for over 15 years with no issues.  When I log a FT4 QSO the mode displayed in my HRD log shows FT4. Then when I upload that FT4 QSO to LOTW and view the uploaded QSO (Most Recent QSOs) the mode is displayed as "DATA".  A change from the FT4 mode in my HRD log that I uploaded.  I might add that this situation only began around 7/16.  Prior to the 16th all my FT4 QSOs that I uploaded were displayed as FT4 on LOTW.  So it appears that something changed around the 16th.  I can confirm that no changes were made here with HRD. 

Hope this make my situation clearer.  I appreciate any help yo can render to resolve the issue.

TNX
Al
W1JHU





On 7/19/2019 1:55 PM, Dave AA6YQ wrote:
+ AA6YQ comments below:

Thanks for your reply.  I am running the 11.8 config.xml and latest TQSL.  All was OK until ARRL began changing the FT4 QSOs as "DATA" and not FT4 as was uploaded.

+ The ARRL has never done that.

When they were tagging them FT4 all was OK.  Only when they changed the tag to DATA did things go to pot.  There is no "DATA" mode stated in the latest ADIF Spec. so why is ARRL changing them to "DATA"?  Seems to me it's an ARRL issue.

+ Let's start with "what leads you conclude that the Mode of your submitted QSOs is being changed from FT4 to DATA"? Please be as specific as you can.

+ Just to be clear, I'm not seeking to argue with you, I am seeking to help you.

            73,

                Dave, AA6YQ








--
Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA



--
Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA

Re: Newbie

C. Morrissey
 

Tnx Wes - vry helpful info - Chuck

On 7/19/2019 2:05 PM, Wes Attaway (N5WA) wrote:
Chuck and others .....

Among other things it is good to know and remember that not every ham
operator uses LOTW. If they don't use LOTW then you will never get a
confirmation via LOTW.

If you get a QSL card then you can go through the LOTW online application
process which does include having any QSL cards checked by a certified card
checker.

So, keep these two things in mind. QSL cards are often still required and
must be checked and must be submitted by the standard "old fashioned"
application process.

-------------------
Wes Attaway (N5WA)
(318) 393-3289 - Shreveport, LA
Computer/Cellphone Forensics
AttawayForensics.com
-------------------

-----Original Message-----
From: ARRL-LoTW@groups.io [mailto:ARRL-LoTW@groups.io] On Behalf Of Dave
AA6YQ
Sent: Friday, July 19, 2019 12:52 PM
To: ARRL-LoTW@groups.io
Subject: Re: [ARRL-LoTW] Newbie

+ AA6YQ comments below

Chuck, I don't think that you understand what LOTW is!?? It is ONLY a way to
get conformations for qso's just like paper qsl cards.?? You still have to
APPLY those conformations to the award that you are after.?? And that is
after your LOTW account is linked to your DXCC accouny.?? Understand that
they are two different things. That said, after you apply what ever qsos
that you have to your aware (DXCC, WAS, whatever).?? You can then see those
qso confirmations in both LOTW and your award account.?? It is much harder
to explain it then it really is in action.
I hope this helps a little.

+ Perhaps this state diagram will help:

<https://lotw.arrl.org/lotw-help/qso-states/>

+ It illustrates that a confirmed QSO can be granted award credit for DXCC,
VUCC, WAS, WAZ, and WPX. As stated above, a confirmed QSO must be included
in an application for an award in order to be granted credit for that award.

+ For example, this article explains how to submit confirmed QSOs for DXCC
awards:

<https://lotw.arrl.org/lotw-help/dxcc-award-credit/>

73,

Dave, AA6YQ





Re: Newbie

C. Morrissey
 

Tnx info

On 7/19/2019 1:52 PM, Dave AA6YQ wrote:
+ AA6YQ comments below

Chuck, I don't think that you understand what LOTW is!?? It is ONLY a way to get conformations for qso's just like paper qsl cards.?? You still have to APPLY those conformations to the award that you are after.?? And that is after your LOTW account is linked to your DXCC accouny.?? Understand that they are two different things. That said, after you apply what ever qsos that you have to your aware (DXCC, WAS, whatever).?? You can then see those qso confirmations in both LOTW and your award account.?? It is much harder to explain it then it really is in action.
I hope this helps a little.

+ Perhaps this state diagram will help:

<https://lotw.arrl.org/lotw-help/qso-states/>

+ It illustrates that a confirmed QSO can be granted award credit for DXCC, VUCC, WAS, WAZ, and WPX. As stated above, a confirmed QSO must be included in an application for an award in order to be granted credit for that award.

+ For example, this article explains how to submit confirmed QSOs for DXCC awards:

<https://lotw.arrl.org/lotw-help/dxcc-award-credit/>

73,

Dave, AA6YQ


Re: Downloaded FT4 QSOs not Verified.

Rick Murphy
 

Alfred,
No logging program, using a bare ADIF file.

LoTW isn't your problem.  I presume that it's something with HRD emitting the QSOs as DATA. Please reach out to them for help.
73,
    -Rick

On Fri, Jul 19, 2019 at 2:29 PM Alfred Reeves <areeves18@...> wrote:
Dave:

Thank you your reply.  To answer your question:
Let's start with "what leads you conclude that the Mode of your submitted QSOs is being changed from FT4 to DATA"? Please be as specific as you can.
Answer: First of all, I'm using the latest version of Ham Radio Deluxe (HRD) for logging as well as uploading and downloading QSO to LOTW.  I have been using it for over 15 years with no issues.  When I log a FT4 QSO the mode displayed in my HRD log shows FT4. Then when I upload that FT4 QSO to LOTW and view the uploaded QSO (Most Recent QSOs) the mode is displayed as "DATA".  A change from the FT4 mode in my HRD log that I uploaded.  I might add that this situation only began around 7/16.  Prior to the 16th all my FT4 QSOs that I uploaded were displayed as FT4 on LOTW.  So it appears that something changed around the 16th.  I can confirm that no changes were made here with HRD. 

Hope this make my situation clearer.  I appreciate any help yo can render to resolve the issue.

TNX
Al
W1JHU





On 7/19/2019 1:55 PM, Dave AA6YQ wrote:
+ AA6YQ comments below:

Thanks for your reply.  I am running the 11.8 config.xml and latest TQSL.  All was OK until ARRL began changing the FT4 QSOs as "DATA" and not FT4 as was uploaded.

+ The ARRL has never done that.

When they were tagging them FT4 all was OK.  Only when they changed the tag to DATA did things go to pot.  There is no "DATA" mode stated in the latest ADIF Spec. so why is ARRL changing them to "DATA"?  Seems to me it's an ARRL issue.

+ Let's start with "what leads you conclude that the Mode of your submitted QSOs is being changed from FT4 to DATA"? Please be as specific as you can.

+ Just to be clear, I'm not seeking to argue with you, I am seeking to help you.

            73,

                Dave, AA6YQ








--
Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA

Re: Downloaded FT4 QSOs not Verified.

Alfred Reeves
 

Dave:

Thank you your reply.  To answer your question:
Let's start with "what leads you conclude that the Mode of your submitted QSOs is being changed from FT4 to DATA"? Please be as specific as you can.
Answer: First of all, I'm using the latest version of Ham Radio Deluxe (HRD) for logging as well as uploading and downloading QSO to LOTW.  I have been using it for over 15 years with no issues.  When I log a FT4 QSO the mode displayed in my HRD log shows FT4. Then when I upload that FT4 QSO to LOTW and view the uploaded QSO (Most Recent QSOs) the mode is displayed as "DATA".  A change from the FT4 mode in my HRD log that I uploaded.  I might add that this situation only began around 7/16.  Prior to the 16th all my FT4 QSOs that I uploaded were displayed as FT4 on LOTW.  So it appears that something changed around the 16th.  I can confirm that no changes were made here with HRD. 

Hope this make my situation clearer.  I appreciate any help yo can render to resolve the issue.

TNX
Al
W1JHU





On 7/19/2019 1:55 PM, Dave AA6YQ wrote:
+ AA6YQ comments below:

Thanks for your reply.  I am running the 11.8 config.xml and latest TQSL.  All was OK until ARRL began changing the FT4 QSOs as "DATA" and not FT4 as was uploaded.

+ The ARRL has never done that.

When they were tagging them FT4 all was OK.  Only when they changed the tag to DATA did things go to pot.  There is no "DATA" mode stated in the latest ADIF Spec. so why is ARRL changing them to "DATA"?  Seems to me it's an ARRL issue.

+ Let's start with "what leads you conclude that the Mode of your submitted QSOs is being changed from FT4 to DATA"? Please be as specific as you can.

+ Just to be clear, I'm not seeking to argue with you, I am seeking to help you.

            73,

                Dave, AA6YQ






Re: Downloaded FT4 QSOs not Verified.

Dave AA6YQ
 

+ AA6YQ comments below

In my opinion, this should of never happened until the FT4 requirements are defined and implemented. Skipping steps, and allowing developers to chose their implementation leads to chaos. The confirmations could of waited until the ADIF requirements were determined and implemented. Once this was done then the logs could of been uploaded and processed by LOTW for confirmations.

+ No one was required to create an FT4=>DATA mapping in TQSL so they could immediately submit FT4 QSOs to LoTW. Users were free to patiently wait a few weeks until ADIF approved an FT4 mode representation for FT4 and the ARRL released an updated Config.xml file, and then submitted all of their FT4 QSOs made to date.

+ Anyone who did create an FT4=>DATA mapping in TQSL so they could immediately submit FT4 QSOs to LoTW could -- after ADIF and the ARRL acted -- remove that mapping, and then resubmit all of their FT4 QSOs.

+ Is it unreasonable to expect users who created an FT4=>DATA mapping in TQSL to remember that they did so?

+ Since one can remove the FT4=>DATA mapping and resubmit one's FT4 QSOs, there's no actual penalty for forgetting.

73,

Dave, AA6YQ

Re: Newbie

Wes Attaway (N5WA)
 

Chuck and others .....

Among other things it is good to know and remember that not every ham
operator uses LOTW. If they don't use LOTW then you will never get a
confirmation via LOTW.

If you get a QSL card then you can go through the LOTW online application
process which does include having any QSL cards checked by a certified card
checker.

So, keep these two things in mind. QSL cards are often still required and
must be checked and must be submitted by the standard "old fashioned"
application process.

-------------------
Wes Attaway (N5WA)
(318) 393-3289 - Shreveport, LA
Computer/Cellphone Forensics
AttawayForensics.com
-------------------

-----Original Message-----
From: ARRL-LoTW@groups.io [mailto:ARRL-LoTW@groups.io] On Behalf Of Dave
AA6YQ
Sent: Friday, July 19, 2019 12:52 PM
To: ARRL-LoTW@groups.io
Subject: Re: [ARRL-LoTW] Newbie

+ AA6YQ comments below

Chuck, I don't think that you understand what LOTW is!?? It is ONLY a way to
get conformations for qso's just like paper qsl cards.?? You still have to
APPLY those conformations to the award that you are after.?? And that is
after your LOTW account is linked to your DXCC accouny.?? Understand that
they are two different things. That said, after you apply what ever qsos
that you have to your aware (DXCC, WAS, whatever).?? You can then see those
qso confirmations in both LOTW and your award account.?? It is much harder
to explain it then it really is in action.
I hope this helps a little.

+ Perhaps this state diagram will help:

<https://lotw.arrl.org/lotw-help/qso-states/>

+ It illustrates that a confirmed QSO can be granted award credit for DXCC,
VUCC, WAS, WAZ, and WPX. As stated above, a confirmed QSO must be included
in an application for an award in order to be granted credit for that award.

+ For example, this article explains how to submit confirmed QSOs for DXCC
awards:

<https://lotw.arrl.org/lotw-help/dxcc-award-credit/>

73,

Dave, AA6YQ