开云体育

ctrl + shift + ? for shortcuts
© 2025 Groups.io

NPOTA


 

开云体育

I’m not sure if this is a DXL problem or a LOTW problem but since the error message is coming from DXL I’ll start here.

?

Recently I worked a station that reported he was in TR23. Along with other NPOTA QSO’s I uploaded to LOTW. All of the other Q’s have been confirmed except the one for TR23. For this one I get this error message using the NPOTA progress report,

?

TR23? N1PSX?????????? 07-Jan-2016 16:50?? 20M???? SSB???? QSO confirmed, Park unconfirmed

?

I sent the other station an email asking if he knew of a problem with his upload and he reported back that no one else has reported any problems with confirmation and he is fairly sure he has up loaded his Q’s as he should.

?

What can be done now?

?

Julio, W4HY


 

开云体育

If I remember correctly this is not a DXL problem, it is a problem the activator does not have his TQSL set up correctly yet. and will have to fix it and up load all his Qs again.

Joe WB9SBD

The Original Rolling Ball Clock
Idle Tyme
Idle-Tyme.com

On 2/22/2016 6:54 AM, 'Julio Peralta' jperalta4@... [dxlab] wrote:

???

I???m not sure if this is a DXL problem or a LOTW problem but since the error message is coming from DXL I???ll start here.

???

Recently I worked a station that reported he was in TR23. Along with other NPOTA QSO???s I uploaded to LOTW. All of the other Q???s have been confirmed except the one for TR23. For this one I get this error message using the NPOTA progress report,

???

TR23??? N1PSX?????????????????????????????? 07-Jan-2016 16:50?????? 20M???????????? SSB?????? ?????? QSO confirmed, Park unconfirmed

???

I sent the other station an email asking if he knew of a problem with his upload and he reported back that no one else has reported any problems with confirmation and he is fairly sure he has up loaded his Q???s as he should.

???

What can be done now?

???

Julio, W4HY



 

开云体育

Joe is correct, the activator uploaded his log and was missing the proper park designator in the TQSL location.
You can verify this by logging into LOTW
select YOUR QSO's
over on the left click Download Report
enter a date which would cover the time for the Q
place a check in th Include QSO details box
download the report and find the contact in question
Near the end of the record it should contain a line TR23
if this is missing you know for sure the upload was incorrect.

73
Bob

On 2/22/2016 7:01 AM, Joe nss@... [dxlab] wrote:

???

If I remember correctly this is not a DXL problem, it is a problem the activator does not have his TQSL set up correctly yet. and will have to fix it and up load all his Qs again.

Joe WB9SBD


The Original Rolling Ball Clock
Idle Tyme
Idle-Tyme.com

On 2/22/2016 6:54 AM, 'Julio Peralta' jperalta4@... [dxlab] wrote:
???

I???m not sure if this is a DXL problem or a LOTW problem but since the error message is coming from DXL I???ll start here.

???

Recently I worked a station that reported he was in TR23. Along with other NPOTA QSO???s I uploaded to LOTW. All of the other Q???s have been confirmed except the one for TR23. For this one I get this error message using the NPOTA progress report,

???

TR23??? N1PSX?????????????????????????????? 07-Jan-2016 16:50?????? 20M???????????? SSB?????? ?????? QSO confirmed, Park unconfirmed

???

I sent the other station an email asking if he knew of a problem with his upload and he reported back that no one else has reported any problems with confirmation and he is fairly sure he has up loaded his Q???s as he should.

???

What can be done now?

???

Julio, W4HY




 

Thanks very much for that info Bob. I ran the report as you suggested and
found the last line in the record to have info just as shown in your post.



So I wonder what the problem is now.



Julio



From: dxlab@... [mailto:dxlab@...]
Sent: Monday, February 22, 2016 8:37 AM
To: dxlab@...
Subject: Re: [dxlab] NPOTA





Joe is correct, the activator uploaded his log and was missing the proper
park designator in the TQSL location.
You can verify this by logging into LOTW
select YOUR QSO's
over on the left click Download Report
enter a date which would cover the time for the Q
place a check in th Include QSO details box
download the report and find the contact in question
Near the end of the record it should contain a line <APP_LoTW_NPSUNIT:4>TR23
if this is missing you know for sure the upload was incorrect.

73
Bob

On 2/22/2016 7:01 AM, Joe nss@... [dxlab] wrote:



If I remember correctly this is not a DXL problem, it is a problem the
activator does not have his TQSL set up correctly yet. and will have to fix
it and up load all his Qs again.

Joe WB9SBD


The Original Rolling Ball Clock
Idle Tyme
Idle-Tyme.com
<>

On 2/22/2016 6:54 AM, 'Julio Peralta' jperalta4@... [dxlab] wrote:



I'm not sure if this is a DXL problem or a LOTW problem but since the error
message is coming from DXL I'll start here.



Recently I worked a station that reported he was in TR23. Along with other
NPOTA QSO's I uploaded to LOTW. All of the other Q's have been confirmed
except the one for TR23. For this one I get this error message using the
NPOTA progress report,



TR23 N1PSX 07-Jan-2016 16:50 20M SSB QSO confirmed,
Park unconfirmed



I sent the other station an email asking if he knew of a problem with his
upload and he reported back that no one else has reported any problems with
confirmation and he is fairly sure he has up loaded his Q's as he should.



What can be done now?



Julio, W4HY


 

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Monday, February 22, 2016 8:02 AM
To: dxlab@...
Subject: Re: [dxlab] NPOTA

If I remember correctly this is not a DXL problem, it is a problem the activator does not have his TQSL set up correctly yet. and
will have to fix it and up load all his Qs again.

It's not a "TQSL Setup" problem. The activator uploaded his or her QSOs using a "Station Location" that does not specify the
NPOTA park code.

73,

Dave, AA6YQ


 

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Monday, February 22, 2016 9:05 AM
To: dxlab@...
Subject: RE: [dxlab] NPOTA

Thanks very much for that info Bob. I ran the report as you suggested and found the last line in the record to have info just as
shown in your post.

So I wonder what the problem is now.

The "problem" is to convince your QSO partner to resubmit your QSO with a "Station Location" that specifies the correct NPOTA
code. As a first step, you could show him or her the QSO details box for a QSO with the Park code properly specified, and the QSO
details box for your QSO with the Park code missing. I suggest copying the ARRL's Norm W3IZ on your message; his email address is

w3iz (at) arrl.org

73,

Dave, AA6YQ


 

开云体育

Isn't that the same that it isn't set up correctly if it is missing something?

If It isn't Correct,, so it must be incorrect,,,

Joe WB9SBD

On 2/22/2016 4:57 PM, ' Dave AA6YQ' aa6yq@... [dxlab] wrote:

???

>>>AA6YQ comments below

-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Monday, February 22, 2016 8:02 AM
To: dxlab@...
Subject: Re: [dxlab] NPOTA

If I remember correctly this is not a DXL problem, it is a problem the activator does not have his TQSL set up correctly yet. and
will have to fix it and up load all his Qs again.

>>>It's not a "TQSL Setup" problem. The activator uploaded his or her QSOs using a "Station Location" that does not specify the
NPOTA park code.

73,

Dave, AA6YQ



 

Perhaps I'm being overly precise, but one specifies a "Station Location" each time one directs TQSL to upload QSOs to LoTW. Thus
"Station Location" is not considered a part of "TQSL Setup" - a term typically used to describe actions taken once or taken
infrequently.

73,

Dave, AA6YQ

-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Monday, February 22, 2016 6:05 PM
To: dxlab@...
Subject: Re: [dxlab] NPOTA



Isn't that the same that it isn't set up correctly if it is missing something?

If It isn't Correct,, so it must be incorrect,,,

Joe WB9SBD


On 2/22/2016 4:57 PM, ' Dave AA6YQ' aa6yq@... [dxlab] wrote:




>>>AA6YQ comments below

-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Monday, February 22, 2016 8:02 AM
To: dxlab@...
Subject: Re: [dxlab] NPOTA

If I remember correctly this is not a DXL problem, it is a problem the activator does not have his TQSL set up correctly
yet. and
will have to fix it and up load all his Qs again.

>>>It's not a "TQSL Setup" problem. The activator uploaded his or her QSOs using a "Station Location" that does not specify
the
NPOTA park code.

73,

Dave, AA6YQ


 

开云体育

Dave one of the members of the list suggested I go to the LOTW site and research the QSO for this info.

?

TR23

?

When I looked up the QSO information I found that exact line in the record. Is that not what is needed to confirm the NPOTA unit?

?

Julio

From: dxlab@... [mailto:dxlab@...]
Sent: Monday, February 22, 2016 6:01 PM
To: dxlab@...
Subject: RE: [dxlab] NPOTA

?

?

>>>AA6YQ comments below

-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Monday, February 22, 2016 9:05 AM
To: dxlab@...
Subject: RE: [dxlab] NPOTA

Thanks very much for that info Bob. I ran the report as you suggested and found the last line in the record to have info just as
shown in your post.

So I wonder what the problem is now.

>>>The "problem" is to convince your QSO partner to resubmit your QSO with a "Station Location" that specifies the correct NPOTA
code. As a first step, you could show him or her the QSO details box for a QSO with the Park code properly specified, and the QSO
details box for your QSO with the Park code missing. I suggest copying the ARRL's Norm W3IZ on your message; his email address is

w3iz (at) arrl.org

73,

Dave, AA6YQ


 

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Tuesday, February 23, 2016 12:50 PM
To: dxlab@...
Subject: RE: [dxlab] NPOTA

Dave one of the members of the list suggested I go to the LOTW site and research the QSO for this info.

<APP_LoTW_NPSUNIT:4>TR23

When I looked up the QSO information I found that exact line in the record. Is that not what is needed to confirm the NPOTA unit?

Perhaps your QSO partner re-submitted your QSO with a "Station Location" that specifies a park code of TR23. Locate the QSO in
DXKeeper's "Log Page Display", right-click its entry, and select "Update from LotW".

73,

Dave, AA6YQ


 

开云体育

Thanks that worked

?

Julio

?

From: dxlab@... [mailto:dxlab@...]
Sent: Tuesday, February 23, 2016 1:15 PM
To: dxlab@...
Subject: RE: [dxlab] NPOTA

?

?

>>>AA6YQ comments below

-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Tuesday, February 23, 2016 12:50 PM
To: dxlab@...
Subject: RE: [dxlab] NPOTA

Dave one of the members of the list suggested I go to the LOTW site and research the QSO for this info.

TR23

When I looked up the QSO information I found that exact line in the record. Is that not what is needed to confirm the NPOTA unit?

>>>Perhaps your QSO partner re-submitted your QSO with a "Station Location" that specifies a park code of TR23. Locate the QSO in
DXKeeper's "Log Page Display", right-click its entry, and select "Update from LotW".

73,

Dave, AA6YQ