+ AA6YQ comment sbelow

I went through Dave's lengthy method to move DXLab to a new PC with Windows 10. Good news: all went well. Bad news: SpotCollector opens with an error message that an old BandModes text file it is looking for does not exist. I had saved the latest BandModes text from a week ago and loaded it into the SpotCollector folder. The old file is "BandModes 2006-12-16.txt" and the new one that I saved before the transfer is "BandModes 2019-05-02.txt".

How do I get SC to find the right file?

+ In the "Sub-band Definition" panel near the bottom of SpotCollector's Configuration window's General tab, click the Select button, and use the "Open" window that appears to select

BandModes 2019-05-02.txt

73,

Dave, AA6YQ

ARRL will not address 60 meters until there are statistics to value it's use.  NR1DX's comments are valid.   If DXab, or some some other recording mechanism, could accumulate statistics on the value and utilization of 60 meters, then (perhaps) ARRL would pay attention.  I have sent multiple emails, only to the the "atta boy" response.

We all know the channels are stupid, but it is what we have.   Doesn't mean that there is not a DX challenge out there to make something happen   Easy is not fun or interesting.

IMHO

Don
WB6BEE

Tried a couple of QSOs. No change in the LotW sent field, it remains U.

Steve, K8JQ

+ AA6YQ comments below

On Thu, May 21, 2020 at 03:05 PM, Steve K8JQ wrote:

My usual method is to filter the Log QSOs tab, then on the QSL tab => Add Requested => Upload to LotW => Sync LotW QSOs => Sync Lotw QSLs. This won't work because when I click Add Requested there are no QSOs added to the queue because all the QSOs have the sent field set to U.

I tried TQSL. It failed. The popup error message box was titled "Already Uploaded QSOs Detected".

+ OK. Locate the Log Page Display entry for one of the QSOs in the group that you say was uploaded but not accepted by LoTW. Right click it and select "update from LoTW" from the pop-up menu. When this operation complete, inspect the QSO's "LoTW QSL Sent" item; to what is it now set?

      73,

           Dave, AA6YQ

 

+ AA6YQ commetns below On Thu, May 21, 2020 at 02:51 PM, Fred - NA2U wrote:

Option 1, Steps 1 and 2
If I set QSL via to QSL cards I do not get an “Update from LOTW” button.

+ Set the "QSL Via" panel to LoTW.

      73,

           Dave, AA6YQ

My usual method is to filter the Log QSOs tab, then on the QSL tab => Add Requested => Upload to LotW => Sync LotW QSOs => Sync Lotw QSLs. This won't work because when I click Add Requested there are no QSOs added to the queue because all the QSOs have the sent field set to U.

I tried TQSL. It failed. The popup error message box was titled "Already Uploaded QSOs Detected".



Steve, K8JQ

Option 1, Steps 1 and 2
If I set QSL via to QSL cards I do not get an “Update from LOTW” button.

I’ll add that the list shows the last failure before the current one was 7/10/18.

73 from the desert,

Fred/NA2U

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

+ 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

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

Man Who Served 11 Presidents Dies of COVID
http://thirdpartyoffers.juno.com/TGL3141/5ec6f7b7aecd277b67eb0st03duc1
Trump Skips the Mask in Public Tour of Ford Plant
http://thirdpartyoffers.juno.com/TGL3141/5ec6f7b7cdf5177b67eb0st03duc2
Former Trump Lawyer Goes Home After a Year in Prison
http://thirdpartyoffers.juno.com/TGL3141/5ec6f7b7ed9c677b67eb0st03duc3

+ Aa6YQ comments below

A CWT is a "CW test". A one hour CW contest that runs three times on Wednesdays. I usually make about a hundred contacts. As far as I am aware, the logs for the three CWTs have the same format, no reason for one to be different from the others. I see no difference among them as I look at them in the Log QSOs window. N1MMLogger+ is the source, import ADIF into DXKeeper.

+ Thanks for the explanation.

+ Try resubmitting the batch that was submitted but not accepted. Does TQSL reject them as "already submitted"?

73,

Dave, AA6YQ

A CWT is a "CW test". A one hour CW contest that runs three times on Wednesdays. I usually make about a hundred contacts. As far as I am aware, the logs for the three CWTs have the same format, no reason for one to be different from the others. I see no difference among them as I look at them in the Log QSOs window. N1MMLogger+ is the source, import ADIF into DXKeeper.

Steve, K8JQ

Thanks for sending me your log, Don.

1. Your log contains 19 empty QSOs, each with no callsign, band, mode, date, or time. An empty QSO is created when you click the New button on the Main window's "Log QSOs" tab, but then never populate the new QSO with information. Whenever you select one of these empty QSOs, DXKeeper will flash the captions of these items in red font, insisting that you either supply valid information or delete the QSO. My advice is to set the Sort panel to Call (lower left corner of the Main window's Log QSOs" tab), which will put all of the empty QSOs at the top of the Log Page Display. Delete each empty QSO one at a time by clicking the Delete button just above the Log Page Display.

2. You should rename the log file you are using to

NK6A.mdb

73,

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

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:

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

+ 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

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.

+ 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

+ 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

#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

+ 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

+ 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