Date   

Re: MSFT vs FT4

neil_zampella
 

That's surprising, as DXKeeper, as does eQSL, follows the ADIF standard which does consider FT4 as a submode of MFSK.

Neil, KN3ILZ

On 6/13/2020 3:22 AM, Björn Ekelund, SM7IUN wrote:
Maybe this has been discussed before but it seems eQSL considers FT4 and MFSK the same mode while DXKeeper does not.

I believe that eQSL's "rules" should apply for eQSL confirmations in DXKeeper.

For cards and LOTW, ARRL's "rules" should of course apply.

Björn


Virus-free. www.avg.com


I found it

Mike Kasrich
 

The "windows" threat....we're good.


Freaking Windows again

Mike Kasrich
 

I had this taken care of but today windows decided commander was a trojan for some reason. Where do I find to restore the app to a happy place?


MSFT vs FT4

Björn SM7IUN
 

Maybe this has been discussed before but it seems eQSL considers FT4 and MFSK the same mode while DXKeeper does not.

I believe that eQSL's "rules" should apply for eQSL confirmations in DXKeeper.

For cards and LOTW, ARRL's "rules" should of course apply.

Björn


Re: DXKeeper and clearning QSL Sent from "R"

Dave AA6YQ
 

+ AA6YQ comments below

On Fri, Jun 12, 2020 at 07:56 PM, n4ww austin regal wrote:

yes all labels printed but forgot to to update log first before clearing the entries.

I don't want to print them all again and then update. How do I update without printing them all again?

+ By generating an ADIF file instead of printing; on the Main window's QSL tab,

1. set the "QSL Via" panel to "ADIF File"

2. populate the QSL Queue by clicking the "Add Requested" button

3. click the "Save ADIF file" button

4. click the "Update Log" button

5. delete the ADIF file you saved in step 3

       73,

               Dave, AA6YQ


Re: DXKeeper and clearning QSL Sent from "R"

n4ww austin regal
 

yes all labels printed but forgot to to update log first before clearing the entries.

I don't want to print them all again and then update. How do I update without printing them all again?

73 doc n4ww

-----Original Message-----
From: Dave AA6YQ <aa6yq@ambersoft.com>
Sent: Jun 12, 2020 8:41 PM
To: DXLab@groups.io
Subject: Re: [DXLab] DXKeeper and clearning QSL Sent from "R"

+ AA6YQ comments below

I use qsl_sent with R request and load it into qsl que and print the labels. Then I try to "update the log" and " "clear" the qsl que. But it doesnt update the log They continue to be "r". I figured this out once but 3 months later I am stuck again.

+ The "Update Log" function removes each QSL Queue entry from which a label was successfully printed; it should not be necessary to click the "Clear" button.

+ Is a label being printed for each QSL Queue entry?

73,

Dave, AA6YQ




Re: DXKeeper and clearning QSL Sent from "R"

Dave AA6YQ
 

+ AA6YQ comments below

I use qsl_sent with R request and load it into qsl que and print the labels. Then I try to "update the log" and " "clear" the qsl que. But it doesnt update the log They continue to be "r". I figured this out once but 3 months later I am stuck again.

+ The "Update Log" function removes each QSL Queue entry from which a label was successfully printed; it should not be necessary to click the "Clear" button.

+ Is a label being printed for each QSL Queue entry?

73,

Dave, AA6YQ


logging and submitting Field Day logs with DXLab

Dave AA6YQ
 

Here's the response to my "how should Field Day Logs be submitted?" query received from ARRL Contest Program Manager Paul N1SFE:

---------------------
For the dupe sheet, it can be a scan of a paper document, an excel spreadsheet, csv file, or anything that shows that some effort
was used to avoid dupes. We do not process the documents in anyway, as Field Day is a non-adjudicated operating event. Complete
station logs are NOT required, but we do accept Cabrillo output from logging programs, if they do active dupe checking, it will
satisfy the requirements in lieu of a paper or electronic dupe sheet.

Cabrillo logs are not processed, so no header or any information in the log is used. We want something submitted that shows the
operators at least made a good effort to avoid working and counting dupes.

8.6. Complete station logs are NOT required for submission, and ARRL does not use the logs. The club should maintain log files for
one year in case they are requested by ARRL HQ. However, a list of stations worked sorted by band and mode (dupe sheet) is
required.

8.7. Cabrillo format log files are NOT required for Field Day entries, but they will be accepted in lieu of the dupe sheets (but do
not constitute an entry unless the web app (or a corresponding summary sheet with complete mailed entry) is also submitted.
---------------------

A recommended approach to logging and submitting Field Day QSOs consistent with Paul's "no duplicates" requirement is here:

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

73,

Dave, AA6YQ


Re: DXKeeper and clearning QSL Sent from "R"

w6de
 

This could be an ARRL DXCC desk or LotW problem.

Try the following.

On DXKeeper, Log QSOs tab do the following:

On the bottom line of the window; Click the UTC button, then click the Date box.  This will get all your QSOs in Date and Time order.  In my case this is 9063 QSOs.

Then click the LotW box.  Some subset of your QSOs will be displayed.  In my case this is 30 QSOs and all those QSOs have are marked U for LotW sent.  Furthermore, the majority of those 30 of those QSOs have been VERIFIED by CARD. 

 

 

Now log on to LotW in a browser window.  Navigate in LotW to “Your QSOs.”  An outlined box labeled Select QSOs to List will appear.

Choose one-at-a-time some of those Call Signs that are displayed in DXKeeper and enter that call sign into the LotW Your QSOs “Call sign worked” box.

 

In my case for the majority of my 30 QSOs there will appear two (2) LotW QSO entries for that QSO single QSO in my DXKeeper log book.

One of those two QSOs will have Hour, Minute, and Second and the frequency of the QSO that matches my DXKeeper log book and the second QSO will have only the Hour and Minute of the QSO and NO QSO frequency (Just the band).

 

My supposition is that I submitted those 30 QSOs via the LotW Online DXCC application process.  And, the ARRL on-line process for submitting Cards process truncated the seconds and did not enter the frequency of the QSO and the earlier QSO (no seconds) was marked as uploaded in the LotW records.  But this leaves the ARRL LotW thinking the QSO was uploaded but leaves your DXLab log book hanging because the phantom ARRL created QSO in LotW isn’t in your DXKeeper log book.

 

I have and still do upload all my QSOs to LotW.

 

Dave, AA6YQ, I can send you screen shots of the above sequences if you desire.

 

73,

Dave, W6DE

 

From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Steve Wedge
Sent: 12 June, 2020 20:02
To: DXLab@groups.io
Subject: Re: [DXLab] DXKeeper and clearning QSL Sent from "R"

 

Aw, damn.  I just checked by clicking "Add Requested" and there are still about 140 Q's that are coming up.  These are mostly from 2013.  I tried uploading them to LoTW, in the hope that these were not duplicates but LoTW says that they are dupes.

So, some of the Q's were resolved but for some reason, there are still some (140) that sem to be enteres on LoTW but aren't confirmed as such in DXk.

Thanks again.  It's better.


Re: DXKeeper and clearning QSL Sent from "R"

Dave AA6YQ
 

+ AA6YQ comments below

I appreciate that this is very complex software. I could never creat anything like this to deal with submissions. That is why I preface everything with "what did I do wrong?" -- because there are so many decision paths to be made.

I am nearly at the point where I'm ready to submit LoTW QSO's for DXCC credit but there are still some QSO's that are out in limbo. Some of this may be the fault of another software vendor but I'd like to get everything on the level. I believe that I had everything sorted out 10 years ago when I went to DXLab. Now that I'm getting more time to work with this, I need to find out where the discrepancies are and how to get them onto LoTW.

I am almost there. The cards discrepancy will sort itself out, eventually, since I'll likely change those values to "already done" or whatever, to clear them. LoTW is different, in that it should agree with what I have in my log.

+ Let's get to the point where all of your QSOs in DXKeeper have been accepted by LoTW. Then we'll move on to your QSL card issues.

73,

Dave, AA6YQ


Re: Problems with a simple command sequence

Dave AA6YQ
 

+ AA6YQ comments below

Dave, I am using an Icom ic7300. Here is the sequence that is currently working:
The following items should be changed for another band <Name 75 Meters> <wait> <QSY 3800> <wait> <Tooltip QSY to 75m> <wait> <Mode LSB> <wait> The following items don't need to be changed <Split Off> <Receive> <LED 2:9, red> <LED green> <end>

+ Thanks, Frank.

73,

Dave, AA6YQ


Re: DXKeeper and clearning QSL Sent from "R"

Dave AA6YQ
 

+ AA6YQ comments below

Aw, damn. I just checked by clicking "Add Requested" and there are still about 140 Q's that are coming up. These are mostly from 2013. I tried uploading them to LoTW, in the hope that these were not duplicates but LoTW says that they are dupes.

So, some of the Q's were resolved but for some reason, there are still some (140) that sem to be enteres on LoTW but aren't confirmed as such in DXk.

+ On the "QSL Configuration" window's LoTW tab, check the "Permit uploading of QSOs already uploaded to LotW" box; then click "Upload to LoTW" on the Main window's QSL tab.

73,

Dave, AA6YQ


Re: DXKeeper and clearning QSL Sent from "R"

Dave AA6YQ
 

That did it, Dave! Thanks!

I was preparing to update DXK next but was waiting to hear back. I tend to update one app at a time, in case something goes off the rails with this computer.

DXK is inspecting 11,522 QSO's, so that takes care of one issue. Now I have to find which 1286 QSO's are NOT in LoTW and figure out how to get them there. They may nave been imports from N1MM or CT (yeah, this log goes back to 1982...).

DXK is inspecting and is taking less time than I imagined it would.

+ When the "CTRL Sync LoTW QSOs" operation is complete, on the Main window's QSL tab (with the "QSL Via" panel still set to LoTW), click the "Add Requested" button; this will populate the QSL Queue with all QSOs not yet submitted to LoTW; if the number of QSOs added to the QSL Queue looks correct, then click the "Upload to LotW" button.

73,

Dave, AA6YQ


Re: DXKeeper and clearning QSL Sent from "R"

Steve Wedge <Steve27302@...>
 

I appreciate that this is very complex software.  I could never creat anything like this to deal with submissions.  That is why I preface everything with "what did I do wrong?" -- because there are so many decision paths to be made.  

I am nearly at the point where I'm ready to submit LoTW QSO's for DXCC credit but there are still some QSO's that are out in limbo.  Some of this may be the fault of another software vendor but I'd like to get everything on the level.  I believe that I had everything sorted out 10 years ago when I went to DXLab.  Now that I'm getting more time to work with this, I need to find out where the discrepancies are and how to get them onto LoTW.  

I am almost there.  The cards discrepancy will sort itself out, eventually, since I'll likely change those values to "already done" or whatever, to clear them.  LoTW is different, in that it should agree with what I have in my log.

Thanks to all who work on this.  Like I've said before, to me it's an art that I don't understand.

73,


Re: DXKeeper QRZ lookup

Steve GW4BKG
 

Thanks Dave,
Another function I was unaware of !
73
Steve
GW4BKG

On 12 Jun 2020, at 20:30, Dave AA6YQ <aa6yq@ambersoft.com> wrote:

+ AA6YQ comments below

Whilst I appreciate that it is possible to have qrz.com populate information into a DXKeeper log record there are some times when
the QSL information is contained further down in a qrz.com page.
Is there a way that the actual orz.com page can be called up from a log entry - perhaps via a right click of the mouse on the CBA
tab.

+ Yes:

1. direct the DXLab Launcher to install and run Pathfinder:

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


2. configure Pathfinder's QRZ.com search to be "automatic" whenever a new callsign is selected:

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

73,

Dave, AA6YQ




Re: Export adif for SOTA - error - incorrect summit format - advice needed

Joe Subich, W4TV
 

The QSO with AA7OY contains: <SOTA_REF:11>W7A/AE--026

I suspect the double hyphen in that record is responsible for the error.

73,

... Joe, W4TV

On 2020-06-12 2:29 PM, Dave AA6YQ wrote:
+ AA6YQ comments below
Incorrect summit format for chased summit
+ I assume that cryptic error message means that one or more of the SOTA designators specified in the SOTA_REF fields in the ADIF records below are in some way erroneous. You are responsible for logging accurate SOTA references; review each SOTA_REF field and correct those that are incorrect.
73,
Dave, AA6YQ
Here is the offending section:
<Band:3>40M <Call:5>NA6MG <APP_DXKEEPER_DXCCPREFIX:1>K <DXCC:3>291 <Freq:5>7.061 <Mode:2>CW <Operator:4>K7TP <QSO_DATE:8>20200611 <TIME_OFF:6>134238 <TIME_ON:6>134228 <RST_Rcvd:3>569 <RST_Sent:3>579 <TX_PWR:5>100.0 <CONT:2>NA <ITUZ:1>6 <CQZ:1>3 <PFX:3>NA6 <STATION_CALLSIGN:4>K7TP <OWNER_CALLSIGN:4>K7TP <SOTA_REF:9>W6/CT-014 <EQSL_QSL_SENT:1>U <EQSL_QSL_RCVD:1>R <EQSL_QSLSDATE:8>20200611 <LOTW_QSL_SENT:1>R <APP_DXKeeper_ClubLogDate:19>4000-01-01 00:00:00 <EOR> <Band:3>40M <Call:5>AA7OY <APP_DXKEEPER_DXCCPREFIX:1>K <DXCC:3>291 <Freq:5>7.061 <Mode:2>CW <Operator:4>K7TP <QSO_DATE:8>20200611 <TIME_OFF:6>154803 <TIME_ON:6>154036 <RST_Rcvd:3>599 <RST_Sent:3>599 <TX_PWR:5>100.0 <CONT:2>NA <PFX:3>AA7 <STATION_CALLSIGN:4>K7TP <OWNER_CALLSIGN:4>K7TP <SOTA_REF:10>W7A/AE-026 <EQSL_QSL_SENT:1>U <EQSL_QSL_RCVD:1>R <EQSL_QSLSDATE:8>20200611 <LOTW_QSL_SENT:1>R <APP_DXKeeper_ClubLogDate:19>4000-01-01 00:00:00 <EOR> <Band:3>30M <Call:5>AA7OY <APP_DXKEEPER_DXCCPREFIX:1>K <DXCC:3>291 <Freq:7>10.1105 <Mode:2>CW <Operator:4>K7TP <QSO_DATE:8>20200611 <TIME_OFF:6>160543 <TIME_ON:6>160318 <RST_Rcvd:3>599 <RST_Sent:3>599 <TX_PWR:5>100.0 <CONT:2>NA <PFX:3>AA7 <STATION_CALLSIGN:4>K7TP <OWNER_CALLSIGN:4>K7TP <SOTA_REF:11>W7A/AE--026 <EQSL_QSL_SENT:1>U <EQSL_QSL_RCVD:1>R <EQSL_QSLSDATE:8>20200611 <LOTW_QSL_SENT:1>R <APP_DXKeeper_ClubLogDate:19>4000-01-01 00:00:00 <EOR> <Band:3>20M <Call:4>N6IZ <APP_DXKEEPER_DXCCPREFIX:1>K <DXCC:3>291 <Freq:6>14.062 <Mode:2>CW <Operator:4>K7TP <QSO_DATE:8>20200611 <TIME_OFF:6>171900 <TIME_ON:6>171900 <RST_Rcvd:3>599 <RST_Sent:3>599 <TX_PWR:4>50.0 <CONT:2>NA <ITUZ:1>6 <CQZ:1>3 <PFX:2>N6 <STATION_CALLSIGN:4>K7TP <OWNER_CALLSIGN:4>K7TP <SOTA_REF:9>W6/NS-139 <EQSL_QSL_SENT:1>R <LOTW_QSL_SENT:1>R <APP_DXKeeper_ClubLogDate:19>4000-01-01 00:00:00 <EOR> <Band:3>30M <Call:4>KX0R <APP_DXKEEPER_DXCCPREFIX:1>K <DXCC:3>291 <Freq:6>10.113 <Mode:2>CW <Operator:4>K7TP <QSO_DATE:8>20200611 <TIME_OFF:6>175012 <TIME_ON:6>174436 <RST_Rcvd:3>599 <RST_Sent:3>599 <TX_PWR:5>100.0 <CONT:2>NA <PFX:3>KX0 <STATION_CALLSIGN:4>K7TP <OWNER_CALLSIGN:4>K7TP <SOTA_REF:10>W0C/SR-052 <EQSL_QSL_SENT:1>U <EQSL_QSL_RCVD:1>R <EQSL_QSLSDATE:8>20200611 <LOTW_QSL_SENT:1>R <APP_DXKeeper_ClubLogDate:19>4000-01-01 00:00:00 <EOR> _._,_._,_ ________________________________


Re: Problems with a simple command sequence

Frank Ventura
 

Dave, I am using an Icom ic7300. Here is the sequence that is currently working:
The following items should be changed for another band
<Name 75 Meters>
<wait>
<QSY 3800>
<wait>
<Tooltip QSY to 75m>
<wait>
<Mode LSB>
<wait>
The following items don't need to be changed
<Split Off>
<Receive>
<LED 2:9, red>
<LED green>
<end>

Thanks
Frank

-----Original Message-----
From: DXLab@groups.io <DXLab@groups.io> On Behalf Of Dave AA6YQ via groups.io
Sent: Friday, June 12, 2020 2:58 PM
To: DXLab@groups.io
Subject: Re: [DXLab] Problems with a simple command sequence

+ AA6YQ comments below

Joe, that really seemed to help. Still need to do some more testing but thanks for the suggestion.

+ What make and model transceiver are you using, Frank?

73,

Dave, AA6YQ


Re: DXKeeper and clearning QSL Sent from "R"

n4ww austin regal
 

The last part of his question is a problem for me also.

I use qsl_sent with R request and load it into qsl que and print the labels. Then I try to "update the log" and " "clear" the qsl que. But it doesnt update the log They continue to be "r". I figured this out once but 3 months later I am stuck again.

Be nice to have a menu that allows change all of these letters back and forth and click "up date log". I know about advance feature and resort to it when all else fails.

-----Original Message-----
From: Dave AA6YQ <aa6yq@ambersoft.com>
Sent: Jun 11, 2020 3:23 PM
To: DXLab@groups.io
Subject: Re: [DXLab] DXKeeper and clearning QSL Sent from "R"

+ AA6YQ comments below

I've been fighting with this off and on for a few years. I'm getting more active again and really want to get this sorted out.

If I go to the QSL tab in LOTW, and I "Add Requested", it populates hundreds of QSO's I don't know why they're still set to R, as I have synched LoTW QSO's, QSL's and all my QSO's are uploaded to LoTW, so WHY isn't the sent status changed to "Y"?

+ On the Main window's QSL tab, set the "QSL Via" panel to LoTW. Note the dates beneath the "Sync LoTW QSOs" and "Sync LoTW QSLs" buttons. When you click these buttons, they direct LoTW to report QSOs accepted or confirmed (respectively) since those dates -- not since the date of the first QSO in your log.

+ These instructions describe a one-time procedure for updating the LoTW status of all logged QSOs when you've come to DXKeeper from another logging application by importing an ADIF file that doesn't specify the LoTW status of every QSO:

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

+ Did you perform this procedure when you first moved to DXKeeper?

Similarly, I get the same thing when switched to cards, labels, or anything else. Some of these QSO's are 30 years old and I don't want to print out over 1000 labels. I just want those fields to be cleared or (preferably) changed to "sent". I don't understand why the status doesn't get changed when I clear all of them.

+ Let's get your QSOs' LoTW status updated first; then we can address their card/label status.

73,

Dave, AA6YQ







Re: DXKeeper and clearning QSL Sent from "R"

Steve Wedge <Steve27302@...>
 

Aw, damn.  I just checked by clicking "Add Requested" and there are still about 140 Q's that are coming up.  These are mostly from 2013.  I tried uploading them to LoTW, in the hope that these were not duplicates but LoTW says that they are dupes.

So, some of the Q's were resolved but for some reason, there are still some (140) that sem to be enteres on LoTW but aren't confirmed as such in DXk.

Thanks again.  It's better.


Re: DXKeeper and clearning QSL Sent from "R"

Steve Wedge <Steve27302@...>
 

That did it, Dave!  Thanks!

I was preparing to update DXK next but was waiting to hear back.  I tend to update one app at a time, in case something goes off the rails with this computer.

DXK is inspecting 11,522 QSO's, so that takes care of one issue.  Now I have to find which 1286 QSO's are NOT in LoTW and figure out how to get them there.  They may nave been imports from N1MM or CT (yeah, this log goes back to 1982...).

DXK is inspecting and is taking less time than I imagined it would.



73,

4861 - 4880 of 199244