Date   

Re: reconcile LOTW vs DXlab

Jamie WW3S
 

found it Dave, thanks for your help....

------ Original Message ------
From: "Dave AA6YQ" <@AA6YQ>
To: DXLab@groups.io
Sent: 1/7/2020 10:22:20 PM
Subject: Re: [DXLab] reconcile LOTW vs DXlab

+ AA6YQ comments below

I dont follow you Dave.....if I complete 1-4, and then 5, displayed are the 323 current ones I have verified, not the missing ones

+ You're right, I got it backwards. in the "Award Progress Filter" panel, check the "Unworked, Worked, Requested, and Confirmed" boxes; uncheck the "Verified" and "Include deleted DXCC entities" boxes.

+ Now you should see the current entities for which you don't have a logged Phone QSO to which DXCC Credit is shown as "granted".

73,

Dave, AA6YQ

------ Original Message ------
From: "Dave AA6YQ" <@AA6YQ>
To: DXLab@groups.io
Sent: 1/7/2020 9:52:08 PM
Subject: Re: [DXLab] reconcile LOTW vs DXlab

+ AA6YQ comments below

So I did my submission from DXlab to LOTW, everything DXlab gathered was also gathered by LOTW, I recently go the mail back from the DXCC desk, and used to DXlab to change submitted to verified.....all bands came out a match, as did most modes, but PHONE did not.....LOTW shows I have 330 and Dxlab only shows 329.......how can I find the missing entity?

+ There are 340 current DXCC entities, so your task is to check the 11 entities that DXKeeper reports have no DXCC award credit for PHONE against LOTW.

+ To obtain that list of 11 entities, click the RAT button on
+ DXKeeper's Main window's "Log QSOs" tab, and do the following on the
+ "Realtime Award Tracking" window's DXCC tab's "Award Progress Filter"
+ panel

1. set the Band selector to ANY

2. set the Mode selector to PHONE

3. uncheck the "Include deleted DXCC entities" box

4. uncheck the Unworked, Worked, Requested, and Confirmed boxes

5. check the "Verified box

+ The "Award Progress" table above the "Award Progress Filter" panel should list the 11 entities for which no phone QSO has been granted DXCC award credit.

+ Check this list of 11 entities against your DXCC "Award Credit
+ Matrix" in LoTW, which you can view by following the instructions in

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

73,

Dave, AA6YQ








--
This email has been checked for viruses by AVG.
https://www.avg.com




Re: SPOT COLLECTOR

Dave AA6YQ
 

+ AA6YQ comments below

Thanks fo your swift reply..,.,., I use my home station as well as several remote rigs...I have each on a MYQTH and the filter and
dxcc progress work... On one of the remotes we are running a bit of a battle for highest dxcc countries . so I was hoping I could
get the band map to color code needed stations on the filtered log for that remote.. From what you say, that is not going to
happen.. No big deal . and thanks.

+ The way to accomplish that would be to setup a second computer running SpotCollector and DXKeeper, with a log file that only
contains QSOs made from "that remote". You'd have to manually ensure that QSOs made with "that remote" are present in both log files
the "that remote only" log, and the "all QSOs" log.

73,

Dave, AA6YQ


Re: SPOT COLLECTOR

John Battin
 

Thanks fo your swift reply..,.,., I use my home station as well as several remote rigs…..I have each on a MYQTH and the filter and dxcc progress work….. On one of the remotes we are running a bit of a battle for highest dxcc countries … so I was hoping I could get the band map to color code needed stations on the filtered log for that remote…. From what you say, that is not going to happen…. No big deal … and thanks.

 

John K9DX

 

Sent from Mail for Windows 10

 

From: Dave AA6YQ
Sent: Wednesday, January 8, 2020 12:15 PM
To: DXLab@groups.io
Subject: Re: [DXLab] SPOT COLLECTOR

 

+ AA6YQ comments bewl

I have my DX keeper filtered to one of my qth.. I want the band map to color dxcc needs for that filtered log and not all of my
qso's.  I have read everything, but am overwhelmed.

+ DXLab's "Real time award tracking" assumes that all QSOs in your log "count" towards your DXCC awards. You can filter the Log Page
Display to contain QSOs from a subset of your "my QTHs" and the run a DXCC progress report to assess your DXCC progress from that
"my QTH" subset alone, but SpotCollector will continue to report "DXCC need" considering all logged QSOs.

+ Were the QSOs you don't want to "count" made from a different DXCC entity than that of your home QTH?

        73,

              Dave, AA6YQ


 


Re: SPOT COLLECTOR

Dave AA6YQ
 

+ AA6YQ comments bewl

I have my DX keeper filtered to one of my qth.. I want the band map to color dxcc needs for that filtered log and not all of my
qso's. I have read everything, but am overwhelmed.

+ DXLab's "Real time award tracking" assumes that all QSOs in your log "count" towards your DXCC awards. You can filter the Log Page
Display to contain QSOs from a subset of your "my QTHs" and the run a DXCC progress report to assess your DXCC progress from that
"my QTH" subset alone, but SpotCollector will continue to report "DXCC need" considering all logged QSOs.

+ Were the QSOs you don't want to "count" made from a different DXCC entity than that of your home QTH?

73,

Dave, AA6YQ


Contest logging

Brian D
 

Until recently for most contests I export an ADIF file from N1MM and load
this into DxKeeper afterwards.

This works, and inserts the correct callsign into "station callsign" in
DXKeeper.

Recently I have been using N1MM-DXK GW v1.1.6 to transfer live into
DXKeeper. This seems to always insert my default callsign into "station
callsign" resulting in incorrect uploads to on line QSLs.

I'm not sure of teh routing betweeen programs so am not sure if it is N1MM,
the gateway, DXKeeper or my own incompetence.

Any ideas?


--
Brian D
G3VGZ


SPOT COLLECTOR

John Battin
 

I have my DX keeper filtered to one of my qth…. I want the band map to color dxcc needs for that filtered log and not all of my qso’s.  I have read everything, but am overwhelmed.

John k9dx

 

Sent from Mail for Windows 10

 


Re: Spot Collector and CPU

Jim McPhee
 

Dave,

That is a neat feature that I had no idea existed. Thanks for pointing it out!
--
Jim McPhee
Placitas, NM
W5ABA


Re: Icom 756Pro RS232 Settings

D. Scott MacKenzie
 

I have had that happen - I have always been of the opinion that Murphy was an optimist


On Wed, Jan 8, 2020 at 1:11 AM Dave AA6YQ <aa6yq@...> wrote:

+ AA6YQ comments below

On Tue, Jan 7, 2020 at 08:24 PM, D. Scott MacKenzie wrote:

Thank you Dave - it has literally been years since I turned on the rig.
Been thinking about getting it going again.

+ If you have a backup transceiver, it's a good idea to have it connected, configured, and ready to go at a moment's notice (with suitable antenna input protection!). There's nothing like an "all-time new one" being QRV to instigate equipment failure.

     73,

             Dave, AA6YQ



--
D. Scott MacKenzie, PhD, FASM


Re: Spotcollector text message alarm

Mike NA5U <mike@...>
 

Dave,
Thanks!
Mike

-----Original Message-----
From: DXLab@groups.io <DXLab@groups.io> On Behalf Of Dave AA6YQ
Sent: Tuesday, January 7, 2020 8:57 PM
To: DXLab@groups.io
Subject: Re: [DXLab] Spotcollector text message alarm

+ AA6YQ comment sbelow

Can someone tell me how to change my settings from receiving each message to the daily summary?

+ Please do the following, Mike:

1. using your web browser, navigate to

<https://groups.io/g/DXLab>


2. Click the Subscription hyperlink beneath the blue Home button near the upper-left corner

3. The "Edit Subscription" page will appear, with 4 tabs; the Membership tab should already be selected.

4. In the "Email Delivery " section, choose the option that best meets your needs

5. Scroll down to the bottom of the page and click the Save button.

73,

Dave, AA6YQ


Re: Inbound OQRS from clublog problem - ErrorLog.txt

Greg
 

Dave

That fixed it.  Had to change the date of last request back to 29/12/2019 and the QSL request was downloaded. I had processed the requests up to 29/12 already.

Many thanks, once again great support.

Greg VK3VT

On 08/01/2020 19:48, Dave AA6YQ wrote:
I just tried the Inbound OQRS function, and received a file containing

error code: 1010

just as you did. I checked the OQRS URL in the Club Log documentation, and see that it changed in February 2018!

I modified DXKeeper 15.3.2 to use the "new" URL; now the downloaded ADIF file contains

-------------------------
ADIF export from Club Log - https://clublog.org
Log export of AA6YQ at Wed, 08 Jan 2020 08:28:11 +0000
Note: this ADIF file is based on the internal records in Club Log and is not the original ADIF you uploaded.

This is a QSL REQUEST ADIF from Club Log and contains only QSL requests

<PROGRAMID:8>Club Log
<PROGRAMVERSION:4>2020
<EOH>
-------------------------

instead of the error message.

I've successfully received OQRS request after February 2018, so something in Club Log must have changed more recently to cause the URL employed by DXKeeper to stop working.

To obtain DXKeeper 15.3.2,

1. download the zip archive from

<http://www.dxlabsuite.com/dxkeeper/DXKeeper1532.zip>

2. Extract the file DXKeeper1532.exe from the archive and place it in your DXKeeper folder

3. update your anti-malware applications to consider DXKeeper1532.exe to be safe

4. use Windows Explorer to navigate to your DXKeeper folder, and run DXKeeper1532.exe


To enable the DXLab Launcher to start DXKeeper 15.3.2, use Windows Explorer to make the following changes in your DXKeeper folder

5. delete the file named DXKeeper.exe

6. make a copy of the file DXKeeper1532.exe and rename this copy DXKeeper.exe


Please let me know how it goes...

73,

Dave, AA6YQ



-----Original Message-----
From: Greg Williams [mailto:@VK3VT]
Sent: Wednesday, January 08, 2020 2:15 AM
To: Dave AA6YQ
Subject: Inbound OQRS from clublog problem - ErrorLog.txt

I have been using the Inbound OQRS facility for some time without issue. After receiving several alerts from clublog that stations had requested bureau cards, I clicked on the "Inbound OQRS" and got the response "Requests received 0" This first happened on 29 Dec 2019. Today I received a further OQRS request so I tried again with "Log debugging information" enabled. Once again I got the "Requests received 0".

I had a look at file "InboundOQRS.adi" and it contained one line - "error code: 1010". I checked a backup of the "InboundOQRS.adi" from
29 Dec 2019 and it contained the same line.

What have I done wrong?

73

Greg VK3VT


Dave attached is the ErrorLog.txt from the above OQRS request around
2020-01-08 06:43:20

Greg



--
This email has been checked for viruses by AVG.
https://www.avg.com


Re: Inbound OQRS from clublog problem

Dave AA6YQ
 

+ AA6YQ comments below

I have been using the Inbound OQRS facility for some time without issue. After receiving several alerts from clublog that stations had requested bureau cards, I clicked on the "Inbound OQRS" and got the response "Requests received 0" This first happened on 29 Dec 2019. Today I received a further OQRS request so I tried again with "Log debugging information" enabled. Once again I got the "Requests received 0".

I had a look at file "InboundOQRS.adi" and it contained one line - "error code: 1010". I checked a backup of the "InboundOQRS.adi" from
29 Dec 2019 and it contained the same line.

+ I just tried the Inbound OQRS function, and received a file containing

error code: 1010

+ just as you did. I checked the OQRS URL in the Club Log documentation, and see that it changed in February 2018!

+ I modified the next version of DXKeeper to use the "new" URL; now the downloaded ADIF file contains

-------------------------
ADIF export from Club Log - https://clublog.org
Log export of AA6YQ at Wed, 08 Jan 2020 08:28:11 +0000
Note: this ADIF file is based on the internal records in Club Log and is not the original ADIF you uploaded.

This is a QSL REQUEST ADIF from Club Log and contains only QSL requests

<PROGRAMID:8>Club Log <PROGRAMVERSION:4>2020
<EOH>
-------------------------

instead of the error message.

I've successfully received OQRS request after February 2018, so something in Club Log must have changed more recently to cause the URL employed by DXKeeper to stop working.

I've sent you the next version of DXKeeper. Please let me know how it goes...

73,

Dave, AA6YQ


Re: Inbound OQRS from clublog problem

Dave AA6YQ
 

+ AA6YQ comments below

I have been using the Inbound OQRS facility for some time without issue. After receiving several alerts from clublog that stations had requested bureau cards, I clicked on the "Inbound OQRS" and got the response "Requests received 0" This first happened on 29 Dec 2019. Today I received a further OQRS request so I tried again with "Log debugging information" enabled. Once again I got the "Requests received 0".

I had a look at file "InboundOQRS.adi" and it contained one line - "error code: 1010". I checked a backup of the "InboundOQRS.adi" from
29 Dec 2019 and it contained the same line.

What have I done wrong?

+ Is there an errorlog.txt file in your DXKeeper folder? If so, please attach it to an email message, and send it to me via

aa6yq (at) ambersoft.com

+ If there's no errorlog.txt file in your DXKeeper folder, please tell me what version number appears in the title bar of DXKeeper's Main window.

73,

Dave, AA6YQ


Inbound OQRS from clublog problem

Greg
 

I have been using the Inbound OQRS facility for some time without issue.  After receiving several alerts from clublog that stations had requested bureau cards, I clicked on the "Inbound OQRS" and got the response "Requests received 0"   This first happened on 29 Dec 2019.  Today I received a further OQRS request so I tried again with "Log debugging information" enabled. Once again I got the "Requests received 0".

I had a look at file "InboundOQRS.adi" and it contained one line - "error code: 1010".   I checked a backup of the "InboundOQRS.adi" from 29 Dec 2019 and it contained the same line.

What have I done wrong?

73

Greg VK3VT


Re: Icom 756Pro RS232 Settings

Dave AA6YQ
 

+ AA6YQ comments below

On Tue, Jan 7, 2020 at 08:24 PM, D. Scott MacKenzie wrote:

Thank you Dave - it has literally been years since I turned on the rig.
Been thinking about getting it going again.

+ If you have a backup transceiver, it's a good idea to have it connected, configured, and ready to go at a moment's notice (with suitable antenna input protection!). There's nothing like an "all-time new one" being QRV to instigate equipment failure.

     73,

             Dave, AA6YQ


Re: Icom 756Pro RS232 Settings

D. Scott MacKenzie
 

Thank you Dave - it has literally been years since I turned on the rig.
Been thinking about getting it going again.

-----Original Message-----
From: DXLab@groups.io <DXLab@groups.io> On Behalf Of Dave AA6YQ
Sent: Tuesday, January 7, 2020 11:20 PM
To: DXLab@groups.io
Subject: Re: [DXLab] Icom 756Pro RS232 Settings

+ AA6YQ comments below

Being stupid, I upgraded to Win 10 without thinking about the files in
DXLabs. It has been multiple years since I set the parity settings for the
rig. Does anyone remember what baud/word/parity/stop and DTR/RTS settings
are for an ICOM 756Pro?

+ Look in the transceiver's CI-V menu settings to determine the baud
+ rate. The word length is 8, the parity is "none", and stop bits
are "1'. Unless you're using them as a power supply for an external CI-V
interface, set DTR and RTS to "OFF".

+ Make sure you configure Commander to use the correct CI-V address, which
you'll also find in your transceiver's menu settings.
The default for a 756Pro is 5C

+ All of the relevant settings are described here:

<https://www.dxlabsuite.com/dxlabwiki/TranceiverControlIcom>

73,

Dave, AA6YQ


Re: Icom 756Pro RS232 Settings

Dave AA6YQ
 

+ AA6YQ comments below

Being stupid, I upgraded to Win 10 without thinking about the files in DXLabs. It has been multiple years since I set the parity
settings for the rig. Does anyone remember what baud/word/parity/stop and DTR/RTS settings are for an ICOM 756Pro?

+ Look in the transceiver's CI-V menu settings to determine the baud rate. The word length is 8, the parity is "none", and stop bits
are "1'. Unless you're using them as a power supply for an external CI-V interface, set DTR and RTS to "OFF".

+ Make sure you configure Commander to use the correct CI-V address, which you'll also find in your transceiver's menu settings.
The default for a 756Pro is 5C

+ All of the relevant settings are described here:

<https://www.dxlabsuite.com/dxlabwiki/TranceiverControlIcom>

73,

Dave, AA6YQ


Icom 756Pro RS232 Settings

D. Scott MacKenzie
 

Being stupid, I upgraded to Win 10 without thinking about the files in DXLabs.  It has been multiple years since I set the parity settings for the rig.  Does anyone remember what baud/word/parity/stop and DTR/RTS settings are for an ICOM 756Pro?

 

I was able to find the port but unable to communicate.

 

Thanks

 

Scott


Re: reconcile LOTW vs DXlab

Dave AA6YQ
 

+ AA6YQ comments below

I dont follow you Dave.....if I complete 1-4, and then 5, displayed are the 323 current ones I have verified, not the missing ones

+ You're right, I got it backwards. in the "Award Progress Filter" panel, check the "Unworked, Worked, Requested, and Confirmed" boxes; uncheck the "Verified" and "Include deleted DXCC entities" boxes.

+ Now you should see the current entities for which you don't have a logged Phone QSO to which DXCC Credit is shown as "granted".

73,

Dave, AA6YQ

------ Original Message ------
From: "Dave AA6YQ" <@AA6YQ>
To: DXLab@groups.io
Sent: 1/7/2020 9:52:08 PM
Subject: Re: [DXLab] reconcile LOTW vs DXlab

+ AA6YQ comments below

So I did my submission from DXlab to LOTW, everything DXlab gathered was also gathered by LOTW, I recently go the mail back from the DXCC desk, and used to DXlab to change submitted to verified.....all bands came out a match, as did most modes, but PHONE did not.....LOTW shows I have 330 and Dxlab only shows 329.......how can I find the missing entity?

+ There are 340 current DXCC entities, so your task is to check the 11 entities that DXKeeper reports have no DXCC award credit for PHONE against LOTW.

+ To obtain that list of 11 entities, click the RAT button on
+ DXKeeper's Main window's "Log QSOs" tab, and do the following on the
+ "Realtime Award Tracking" window's DXCC tab's "Award Progress Filter"
+ panel

1. set the Band selector to ANY

2. set the Mode selector to PHONE

3. uncheck the "Include deleted DXCC entities" box

4. uncheck the Unworked, Worked, Requested, and Confirmed boxes

5. check the "Verified box

+ The "Award Progress" table above the "Award Progress Filter" panel should list the 11 entities for which no phone QSO has been granted DXCC award credit.

+ Check this list of 11 entities against your DXCC "Award Credit
+ Matrix" in LoTW, which you can view by following the instructions in

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

73,

Dave, AA6YQ








--
This email has been checked for viruses by AVG.
https://www.avg.com


Re: reconcile LOTW vs DXlab

Jamie WW3S
 

I dont follow you Dave.....if I complete 1-4, and then 5, displayed are the 323 current ones I have verified, not the missing ones

------ Original Message ------
From: "Dave AA6YQ" <@AA6YQ>
To: DXLab@groups.io
Sent: 1/7/2020 9:52:08 PM
Subject: Re: [DXLab] reconcile LOTW vs DXlab

+ AA6YQ comments below

So I did my submission from DXlab to LOTW, everything DXlab gathered was also gathered by LOTW, I recently go the mail back from the DXCC desk, and used to DXlab to change submitted to verified.....all bands came out a match, as did most modes, but PHONE did not.....LOTW shows I have 330 and Dxlab only shows 329.......how can I find the missing entity?

+ There are 340 current DXCC entities, so your task is to check the 11 entities that DXKeeper reports have no DXCC award credit for PHONE against LOTW.

+ To obtain that list of 11 entities, click the RAT button on DXKeeper's Main window's "Log QSOs" tab, and do the following on the "Realtime Award Tracking" window's DXCC tab's "Award Progress Filter" panel

1. set the Band selector to ANY

2. set the Mode selector to PHONE

3. uncheck the "Include deleted DXCC entities" box

4. uncheck the Unworked, Worked, Requested, and Confirmed boxes

5. check the "Verified box

+ The "Award Progress" table above the "Award Progress Filter" panel should list the 11 entities for which no phone QSO has been granted DXCC award credit.

+ Check this list of 11 entities against your DXCC "Award Credit Matrix" in LoTW, which you can view by following the instructions in

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

73,

Dave, AA6YQ




Re: Spotcollector text message alarm

Dave AA6YQ
 

+ AA6YQ comment sbelow

Can someone tell me how to change my settings from receiving each message to the daily summary?

+ Please do the following, Mike:

1. using your web browser, navigate to

<https://groups.io/g/DXLab>


2. Click the Subscription hyperlink beneath the blue Home button near the upper-left corner

3. The "Edit Subscription" page will appear, with 4 tabs; the Membership tab should already be selected.

4. In the "Email Delivery " section, choose the option that best meets your needs

5. Scroll down to the bottom of the page and click the Save button.

73,

Dave, AA6YQ