Date   

Re: assuming LoTW confirmations "count" for IOTA might not be a good idea

Dave AA6YQ
 

* more AA6YQ comments below

those requirements may be enough for IOTA to consider a QSL as a confirmation but I'm not sure just those attributes will be enough for an accepted IOTA confirmation. For example their requirements for paper cards are much stricter in that the IOTA reference must be printed on the original card, i.e. writing it on afterwards is not acceptable, the information must be provided by the DX station. Seehttps://www.iota-world.org/islands-on-the-air/qsl-card-requirements.html . I would be surprised if LoTW matches would be acceptable without an IOTA reference from the DX station.

+ DXLab's realtime award tracking for IOTA requires each QSO to specify an IOTA tag. The question is whether IOTA will require your QSO partner to have specified an IOTA tag in the "Station Location" used to submit your QSO.
that does seem to be unconfirmed so far but I'll bet that is exactly what they will require. They are very strict on that with paper QSLs and I doubt that will change. Is all too common for island stations not to include their IOTA reference on QSLs and I have no doubt many also do not include it in their LoTW Station Locations. A similar situation exists for a great deal of US stations who do not specify their grid square on QSLs which makes them invalid for European grid based awards, particularly for hard earned contacts on 6m.

* The good news is that it's relatively easy to send an email message to a QSO partner asking them to more fully (or accurately) populate a "Station Location" and resubmit your QSO to LoTW. I've had success with this on several occasions.

* The dark side of this capability is that a user can resubmit QSOs with a "Station Location" that contains inaccurate location information, depriving you of a grid or state confirmation that you previously possessed.

73,

Dave, AA6YQ


Re: URE QDure paper QSL System

Herman / PA3BFH
 

Hi Dave

Ok thanks, I didn't know about the default ADIF value, will see what they have to say to that.

73,

Herman / PA3BFH

Op 21-5-2020 om 22:55 schreef Dave AA6YQ:

+ AA6YQ comments below

What I need is the option "N" in the QSL rcvd Box...
It is available in the QSL sent box, but for what I want to do the QDure system triggers on the QSL rcvd Box.
QSL rcvd = Y means you have received an incoming QSL and you want to answer: "tks QSL" on the card, QSL rcvd = N means no QSL received, so you're requesting one: "pse QSL".. This is what I need, but not p[ossible (?).


And in the advanced sorts, filters & modifiers, Modify QSOs in Log Page Display, Item name QSL_Rcvd/Item new value options available are R,Y,S,V,I and X, so no "N" and also not possible to add the "N" in the blank spot...

I sent the original batch with QSL_sent as "R"equested, but QDure wants an upload as above.

Any ideas??

+ ADIF specifies that the default value for QSL_RCVD is 'N':

<http://adif.org.uk/310/ADIF_310.htm#QSO_Field_QSL_RCVD>;

+ As stated in

<http://adif.org.uk/310/ADIF_310.htm#default_value>;

"A Field can specify a Default Value to be assumed when that Field is not specified in a QSO record, or when a Data-Specifier for that Field contains no data."

+ Thus I suggest that you contact QDure and ask them to correctly implement the ADIF specification for QSL_Rcvd.

73,

Dave, AA6YQ


--
Herman van den Berg / PA3BFH
Hoofdweg 132
1433 JX kudelstaart
Tel 0297 322011


Re: Failure to Upload Qs to LOTW

Dave AA6YQ
 

+ AA6YQ comments below

On May 21, 2020, at 1:31 PM, Dave AA6YQ <aa6yq@ambersoft.com> wrote:

?* More AA6YQ comments below
+ First, let's determine why your QSOs weren't accepted the first time you submitted them to LoTW:

1. On the Main window's QSL tab, click "Sync LoTW QSOs", and wait for it to complete
#DONE

2. On the Main window's "Lot QSOs" tab, click the Filter panel's LoTW button; this will filter the Log Page Display to contain QSOs uploaded to LoTW, but not accepted by LoTW

+ How many QSOs are now present in the Log Page Display?
#6590

* That's a lot of submitted but unaccepted QSOs. How many QSOs does your log contain in total?
#117,118

+ So the question is, which will be faster:

A. 6590 individual requests sent to LoTW to report a QSO's status so that DXKeeper can update each one

B. Directing LoTW to report that status of all 117,118 of your QSOs, so that DXKeeper can update them each of them

+ I'll guess that A will be faster:

1. On the Main window's "Lot QSOs" tab, click the Filter panel's LoTW button; your 6590 QSOs should appear in the Log Page Display

2. On the Main window's QSL tab

2a. set the "QSL Via" panel to QSL

2b. click the "Update from LoTW" button, and confirm that you want DXKeeper to query LoTW for the status of each of those 6590 QSOs

+ This step will take a long time; I suggest that you initiate it before retiring for the evening; don't be surprised if it's still running in the morning.

3. On the Main window's "Lot QSOs" tab, click the Filter panel's LoTW button; how many QSOs are now present in the Log Page Display?

73,

Dave, AA6YQ


Re: assuming LoTW confirmations "count" for IOTA might not be a good idea

g4wjs
 

On 21/05/2020 21:18, Dave AA6YQ wrote:
+ AA6YQ comments below

those requirements may be enough for IOTA to consider a QSL as a confirmation but I'm not sure just those attributes will be enough for an accepted IOTA confirmation. For example their requirements for paper cards are much stricter in that the IOTA reference must be printed on the original card, i.e. writing it on afterwards is not acceptable, the information must be provided by the DX station. Seehttps://www.iota-world.org/islands-on-the-air/qsl-card-requirements.html . I would be surprised if LoTW matches would be acceptable without an IOTA reference from the DX station.

+ DXLab's realtime award tracking for IOTA requires each QSO to specify an IOTA tag. The question is whether IOTA will require your QSO partner to have specified an IOTA tag in the "Station Location" used to submit your QSO.

73,

Dave, AA6YQ
Hi Dave,

that does seem to be unconfirmed so far but I'll bet that is exactly what they will require. They are very strict on that with paper QSLs and I doubt that will change. Is all too common for island stations not to include their IOTA reference on QSLs and I have no doubt many also do not include it in their LoTW Station Locations. A similar situation exists for a great deal of US stations who do not specify their grid square on QSLs which makes them invalid for European grid based awards, particularly for hard earned contacts on 6m.

73
bill
G4WJS.



--
73

Bill

G4WJS.


Re: URE QDure paper QSL System

Dave AA6YQ
 

+ AA6YQ comments below

What I need is the option "N" in the QSL rcvd Box...
It is available in the QSL sent box, but for what I want to do the QDure system triggers on the QSL rcvd Box.
QSL rcvd = Y means you have received an incoming QSL and you want to answer: "tks QSL" on the card, QSL rcvd = N means no QSL received, so you're requesting one: "pse QSL".. This is what I need, but not p[ossible (?).


And in the advanced sorts, filters & modifiers, Modify QSOs in Log Page Display, Item name QSL_Rcvd/Item new value options available are R,Y,S,V,I and X, so no "N" and also not possible to add the "N" in the blank spot...

I sent the original batch with QSL_sent as "R"equested, but QDure wants an upload as above.

Any ideas??

+ ADIF specifies that the default value for QSL_RCVD is 'N':

<http://adif.org.uk/310/ADIF_310.htm#QSO_Field_QSL_RCVD>;

+ As stated in

<http://adif.org.uk/310/ADIF_310.htm#default_value>;

"A Field can specify a Default Value to be assumed when that Field is not specified in a QSO record, or when a Data-Specifier for that Field contains no data."

+ Thus I suggest that you contact QDure and ask them to correctly implement the ADIF specification for QSL_Rcvd.

73,

Dave, AA6YQ


Re: 60mtrs in DXView?

Dave AA6YQ
 

+ AA6YQ comments below

Would it be possible to add 60Mtrs to the DXView Info tables?

+ It is certainly possible, but I will not do so: I agree with the ARRL that 60m is too narrow a band for DXing (which is why QSOs on 60m don't count for DXCC awards), and so will do nothing to encourage its use for DXing.

73,

Dave, AA6YQ


Re: Failure to Upload Qs to LOTW

Fred - NA2U
 

#below. I,too, was surprised by the large number. I don’t understand why.

73 from the desert,

Fred/NA2U

On May 21, 2020, at 1:31 PM, Dave AA6YQ <aa6yq@ambersoft.com> wrote:

* More AA6YQ comments below
+ First, let's determine why your QSOs weren't accepted the first time you submitted them to LoTW:

1. On the Main window's QSL tab, click "Sync LoTW QSOs", and wait for it to complete
#DONE

2. On the Main window's "Lot QSOs" tab, click the Filter panel's LoTW button; this will filter the Log Page Display to contain QSOs uploaded to LoTW, but not accepted by LoTW

+ How many QSOs are now present in the Log Page Display?
#6590

* That's a lot of submitted but unaccepted QSOs. How many QSOs does your log contain in total?
#117,118

73,

Dave, AA6YQ





____________________________________________________________
Sponsored by https://www.newser.com/?utm_source=part&;utm_medium=uol&utm_campaign=rss_taglines_more

Hurricane Forecast Isn't Great News
http://thirdpartyoffers.juno.com/TGL3141/5ec6e7e6bc55067e57c7dst01duc1
Nation Has a New Spy Chief
http://thirdpartyoffers.juno.com/TGL3141/5ec6e7e6d9aec67e57c7dst01duc2
Trump Is Scrapping Treaty With Russia on Surveillance
http://thirdpartyoffers.juno.com/TGL3141/5ec6e7e747b567e57c7dst01duc3


Re: LotW sent field is set to U but QSOs are not in LotW

Dave AA6YQ
 

+ AA6YQ comments below

I made some contacts in each of the three CWTs yesterday.

+ What's a CWT ?

Uploaded to LotW per the instructions on UploadLotWLogPageDisplay - DX Lab Suite Wiki <https://www.dxlabsuite.com/dxlabwiki/UploadLotWLogPageDisplay>; , or so I thought. The 1300Z and 0300Z logs appear to have uploaded and sync'ed OK.

The 1900Z CWT appears not to have been successful. The LotW sent field is set to U for all of these QSOs. But when I look at the LotW web page Your QSOs, they are not in LotW.

+ How are the QSOs in your 1900Z CWT different than those in your 1300Z and 0300Z logs?

73,

Dave, AA6YQ


Re: URE QDure paper QSL System

Dave AA6YQ
 

+ AA6YQ comments below

Since GlobalQSL seems to have stopped working I'm checking other QSL services.

The QDure sytem by the Spanish club URE (https://qsl.ure.es/en/) is one of these.

I sent a batch in and noticed the item PSE QSL/TKS QSL was not working, and I had to manually tick the box for PSE QSL.... (76 times ough...)

+ There's an "Outgoing QSLs request confirmation unless already confirmed" option in the General panel on the "QSL Configuration" window's General tab.


Checking with URE they informed me an adif field <QSL_RCVD:1>Y for TKS QSL and a field ,QSL_RCVD:1>N for PSE QSL is expected...

Well none of the QSLs received in DXKeeper was marked as "N"....

I can't find this option in DXKeeper, is it possible to add??

+ You can use the "Modify QSOs" panel at the bottom of the "Advanced Sorts, Filters, and Modifiers" window to do this "en masse":

<https://www.dxlabsuite.com/dxlabwiki/QSOModifying>;

73,

Dave, AA6YQ


Re: Failure to Upload Qs to LOTW

Dave AA6YQ
 

* More AA6YQ comments below
+ First, let's determine why your QSOs weren't accepted the first time you submitted them to LoTW:

1. On the Main window's QSL tab, click "Sync LoTW QSOs", and wait for it to complete
#DONE

2. On the Main window's "Lot QSOs" tab, click the Filter panel's LoTW button; this will filter the Log Page Display to contain QSOs uploaded to LoTW, but not accepted by LoTW

+ How many QSOs are now present in the Log Page Display?
#6590

* That's a lot of submitted but unaccepted QSOs. How many QSOs does your log contain in total?

73,

Dave, AA6YQ


Re: assuming LoTW confirmations "count" for IOTA might not be a good idea

Dave AA6YQ
 

* AA6YQ comments below

+ LoTW has all the information that IOTA says it need to accept LoTW
confirmations: callsign, mode, and band. See this IOTA document:
https://www.iota-world.org/info/lotw_qso_matching-en.pdf

I am afraid that is not the case.
The fields specified in the PDF document (callsign, band and mode) are
not mandatory, they simply allow the user to search for a specific
operation and/or for QSOs made on specific bands and/or modes.

The information IOTA needs to accept paperless QSLs for IOTA credit are:
DX callsign, island name, IOTA reference, date & time of the first QSO,
and date & time of the last QSO.

* All of which is highly likely to be included in the logged QSO.


Operations whose DXCC Entity in its entirety matches only one IOTA Group
(e.g. EA8, EA6, OY, ZD7, ZD8, D6, T33, VK9N, VK9L, HC8, P4, VP9, ZF and
many, many others) are not a problem, as they are identified by their
unique DXCC Entity Code.

When the DXCC Entity includes two or more IOTA Groups, investigations are
needed. This is what the IOTA Operations Manager is doing in order to
allow LoTW Matching for thousands of other activities. The island name is
mandatory.

* If "Island Name" is mandatory, IOTA will have to specify an ADIF field for that data item.


As for the use of LoTW, "ARRL Director of Operations Norm Fusaro, W3IZ,
points out that LoTW has, for years, allowed award sponsors access to a
utility that lets them verify contacts in LoTW.

* That's never been announced.

'The IOTA folks have
begun using this utility, but still check the QSOs against known IOTA
operations,' he explained, noting that applicants cannot apply for IOTA
awards through LoTW".

* If that was true, it would not be necessary for users to supply their LoTW username and password to IOTA - as the recent IOTA announcement states.

* IOTA's announcement has been a sequence of inconsistencies. Not quite a "goat rodeo", but getting there.

73,

Dave, AA6YQ


Re: assuming LoTW confirmations "count" for IOTA might not be a good idea

Dave AA6YQ
 

+ AA6YQ comments below

those requirements may be enough for IOTA to consider a QSL as a confirmation but I'm not sure just those attributes will be enough for an accepted IOTA confirmation. For example their requirements for paper cards are much stricter in that the IOTA reference must be printed on the original card, i.e. writing it on afterwards is not acceptable, the information must be provided by the DX station. See https://www.iota-world.org/islands-on-the-air/qsl-card-requirements.html . I would be surprised if LoTW matches would be acceptable without an IOTA reference from the DX station.

+ DXLab's realtime award tracking for IOTA requires each QSO to specify an IOTA tag. The question is whether IOTA will require your QSO partner to have specified an IOTA tag in the "Station Location" used to submit your QSO.

73,

Dave, AA6YQ


Re: 60mtrs in DXView?

Dave / NR1DX
 

Be that as it may I now have 122 countries worked and 113 confirmed 0n 60M.  I only need 6 more states to have WAS on 60M. Looks like a "real"  band to me 8^)

Dave
NR1DX

On 5/21/2020 2:46 PM, Joe Subich, W4TV wrote:

Dave has previously indicated that 60 M would not be added to DXView
or the real time progress tables until the US has a real "band" (as
opposed to five discrete channels) and ARRL adds a single band 60 M
award to the DXCC program.

To paraphrase his comments, 60 meters is not suitable for DXing given
the current allocations and sharing requirements.

In the meantime, one can filter the log for 60 M QSOs and run a
DXCC Progress report on the filtered log.  If that is being done
often, it is relatively easy to create a script to automate the
process.

73,

   ... Joe, W4TV


On 2020-05-21 1:06 PM, Brian Bowers G0VAX wrote:
Hi Dave,
Would it be possible to add 60Mtrs to the DXView Info tables?
I find it so useful when querying worked or confirmed band/mode spots.

Best Wishes

Brian G0VAX


--
Dave
Manuals@ArtekManuals.com
www.ArtekManuals.com
--
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus


Re: URE QDure paper QSL System

Herman / PA3BFH
 


Hi Carl,

Yes I know, but....

What I need is the option "N" in the QSL rcvd Box...
It is available in the QSL sent box, but for what I want to do the QDure system triggers on the QSL rcvd Box.
QSL rcvd = Y means you have received an incoming QSL and you want to answer: "tks QSL" on the card,
QSL rcvd = N means no QSL received, so you're requesting one: "pse QSL".. This is what I need, but not
p[ossible (?).

And in the advanced sorts, filters & modifiers, Modify QSOs in Log Page Display, Item name QSL_Rcvd/Item new value options available are R,Y,S,V,I and X, so no "N" and also not possible to add the "N" in the blank spot...

I sent the original batch with QSL_sent as "R"equested, but QDure wants an upload as above..

Any ideas??

Tks/73,
Herman
PA3BFH

-------- Doorgestuurd bericht --------
Onderwerp: Re: [DXLab] URE QDure paper QSL System
Datum: Thu, 21 May 2020 09:01:58 -0700
Van: Carl - WC4H via groups.io <wc4h.dx@...>
Antwoord-naar: DXLab@groups.io
Aan: DXLab@groups.io


Hi Herman.

If you click on  the QSL check box on the upper right of the Log QSOs tab, it will open the display of the QSL panel on the left side. You will see "sent" and "rcvd" dropdown boxes there.  You can select the Y among other values.

You can also do a mass change if you desire.

73.
Carl - WC4H


Re: 60mtrs in DXView?

Joe Subich, W4TV
 

Dave has previously indicated that 60 M would not be added to DXView
or the real time progress tables until the US has a real "band" (as
opposed to five discrete channels) and ARRL adds a single band 60 M
award to the DXCC program.

To paraphrase his comments, 60 meters is not suitable for DXing given
the current allocations and sharing requirements.

In the meantime, one can filter the log for 60 M QSOs and run a
DXCC Progress report on the filtered log. If that is being done
often, it is relatively easy to create a script to automate the
process.

73,

... Joe, W4TV

On 2020-05-21 1:06 PM, Brian Bowers G0VAX wrote:
Hi Dave,
Would it be possible to add 60Mtrs to the DXView Info tables?
I find it so useful when querying worked or confirmed band/mode spots.
Best Wishes
Brian G0VAX


Re: An iota of work for Dave ...

w6de
 

Joe, Peter:
Thank you pointing out my errors and I offer my apology to the group.

73,
Dave, w6de

-----Original Message-----
From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Joe Subich, W4TV
Sent: 21 May, 2020 02:17
To: DXLab@groups.io
Subject: Re: [DXLab] An iota of work for Dave ...


On 2020-05-20 7:47 PM, w6de wrote:

However, US hams have to be members of the ARRL to use the LotW
program, so in essence you are already a LotW supporter.
*THAT IS ABSOLUTELY NOT TRUE!*

There is no requirement to be an ARRL member to use (upload) to LotW
in any country. The only requirement is that a US amateur must be an
ARRL member in order to apply for/receive ARRL awards (DXCC, WAS, VUCC).

73,

... Joe, W4TV
---------------------------------------------
Um, no. When I use LOTW credits for WAS, I pay a fee for using those credits ON TOP OF the fee for the award. When I use LOTW credits for DXCC, I pay a fee for using those credits ON TOP OF the fee for the award. Same for VUCC. I have claimed all of those (multiples of WAS and DXCC) via LOTW. In these cases, the LOTW fees and the award fees all go to the ARRL.

When I finally apply for WPX using LOTW credits, I will I pay a fee for using them to ARRL. To get the award, I will pay a fee to CQ magazine, issuers of the WPX award. I'm sure this is true for WAZ as well, but since I am still 4 or 5 CQ Zones short, I've never looked into it.

Everyone else is freeloading off of the ARRL.

--
Peter Laws | N5UWY | plaws plaws net | Travel by Train!

---------------------------------------------
On 2020-05-20 7:47 PM, w6de wrote:
The fees paid are for awards issued by the organization collecting the fees. ARRL does not manage the IOTA program and does not issue IOTA Awards.
You pay IOTA for IOTA Awards, you pay ARRL for ARRL Awards, you pay CQ for CQ Awards (e.g., WAZ, WPX).
The IOTA pulling QSO information from LotW is information about your potential IOTA Awards that you will pay IOTA for.
If you already upload your DXKeeper QSOs to ClubLog the IOTA can get your QSO information from ClubLog and you don't need to give the IOTA your ARRL LotW credentials.
Note: YOU as an IOTA member initiate these IOTA queries to LotW and/or ClubLog from within your IOTA log-on.

If you are concerned about supporting the ARRL LotW program you can always make donations to the ARRL. However, US hams have to be members of the ARRL to use the LotW program, so in essence you are already a LotW supporter.

73,
Dave, w6de


60mtrs in DXView?

Brian Bowers G0VAX
 

Hi Dave,
Would it be possible to add 60Mtrs to the DXView Info tables?
I find it so useful when querying worked or confirmed band/mode spots.

Best Wishes

Brian G0VAX


Re: URE QDure paper QSL System

Carl - WC4H
 

Hi Herman.

If you click on  the QSL check box on the upper right of the Log QSOs tab, it will open the display of the QSL panel on the left side. You will see "sent" and "rcvd" dropdown boxes there.  You can select the Y among other values.

You can also do a mass change if you desire.

73.
Carl - WC4H


LotW sent field is set to U but QSOs are not in LotW

Steve K8JQ
 

Dave,

I made some contacts in each of the three CWTs yesterday. Uploaded to LotW per the instructions on UploadLotWLogPageDisplay - DX Lab Suite Wiki , or so I thought. The 1300Z and 0300Z logs appear to have uploaded and sync'ed OK.

The 1900Z CWT appears not to have been successful. The LotW sent field is set to U for all of these QSOs. But when I look at the LotW web page Your QSOs, they are not in LotW.

How can I recover from this?

Thank you.

Steve, K8JQ


URE QDure paper QSL System

Herman / PA3BFH
 

Hi Dave (All),

Since GlobalQSL seems to have stopped working I'm checking other QSL services.

The QDure sytem by the Spanish club URE (https://qsl.ure.es/en/) is one of these.

I sent a batch in and noticed the item PSE QSL/TKS QSL was not working, and I had to manually tick the box for PSE QSL.... (76 times ough...)

Checking with URE they informed me an adif field <QSL_RCVD:1>Y for TKS QSL and a field ,QSL_RCVD:1>N for PSE QSL is expected...

Well none of the QSLs received in DXKeeper was marked as "N"....

I can't find this option in DXKeeper, is it possible to add??

Or do I need new glasses??

Tks / 73,

--
Herman van den Berg / PA3BFH
Hoofdweg 132
1433 JX kudelstaart
Tel 0297 322011

5441 - 5460 of 199241